Specifying semantic information on functional requirements

OpenAIRE

YAO, WUPING

2012-01-01

Requirements engineering is a challenging process in software development projects. Requirements, in general, are documented in natural language. They often have issues related to ambiguity, completeness and consistency. How to improve the quality of requirements documentation remains a classic research topic. This research aims at improving the way of editing and documenting functional requirements. We propose a meta-model to specify the semantic information of functional requirements, and d...

Joint Simulation System (JSIMS) Functional Requirements Document (FRD); A User's Perspective on the Future, Version 1.O

National Research Council Canada - National Science Library

1996-01-01

The purpose of this document is to define JSIMS functional requirements in a level of detail that is meaningful to both the JSIMS developmental community and the expected future users of the system...

Supplemental design requirements document, Project W026

International Nuclear Information System (INIS)

Weidert, J.R.

1993-01-01

This document supplements and extends the Functional Design Criteria, SP-W026-FDC-001, for the Waste Receiving and Processing Facility (WRAP), Module 1. It provides additional detailed requirements, summarizes key Westinghouse Hanford Company design guidance, and establishes baseline technical agreements to be used in definitive design of the WRAP-1 facility. Revision 3 of the Supplemental Design Requirements Document has been assigned an Impact Level of 3ESQ based on the content of the entire revision. The actual changes made from Revision 2 have an Impact Level of 3S and the basis for these changes was previously reviewed and approved per WHC correspondence No. 9355770

Preliminary design requirements document (DRD) for Project W-236B, ''Initial Pretreatment Module''

International Nuclear Information System (INIS)

Swanson, L.M.

1995-01-01

The scope of this Design Requirements Document (DRD) is to identify and define the functions, with associated requirements, which must be performed to separate Hanford Site tank waste supernatants into low-level and high-level fractions. This documents sets forth function requirements, performance requirements, and design constraints necessary to begin conceptual design for the Initial Pretreatment Module (IPM). System and physical interfaces between the IPM project and the Tank Waste Remediation System (TWRS) are identified. The constraints, performance requirements, and transfer of information and data across a technical interface will be documented in an Interface Control Document. Supplemental DRDs will be prepared to provide more detailed requirements specific to systems described in the DRD

Project W-236A, work plan for preparation of a design requirements document

International Nuclear Information System (INIS)

Groth, B.D.

1995-01-01

This work plan outlines the tasks necessary, and defines the organizational responsibilities for preparing a Design Requirements Document (DRD) for project W-236A, Multi-Function Waste Tank Facility (MWTF). A DRD is a Systems Engineering document which bounds, at a high level, the requirements of a discrete system element of the Tank Waste Remediation System (TWRS) Program. This system element is usually assigned to a specific project, in this case the MWTF. The DRD is the document that connects the TWRS program requirements with the highest level projects requirements and provides the project's link to the overall TWRS mission. The MWTF DRD effort is somewhat unique in that the project is already in detailed design, whereas a DRO is normally prepared prior to preliminary design. The MWTF design effort was initiated with a Functional Design Criteria (FDC) and a Supplemental Design Requirements Document (SDRD) bounding the high level requirements. Another unique aspect of this effort is that some of the TWRS program requirements are still in development. Because of these unique aspects of the MWTF DRD development, the MWTF will be developed from existing TWRS Program requirements and project specific requirements contained in the FDC and SDRD. The following list describes the objectives of the MWTF DRD: determine the primary functions of the tanks through a functional decomposition of the TWRS Program high level functions; allocate the primary functions to a sub-system architecture for the tanks; define the fundamental design features in terms of performance requirements for the system and subsystems; identify system interfaces and design constraints; and document the results in a DRD

Design requirements document for project W-520, immobilized low-activity waste disposal

International Nuclear Information System (INIS)

Ashworth, S.C.

1998-01-01

This design requirements document (DRD) identifies the functions that must be performed to accept, handle, and dispose of the immobilized low-activity waste (ILAW) produced by the Tank Waste Remediation System (TWRS) private treatment contractors and close the facility. It identifies the requirements that are associated with those functions and that must be met. The functional and performance requirements in this document provide the basis for the conceptual design of the Tank Waste Remediation System Immobilized Low-Activity Waste disposal facility project (W-520) and provides traceability from the program-level requirements to the project design activity

Design requirements document for project W-520, immobilized low-activity waste disposal

Energy Technology Data Exchange (ETDEWEB)

Ashworth, S.C.

1998-08-06

This design requirements document (DRD) identifies the functions that must be performed to accept, handle, and dispose of the immobilized low-activity waste (ILAW) produced by the Tank Waste Remediation System (TWRS) private treatment contractors and close the facility. It identifies the requirements that are associated with those functions and that must be met. The functional and performance requirements in this document provide the basis for the conceptual design of the Tank Waste Remediation System Immobilized Low-Activity Waste disposal facility project (W-520) and provides traceability from the program-level requirements to the project design activity.

Project W-441 cold vacuum drying facility design requirements document

International Nuclear Information System (INIS)

O'Neill, C.T.

1997-01-01

This document has been prepared and is being released for Project W-441 to record the design basis for the design of the Cold Vacuum Drying Facility. This document sets forth the physical design criteria, Codes and Standards, and functional requirements that were used in the design of the Cold Vacuum Drying Facility. This document contains section 3, 4, 6, and 9 of the Cold Vacuum Drying Facility Design Requirements Document. The remaining sections will be issued at a later date. The purpose of the Facility is to dry, weld, and inspect the Multi-Canister Overpacks before transport to dry storage

Design requirements document for Project W-465, immobilized low-activity waste interim storage

International Nuclear Information System (INIS)

Burbank, D.A.

1998-01-01

The scope of this Design Requirements Document (DRD) is to identify the functions and associated requirements that must be performed to accept, transport, handle, and store immobilized low-activity waste (ILAW) produced by the privatized Tank Waste Remediation System (TWRS) treatment contractors. The functional and performance requirements in this document provide the basis for the conceptual design of the TWRS ILAW Interim Storage facility project and provides traceability from the program level requirements to the project design activity. Technical and programmatic risk associated with the TWRS planning basis are discussed in the Tank Waste Remediation System Decisions and Risk Assessment (Johnson 1994). The design requirements provided in this document will be augmented by additional detailed design data documented by the project

Preliminary Design Requirements Document for Project W-314

Energy Technology Data Exchange (ETDEWEB)

MCGREW, D.L.

2000-04-27

This document sets forth functional requirements, performance requirements, and design constraints for the tank farm systems elements identified in Section 3.1 of this document. These requirements shall be used to develop the Design Requirements Baseline for those system elements. System Overview--The tank farm system at Hanford Site currently consists of 149 single shell tanks and 28 double shell tanks with associated facilities and equipment, located in 18 separate groupings. Each grouping is known as a tank farm. They are located in the areas designated as 200 West and 200 East. Table 1-1 shows the number of tanks in each farm. The farms are connected together through a transfer system consisting of piping, diversion boxes, Double Contained Receiver Tanks (DCRT) and other miscellaneous facilities and elements. The tank farm system also connects to a series of processing plants which generate radioactive and hazardous wastes. The primary functions of the tank farm system are to store, transfer, concentrate, and characterize radioactive and hazardous waste generated at Hanford, until the waste can be safely retrieved, processed and dispositioned. The systems provided by Project W-314 support the store and transfer waste functions. The system elements to be upgraded by Project W-314 are identified in Section 3.1.

Preliminary Design Requirements Document for Project W-314

International Nuclear Information System (INIS)

MCGREW, D.L.

2000-01-01

This document sets forth functional requirements, performance requirements, and design constraints for the tank farm systems elements identified in Section 3.1 of this document. These requirements shall be used to develop the Design Requirements Baseline for those system elements. System Overview--The tank farm system at Hanford Site currently consists of 149 single shell tanks and 28 double shell tanks with associated facilities and equipment, located in 18 separate groupings. Each grouping is known as a tank farm. They are located in the areas designated as 200 West and 200 East. Table 1-1 shows the number of tanks in each farm. The farms are connected together through a transfer system consisting of piping, diversion boxes, Double Contained Receiver Tanks (DCRT) and other miscellaneous facilities and elements. The tank farm system also connects to a series of processing plants which generate radioactive and hazardous wastes. The primary functions of the tank farm system are to store, transfer, concentrate, and characterize radioactive and hazardous waste generated at Hanford, until the waste can be safely retrieved, processed and dispositioned. The systems provided by Project W-314 support the store and transfer waste functions. The system elements to be upgraded by Project W-314 are identified in Section 3.1

Documenting control system functionality for digital control implementations

International Nuclear Information System (INIS)

Harber, J.; Borairi, M.; Tikku, S.; Josefowicz, A.

2006-01-01

In past CANDU designs, plant control was accomplished by a combination of digital control computers, analogue controllers, and hardwired relay logic. Functionality for these various control systems, each using different hardware, was documented in varied formats such as text based program specifications, relay logic diagrams, and other various specification documents. The choice of formats was influenced by the hardware used and often required different specialized skills for different applications. The programmable electronic systems in new CANDU designs are realized in a manner consistent with latest international standards (e.g., the IEC 61513 standard). New CANDU designs make extensive use of modern digital control technology, with the benefit that functionality can be implemented on a limited number of control platforms, reducing development and maintenance cost. This approach can take advantage of tools that allow the plant control system functional and performance requirements to be documented using graphical representations. Modern graphical methods supplemented by information databases can be used to provide a clear and comprehensive set of requirements for software and system development. Overview diagrams of system functionality provide a common understanding of the system boundaries and interfaces. Important requirements are readily traced through the development process. This improved reviewability helps to ensure consistency with the safety and and production design requirements of the system. Encapsulation of commonly used functions into custom-defined function blocks, such as typical motor control centre interfaces, process interlocks, median selects etc, eases the burden on designers to understand and analyze the detailed functionality of each instance of use of this logic. A library of encapsulated functions will be established for complex functions that are reused in the control logic development. By encapsulation and standardisation of such

Detector Control System for an LHC experiment - User Requirements Document

CERN Document Server

CERN. Geneva

1997-01-01

The purpose of this document is to provide the user requirements for a detector control system kernel for the LHC experiments following the ESA standard PSS-05 [1]. The first issue will be used to provide the basis for an evaluation of possible development philosophies for a kernel DCS. As such it will cover all the major functionality but only to a level of detail sufficient for such an evaluation to be performed. Many of the requirements are therefore intentionally high level and generic, and are meant to outline the functionality that would be required of the kernel DCS, but not yet to the level of the detail required for implementation. The document is also written in a generic fashion in order not to rule out any implementation technology.

Functional Requirements for an Electronic Work Package System

Energy Technology Data Exchange (ETDEWEB)

Oxstrand, Johanna H. [Idaho National Lab. (INL), Idaho Falls, ID (United States)

2016-12-01

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

Waste Receiving and Packaging, Module 2A, Supplemental Design Requirements Document

International Nuclear Information System (INIS)

Lamberd, D.L.; Boothe, G.F.; Hinkle, A.L.; Horgos, R.M.; LeClair, M.D.; Nash, C.R.; Ocampo, V.P.; Pauly, T.R.; Stroup, J.L.; Weingardt, K.M.

1994-01-01

The Supplemental Design Requirements Document (SDRD) is used to communicate plant design information from Westinghouse Hanford Company (WHC) to the US Department of Energy (DOE) and the cognizant Architect Engineer (A/E). Information in the SDRD serves two purposes: to convey design requirements that are too detailed for inclusion in a Functional Design Criteria (FDC) report; and to serve as a means of change control for design commitments in the Conceptual Design Report. The mission of WRAP 2A on the Hanford site is the treatment of contact handled low level mixed waste (MW) for final disposal. The overall systems engineering steps used to reach construction and operation of WRAP 2A are depicted in Figure 1. The WRAP 2A SDRD focuses on the requirements to address the functional analysis provided in Figure 1. This information is provided in sections 2 through 5 of this SDRD. The mission analysis and functional analysis are to be provided in a separate supporting document. The organization of sections 2 through 5 corresponds to the requirements identified in the WRAP 2A functional analysis

Airspace Operations Demo Functional Requirements Matrix

Science.gov (United States)

2005-01-01

The Flight IPT assessed the reasonableness of demonstrating each of the Access 5 Step 1 functional requirements. The functional requirements listed in this matrix are from the September 2005 release of the Access 5 Functional Requirements Document. The demonstration mission considered was a notional Western US mission (WUS). The conclusion of the assessment is that 90% of the Access 5 Step 1 functional requirements can be demonstrated using the notional Western US mission.

Civilian Radioactive Waste Management System Requirements Document (CRP)

International Nuclear Information System (INIS)

C.A. Kouts

2006-01-01

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

A Framework for Requirement Elicitation, Analysis, Documentation and Prioritisation under Uncertainty

NARCIS (Netherlands)

Rajabali Nejad, Mohammadreza; Mladenov, V.

2015-01-01

This paper offers a pluralistic framework for coping with requirements in the early phases of design where there is lack of knowledge about a system, its architect and functions. The framework is used to elicit, analyze, document and prioritize the requirements. It embeds probabilistic approach and

22 CFR 40.71 - Documentation requirements for immigrants.

Science.gov (United States)

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

DOE Integrated Safeguards and Security (DISS) historical document archival and retrieval analysis, requirements and recommendations

Energy Technology Data Exchange (ETDEWEB)

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

1994-10-07

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

Fiscal year 1999 waste information requirements document

International Nuclear Information System (INIS)

Adams, M.R.

1998-01-01

The Waste Information Requirements Document (WIRD) has the following purposes: To describe the overall drivers that require characterization information and to document their source; To define how characterization is going to satisfy the drivers, close issues, and measure and report progress; and To describe deliverables and acceptance criteria for characterization. Characterization information is required to maintain regulatory compliance, perform operations and maintenance, resolve safety issues, and prepare for disposal of waste. Commitments addressing these requirements are derived from the Hanford Federal Facility Agreement and Consent Order, also known as the Tri-Party Agreement; the Recommendation 93-5 Implementation Plan (DOE-RL 1996a) to the Defense Nuclear Facilities Safety Board (DNFSB); and other requirement sources listed in Section 2.0. The Waste Information Requirements Document replaces the tank waste analysis plans and the tank characterization plan previously required by the Tri-Party Agreement, Milestone M-44-01 and M-44-02 series

The JPL functional requirements tool

Science.gov (United States)

Giffin, Geoff; Skinner, Judith; Stoller, Richard

1987-01-01

Planetary spacecraft are complex vehicles which are built according to many thousands of requirements. Problems encountered in documenting and maintaining these requirements led to the current attempt to reduce or eliminate these problems by a computer automated data base Functional Requirements Tool. The tool developed at JPL and in use on several JPL Projects is described. The organization and functionality of the Tool, together with an explanation of the data base inputs, their relationships, and use are presented. Methods of interfacing with external documents, representation of tables and figures, and methods of approval and change processing are discussed. The options available for disseminating information from the Tool are identified. The implementation of the Requirements Tool is outlined, and the operation is summarized. The conclusions drawn from this work is that the Requirements Tool represents a useful addition to the System Engineer's Tool kit, it is not currently available elsewhere, and a clear development path exists to expand the capabilities of the Tool to serve larger and more complex projects.

Documentation requirements for radiation sterilization

DEFF Research Database (Denmark)

Miller, A.

1995-01-01

Several standards are recently approved or are under development by the standard organizations ISO and CEN in the field of radiation sterilization. Particularly in Europe these standards define new requirements on some issues and on other issues they emphasize the necessary documentation for appr......Several standards are recently approved or are under development by the standard organizations ISO and CEN in the field of radiation sterilization. Particularly in Europe these standards define new requirements on some issues and on other issues they emphasize the necessary documentation...... for approval of radiation sterilized products. The impact of these standards on the radiation sterilization is discussed, with special attention given to a few special issues, mainly traceability and uncertainty of measurement results....

Environmental Restoration Remedial Action quality assurance requirements document

International Nuclear Information System (INIS)

1991-01-01

This document defines the quality assurance requirements for the US Department of Energy-Richland Operations Office Environmental Restoration Remedial Action program at the Hanford Site. The Environmental Restoration Remedial Action program implements significant commitments made by the US Department of Energy in the Hanford Federal Facility Agreement and Consent Order entered into with the Washington State Department of Ecology and the US Environmental Protection Agency. This document combines quality assurance requirements from various source documents into one set of requirements for use by the US Department of Energy-Richland Operations Office and other Environmental Restoration Remedial Action program participants. This document will serve as the basis for developing Quality Assurance Program Plans and implementing procedures by the participants. The requirements of this document will be applied to activities affecting quality, using a graded approach based on the importance of the item, service, or activity to the program objectives. The Quality Assurance Program that will be established using this document as the basis, together with other program and technical documents, form an integrated management control system for conducting the Environmental Restoration Remedial Action program activities in a manner that provides safety and protects the environment and public health

Collision Avoidance Functional Requirements for Step 1. Revision 6

Science.gov (United States)

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.

Advanced light water reactor utility requirements document: Volume 1--ALWR policy and summary of top-tier requirements

International Nuclear Information System (INIS)

Anon.

1990-01-01

The U.S. utilities are leading an industry wide effort to establish the technical foundation for the design of the Advanced Light Water Reactor (ALWR). This effort, the ALWR Program, is being managed for the U.S. electric utility industry by the Electric Power Research Institute (EPRI) and includes participation and sponsorship of several international utility companies and close cooperation with the U.S. Department of Energy (DOE). The cornerstone of the ALWR Program is a set of utility design requirements which are contained in the ALWR Requirements Document. The purpose of the Requirement Document is to present a clear, complete statement of utility desires for their next generation of nuclear plants. The Requirements Document covers the entire plant up to the grid interface. It therefore is the basis for an integrated plant design, i.e., nuclear steam supply system and balance of plant, and it emphasizes those areas which are most important to the objective of achieving an ALWR which is excellent with respect to safety, performance, constructibility, and economics. The document applies to both Pressurized Water Reactors (PWRs) and Boiling Water Reactors (BWRs). The Requirements Document is organized in three volumes. Volume 1 summarizes AlWR Program policy statements and top-tier requirements. The top-tier design requirements are categorized by major functions, including safety and investment protection, performance, and design process and constructibility. There is also a set of general design requirements, such as simplification and proven technology, which apply broadly to the ALWR design, and a set of economic goals for the ALWR program. The top-tier design requirements are described further in Volume 1 and are formally invoked as requirements in Volumes 2 and 3

Functional and operational requirements document : building 1012, Battery and Energy Storage Device Test Facility, Sandia National Laboratories, New Mexico.

Energy Technology Data Exchange (ETDEWEB)

Johns, William H. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States)

2013-11-01

This report provides an overview of information, prior studies, and analyses relevant to the development of functional and operational requirements for electrochemical testing of batteries and energy storage devices carried out by Sandia Organization 2546, Advanced Power Sources R&D. Electrochemical operations for this group are scheduled to transition from Sandia Building 894 to a new Building located in Sandia TA-II referred to as Building 1012. This report also provides background on select design considerations and identifies the Safety Goals, Stakeholder Objectives, and Design Objectives required by the Sandia Design Team to develop the Performance Criteria necessary to the design of Building 1012. This document recognizes the Architecture-Engineering (A-E) Team as the primary design entity. Where safety considerations are identified, suggestions are provided to provide context for the corresponding operational requirement(s).

Fluor Daniel Hanford contract standards/requirements identification document

Energy Technology Data Exchange (ETDEWEB)

Bennett, G.L.

1997-04-24

This document, the Standards/Requirements Identification Document (S/RID) for the Fluor Daniel Hanford Contract, represents the necessary and sufficient requirements to provide an adequate level of protection of the worker, public health and safety, and the environment.

Fluor Daniel Hanford company standards requirements identification document

International Nuclear Information System (INIS)

Bennett, G.L.

1997-01-01

This document, the Standards/Requirements Identification Document (S/RID) for the Fluor Daniel Hanford Contract, represents the necessary and sufficient requirements to provide an adequate level of protection of the worker, public health and safety, and the environment

Functions and requirements for single-shell tank leakage mitigation

International Nuclear Information System (INIS)

Cruse, J.M.

1994-01-01

This document provides the initial functions and requirements for the leakage mitigation mission applicable to past and potential future leakage from the Hanford Site's 149 single-shell high-level waste tanks. This mission is a part of the overall mission of the Westinghouse Hanford Company Tank Waste Remediation System division to remediate the tank waste in a safe and acceptable manner. Systems engineering principles are being applied to this effort. A Mission Analysis has been completed, this document reflects the next step in the systems engineering approach to decompose the mission into primary functions and requirements. The functions and requirements in this document apply to mitigative actions to be taken regarding below ground leaks from SST containment boundaries and the resulting soil contamination. Leakage mitigation is invoked in the TWRS Program in three fourth level functions: (1) Store Waste, (2) Retrieve Waste, and (3) Disposition Excess Facilities

Spent Nuclear Fuel Project Canister Storage Building Functions and Requirements

International Nuclear Information System (INIS)

KLEM, M.J.

2000-01-01

In 1998, a major change in the technical strategy for managing Multi Canister Overpacks (MCO) while stored within the Canister Storage Building (CSB) occurred. The technical strategy is documented in Baseline Change Request (BCR) No. SNF-98-006, Simplified SNF Project Baseline (MCO Sealing) (FDH 1998). This BCR deleted the hot conditioning process initially adopted for the Spent Nuclear Fuel Project (SNF Project) as documented in WHC-SD-SNF-SP-005, Integrated Process Strategy for K Basins Spent Nuclear Fuel (WHC 199.5). In summary, MCOs containing Spent Nuclear Fuel (SNF) from K Basins would be placed in interim storage following processing through the Cold Vacuum Drying (CVD) facility. With this change, the needs for the Hot Conditioning System (HCS) and inerting/pressure retaining capabilities of the CSB storage tubes and the MCO Handling Machine (MHM) were eliminated. Mechanical seals will be used on the MCOs prior to transport to the CSB. Covers will be welded on the MCOs for the final seal at the CSB. Approval of BCR No. SNF-98-006, imposed the need to review and update the CSB functions and requirements baseline documented herein including changing the document title to ''Spent Nuclear Fuel Project Canister Storage Building Functions and Requirements.'' This revision aligns the functions and requirements baseline with the CSB Simplified SNF Project Baseline (MCO Sealing). This document represents the Canister Storage Building (CSB) Subproject technical baseline. It establishes the functions and requirements baseline for the implementation of the CSB Subproject. The document is organized in eight sections. Sections 1.0 Introduction and 2.0 Overview provide brief introductions to the document and the CSB Subproject. Sections 3.0 Functions, 4.0 Requirements, 5.0 Architecture, and 6.0 Interfaces provide the data described by their titles. Section 7.0 Glossary lists the acronyms and defines the terms used in this document. Section 8.0 References lists the

Spectrum analysis on quality requirements consideration in software design documents.

Science.gov (United States)

Kaiya, Haruhiko; Umemura, Masahiro; Ogata, Shinpei; Kaijiri, Kenji

2013-12-01

Software quality requirements defined in the requirements analysis stage should be implemented in the final products, such as source codes and system deployment. To guarantee this meta-requirement, quality requirements should be considered in the intermediate stages, such as the design stage or the architectural definition stage. We propose a novel method for checking whether quality requirements are considered in the design stage. In this method, a technique called "spectrum analysis for quality requirements" is applied not only to requirements specifications but also to design documents. The technique enables us to derive the spectrum of a document, and quality requirements considerations in the document are numerically represented in the spectrum. We can thus objectively identify whether the considerations of quality requirements in a requirements document are adapted to its design document. To validate the method, we applied it to commercial software systems with the help of a supporting tool, and we confirmed that the method worked well.

Managing Requirements-Documents to Data

Science.gov (United States)

Orr, Kevin; Hudson, Abe

2017-01-01

Managing Requirements on long term projects like International Space Station (ISS) can go thru many phases, from initial product development to almost over 20 years of operations and sustainment. Over that time many authorized changes have been made to the requirement set, that apply to any new systems that would visit the ISS today, like commercial cargo/crew vehicles or payloads. Explore the benefits of managing requirements in a database while satisfying traditional documents needs for contracts and stakeholder/user consumption that are not tied into the database.

Functions and requirements for Project W-236B, Initial Pretreatment Module: Revision 1

International Nuclear Information System (INIS)

Swanson, L.M.

1994-01-01

Hanford Site tank waste supernatants will be pretreated to separate the low-level and high-level fractions. The low-level waste fraction, containing the bulk of the chemical constituents, must be processed into a vitrified waste product which will be disposed of onsite, in a safe, environmentally sound, and cost effective manner. The high-level waste fraction separated during supernatant pretreatment (primarily cesium) will be recombined with an additional high-level waste fraction generated from pretreatment of the tank waste sludges and solids. This combined high-level waste fraction will be immobilized as glass and disposed in a geological repository. The purpose of this document is to establish the functional requirements baseline for Project W-236B, Initial Pretreatment Module, by defining the level 5 and 6 functions and requirements for the project. A functional analysis approach has been used to break down the program functions and associated physical requirements that each function must meet. As the systems engineering process evolves, the design requirements document will replace this preliminary functions and requirements document. The design requirements document (DRD) will identify key decisions and associated uncertainties that impact the project. A revision of this document to a DRD is not expected to change the performance requirements or open issues. However, additional requirements and issues may be identified

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

Science.gov (United States)

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

1988-01-01

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

Functions and requirements for the INEL light duty utility arm gripper end effector

International Nuclear Information System (INIS)

Pace, D.P.; Barnes, G.E.

1995-02-01

This gripper end effector system functions and requirements document defines the system functions that the end effector must perform as well as the requirements the design must meet. Safety, quality assurance, operations, environmental conditions, and regulatory requirements have been considered. The main purpose of this document is to provide a basis for the end effector engineering, design, and fabrication activities. The document shall be the living reference document to initiate the development activities and will be updated as system technologies are finalized

Functions and requirements for the INEL light duty utility arm sampler end effector

International Nuclear Information System (INIS)

Pace, D.P.; Barnes, G.E.

1995-02-01

This sampler end effector system functions and requirements document defines the system functions that the end effector must perform as well as the requirements the design must meet. Safety, quality assurance, operations, environmental conditions, and regulatory requirements have been considered. The main purpose of this document is to provide a basis for the end effector engineering, design, and fabrication activities. The document shall be the living reference document to initiate the development activities and will be updated as system technologies are finalized

High level waste storage tanks 242-A evaporator standards/requirement identification document

International Nuclear Information System (INIS)

Biebesheimer, E.

1996-01-01

This document, the Standards/Requirements Identification Document (S/RIDS) for the subject facility, represents the necessary and sufficient requirements to provide an adequate level of protection of the worker, public health and safety, and the environment. It lists those source documents from which requirements were extracted, and those requirements documents considered, but from which no requirements where taken. Documents considered as source documents included State and Federal Regulations, DOE Orders, and DOE Standards

Functions and requirements for Hanford single-shell tank leakage detection and monitoring

International Nuclear Information System (INIS)

Cruse, J.M.; Ohl, P.C.

1995-01-01

This document provides the initial functions and requirements for leakage detection and monitoring applicable to past and potential future leakage from the Hanford Site's 149 single-shell high-level waste tanks. This mission is a part of the overall mission of the Westinghouse Hanford Company Tank Waste Remediation System division to remediate the tank waste in a safe and acceptable manner. Systems engineering principles are being applied to this effort. This document reflects the an initial step in the systems engineering approach to decompose the mission into primary functions and requirements. The document is considered approximately 30% complete relative to the effort required to produce a final version that can be used to support demonstration and/or procurement of technologies. The functions and requirements in this document apply to detection and monitoring of below ground leaks from SST containment boundaries and the resulting soil contamination. Leakage detection and monitoring is invoked in the TWRS Program in three fourth level functions: (1) Store Waste, (2) Retrieve Waste, and (3) Disposition Excess Facilities (as identified in DOE/RL-92-60 Rev. 1, Tank Waste Remediation System Functions and Requirements)

Human Systems Integration: Requirements and Functional Decomposition

Science.gov (United States)

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

2005-01-01

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

Functional requirements for gas characterization system computer software

International Nuclear Information System (INIS)

Tate, D.D.

1996-01-01

This document provides the Functional Requirements for the Computer Software operating the Gas Characterization System (GCS), which monitors the combustible gasses in the vapor space of selected tanks. Necessary computer functions are defined to support design, testing, operation, and change control. The GCS requires several individual computers to address the control and data acquisition functions of instruments and sensors. These computers are networked for communication, and must multi-task to accommodate operation in parallel

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

Science.gov (United States)

Stephens, J. Briscoe; Grider, Gary W.

1992-01-01

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

Requirements Document for Development of a Livermore Tomography Tools Interface

Energy Technology Data Exchange (ETDEWEB)

Seetho, I. M. [Lawrence Livermore National Lab. (LLNL), Livermore, CA (United States)

2017-02-09

In this document, we outline an exercise performed at LLNL to evaluate the user interface deficits of a LLNL-developed CT reconstruction software package, Livermore Tomography Tools (LTT). We observe that a difficult-to-use command line interface and the lack of support functions compound to generate a bottleneck in the CT reconstruction process when input parameters to key functions are not well known. Through the exercise of systems engineering best practices, we generate key performance parameters for a LTT interface refresh, and specify a combination of back-end (“test-mode” functions) and front-end (graphical user interface visualization and command scripting tools) solutions to LTT’s poor user interface that aim to mitigate issues and lower costs associated with CT reconstruction using LTT. Key functional and non-functional requirements and risk mitigation strategies for the solution are outlined and discussed.

Fiscal year 1997-1998 waste information requirements document

International Nuclear Information System (INIS)

Poppiti, J.A.

1997-01-01

The Waste Information Requirements Document describes the activities of the Tank Waste Remediation System (TWRS) Characterization Project that provide characterization information on Hanford Site waste tanks. The characterization information is required to perform operations and meet the commitments of TWRS end users. These commitments are derived from the Hanford Federal Facility Agreement and Consent Order, also known as the Tri-Party Agreement; the Recommendation 93-5 Implementation Plan to the Defense Nuclear Facilities Safety Board (DNFSB); and other directives as listed in Section 4.0. This Waste Information Requirement Document applies to Fiscal Years 1997 and 1998 activities. Its contents are based on the best information available in August 1997. The format and content are based on the directions of DOE-RL (Sieracki, 1997) and Fluor Daniel Hanford Incorporated (Umek, 1997). Activities, such as the revision of the Tank Characterization Technical Sampling Basis (Brown et al. 1997), the revision of the data quality objectives (DQOs), issue closures, discussions with Ecology, and management decisions may cause subsequent updates to the Waste Information Requirements Document

ISS Crew Transportation and Services Requirements Document

Science.gov (United States)

Bayt, Robert L. (Compiler); Lueders, Kathryn L. (Compiler)

2016-01-01

The ISS Crew Transportation and Services Requirements Document (CCT-REQ-1130) contains all technical, safety, and crew health medical requirements that are mandatory for achieving a Crew Transportation System Certification that will allow for International Space Station delivery and return of NASA crew and limited cargo. Previously approved on TN23183.

ENHANCED CHARACTERIZATION OF THE REPOSITORY BLOCK REQUIREMENTS DOCUMENT (ECRB-RD)

International Nuclear Information System (INIS)

G.M. Teraoka

1998-01-01

This Enhanced Characterization of the Repository Block Requirements Document (ECRB-RD) provides applicable design and construction requirements for the Enhanced Characterization of the Repository Block (ECRB) East-West Drift and its associated equipment. This document also identifies the applicable requirements from the Exploratory Studies Facilities Design Requirements (ESFDR) Document (YMPICM-00 19, Revision 2, ICN- 1) for design and construction of the ECRB East-West Drift, ground support, constructor support utilities and components. These requirements have been tailored specifically for the ECRB East-West Drift design and construction. The allocated requirements for the ECRB East-West Drift are in Sections III through VI. The requirements in sections III through VI contain requirement numbers from the ESFDR, Rev 2, ICN-1 for reference back to the ESFDR. Each requirement in the ECRB-RD also identifies a trace to the Site Design and Test Requirements Document (YMP/CM-0021, Rev. 2, ICN-1) and 10CFR60 similar to the style used in the ESFDR. These traces to 10CFR60 are consistent with the 1995 version of 10CFR60 used by the SD and TRD and the ESFDR. Those ESFDR requirements statements that were technically modified are identified as such and those that were derived as part of this allocation are also identified. An activity evaluation has been performed in accordance with QAP-2-0 and has determined that the QA program is applicable to this document. Therefore, the development of this document was performed in compliance with QAP-3-5, Revision 7, Development of Technical Documents and checked and reviewed in compliance with Section 5.3. This is consistent with the IOC from R. Stambaugh to M. Lugo on the subject of ECRB-RD, Revision 1, TDPP Applicability (LV.SEI.,RMS.03/98-0 12, Dated 3/12/98). The ECRB East-West Drift includes those excavated underground openings to support enhanced characterization testing activities for the repository block and provides potential

HTGR Industrial Application Functional and Operational Requirements

International Nuclear Information System (INIS)

Demick, L.E.

2010-01-01

This document specifies the functional and performance requirements to be used in the development of the conceptual design of a high temperature gas-cooled reactor (HTGR) based plant supplying energy to a typical industrial facility. These requirements were developed from collaboration with industry and HTGR suppliers over the preceding three years to identify the energy needs of industrial processes for which the HTGR technology is technically and economically viable. The functional and performance requirements specified herein are an effective representation of the industrial sector energy needs and an effective basis for developing a conceptual design of the plant that will serve the broadest range of industrial applications.

Documentation and verification required for type A packaging use

Energy Technology Data Exchange (ETDEWEB)

O`Brien, J.H.

1997-07-30

This document furnishes knowledge and methods for verifying compliance with the U.S. Department of Transportation (DOT) packaging requirements for shipping Type A quantities of radioactive material. The primary emphasis is on the requirements identified in 49 CFR 173.415(a), which states, ``Each offeror of a Specification 7A package must maintain on file for at least one year after the shipment, and shall provide to DOT on request, complete documentation of tests and an engineering evaluation of comparative data showing that the construction methods, packaging design, and materials of construction comply with that specification.`` This guidance document uses a checklist to show compliance.

Documentation and verification required for type A packaging use

International Nuclear Information System (INIS)

O'Brien, J.H.

1997-01-01

This document furnishes knowledge and methods for verifying compliance with the U.S. Department of Transportation (DOT) packaging requirements for shipping Type A quantities of radioactive material. The primary emphasis is on the requirements identified in 49 CFR 173.415(a), which states, ''Each offeror of a Specification 7A package must maintain on file for at least one year after the shipment, and shall provide to DOT on request, complete documentation of tests and an engineering evaluation of comparative data showing that the construction methods, packaging design, and materials of construction comply with that specification.'' This guidance document uses a checklist to show compliance

From document to database: modernizing requirements management

International Nuclear Information System (INIS)

Giajnorio, J.; Hamilton, S.

2007-01-01

The creation, communication, and management of design requirements are central to the successful completion of any large engineering project, both technically and commercially. Design requirements in the Canadian nuclear industry are typically numbered lists in multiple documents created using word processing software. As an alternative, GE Nuclear Products implemented a central requirements management database for a major project at Bruce Power. The database configured the off-the-shelf software product, Telelogic Doors, to GE's requirements structure. This paper describes the advantages realized by this scheme. Examples include traceability from customer requirements through to test procedures, concurrent engineering, and automated change history. (author)

EUR, an European utility requirements documents for future LWR power stations

International Nuclear Information System (INIS)

Berbey, Pierre; Lienard, Michel; Redon, Ramon; Essmann, Juergen; Taylor, David T.

2004-01-01

A group of the major European utilities are developing a common requirement document which will be used for the LWR nuclear power plants to be built in Europe from the beginning of the next century. This document provides harmonised policies and technical requirements that will allow the implementation of a design developed in one country into another one. The objectives and contents of the document, the organisation set up for its production and the main requirements are summarised in the paper. (author)

B plant standards/requirements identification document (S/RID)

Energy Technology Data Exchange (ETDEWEB)

Maddox, B.S., Westinghouse Hanford

1996-07-29

This Standards/Requirements Identification Document (S/RID) set forth the Environmental Safety and Health (ES{ampersand}H) standards/requirements for the B Plant. This S/RID is applicable to the appropriate life cycle phases of design, construction,operation, and preparation for decommissioning. These standards/requirements are adequate to ensure the protection of the health and safety of workers, the public, and the environment.

Requirements for the data transfer during the examination of design documentation

Directory of Open Access Journals (Sweden)

Karakozova Irina

2017-01-01

Full Text Available When you transfer the design documents to the examination office, number of incompatible electronic documents increases dramatically. The article discusses the way to solve the problem of transferring of the text and graphic data of design documentation for state and non-state expertise, as well as verification of estimates and requirement management. The methods for the recognition of the system elements and requirements for the transferring of text and graphic design documents are provided. The need to use the classification and coding of various elements of information systems (structures, objects, resources, requirements, contracts, etc. in data transferring systems is indicated separately. The authors have developed a sequence of document processing and transmission of data during the examination, and propose a language for describing the construction of the facility, taking into account the classification criteria of the structures and construction works.

Gas Test Loop Functional and Technical Requirements

International Nuclear Information System (INIS)

Glen R. Longhurst; Soli T. Khericha; James L. Jones

2004-01-01

This document defines the technical and functional requirements for a gas test loop (GTL) to be constructed for the purpose of providing a high intensity fast-flux irradiation environment for developers of advanced concept nuclear reactors. This capability is needed to meet fuels and materials testing requirements of the designers of Generation IV (GEN IV) reactors and other programs within the purview of the Advanced Fuel Cycle Initiative (AFCI). Space nuclear power development programs may also benefit by the services the GTL will offer. The overall GTL technical objective is to provide developers with the means for investigating and qualifying fuels and materials needed for advanced reactor concepts. The testing environment includes a fast-flux neutron spectrum of sufficient intensity to perform accelerated irradiation testing. Appropriate irradiation temperature, gaseous environment, test volume, diagnostics, and access and handling features are also needed. This document serves to identify those requirements as well as generic requirements applicable to any system of this kind

Gas Test Loop Functional and Technical Requirements

Energy Technology Data Exchange (ETDEWEB)

Glen R. Longhurst; Soli T. Khericha; James L. Jones

2004-09-01

This document defines the technical and functional requirements for a gas test loop (GTL) to be constructed for the purpose of providing a high intensity fast-flux irradiation environment for developers of advanced concept nuclear reactors. This capability is needed to meet fuels and materials testing requirements of the designers of Generation IV (GEN IV) reactors and other programs within the purview of the Advanced Fuel Cycle Initiative (AFCI). Space nuclear power development programs may also benefit by the services the GTL will offer. The overall GTL technical objective is to provide developers with the means for investigating and qualifying fuels and materials needed for advanced reactor concepts. The testing environment includes a fast-flux neutron spectrum of sufficient intensity to perform accelerated irradiation testing. Appropriate irradiation temperature, gaseous environment, test volume, diagnostics, and access and handling features are also needed. This document serves to identify those requirements as well as generic requirements applicable to any system of this kind.

The European Utility Requirement Document

International Nuclear Information System (INIS)

Roche, I.I.

1999-01-01

The major European electricity producers work on a common requirement document for future LWR plants since 1992. They aim at requirements acceptable together by the owners, the public and the authorities. Thus the designers can develop standard LWR designs acceptable everywhere in Europe and the utilities can open their consultations to vendors on common bases. Such a standardisation promotes an improvement of generation costs and of safety : public and authorities acceptance should be improved as well ; significant savings are expected in development and construction costs. Since the early stages of the project, the EUR group has grown significantly. It now includes utilities from nine European countries. Utilities from two other European countries are joining the group. Specific cooperation agreements are also in progress with a few extra-European partners

Functions and Requirements for Debris Removal System-Project A.2

International Nuclear Information System (INIS)

PRECECHTEL, D.R.

1999-01-01

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

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

International Nuclear Information System (INIS)

Groth, B.D.

1995-01-01

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

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

International Nuclear Information System (INIS)

GLASSCOCK, J.A.

2000-01-01

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

Hanford Tanks Initiative requirements and document management process guide

International Nuclear Information System (INIS)

Schaus, P.S.

1998-01-01

This revision of the guide provides updated references to project management level Program Management and Assessment Configuration Management activities, and provides working level directions for submitting requirements and project documentation related to the Hanford Tanks Initiative (HTI) project. This includes documents and information created by HTI, as well as non-HTI generated materials submitted to the project

Space station data system analysis/architecture study. Task 1: Functional requirements definition, DR-5. Appendix: Requirements data base

Science.gov (United States)

1985-01-01

Appendix A contains data that characterize the system functions in sufficient depth as to determine the requirements for the Space Station Data System (SSDS). This data is in the form of: (1) top down traceability report; (2) bottom up traceability report; (3) requirements data sheets; and (4) cross index of requirements paragraphs of the source documents and the requirements numbers. A data base users guide is included that interested parties can use to access the requirements data base and get up to date information about the functions.

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

Science.gov (United States)

1972-01-01

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

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 2

International Nuclear Information System (INIS)

1994-04-01

The Quality Assurance Functional Area Requirements Identification Document (RID), addresses the programmatic requirements that ensure risks and environmental impacts are minimized, ensure safety, reliability, and performance are maximized through the application of effective management systems commensurate with the risks posed by the Tank Farm Facility and its operation. This RID incorporates guidance intended to provide Tank Farms management with the necessary requirements information to develop, upgrade, or assess the effectiveness of a Quality Assurance Program in the performance of organizational and functional activities. Quality Assurance is defined as all those planned and systematic actions necessary to provide adequate confidence that a facility, structure, system, or component will perform satisfactorily and safely in service. This document will provide the specific requirements to meet DNFSB recommendations and the guidance provided in DOE Order 5700.6C, utilizing industry codes, standards, regulatory guidelines, and industry good practices that have proven to be essential elements for an effective and efficient Quality Assurance Program as the nuclear industry has matured over the last thirty years

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 2

Energy Technology Data Exchange (ETDEWEB)

1994-04-01

The Quality Assurance Functional Area Requirements Identification Document (RID), addresses the programmatic requirements that ensure risks and environmental impacts are minimized, ensure safety, reliability, and performance are maximized through the application of effective management systems commensurate with the risks posed by the Tank Farm Facility and its operation. This RID incorporates guidance intended to provide Tank Farms management with the necessary requirements information to develop, upgrade, or assess the effectiveness of a Quality Assurance Program in the performance of organizational and functional activities. Quality Assurance is defined as all those planned and systematic actions necessary to provide adequate confidence that a facility, structure, system, or component will perform satisfactorily and safely in service. This document will provide the specific requirements to meet DNFSB recommendations and the guidance provided in DOE Order 5700.6C, utilizing industry codes, standards, regulatory guidelines, and industry good practices that have proven to be essential elements for an effective and efficient Quality Assurance Program as the nuclear industry has matured over the last thirty years.

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

Energy Technology Data Exchange (ETDEWEB)

GLASSCOCK, J.A.

2000-01-27

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

Future CANDU nuclear power plant design requirements document executive summary

International Nuclear Information System (INIS)

Lee, Duk Su; Chang, Woo Hyun; Lee, Nam Young; S. A. Usmani

1996-03-01

The future CANDU Requirements Document (FCRED) describes a clear and complete statement of utility requirements for the next generation of CANDU nuclear power plants including those in Korea. The requirements are based on proven technology of PHWR experience and are intended to be consistent with those specified in the current international requirement documents. Furthermore, these integrated set of design requirements, incorporate utility input to the extent currently available and assure a simple, robust and more forgiving design that enhances the performance and safety. The FCRED addresses the entire plant, including the nuclear steam supply system and the balance of the plant, up to the interface with the utility grid at the distribution side of the circuit breakers which connect the switchyard to the transmission lines. Requirements for processing of low level radioactive waste at the plant site and spent fuel storage requirements are included in the FCRED. Off-site waste disposal is beyond the scope of the FCRED. 2 tabs., 1 fig. (Author) .new

Lawrence Livermore National Laboratory Emergency Response Capability Baseline Needs Assessment Requirement Document

Energy Technology Data Exchange (ETDEWEB)

Sharry, J A

2009-12-30

This revision of the LLNL Fire Protection Baseline Needs Assessment (BNA) was prepared by John A. Sharry, LLNL Fire Marshal and LLNL Division Leader for Fire Protection and reviewed by Martin Gresho, Sandia/CA Fire Marshal. The document follows and expands upon the format and contents of the DOE Model Fire Protection Baseline Capabilities Assessment document contained on the DOE Fire Protection Web Site, but only address emergency response. The original LLNL BNA was created on April 23, 1997 as a means of collecting all requirements concerning emergency response capabilities at LLNL (including response to emergencies at Sandia/CA) into one BNA document. The original BNA documented the basis for emergency response, emergency personnel staffing, and emergency response equipment over the years. The BNA has been updated and reissued five times since in 1998, 1999, 2000, 2002, and 2004. A significant format change was performed in the 2004 update of the BNA in that it was 'zero based.' Starting with the requirement documents, the 2004 BNA evaluated the requirements, and determined minimum needs without regard to previous evaluations. This 2010 update maintains the same basic format and requirements as the 2004 BNA. In this 2010 BNA, as in the previous BNA, the document has been intentionally divided into two separate documents - the needs assessment (1) and the compliance assessment (2). The needs assessment will be referred to as the BNA and the compliance assessment will be referred to as the BNA Compliance Assessment. The primary driver for separation is that the needs assessment identifies the detailed applicable regulations (primarily NFPA Standards) for emergency response capabilities based on the hazards present at LLNL and Sandia/CA and the geographical location of the facilities. The needs assessment also identifies areas where the modification of the requirements in the applicable NFPA standards is appropriate, due to the improved fire protection

7 CFR 1488.8 - Documents required after delivery.

Science.gov (United States)

2010-01-01

... 7 Agriculture 10 2010-01-01 2010-01-01 false Documents required after delivery. 1488.8 Section... delivery. (a) CCC will purchase an exporter's account receivable only if the Treasurer, Commodity Credit... or Assistant Treasurer, CCC, after date of delivery of commodities exported or to be exported under...

Westinghouse Hanford Company (WHC) standards/requirements identification document (S/RID)

Energy Technology Data Exchange (ETDEWEB)

Bennett, G.L.

1996-03-15

This Standards/Requirements Identification Document (S/RID) set forth the Environmental Safety and Health (ES&H) standards/requirements for Westinghouse Hanford Company Level Programs, where implementation and compliance is the responsibility of these organizations. These standards/requirements are adequate to ensure the protection of the health and safety of workers, the public, and the environment.

IDC Re-Engineering Phase 2 System Requirements Document V1.3.

Energy Technology Data Exchange (ETDEWEB)

Harris, James M. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Burns, John F. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Satpathi, Meara Allena [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States)

2015-12-01

This System Requirements Document (SRD) defines waveform data processing requirements for the International Data Centre (IDC) of the Comprehensive Nuclear Test Ban Treaty Organization (CTBTO). The IDC applies, on a routine basis, automatic processing methods and interactive analysis to raw International Monitoring System (IMS) data in order to produce, archive, and distribute standard IDC products on behalf of all States Parties. The routine processing includes characterization of events with the objective of screening out events considered to be consistent with natural phenomena or non-nuclear, man-made phenomena. This document does not address requirements concerning acquisition, processing and analysis of radionuclide data but includes requirements for the dissemination of radionuclide data and products.

IDC Re-Engineering Phase 2 System Requirements Document Version 1.4

Energy Technology Data Exchange (ETDEWEB)

Harris, James M. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Burns, John F. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Satpathi, Meara Allena [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States)

2017-01-01

This System Requirements Document (SRD) defines waveform data processing requirements for the International Data Centre (IDC) of the Comprehensive Nuclear Test Ban Treaty Organization (CTBTO). The IDC applies, on a routine basis, automatic processing methods and interactive analysis to raw International Monitoring System (IMS) data in order to produce, archive, and distribute standard IDC products on behalf of all States Parties. The routine processing includes characterization of events with the objective of screening out events considered to be consistent with natural phenomena or non-nuclear, man-made phenomena. This document does not address requirements concerning acquisition, processing and analysis of radionuclide data, but includes requirements for the dissemination of radionuclide data and products.

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

Science.gov (United States)

Swink, Jay R.; Goins, Richard T.

1992-01-01

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

Westinghouse Hanford Company (WHC) standards/requirements identification document (S/RID)

International Nuclear Information System (INIS)

Bennett, G.L.

1996-01-01

This Standards/Requirements Identification Document (S/RID) set forth the Environmental Safety and Health (ES ampersand amp;H) standards/requirements for Westinghouse Hanford Company Level Programs, where implementation and compliance is the responsibility of these organizations. These standards/requirements are adequate to ensure the protection of the health and safety of workers, the public, and the environment

CH2M Hill Hanford Group, Inc., Standards and Requirements Identification Document (SRID) Requirements Management System and Requirements Specification

International Nuclear Information System (INIS)

JOHNSON, A.L.

2000-01-01

The current Tank Farm Contractor (TFC) for the U. S. Department of Energy, Office of River Protection (ORP), River Protection Project (RPP), CH2M Hill Hanford Group, Inc. (CHG), will use a computer based requirements management system. The system will serve as a tool to assist in identifying, capturing, and maintaining the Standards/Requirements Identification Document (S/RID) requirements and links to implementing procedures and other documents. By managing requirements as one integrated set, CHG will be able to carry out its mission more efficiently and effectively. CHG has chosen the Dynamic Object Oriented Requirements System (DOORS(trademark)) as the preferred computer based requirements management system. Accordingly, the S/RID program will use DOORS(trademark). DOORS(trademark) will replace the Environmental Requirements Management Interface (ERMI) system as the tool for S/RID data management. The DOORS(trademark) S/RID test project currently resides on the DOORSTM test server. The S/RID project will be migrated to the DOORS(trademark) production server. After the migration the S/RID project will be considered a production project and will no longer reside on the test server

Plutonium Finishing Plant (PFP) Standards/Requirements Identification Document (S/RID)

Energy Technology Data Exchange (ETDEWEB)

Maddox, B.S.

1996-01-01

This Standards/Requirements Identification Document (S/RID) sets forth the Environmental Safety and Health (ESH) standards/requirements for the Plutonium Finishing Plant (PFP). This S/RID is applicable to the appropriate life cycle phases of design, construction, operation, and preparation for decommissioning. These standards/requirements are adequate to ensure the protection of the health and safety of workers, the public, and the environment.

Plutonium Finishing Plant (PFP) Standards/Requirements Identification Document (S/RID)

International Nuclear Information System (INIS)

Maddox, B.S.

1996-01-01

This Standards/Requirements Identification Document (S/RID) sets forth the Environmental Safety and Health (ESH) standards/requirements for the Plutonium Finishing Plant (PFP). This S/RID is applicable to the appropriate life cycle phases of design, construction, operation, and preparation for decommissioning. These standards/requirements are adequate to ensure the protection of the health and safety of workers, the public, and the environment

17 CFR 4.31 - Required delivery of Disclosure Document to prospective clients.

Science.gov (United States)

2010-04-01

... Disclosure Document to prospective clients. 4.31 Section 4.31 Commodity and Securities Exchanges COMMODITY... Advisors § 4.31 Required delivery of Disclosure Document to prospective clients. (a) Each commodity trading... prospective client a Disclosure Document containing the information set forth in §§ 4.34 and 4.35 for the...

Environmental restoration remedial action quality assurance requirements document

International Nuclear Information System (INIS)

Cote, R.F.

1991-01-01

The environmental Restoration Remedial Action Quality Assurance Requirements Document (DOE/RL 90-28) defines the quality assurance program requirements for the US Department of Energy-Richland Field Office Environmental Restoration Remedial Action Program at the Hanford Site, Richland, Washington. This paper describes the objectives outlined in DOE/RL 90-28. The Environmental Restoration Remedial Action Program implements significant commitments made by the US Department of Energy in the Hanford Federal Facility Agreement and Consent Order entered into with the Washington State Department of Ecology and the US Environmental Protection Agency

Functions and requirements for 105-KE Basin sludge retrieval and packaging

International Nuclear Information System (INIS)

Feigenbutz, L.V.

1994-01-01

Sludge, and the clouding due to sludge, interferes with basin operation and maintenance activities. This document defines the overall functions and requirements for sludge retrieval and packaging activities to be performed in the 105-KE Basin

Supplmental design requirements document enhanced radioactive and mixed waste storage: Phase 5, Project W-113

International Nuclear Information System (INIS)

Ocampo, V.P.

1994-11-01

This Supplemental Design Requirements Document (SDRD) is used to communicate Project W-113 specific plant design information from Westinghouse Hanford Company (WHC) to the United States Department of Energy (DOE) and the cognizant Architect Engineer (A/E). The SDRD is prepared after the completion of the project Conceptual Design report (CDR) and prior to the initiation of definitive design. Information in the SDRD serves two purposes: to convey design requirements that are too detailed for inclusion in the Functional Design Criteria (FDC) report and to serve as a means of change control for design commitments in the Title I and Title II design. The Solid Waste Retrieval Project (W-113) SDRD has been restructured from the equipment based outline used in previous SDRDs to a functional systems outline. This was done to facilitate identification of deficiencies in the information provided in the initial draft SDRD and aid design confirmation. The format and content of this SDRD adhere as closely as practicable to the requirements of WHC-CM-6-1, Standard Engineering Practices for Functional Design Criteria

ELECTRICAL POWER SYSTEM DESCRIPTION DOCUMENT

Energy Technology Data Exchange (ETDEWEB)

M. Maniyar

2004-06-22

The purpose of this revision of the System Description Document (SDD) is to establish requirements that drive the design of the electrical power system and their bases to allow the design effort to proceed to License Application. This SDD is a living document that will be revised at strategic points as the design matures over time. This SDD identifies the requirements and describes the system design as they exist at this time, with emphasis on those attributes of the design provided to meet the requirements. This SDD has been developed to be an engineering tool for design control. Accordingly, the primary audience are design engineers. This type of SDD leads and follows the design process. It leads the design process with regard to the flow down of upper tier requirements onto the system. Knowledge of these requirements is essential to performing the design process. This SDD follows the design with regard to the description of the system. The description provided in the SDD is a reflection of the results of the design process to date. Functional and operational requirements applicable to this system are obtained from ''Project Functional and Operational Requirements'' (F&OR) (Siddoway, 2003). Other requirements to support the design process have been taken from higher level requirements documents such as ''Project Design Criteria Document'' (PDC) (Doraswamy 2004), the fire hazards analyses, and the preclosure safety analysis. The above mentioned low-level documents address ''Project Requirements Document'' (PRD) (Canori and Leitner 2003) requirements. This SDD includes several appendices with supporting information. Appendix B lists key system charts, diagrams, drawings, and lists; and Appendix C is a list of system procedures.

Functions and Requirements and Specifications for Replacement of the Computer Automated Surveillance System (CASS)

International Nuclear Information System (INIS)

SCAIEF, C.C.

1999-01-01

This functions, requirements and specifications document defines the baseline requirements and criteria for the design, purchase, fabrication, construction, installation, and operation of the system to replace the Computer Automated Surveillance System (CASS) alarm monitoring

50 CFR 23.19 - What CITES documents are required to export Appendix-I plants?

Science.gov (United States)

2010-10-01

... 50 Wildlife and Fisheries 6 2010-10-01 2010-10-01 false What CITES documents are required to... ENDANGERED SPECIES OF WILD FAUNA AND FLORA (CITES) Prohibitions, Exemptions, and Requirements § 23.19 What CITES documents are required to export Appendix-I plants? Answer the questions in the following decision...

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 3

Energy Technology Data Exchange (ETDEWEB)

1994-04-01

The Safeguards and Security (S&S) Functional Area address the programmatic and technical requirements, controls, and standards which assure compliance with applicable S&S laws and regulations. Numerous S&S responsibilities are performed on behalf of the Tank Farm Facility by site level organizations. Certain other responsibilities are shared, and the remainder are the sole responsibility of the Tank Farm Facility. This Requirements Identification Document describes a complete functional Safeguards and Security Program that is presumed to be the responsibility of the Tank Farm Facility. The following list identifies the programmatic elements in the S&S Functional Area: Program Management, Protection Program Scope and Evaluation, Personnel Security, Physical Security Systems, Protection Program Operations, Material Control and Accountability, Information Security, and Key Program Interfaces.

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 3

International Nuclear Information System (INIS)

1994-04-01

The Safeguards and Security (S ampersand S) Functional Area address the programmatic and technical requirements, controls, and standards which assure compliance with applicable S ampersand S laws and regulations. Numerous S ampersand S responsibilities are performed on behalf of the Tank Farm Facility by site level organizations. Certain other responsibilities are shared, and the remainder are the sole responsibility of the Tank Farm Facility. This Requirements Identification Document describes a complete functional Safeguards and Security Program that is presumed to be the responsibility of the Tank Farm Facility. The following list identifies the programmatic elements in the S ampersand S Functional Area: Program Management, Protection Program Scope and Evaluation, Personnel Security, Physical Security Systems, Protection Program Operations, Material Control and Accountability, Information Security, and Key Program Interfaces

Functional requirements for portable exhauster system to be used during saltwell pumping

International Nuclear Information System (INIS)

Nelson, O.D.

1998-01-01

This document defines functional requirements for portable exhausters used to ventilate primary tanks during saltwell pumping, and provide back-up to primary and annulus ventilation systems at C-106 and AY-102

Test Protocols for Advanced Inverter Interoperability Functions – Main Document

Energy Technology Data Exchange (ETDEWEB)

Johnson, Jay Dean [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Gonzalez, Sigifredo [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Ralph, Mark E. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Ellis, Abraham [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Broderick, Robert Joseph [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States)

2013-11-01

Distributed energy resources (DER) such as photovoltaic (PV) systems, when deployed in a large scale, are capable of influencing significantly the operation of power systems. Looking to the future, stakeholders are working on standards to make it possible to manage the potentially complex interactions between DER and the power system. In 2009, the Electric Power Research Institute (EPRI), Sandia National Laboratories (SNL) with the U.S. Department of Energy (DOE), and the Solar Electric Power Association (SEPA) initiated a large industry collaborative to identify and standardize definitions for a set of DER grid support functions. While the initial effort concentrated on grid-tied PV inverters and energy storage systems, the concepts have applicability to all DER. A partial product of this on-going effort is a reference definitions document (IEC TR 61850-90-7, Object models for power converters in distributed energy resources (DER) systems) that has become a basis for expansion of related International Electrotechnical Commission (IEC) standards, and is supported by US National Institute of Standards and Technology (NIST) Smart Grid Interoperability Panel (SGIP). Some industry-led organizations advancing communications protocols have also embraced this work. As standards continue to evolve, it is necessary to develop test protocols to independently verify that the inverters are properly executing the advanced functions. Interoperability is assured by establishing common definitions for the functions and a method to test compliance with operational requirements. This document describes test protocols developed by SNL to evaluate the electrical performance and operational capabilities of PV inverters and energy storage, as described in IEC TR 61850-90-7. While many of these functions are not currently required by existing grid codes or may not be widely available commercially, the industry is rapidly moving in that direction. Interoperability issues are already

ELECTRICAL SUPPORT SYSTEM DESCRIPTION DOCUMENT

International Nuclear Information System (INIS)

Roy, S.

2004-01-01

The purpose of this revision of the System Design Description (SDD) is to establish requirements that drive the design of the electrical support system and their bases to allow the design effort to proceed to License Application. This SDD is a living document that will be revised at strategic points as the design matures over time. This SDD identifies the requirements and describes the system design as they exist at this time, with emphasis on those attributes of the design provided to meet the requirements. This SDD has been developed to be an engineering tool for design control. Accordingly, the primary audience/users are design engineers. This type of SDD both ''leads'' and ''trails'' the design process. It leads the design process with regard to the flow down of upper tier requirements onto the system. Knowledge of these requirements is essential in performing the design process. The SDD trails the design with regard to the description of the system. The description provided in the SDD is a reflection of the results of the design process to date. Functional and operational requirements applicable to electrical support systems are obtained from the ''Project Functional and Operational Requirements'' (F andOR) (Siddoway 2003). Other requirements to support the design process have been taken from higher-level requirements documents such as the ''Project Design Criteria Document'' (PDC) (Doraswamy 2004), and fire hazards analyses. The above-mentioned low-level documents address ''Project Requirements Document'' (PRD) (Canon and Leitner 2003) requirements. This SDD contains several appendices that include supporting information. Appendix B lists key system charts, diagrams, drawings, and lists, and Appendix C includes a list of system procedures

System requirements and design description for the document basis database interface (DocBasis)

International Nuclear Information System (INIS)

Lehman, W.J.

1997-01-01

This document describes system requirements and the design description for the Document Basis Database Interface (DocBasis). The DocBasis application is used to manage procedures used within the tank farms. The application maintains information in a small database to track the document basis for a procedure, as well as the current version/modification level and the basis for the procedure. The basis for each procedure is substantiated by Administrative, Technical, Procedural, and Regulatory requirements. The DocBasis user interface was developed by Science Applications International Corporation (SAIC)

Performing the processing required for automatically get a PDF/A version of the CERN Library documentation

CERN Document Server

Molina Garcia-Retamero, Antonio

2015-01-01

The aim of the project was to perform the processing required for automatically get a PDF/A version of the CERN Library documentation. For this, it is necessary to extract as much metadata as possible from the sources files, inject the required data into the original source files creating new ones ready for being compiled with all related dependencies. Besides, I’ve proposed the creation of a HTML version consistent with the PDF and navigable for easy access, I’ve been trying to perform some Natural Language Processing for extracting metadata, I’ve proposed the injection of the cern library documentation into the HTML version of the long writeups where it is referenced (for instance, when a CERN Library function is referenced in a sample code) Finally, I’ve designed and implemented a Graphical User Interface in order to simplify the process for the user.

NRC review of Electric Power Research Institute's advanced light water reactor utility requirements document. Passive plant designs, chapter 1, project number 669

International Nuclear Information System (INIS)

1994-08-01

The Electric Power Research Institute (EPRI) is preparing a compendium of technical requirements, referred to as the open-quotes Advanced Light Water Reactor [ALWR] Utility Requirements Documentclose quotes, that is acceptable to the design of an ALWR power plant. When completed, this document is intended to be a comprehensive statement of utility requirements for the design, construction, and performance of an ALWR power plant for the 1990s and beyond. The Requirements Document consists of three volumes. Volume 1, open-quotes ALWR Policy and Summary of Top-Tier Requirementsclose quotes, is a management-level synopsis of the Requirements Document, including the design objectives and philosophy, the overall physical configuration and features of a future nuclear plant design, and the steps necessary to take the proposed ALWR design criteria beyond the conceptual design state to a completed, functioning power plant. Volume II consists of 13 chapters and contains utility design requirements for an evolutionary nuclear power plant [approximately 1350 megawatts-electric (MWe)]. Volume III contains utility design requirements for nuclear plants for which passive features will be used in their designs (approximately 600 MWe). In April 1992, the staff of the Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, issued Volume 1 and Volume 2 (Parts 1 and 2) of its safety evaluation report (SER) to document the results of its review of Volumes 1 and 2 of the Requirements Document. Volume 1, open-quotes NRC Review of Electric Power Research Institute's Advanced Light Water Reactor Utility Requirements Document - Program Summaryclose quotes, provided a discussion of the overall purpose and scope of the Requirements Document, the background of the staff's review, the review approach used by the staff, and a summary of the policy and technical issues raised by the staff during its review

305 Building K basin mockup facility functions and requirements

International Nuclear Information System (INIS)

Steele, R.M.

1994-01-01

This document develops functions and requirements for installation and operation of a cold mockup test facility within the 305 Building. The test facility will emulate a portion of a typical spent nuclear fuel storage basin (e.g., 105-KE Basin) to support evaluation of equipment and processes for safe storage and disposition of the spent nuclear fuel currently within the K Basins

ELECTRICAL SUPPORT SYSTEM DESCRIPTION DOCUMENT

Energy Technology Data Exchange (ETDEWEB)

S. Roy

2004-06-24

The purpose of this revision of the System Design Description (SDD) is to establish requirements that drive the design of the electrical support system and their bases to allow the design effort to proceed to License Application. This SDD is a living document that will be revised at strategic points as the design matures over time. This SDD identifies the requirements and describes the system design as they exist at this time, with emphasis on those attributes of the design provided to meet the requirements. This SDD has been developed to be an engineering tool for design control. Accordingly, the primary audience/users are design engineers. This type of SDD both ''leads'' and ''trails'' the design process. It leads the design process with regard to the flow down of upper tier requirements onto the system. Knowledge of these requirements is essential in performing the design process. The SDD trails the design with regard to the description of the system. The description provided in the SDD is a reflection of the results of the design process to date. Functional and operational requirements applicable to electrical support systems are obtained from the ''Project Functional and Operational Requirements'' (F&OR) (Siddoway 2003). Other requirements to support the design process have been taken from higher-level requirements documents such as the ''Project Design Criteria Document'' (PDC) (Doraswamy 2004), and fire hazards analyses. The above-mentioned low-level documents address ''Project Requirements Document'' (PRD) (Canon and Leitner 2003) requirements. This SDD contains several appendices that include supporting information. Appendix B lists key system charts, diagrams, drawings, and lists, and Appendix C includes a list of system procedures.

Advanced flight deck/crew station simulator functional requirements

Science.gov (United States)

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

1980-01-01

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

Supplemental design requirements document solid waste operations complex

International Nuclear Information System (INIS)

Ocampo, V.P.; Boothe, G.F.; Broz, D.R.; Eaton, H.E.; Greager, T.M.; Huckfeldt, R.A.; Kooiker, S.L.; Lamberd, D.L.; Lang, L.L.; Myers, J.B.

1994-11-01

This document provides additional and supplemental information to the WHC-SD-W112-FDC-001, WHC-SD-W113-FDC-001, and WHC-SD-W100-FDC-001. It provides additional requirements for the design and summarizes Westinghouse Hanford Company key design guidance and establishes the technical baseline agreements to be used for definitive design common to the Solid Waste Operations Complex (SWOC) Facilities (Project W-112, Project W-113, and WRAP 2A)

Waste encapsulation storage facility (WESF) standards/requirements identification document (S/RIDS)

Energy Technology Data Exchange (ETDEWEB)

Maddox, B.S., Westinghouse Hanford

1996-07-29

This Standards/Requirements Identification Document (S/RID) sets forth the Environmental Safety and Health (ES{ampersand}H) standards/requirements for the Waste Encapsulation Storage Facility (WESF). This S/RID is applicable to the appropriate life cycle phases of design, construction, operation, and preparation for decommissioning. These standards/requirements are adequate to ensure the protection of the health and safety of workers, the public, and the environment.

NRC review of Electric Power Research Institute's advanced light water reactor utility requirements document. Passive plant designs, chapters 2-13, project number 669

International Nuclear Information System (INIS)

1994-08-01

The Electric Power Research Institute (EPRI) is preparing a compendium of technical requirements, referred to as the open-quotes Advanced Light Water Reactor [ALWR] Utility Requirements Documentclose quotes, that is acceptable to the design of an ALWR power plant. When completed, this document is intended to be a comprehensive statement of utility requirements for the design, construction, and performance of an ALWR power plant for the 1990s and beyond. The Requirements Document consists of three volumes. Volume I, open-quotes ALWR Policy and Summary of Top-Tier Requirementsclose quotes, is a management-level synopsis of the Requirements Document, including the design objectives and philosophy, the overall physical configuration and features of a future nuclear plant design, and the steps necessary to take the proposed ALWR design criteria beyond the conceptual design state to a completed, functioning power plant. Volume II consists of 13 chapters and contains utility design requirements for an evolutionary nuclear power plant [approximately 1350 megawatts-electric (MWe)]. Volume III contains utility design requirements for nuclear plants for which passive features will be used in their designs (approximately 600 MWe). In April 1992, the staff of the Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, issued Volume 1 and Volume 2 (Parts 1 and 2) of its safety evaluation report (SER) to document the results of its review of Volumes 1 and 2 of the Requirements Document. Volume 1, open-quotes NRC Review of Electric Power Research Institute's Advanced Light Water Reactor Utility Requirements Document - Program Summaryclose quotes, provided a discussion of the overall purpose and scope of the Requirements Document, the background of the staff's review, the review approach used by the staff, and a summary of the policy and technical issues raised by the staff during its review

Program prioritization system user requirements document for Gas Cooled Reactor Associates

International Nuclear Information System (INIS)

1981-01-01

Efficient management of the national HTGR program requires the establishment of an information system that will facilitate a more rational allocation of resources and task prioritization consistent with program policies. The system described in this document provides a data analysis mechanism for processing top level summary status and planning information in a rapid, timely and selective manner. Data produced by the system can be used by management to provide a rational basis for prioritizing tasks, evaluating program changes and program planning regarding costs, schedules and overall program development logic. The purpose of this document is to delineate the program prioritization system (PPS) requirements for use as a guide to acquiring and implementing the system

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 1

Energy Technology Data Exchange (ETDEWEB)

1994-04-01

The purpose of this Requirements Identification Document (RID) section is to identify, in one location, all of the facility specific requirements and good industry practices which are necessary or important to establish an effective Issues Management Program for the Tank Farm Facility. The Management Systems Functional Area includes the site management commitment to environmental safety and health (ES&H) policies and controls, to compliance management, to development and management of policy and procedures, to occurrence reporting and corrective actions, resource and issue management, and to the self-assessment process.

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 1

International Nuclear Information System (INIS)

1994-04-01

The purpose of this Requirements Identification Document (RID) section is to identify, in one location, all of the facility specific requirements and good industry practices which are necessary or important to establish an effective Issues Management Program for the Tank Farm Facility. The Management Systems Functional Area includes the site management commitment to environmental safety and health (ES ampersand H) policies and controls, to compliance management, to development and management of policy and procedures, to occurrence reporting and corrective actions, resource and issue management, and to the self-assessment process

CASK/MSC/WP PREPARATION SYSTEM DESCRIPTION DOCUMENT

International Nuclear Information System (INIS)

S. Drummond

2005-01-01

The purpose of this system description document (SDD) is to establish requirements that drive the design of the Cask/MSC/WP preparation system and their bases to allow the design effort to proceed to license application. This SDD is a living document that will be revised at strategic points as the design matures over time. This SDD identifies the requirements and describes the system design, as they exist at this time, with emphasis on those attributes of the design provided to meet the requirements. This SDD has been developed to be an engineering tool for design control. Accordingly, the primary audience and users are design engineers. This type of SDD both leads and trails the design process. It leads the design process with regard to the flow down of upper tier requirements onto the system. Knowledge of these requirements is essential in performing the design process. This SDD trails the design with regard to the description of the system. The description provided in the SDD is a reflection of the results of the design process to date. This SDD addresses the ''Project Requirements Document'' (PRD) (Canori and Leitner 2003 [DIRS 166275]) requirements. Additional PRD requirements may be cited, as applicable, to drive the design of specific aspects of the system, with justifications provided in the basis. Functional and operational requirements applicable to this system are obtained from the ''Project Functional and Operational Requirements'' (F and OR) (Curry 2004 [DIRS 170557]) document. Other requirements to support the design process have been taken from higher-level requirements documents such as the ''Project Design Criteria Document'' (PDC) (BSC 2004 [DIRS 171599]) and the preclosure safety analyses

High-level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID)

Energy Technology Data Exchange (ETDEWEB)

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Identification Document (S/RID) is contained in multiple volumes. This document (Volume 3) presents the standards and requirements for the following sections: Safeguards and Security, Engineering Design, and Maintenance.

High-level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID)

International Nuclear Information System (INIS)

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Identification Document (S/RID) is contained in multiple volumes. This document (Volume 3) presents the standards and requirements for the following sections: Safeguards and Security, Engineering Design, and Maintenance

Functions and requirements for a cesium demonstration unit

International Nuclear Information System (INIS)

Howden, G.F.

1994-04-01

Westinghouse Hanford Company is investigating alternative means to pretreat the wastes in the Hanford radioactive waste storage tanks. Alternatives include (but are not limited to) in-tank pretreatment, use of above ground transportable compact processing units (CPU) located adjacent to a tank farm, and fixed processing facilities. This document provides the functions and requirements for a CPU to remove cesium from tank waste as a demonstration of the CPU concept. It is therefore identified as the Cesium Demonstration Unit CDU

45 CFR 400.43 - Requirements for documentation of refugee status.

Science.gov (United States)

2010-10-01

... 45 Public Welfare 2 2010-10-01 2010-10-01 false Requirements for documentation of refugee status. 400.43 Section 400.43 Public Welfare Regulations Relating to Public Welfare OFFICE OF REFUGEE RESETTLEMENT, ADMINISTRATION FOR CHILDREN AND FAMILIES, DEPARTMENT OF HEALTH AND HUMAN SERVICES REFUGEE...

Functions and Requirements for Automated Liquid Level Gauge Instruments in Single-Shell and Double-Shell Tank Farms

International Nuclear Information System (INIS)

CARPENTER, K.E.

1999-01-01

This functions and requirements document defines the baseline requirements and criteria for the design, purchase, fabrication, construction, installation, and operation of automated liquid level gauge instruments in the Tank Farms. This document is intended to become the technical baseline for current and future installation, operation and maintenance of automated liquid level gauges in single-shell and double-shell tank farms

Hanford analytical services quality assurance requirements documents. Volume 1: Administrative Requirements

International Nuclear Information System (INIS)

Hyatt, J.E.

1997-01-01

Hanford Analytical Services Quality Assurance Requirements Document (HASQARD) is issued by the Analytical Services, Program of the Waste Management Division, US Department of Energy (US DOE), Richland Operations Office (DOE-RL). The HASQARD establishes quality requirements in response to DOE Order 5700.6C (DOE 1991b). The HASQARD is designed to meet the needs of DOE-RL for maintaining a consistent level of quality for sampling and field and laboratory analytical services provided by contractor and commercial field and laboratory analytical operations. The HASQARD serves as the quality basis for all sampling and field/laboratory analytical services provided to DOE-RL through the Analytical Services Program of the Waste Management Division in support of Hanford Site environmental cleanup efforts. This includes work performed by contractor and commercial laboratories and covers radiological and nonradiological analyses. The HASQARD applies to field sampling, field analysis, and research and development activities that support work conducted under the Hanford Federal Facility Agreement and Consent Order Tri-Party Agreement and regulatory permit applications and applicable permit requirements described in subsections of this volume. The HASQARD applies to work done to support process chemistry analysis (e.g., ongoing site waste treatment and characterization operations) and research and development projects related to Hanford Site environmental cleanup activities. This ensures a uniform quality umbrella to analytical site activities predicated on the concepts contained in the HASQARD. Using HASQARD will ensure data of known quality and technical defensibility of the methods used to obtain that data. The HASQARD is made up of four volumes: Volume 1, Administrative Requirements; Volume 2, Sampling Technical Requirements; Volume 3, Field Analytical Technical Requirements; and Volume 4, Laboratory Technical Requirements. Volume 1 describes the administrative requirements

CASK/MSC/WP PREPARATION SYSTEM DESCRIPTION DOCUMENT

Energy Technology Data Exchange (ETDEWEB)

S. Drummond

2005-04-12

The purpose of this system description document (SDD) is to establish requirements that drive the design of the Cask/MSC/WP preparation system and their bases to allow the design effort to proceed to license application. This SDD is a living document that will be revised at strategic points as the design matures over time. This SDD identifies the requirements and describes the system design, as they exist at this time, with emphasis on those attributes of the design provided to meet the requirements. This SDD has been developed to be an engineering tool for design control. Accordingly, the primary audience and users are design engineers. This type of SDD both leads and trails the design process. It leads the design process with regard to the flow down of upper tier requirements onto the system. Knowledge of these requirements is essential in performing the design process. This SDD trails the design with regard to the description of the system. The description provided in the SDD is a reflection of the results of the design process to date. This SDD addresses the ''Project Requirements Document'' (PRD) (Canori and Leitner 2003 [DIRS 166275]) requirements. Additional PRD requirements may be cited, as applicable, to drive the design of specific aspects of the system, with justifications provided in the basis. Functional and operational requirements applicable to this system are obtained from the ''Project Functional and Operational Requirements'' (F&OR) (Curry 2004 [DIRS 170557]) document. Other requirements to support the design process have been taken from higher-level requirements documents such as the ''Project Design Criteria Document'' (PDC) (BSC 2004 [DIRS 171599]) and the preclosure safety analyses.

Analysis of compatibility of current Czech initial documentation in the area of technical assurance of nuclear safety with the requirements of the EUR document

International Nuclear Information System (INIS)

Zdebor, J.; Zdebor, R.; Kratochvil, L.

2001-11-01

The publication is structured as follows: Description of existing documentation. General requirements, goals, principles and design principles: Documents being compared; Method of comparison; Results and partial evaluation of comparison of requirements between EUR and Czech regulations (basic goals and safety philosophy; quantitative safety objectives; basic design requirements; extended design requirements; external and internal threats; technical requirements; site conditions); Summary of the comparison of safety requirements. Comparison of requirements for the systems: Requirements for the nuclear reactor unit systems; Barrier systems (fuel system; reactor cooling system; containment system); Remaining systems (control systems; protection systems; coolant makeup and purification system; residual heat removal system; emergency cooling system; power systems); Common technical requirements for systems (technical requirements for systems; internal and external events). (P.A.)

50 CFR 23.25 - What additional information is required on a non-Party CITES document?

Science.gov (United States)

2010-10-01

... a non-Party CITES document? 23.25 Section 23.25 Wildlife and Fisheries UNITED STATES FISH AND... IN ENDANGERED SPECIES OF WILD FAUNA AND FLORA (CITES) Prohibitions, Exemptions, and Requirements § 23.25 What additional information is required on a non-Party CITES document? (a) Purpose. Under Article...

SNF AGING SYSTEM DESCRIPTION DOCUMENT

Energy Technology Data Exchange (ETDEWEB)

L.L. Swanson

2005-04-06

The purpose of this system description document (SDD) is to establish requirements that drive the design of the spent nuclear fuel (SNF) aging system and associated bases, which will allow the design effort to proceed. This SDD will be revised at strategic points as the design matures. This SDD identifies the requirements and describes the system design, as it currently exists, with emphasis on attributes of the design provided to meet the requirements. This SDD is an engineering tool for design control; accordingly, the primary audience and users are design engineers. This SDD is part of an iterative design process. It leads the design process with regard to the flow down of upper tier requirements onto the system. Knowledge of these requirements is essential in performing the design process. The SDD follows the design with regard to the description of the system. The description provided in the SDD reflects the current results of the design process. Throughout this SDD, the term aging cask applies to vertical site-specific casks and to horizontal aging modules. The term overpack is a vertical site-specific cask that contains a dual-purpose canister (DPC) or a disposable canister. Functional and operational requirements applicable to this system were obtained from ''Project Functional and Operational Requirements'' (F&OR) (Curry 2004 [DIRS 170557]). Other requirements that support the design process were taken from documents such as ''Project Design Criteria Document'' (PDC) (BSC 2004 [DES 171599]), ''Site Fire Hazards Analyses'' (BSC 2005 [DIRS 172174]), and ''Nuclear Safety Design Bases for License Application'' (BSC 2005 [DIRS 171512]). The documents address requirements in the ''Project Requirements Document'' (PRD) (Canori and Leitner 2003 [DIRS 166275]). This SDD includes several appendices. Appendix A is a Glossary; Appendix B is a list of key system charts

SNF AGING SYSTEM DESCRIPTION DOCUMENT

International Nuclear Information System (INIS)

L.L. Swanson

2005-01-01

The purpose of this system description document (SDD) is to establish requirements that drive the design of the spent nuclear fuel (SNF) aging system and associated bases, which will allow the design effort to proceed. This SDD will be revised at strategic points as the design matures. This SDD identifies the requirements and describes the system design, as it currently exists, with emphasis on attributes of the design provided to meet the requirements. This SDD is an engineering tool for design control; accordingly, the primary audience and users are design engineers. This SDD is part of an iterative design process. It leads the design process with regard to the flow down of upper tier requirements onto the system. Knowledge of these requirements is essential in performing the design process. The SDD follows the design with regard to the description of the system. The description provided in the SDD reflects the current results of the design process. Throughout this SDD, the term aging cask applies to vertical site-specific casks and to horizontal aging modules. The term overpack is a vertical site-specific cask that contains a dual-purpose canister (DPC) or a disposable canister. Functional and operational requirements applicable to this system were obtained from ''Project Functional and Operational Requirements'' (F andOR) (Curry 2004 [DIRS 170557]). Other requirements that support the design process were taken from documents such as ''Project Design Criteria Document'' (PDC) (BSC 2004 [DES 171599]), ''Site Fire Hazards Analyses'' (BSC 2005 [DIRS 172174]), and ''Nuclear Safety Design Bases for License Application'' (BSC 2005 [DIRS 171512]). The documents address requirements in the ''Project Requirements Document'' (PRD) (Canori and Leitner 2003 [DIRS 166275]). This SDD includes several appendices. Appendix A is a Glossary; Appendix B is a list of key system charts, diagrams, drawings, lists and additional supporting information; and Appendix C is a list of

48 CFR 752.7005 - Submission requirements for development experience documents.

Science.gov (United States)

2010-10-01

... (referenced in paragraph (a)(1) of this clause) in electronic format and hard copy (one copy) to U.S. Agency... final equivalent of the hard copy submitted. (iv) Acceptable software formats for electronic documents... paragraph (b)(1)(i) of this clause. (2) Format. (i) Descriptive information is required for all Contractor...

Fiscal Year 2001 Tank Characterization Technical Sampling Basis and Waste Information Requirements Document

International Nuclear Information System (INIS)

ADAMS, M.R.

2000-01-01

The Fiscal Year 2001 Tank Characterization Technical Sampling Basis and Waste Information Requirements Document (TSB-WIRD) has the following purposes: (1) To identify and integrate sampling and analysis needs for fiscal year (FY) 2001 and beyond. (2) To describe the overall drivers that require characterization information and to document their source. (3) To describe the process for identifying, prioritizing, and weighting issues that require characterization information to resolve. (4) To define the method for determining sampling priorities and to present the sampling priorities on a tank-by-tank basis. (5) To define how the characterization program is going to satisfy the drivers, close issues, and report progress. (6)To describe deliverables and acceptance criteria for characterization deliverables

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 5

Energy Technology Data Exchange (ETDEWEB)

1994-04-01

The Fire Protection functional area for the Hanford Site Tank Farm facilities and support structures is based on the application of relevant DOE orders, regulations, and industry codes and standards. The fire protection program defined in this document may be divided into three areas: (1) organizational, (2) administrative programmatic features, and (3) technical features. The information presented in each section is in the form of program elements and orders, regulations, industry codes, and standards that serve as the attributes of a fire protection program for the Tank Farm facilities. Upon completion this document will be utilized as the basis to evaluate compliance of the fire protection program being implemented for the Tank Farm facilities with the requirements of DOE orders and industry codes and standards.

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 5

International Nuclear Information System (INIS)

1994-04-01

The Fire Protection functional area for the Hanford Site Tank Farm facilities and support structures is based on the application of relevant DOE orders, regulations, and industry codes and standards. The fire protection program defined in this document may be divided into three areas: (1) organizational, (2) administrative programmatic features, and (3) technical features. The information presented in each section is in the form of program elements and orders, regulations, industry codes, and standards that serve as the attributes of a fire protection program for the Tank Farm facilities. Upon completion this document will be utilized as the basis to evaluate compliance of the fire protection program being implemented for the Tank Farm facilities with the requirements of DOE orders and industry codes and standards

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

International Nuclear Information System (INIS)

Garrison, R.C.

1995-01-01

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

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

Science.gov (United States)

1980-01-01

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

Repository-based software engineering program: Concept document

Science.gov (United States)

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.

50 CFR 23.53 - What are the requirements for obtaining a retrospective CITES document?

Science.gov (United States)

2010-10-01

... retrospective CITES document? 23.53 Section 23.53 Wildlife and Fisheries UNITED STATES FISH AND WILDLIFE SERVICE... ENDANGERED SPECIES OF WILD FAUNA AND FLORA (CITES) Application Procedures, Criteria, and Conditions § 23.53 What are the requirements for obtaining a retrospective CITES document? (a) Purpose. Retrospective...

Functional requirements of road lighting.

NARCIS (Netherlands)

Schreuder, D.A.

1975-01-01

The functional, technical and visual requirements for public lighting are discussed. The improvement of the presentation of information to the road user is the main functional requirement. The visual requirements can be deduced from the functional requirement of enabling drivers to follow the

High-level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID), Volume 4

Energy Technology Data Exchange (ETDEWEB)

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Identification Document (S/RID) is contained in multiple volumes. This document (Volume 4) presents the standards and requirements for the following sections: Radiation Protection and Operations.

High-level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID), Volume 4

International Nuclear Information System (INIS)

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Identification Document (S/RID) is contained in multiple volumes. This document (Volume 4) presents the standards and requirements for the following sections: Radiation Protection and Operations

Monitored Geologic Repository Project Description Document

International Nuclear Information System (INIS)

Curry, P. M.

2001-01-01

The primary objective of the Monitored Geologic Repository Project Description Document (PDD) is to allocate the functions, requirements, and assumptions to the systems at Level 5 of the Civilian Radioactive Waste Management System (CRWMS) architecture identified in Section 4. It provides traceability of the requirements to those contained in Section 3 of the ''Monitored Geologic Repository Requirements Document'' (MGR RD) (YMP 2000a) and other higher-level requirements documents. In addition, the PDD allocates design related assumptions to work products of non-design organizations. The document provides Monitored Geologic Repository (MGR) technical requirements in support of design and performance assessment in preparing for the Site Recommendation (SR) and License Application (LA) milestones. The technical requirements documented in the PDD are to be captured in the System Description Documents (SDDs) which address each of the systems at Level 5 of the CRWMS architecture. The design engineers obtain the technical requirements from the SDDs and by reference from the SDDs to the PDD. The design organizations and other organizations will obtain design related assumptions directly from the PDD. These organizations may establish additional assumptions for their individual activities, but such assumptions are not to conflict with the assumptions in the PDD. The PDD will serve as the primary link between the technical requirements captured in the SDDs and the design requirements captured in US Department of Energy (DOE) documents. The approved PDD is placed under Level 3 baseline control by the CRWMS Management and Operating Contractor (M and O) and the following portions of the PDD constitute the Technical Design Baseline for the MGR: the design characteristics listed in Table 1-1, the MGR Architecture (Section 4.1), the Technical Requirements (Section 5), and the Controlled Project Assumptions (Section 6)

High-level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID), Volume 5

International Nuclear Information System (INIS)

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Identification Document (S/RID) is contained in multiple volumes. This document (Volume 5) outlines the standards and requirements for the Fire Protection and Packaging and Transportation sections

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

International Nuclear Information System (INIS)

ROOT, R.W.

1999-01-01

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

NRC review of Electric Power Research Institute's Advanced Light Reactor Utility Requirements Document - Program summary, Project No. 669

International Nuclear Information System (INIS)

1992-08-01

The staff of the US Nuclear Regulatory Commission has prepared Volume 1 of a safety evaluation report (SER), ''NRC Review of Electric Power Research Institute's Advanced Light Water Reactor Utility Requirements Document -- Program Summary,'' to document the results of its review of the Electric Power Research Institute's ''Advanced Light Water Reactor Utility Requirements Document.'' This SER provides a discussion of the overall purpose and scope of the Requirements Document, the background of the staff's review, the review approach used by the staff, and a summary of the policy and technical issues raised by the staff during its review

Functional Requirements for Onboard Management of Space Shuttle Consumables. Volume 2

Science.gov (United States)

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

1973-01-01

This report documents the results of the study "Functional Requirements for Onboard Management of Space Shuttle Consumables." The study was conducted for the Mission Planning and Analysis Division of the NASA Lyndon B. Johnson Space Center, Houston, Texas, between 3 July 1972 and 16 November 1973. The overall study program objective was two-fold. The first objective was to define a generalized consumable management concept which is applicable to advanced spacecraft. The second objective was to develop a specific consumables management concept for the Space Shuttle vehicle and to generate the functional requirements for the onboard portion of that concept. Consumables management is the process of controlling or influencing the usage of expendable materials involved in vehicle subsystem operation. The report consists of two volumes. Volume I presents a description of the study activities related to general approaches for developing consumable management, concepts for advanced spacecraft applications, and functional requirements for a Shuttle consumables management concept. Volume II presents a detailed description of the onboard consumables management concept proposed for use on the Space Shuttle.

High-level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID), Volume 2

International Nuclear Information System (INIS)

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Document (S/RID) is contained in multiple volumes. This document (Volume 2) presents the standards and requirements for the following sections: Quality Assurance, Training and Qualification, Emergency Planning and Preparedness, and Construction

High-level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID), Volume 2

Energy Technology Data Exchange (ETDEWEB)

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Document (S/RID) is contained in multiple volumes. This document (Volume 2) presents the standards and requirements for the following sections: Quality Assurance, Training and Qualification, Emergency Planning and Preparedness, and Construction.

Software requirements specification document for the AREST code development

International Nuclear Information System (INIS)

Engel, D.W.; McGrail, B.P.; Whitney, P.D.; Gray, W.J.; Williford, R.E.; White, M.D.; Eslinger, P.W.; Altenhofen, M.K.

1993-11-01

The Analysis of the Repository Source Term (AREST) computer code was selected in 1992 by the U.S. Department of Energy. The AREST code will be used to analyze the performance of an underground high level nuclear waste repository. The AREST code is being modified by the Pacific Northwest Laboratory (PNL) in order to evaluate the engineered barrier and waste package designs, model regulatory compliance, analyze sensitivities, and support total systems performance assessment modeling. The current version of the AREST code was developed to be a very useful tool for analyzing model uncertainties and sensitivities to input parameters. The code has also been used successfully in supplying source-terms that were used in a total systems performance assessment. The current version, however, has been found to be inadequate for the comparison and selection of a design for the waste package. This is due to the assumptions and simplifications made in the selection of the process and system models. Thus, the new version of the AREST code will be designed to focus on the details of the individual processes and implementation of more realistic models. This document describes the requirements of the new models that will be implemented. Included in this document is a section describing the near-field environmental conditions for this waste package modeling, description of the new process models that will be implemented, and a description of the computer requirements for the new version of the AREST code

Army Materiel Requirements Documents: Qualitative Analysis of Efficiency and Effectiveness

Science.gov (United States)

2013-06-01

focuses on the program’s time to execute their mission based off the MRDs/MCDs. We measure efficiency based on two BPP initiatives: (1) Build...definitions of each BPP initiative during our interviews. A poor rating indicates the requirement documents did not sufficiently support the program...in terms of efficiency and effectiveness according to BPP initiatives. For efficiency, we assign a qualitative measure based on SME responses across

High level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID), Volume 6

Energy Technology Data Exchange (ETDEWEB)

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Identification Document (S/RID) is contained in multiple volumes. This document (Volume 6) outlines the standards and requirements for the sections on: Environmental Restoration and Waste Management, Research and Development and Experimental Activities, and Nuclear Safety.

High level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID), Volume 6

International Nuclear Information System (INIS)

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Identification Document (S/RID) is contained in multiple volumes. This document (Volume 6) outlines the standards and requirements for the sections on: Environmental Restoration and Waste Management, Research and Development and Experimental Activities, and Nuclear Safety

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

Science.gov (United States)

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

23 CFR 420.111 - What are the documentation requirements for use of FHWA planning and research funds?

Science.gov (United States)

2010-04-01

... and Research Funds § 420.111 What are the documentation requirements for use of FHWA planning and... 23 Highways 1 2010-04-01 2010-04-01 false What are the documentation requirements for use of FHWA planning and research funds? 420.111 Section 420.111 Highways FEDERAL HIGHWAY ADMINISTRATION, DEPARTMENT OF...

Standards/requirements identification documents (S/RIDS)

International Nuclear Information System (INIS)

Beckman, W.H.; Alhadeff, N.

1994-01-01

This paper describes the Fernald Environmental Restoration Management Corporation's (FERMCO) Standards/Requirement Identification Documents (S/RIDs) Development Program, the unique process used to implement it, and the status of the program. We will also discuss the lessons learned as the development program was implemented. The Department of Energy (DOE) established the Fernald site to produce uranium metals for the nation's defense programs in 1953. In 1989, DOE suspended production and, in 1991, the mission of the site was formally changed to one of environmental cleanup and restoration. The site was renamed the Fernald Environmental Management Project (FEMP) to reflect this change. From its inception until November 1992, the site was managed under a Management and Operating contract. As a result in the change in mission, DOE awarded an Environmental Restoration Management Contract (ERMC), focusing on restoration. FERMCO assumed management of the site December 1, 1992. The joint DOE/FERMCO mission is to protect human health and the environment through the safe, early, and least-cost final clean-up of the site in compliance with all applicable regulations and commitments while addressing stakeholder concerns. DOE has managed nuclear facilities primarily through its oversight of Management and Operating contractors. These contractors were responsible for formulating, selecting, and administering standards controlling design, construction, operations, and maintenance. The DOE Operations Office Manager was responsible for approving individual contractor practices and the governing site standards and requirements to be met. Due to the absence of comprehensive nuclear industry standards when most DOE sites were first established, Management and Operating contractors had to apply existing non-nuclear industry standards and, in many cases, formulate new technical standards to address unique applications

Making project documentation a positive tool for management

International Nuclear Information System (INIS)

Shirley, C.G.

1986-01-01

Sandia National Laboratories is constructing Particle Beam Fusion Accelerator II, a research facility built as a major project of the U.S. Department of Energy and theoretically capable of controlled nuclear fusion. To manage technical development, the project team has evolved a documentation system with both conventional and unconventional elements. Project documentation is functional because it is usable and authoritative. Usability results from layering by audience and purpose, appropriate sequence and format, accessibility, directness, and currency. Authority results from comprehensiveness, document control, insistence on written requirements, and consistency in applying procedures. As basic communication models illustrate, every document needs a producer, a recipient, a subject, and a feedback path. Managers can promote functional documentation by planning for feedback, using fulltime documentors wisely, setting priorities, planning for effective data collection, and treating documentation as a subproject

50 CFR 23.20 - What CITES documents are required for international trade?

Science.gov (United States)

2010-10-01

... international trade? 23.20 Section 23.20 Wildlife and Fisheries UNITED STATES FISH AND WILDLIFE SERVICE..., EXPORTATION, AND IMPORTATION OF WILDLIFE AND PLANTS (CONTINUED) CONVENTION ON INTERNATIONAL TRADE IN... CITES documents are required for international trade? (a) Purpose. Articles III, IV, and V of the Treaty...

Determining if a change to a proposal requires additional NEPA documentation: the Smithsonian Solution; TOPICAL

International Nuclear Information System (INIS)

ECCLESTON, C.H.

1999-01-01

Proposed actions tend to evolve over time. Once National Environmental Policy Act (NEPA) documentation is completed, agencies are at risk that subsequent changes may not be adequately covered or that existing NEPA documentation maybe completely invalidated. Neither NEPA nor its subsequent regulations provide sufficient direction for determining the degree to which a proposed action may change before preparation of new or supplemental documentation is necessary. Yet, decisionmakers are routinely involved in determining if a change to a proposed action departs, to such an extent, from the description presented in the NEPA document that additional documentation is necessary. Experience demonstrates that no two decisionmakers will completely agree, one decisionmaker might believe that a particular change would not require additional documentation, while the other concludes the exact opposite. Lacking definitive direction, decisionmakers and critics alike may point to a universe of potential considerations as the basis for defending their claim that a change in an action does or does not require new or additional NEPA documentation. Assertions are often based on equivocal opinions that can be neither proved nor disproved. Moreover, decisionmakers are frequently placed in an arduous dilemma of justifying a decision, for which there is no generally accepted methodology on which to base the decision. Lack of definitive direction can prolong the decisionmaking process, resulting in project delays. This can also lead to inappropriate levels of NEPA documentation, inconsistencies in decisionmaking, and increased risk of a legal challenge because of insufficient documentation. Clearly, a more systematic and less subjective approach is needed, A tool for streamlining the NEPA process, by reducing this degree of subjectivity, is presented in this paper

Functions and Requirements for West Valley Demonstration Project Tank Lay-up

International Nuclear Information System (INIS)

Elmore, Monte R.; Henderson, Colin

2002-01-01

Documents completion of Milestone A.1-1, ''Issue Functions and Requirements for WVDP Tank Lay-Up,'' in Technical Task Plan TTP RL3-WT21A - ''Post-Retrieval and Pre-Closure HLW Tank Lay-Up.'' This task is a collaborative effort among Pacific Northwest National Laboratory, Jacobs Engineering Group Inc., and West Valley Nuclear Services (WVNS). Because of the site-specific nature of this task, the involvement of WVNS personnel is critical to the success of this task

Cold Pump Test and Training and Mock-Up Facility Functions and Requirements

International Nuclear Information System (INIS)

BELLOMY, J.R.

2000-01-01

This document defines the functions and requirements (F and R) for a test facility to provide for pre-deployment, checkout, testing, and training for the underground storage tank retrieval equipment, systems, and crews that will be developed or deployed as part of Waste Feed Delivery. The F and R for a River Protection Project retrieval test facility, one that supports a production mode tank farm system, are identified

Electronic document management meets environmental restoration recordkeeping requirements: A case study

International Nuclear Information System (INIS)

Burnham, S.L.

1995-01-01

Efforts at migrating records management at five Department of Energy sites operated under management by Lockheed Martin Energy Systems, Inc. for Environmental Restoration (ER) business activities are described. The corporate environment, project definition, records keeping requirements are described first. Then an evaluation of electronic document management technologies and of internal and commercially available systems are provided. Finally adopted incremental implementation strategy and lessons learned are discussed

Report on task 4.1.3. - Survey of anticipated functional requirement for operator support systems

International Nuclear Information System (INIS)

Silvani, V.

1993-01-01

This is a preliminary report summarizing some topics related to the surveillance activity on anticipated functional requirements of the Operator Support Systems (OSS's) in NPP's. Additional information are expected will be available by analyzing the questionnaire. Functionalities examined are those referring to system functions, user's needs, technology trend, standard status. For practical purposes this document is divided in two main sections: the first section presents a summary of major OSS requirements and related problems as derived from the existing literature; the second section presents a study of OSS to be used to support the operator training presently under development in ENEA. Finally, appendix 2 reports a summary of major functions performed by the OSS's presently in operation or under development in laboratories. Refs, 1 tab

NWTS program criteria for mined geologic disposal of nuclear waste: program objectives, functional requirements, and system performance criteria

International Nuclear Information System (INIS)

1982-03-01

The NWTS-33 series, of which this document is a part, provides guidance for the National Waste Terminal Storage (NWTS) program in the development and implementation of licensed mined geologic disposal systems for solidified high-level and TRU wastes. Program objectives, functional requirements, and system performance criteria are found in this document. At the present time final criteria have not been issued by the Nuclear Regulatory Commission (NRC) and Environmental Protection Agency (EPA). The criteria in these documents have been developed on the basis of DOE's judgment of what is required to protect the health and safety of the public and the quality of the environment. It is expected that these criteria will be consistent with regulatory standards. The criteria will be re-evaluated on a periodic basis to ensure that they remain consistent with national waste management policy and regulatory requirements. A re-evaluation will be made when final criteria are promulgated by the NRC and EPA. A background section that briefly describes the mined geologic disposal system and explains the hierarchy and application of the NWTS criteria is included in Section 2.0. Secton 3.0 presents the program objectives, Section 4.0 functional requirements, Secton 5.0 the system performance criteria, and Section 6.0 quality assurance and standards. A draft of this document was issued for public comment in April 1981. Appendix A contains the DOE responses to the comments received. Appendix B is a glossary

Integrity Based Access Control Model for Multilevel XML Document

Institute of Scientific and Technical Information of China (English)

HONG Fan; FENG Xue-bin; HUANO Zhi; ZHENG Ming-hui

2008-01-01

XML's increasing popularity highlights the security demand for XML documents. A mandatory access control model for XML document is presented on the basis of investigation of the function dependency of XML documents and discussion of the integrity properties of multilevel XML document. Then, the algorithms for decomposition/recovery multilevel XML document into/from single level document are given, and the manipulation rules for typical operations of XQuery and XUpdate: QUERY, INSERT,UPDATE, and REMOVE, are elaborated. The multilevel XML document access model can meet the requirement of sensitive information processing application.

Guidance for preparing user requirements documents for small and medium reactors and their application

International Nuclear Information System (INIS)

2000-08-01

During the past decade, several countries with highly developed nuclear power programs established user required documents (URDs) to guide the development and implementation of advanced light water reactors. These efforts built upon the extensive experience with operating reactors and included new insights from ongoing research and development to enhance the economic performance and safety of future nuclear power plants. Subsequently, a number of developing countries with plans for introducing nuclear energy into their national programs expressed strong interest in establishing analogous requirements. The IAEA has therefore taken the initiative to assist in the elaboration of such requirements. Building upon relevant documents this report recommends a URD structure and content outline to support developing countries in preparing their URDs for various applications of small and medium reactors (e.g. electricity generation and/or desalination). This report was prepared by representatives from both developing and developed Member States

Determination of Waste Isolation Pilot Plant (WIPP) management and institutional requirements documents for contact-handled (CH) critical systems

International Nuclear Information System (INIS)

1990-01-01

This document lists the critical requirements documents applicable to the receipt of contact-handled waste at the Waste Isolation Pilot Plant. It also describes the processes used to determine the applicability of each document. This analysis is based on the applicable documents that were in effect in the February 1988 time frame. 2 refs

10-MWe pilot-plant-receiver panel test requirements document solar thermal test facility

Energy Technology Data Exchange (ETDEWEB)

1978-08-25

Testing plans for a full-scale test receiver panel and supporting hardware which essentially duplicate both physically and functionally, the design planned for the Barstow Solar Pilot Plant are presented. Testing is to include operation during normal start and shutdown, intermittent cloud conditions, and emergencies to determine the panel's transient and steady state operating characteristics and performance under conditions equal to or exceeding those expected in the pilot plant. The effects of variations of input and output conditions on receiver operation are also to be investigated. Test hardware are described, including the pilot plant receiver, the test receiver assembly, receiver panel, flow control, electrical control and instrumentation, and structural assembly. Requirements for the Solar Thermal Test Facility for the tests are given. The safety of the system is briefly discussed, and procedures are described for assembly, installation, checkout, normal and abnormal operations, maintenance, removal and disposition. Also briefly discussed are quality assurance, contract responsibilities, and test documentation. (LEW)

Waste Management System Requirements Document

International Nuclear Information System (INIS)

1992-02-01

This DCP establishes an interim plan for the Office of Civilian Radioactive Waste Management (OCRWM) technical baseline until the results of the OCRWM Document Hierarchy Task Force can be implemented. This plan is needed to maintain continuity in the Program for ongoing work in the areas of Waste Acceptance, Transportation, Monitored Retrievable Storage (MRS) and Yucca Mountain Site Characterization

High-level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID), Volume 7. Revision 1

Energy Technology Data Exchange (ETDEWEB)

Burt, D.L.

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Identification Document (S/RID) is contained in multiple volumes. This document (Volume 7) presents the standards and requirements for the following sections: Occupational Safety and Health, and Environmental Protection.

High-level waste storage tank farms/242-A evaporator Standards/Requirements Identification Document (S/RID), Volume 7. Revision 1

International Nuclear Information System (INIS)

Burt, D.L.

1994-04-01

The High-Level Waste Storage Tank Farms/242-A Evaporator Standards/Requirements Identification Document (S/RID) is contained in multiple volumes. This document (Volume 7) presents the standards and requirements for the following sections: Occupational Safety and Health, and Environmental Protection

Monitored Geologic Repository Project Description Document

International Nuclear Information System (INIS)

Curry, P.

2000-01-01

The primary objective of the Monitored Geologic Repository Project Description Document (PDD) is to allocate the functions, requirements, and assumptions to the systems at Level 5 of the Civilian Radioactive Waste Management System (CRWMS) architecture identified in Section 4. It provides traceability of the requirements to those contained in Section 3 of the ''Monitored Geologic Repository Requirements Document'' (MGR RD) (CRWMS M and O 2000b) and other higher-level requirements documents. In addition, the PDD allocates design related assumptions to work products of non-design organizations. The document provides Monitored Geologic Repository (MGR) engineering design basis in support of design and performance assessment in preparing for the Site Recommendation (SR) and License Application (LA) milestones. The engineering design basis documented in the PDD is to be captured in the System Description Documents (SDDs) which address each of the systems at Level 5 of the CRWMS architecture. The design engineers obtain the engineering design basis from the SDDs and by reference from the SDDs to the PDD. The design organizations and other organizations will obtain design related assumptions directly from the PDD. These organizations may establish additional assumptions for their individual activities, but such assumptions are not to conflict with the assumptions in the PDD. The PDD will serve as the primary link between the engineering design basis captured in the SDDs and the design requirements captured in U.S. Department of Energy (DOE) documents. The approved PDD is placed under Level 3 baseline control by the CRWMS Management and Operating Contractor (M and O) and the following portions of the PDD constitute the Technical Design Baseline for the MGR: the design characteristics listed in Table 2-1, the MGR Architecture (Section 4.1),the Engineering Design Bases (Section 5), and the Controlled Project Assumptions (Section 6)

Emergency Response Capability Baseline Needs Assessment - Requirements Document

Energy Technology Data Exchange (ETDEWEB)

Sharry, J A

2016-10-04

This document was prepared by John A. Sharry, LLNL Fire Marshal and LLNL Division Leader for Fire Protection and reviewed by LLNL Emergency Management Department Head James Colson. The document follows and expands upon the format and contents of the DOE Model Fire Protection Baseline Capabilities Assessment document contained on the DOE Fire Protection Web Site, but only addresses emergency response.

Space Station data system analysis/architecture study. Task 1: Functional requirements definition, DR-5

Science.gov (United States)

1985-01-01

The initial task in the Space Station Data System (SSDS) Analysis/Architecture Study is the definition of the functional and key performance requirements for the SSDS. The SSDS is the set of hardware and software, both on the ground and in space, that provides the basic data management services for Space Station customers and systems. The primary purpose of the requirements development activity was to provide a coordinated, documented requirements set as a basis for the system definition of the SSDS and for other subsequent study activities. These requirements should also prove useful to other Space Station activities in that they provide an indication of the scope of the information services and systems that will be needed in the Space Station program. The major results of the requirements development task are as follows: (1) identification of a conceptual topology and architecture for the end-to-end Space Station Information Systems (SSIS); (2) development of a complete set of functional requirements and design drivers for the SSIS; (3) development of functional requirements and key performance requirements for the Space Station Data System (SSDS); and (4) definition of an operating concept for the SSIS. The operating concept was developed both from a Space Station payload customer and operator perspective in order to allow a requirements practicality assessment.

Development of functional requirements for electronic health communication: preliminary results from the ELIN project.

Science.gov (United States)

Christensen, Tom; Grimsmo, Anders

2005-01-01

User participation is important for developing a functional requirements specification for electronic communication. General practitioners and practising specialists, however, often work in small practices without the resources to develop and present their requirements. It was necessary to find a method that could engage practising doctors in order to promote their needs related to electronic communication. Qualitative research methods were used, starting a process to develop and study documents and collect data from meetings in project groups. Triangulation was used, in that the participants were organised into a panel of experts, a user group, a supplier group and an editorial committee. The panel of experts created a list of functional requirements for electronic communication in health care, consisting of 197 requirements, in addition to 67 requirements selected from an existing Norwegian standard for electronic patient records (EPRs). Elimination of paper copies sent in parallel with electronic messages, optimal workflow, a common electronic 'envelope' with directory services for units and end-users, and defined requirements for content with the possibility of decision support were the most important requirements. The results indicate that we have found a method of developing functional requirements which provides valid results both for practising doctors and for suppliers of EPR systems.

Environmental restoration value engineering guidance document

International Nuclear Information System (INIS)

1995-07-01

This document provides guidance on Value Engineering (VE). VE is an organized team effort led by a person trained in the methodology to analyze the functions of projects, systems, equipment, facilities, services, and processes for achieving the essential functions at the lowest life cycle cost while maintaining required performance, reliability, availability, quality, and safety. VE has proven to be a superior tool to improve up-front project planning, cut costs, and create a better value for each dollar spent. This document forms the basis for the Environmental Restoration VE Program, describes the VE process, and provides recommendations on when it can be most useful on ER projects

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 7

Energy Technology Data Exchange (ETDEWEB)

1994-04-01

This Requirements Identification Document (RID) describes an Occupational Health and Safety Program as defined through the Relevant DOE Orders, regulations, industry codes/standards, industry guidance documents and, as appropriate, good industry practice. The definition of an Occupational Health and Safety Program as specified by this document is intended to address Defense Nuclear Facilities Safety Board Recommendations 90-2 and 91-1, which call for the strengthening of DOE complex activities through the identification and application of relevant standards which supplement or exceed requirements mandated by DOE Orders. This RID applies to the activities, personnel, structures, systems, components, and programs involved in maintaining the facility and executing the mission of the High-Level Waste Storage Tank Farms.

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 7

International Nuclear Information System (INIS)

1994-04-01

This Requirements Identification Document (RID) describes an Occupational Health and Safety Program as defined through the Relevant DOE Orders, regulations, industry codes/standards, industry guidance documents and, as appropriate, good industry practice. The definition of an Occupational Health and Safety Program as specified by this document is intended to address Defense Nuclear Facilities Safety Board Recommendations 90-2 and 91-1, which call for the strengthening of DOE complex activities through the identification and application of relevant standards which supplement or exceed requirements mandated by DOE Orders. This RID applies to the activities, personnel, structures, systems, components, and programs involved in maintaining the facility and executing the mission of the High-Level Waste Storage Tank Farms

20 CFR 669.660 - What planning documents and information are required in the application for MSFW youth grants and...

Science.gov (United States)

2010-04-01

... 20 Employees' Benefits 3 2010-04-01 2010-04-01 false What planning documents and information are... PROGRAM UNDER TITLE I OF THE WORKFORCE INVESTMENT ACT The MSFW Youth Program § 669.660 What planning...? The required planning documents and other required information and the submission dates for filing are...

NRC review of Electric Power Research Institute's Advanced Light Water Reactor Utility Requirements Document - Evolutionary plant designs, Chapter 1, Project No. 669

International Nuclear Information System (INIS)

1992-08-01

The staff of the US Nuclear Regulatory Commission has prepared Volume 2 (Parts 1 and 2) of a safety evaluation report (SER), ''NRC Review of Electric Power Research Institute's Advanced Light Water Reactor Utility Requirements Document -- Evolutionary Plant Designs,'' to document the results of its review of the Electric Power Research Institute's ''Advanced Light Water Reactor Utility Requirements Document.'' This SER gives the results of the staff's review of Volume II of the Requirements Document for evolutionary plant designs, which consists of 13 chapters and contains utility design requirements for an evolutionary nuclear power plant (approximately 1300 megawatts-electric)

Non-functional Avionics Requirements

Science.gov (United States)

Paulitsch, Michael; Ruess, Harald; Sorea, Maria

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

International standards to document remaining autonomic function after spinal cord injury

DEFF Research Database (Denmark)

Krassioukov, Andrei; Biering-Sørensen, Fin; Donovan, William

2012-01-01

This is the first guideline describing the International Standards to document remaining Autonomic Function after Spinal Cord Injury (ISAFSCI). This guideline should be used as an adjunct to the International Standards for Neurological Classification of Spinal Cord Injury (ISNCSCI) including the ...

A documentation system for decommissioning of nuclear power plants

International Nuclear Information System (INIS)

Glock, H.J.; Mueller, F.; Schwarz, H.

1984-01-01

A NPP's life cycle from the beginning of planning to its complete dismantling will last about 80 to 100 years. For this long time a documentation system has to be kept in stable working condition which provides access to an information base including 1.5 to 2 million pages and 200 to 250 thousand engineering drawings. As an appropriate base the documentation system IFODOK is proposed which is supported by computer and data base management software. In cooperation with NPP operating people a ground level thesaurus has been developed which is structured according to the rules of INFODOK's documentation language. The form of the information units which INFODOK maintains has been adapted to the requirements of KKW documentation and the related data record is described. Within a layer model the requirements to the software resulting from the demanded performance of the system are explained. The model also describes the interfaces between the substantial system components (application programs, data base management system, operating system) as well as within the different layers. The requirements which the system's hardware has to meet are described functionally and quantitatively in details. The application program' components have been extended by some functions. An automatic microfilm storage and retrieval system which may be integrated to the overall system and coupled to the computer by an interface is specified. The organization of the computer assisted documentation process including the required backup and refreshment procedures is described in its basic characteristics. This description of an DP system's prototype presents the base for the application of INFODOK to the documentation of NPP's information bases during their whole life time

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

Science.gov (United States)

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

47 CFR 80.1081 - Functional requirements.

Science.gov (United States)

2010-10-01

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

I-15 integrated corridor management : system requirements.

Science.gov (United States)

2011-07-01

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

NRC review of Electric Power Research Institute's Advanced Light Water Reactor Utility Requirements Document - Evolutionary plant designs, Chapters 2--13, Project No. 669

International Nuclear Information System (INIS)

1992-08-01

The staff of the US Nuclear Regulatory Commission has prepared Volume 2 (Parts 1 and 2) of a safety evaluation report (SER), ''NRC Review of Electric Power Research Institute's Advanced Light Water Reactor Utility Requirements Document -- Evolutionary Plant Designs,'' to document the results of its review of the Electric Power Research Institute's ''Advanced Light Water Reactor Utility Requirements Document.'' This SER gives the results of the staff's review of Volume II of the Requirements Document for evolutionary plant designs, which consists of 13 chapters and contains utility design requirements for an evolutionary nuclear power plant (approximately 1300 megawatts-electric)

Operator-centered technical documentation of the power plant control system. Betreibergerechte, betriebstechnische Dokumentation der Kraftwerks-Leittechnik

Energy Technology Data Exchange (ETDEWEB)

Welfonder, E

1986-01-01

The report - starting with an overview of the general structure of documentation - includes in chapter 3 an assortment of the main expectations to be had by the technical staff towards control system documentation. These are divided into: general basic requirements; testable compulsory requirements; practical recommendations and information for the manufacturer. In chapter 4 these documentation requirements are reflected to the present state of technical documentation. The main emphasis of the report however is laid on the sample documentation for one control system area presented in chapter 5. This sample documentation is based on a hierarchically structured and function related documentary method developed by the University of Stuttgart on the basis of the derived requirements and the present usual control system documentation. This function-related documentary method proves to be useful, not only for the technical staff in his rapid search for control system disturbances, but also offers - due to its clear and homogeneous meshed structure - considerable advantages for control system planning, projecting and initial start ups. As the presented documentation method is furthermore independent of the control system manufacturers, it is important that all participants try to use it uniformly.

Instructions for submittal and control of FFTF design documents and design related documentation

International Nuclear Information System (INIS)

Grush, R.E.

1976-10-01

This document provides the system and requirements for management of FFTF technical data prepared by Westinghouse Hanford (HEDL), and design contractors, the construction contractor and lower tier equipment suppliers. Included in this document are provisions for the review, approval, release, change control, and accounting of FFTF design disclosure and base documentation. Also included are provisions for submittal of other design related documents for review and approval consistent with applicable requirements of RDT-Standard F 2-2, ''Quality Assurance Program Requirements.''

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

Science.gov (United States)

2005-01-01

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

A study to develop the domestic functional requirements of the specific safety systems of CANDU

Energy Technology Data Exchange (ETDEWEB)

Kim, Man Woong [Korea Institute of Nuclear Safety, Taejon (Korea, Republic of); Lee, Jae Young; Park, Kun Chul [Handong Global Univ., Pohang (Korea, Republic of)] (and others)

2003-03-15

The present research has been made to develop and review critically the functional requirements of the specific safety systems of CANDU such as SDS-1, SDS2, ECCS, and containment. Based on R documents for this, a systematic study was made to develop the domestic regulation statements. Also, the conventional laws are carefully reviewed to see the compatibility to CANDU. Also, the safety assessment method for CANDU was studied by reviewing C documents and recommendation of IAEA. Through the present works, the vague policy in the CANDU safety regulation is cleaning up in a systematic form and a new frame to measure the objective risk of nuclear power plants was developed.

A study to develop the domestic functional requirements of the specific safety systems of CANDU

Energy Technology Data Exchange (ETDEWEB)

Kim, Man Woong; Lee, Jae Young; Bang, Kwang Hyun [Handong Global Univ., Pohang (Korea, Republic of)] (and others)

2001-03-15

The present research has been made to develop and review critically the functional requirements of the specific safety systems of CANDU such as SOS-1, SOS-2, ECCS and containment. Based on R documents for this, a systematic study was made to develop the domestic regulation statements. Also, the conventional laws are carefully reviewed to see the compatibility to CANDU. Also, the safety assessment method for CANDU was studied by reviewing C documents and recommendation of IAEA. Through the present works, the vague policy in the CANDU safety regulation is cleaning up in a systematic form and a new frame to measure the objective risk of nuclear power plants was developed.

Functional Requirement Analysis and Function Allocation for APR 1400

International Nuclear Information System (INIS)

Nuraslinda, Anuar; Florah, Kamanja; Noloyiso, Mtoko and others

2013-01-01

This paper intends to fulfill the FRA and FA of the HFE as required in Chapter 4 of NUREG-0711 rev. 3 for APR1400 to satisfy both plant safety and power generation objectives. This paper aims to evaluate the FRA and FA for APR1400. The allocation of function is done at the system level for all processes for both the power generation and safety goals, following the NUREG/CR-3331 guideline. As a conclusion, this paper has successfully implemented the requirements and methodology specified in NUREG-0711 for APR 1400. The Functional Requirement Analysis (FRA) and Function Allocation (FA) are required by the regulation in the Human Factors Engineering (HFE) program. The FRA defines the functions, processes, and system for plant safety and power generation. The FA allocates the functions to human operator, automation, or a combination of two. The FRA and FA for APR1400 have been performed in the very early stage of development but only for the plant safety. However, the analysis did not include the goal of power generation and also did not fully satisfy the latest revision of NUREG-0711

Are functional foods redefining nutritional requirements?

Science.gov (United States)

Jones, Peter J; Varady, Krista A

2008-02-01

Functional foods are increasing in popularity owing to their ability to confer health and physiological benefits. Nevertheless, the notion that functional foods improve health when providing nutrients at levels above and beyond existing recommended intakes is inconsistent with the definition of requirement. This disparity highlights the need for an alternative definition of nutrient requirement. The present objective is to examine distinctions between optimization of health, as defined by what we currently deem as required intakes, versus adding physiological benefit using bioactive agents found in functional foods. Presently, requirement is defined as the lowest amount of intake of a nutrient that will maintain a defined level of nourishment for a specific indicator of adequacy. In contrast, functional foods are described as ingredients that are not necessary for body function, yet provide added physiological benefit that confer better overall health. Plant sterols are one example of such an ingredient. Plant sterols lower plasma cholesterol concentrations, and may thus be considered essential nutrients in physiological situations where circulating cholesterol concentrations are high. Similarly, intakes of omega-3 fats beyond existing requirement may confer additional health benefits such as hypolipidemic and anti-diabetic effects. These examples underscore the inconsistencies between what is defined as a nutrient requirement versus what is identified as a health benefit of a functional food. Such discrepancies emphasize the need for a more all-encompassing definition of a nutrient requirement; that is, one that moves beyond the prevention of overt deficiency to encompass improved health and disease risk reduction.

Towards the Proper Integration of Extra-Functional Requirements

Directory of Open Access Journals (Sweden)

Elke Hochmuller

1999-05-01

Full Text Available In spite of the many achievements in software engineering, proper treatment of extra-functional requirements (also known as non-functional requirements within the software development process is still a challenge to our discipline. The application of functionality-biased software development methodologies can lead to major contradictions in the joint modelling of functional and extra-functional requirements. Based on a thorough discussion on the nature of extra-functional requirements as well as on open issues in coping with them, this paper emphasizes the role of extra-functional requirements in the software development process. Particularly, a framework supporting the explicit integration of extra functional requirements into a conventional phase-driven process model is proposed and outlined.

SRS control system upgrade requirements

International Nuclear Information System (INIS)

Hill, L.F.

1998-01-01

This document defines requirements for an upgrade of the Sodium Removal System (SRS) control system. The upgrade is being performed to solve a number of maintainability and operability issues. The upgraded system will provide the same functions, controls and interlocks as the present system, and in addition provide enhanced functionality in areas discussed in this document

50 CFR 23.18 - What CITES documents are required to export Appendix-I wildlife?

Science.gov (United States)

2010-10-01

... 50 Wildlife and Fisheries 6 2010-10-01 2010-10-01 false What CITES documents are required to export Appendix-I wildlife? 23.18 Section 23.18 Wildlife and Fisheries UNITED STATES FISH AND WILDLIFE..., EXPORTATION, AND IMPORTATION OF WILDLIFE AND PLANTS (CONTINUED) CONVENTION ON INTERNATIONAL TRADE IN...

1 CFR 5.2 - Documents required to be filed for public inspection and published.

Science.gov (United States)

2010-01-01

... inspection and published. 5.2 Section 5.2 General Provisions ADMINISTRATIVE COMMITTEE OF THE FEDERAL REGISTER THE FEDERAL REGISTER GENERAL § 5.2 Documents required to be filed for public inspection and published... Register and published in the Federal Register: (a) Presidential proclamations and Executive orders in the...

Towards the Proper Integration of Extra-Functional Requirements

OpenAIRE

Elke Hochmuller

1999-01-01

In spite of the many achievements in software engineering, proper treatment of extra-functional requirements (also known as non-functional requirements) within the software development process is still a challenge to our discipline. The application of functionality-biased software development methodologies can lead to major contradictions in the joint modelling of functional and extra-functional requirements. Based on a thorough discussion on the nature of extra-functional requirements as wel...

Design basis document open-item resolution and reportability

International Nuclear Information System (INIS)

Gambhir, S.K.; Livingston, B.R.; Purcell, J.J.; Erickson, E.A.

1989-01-01

In the process of reconstituting the design bases for older nuclear power plants, information or references may not be available to fully define the design requirements or to document and verify the adequacy of the design. Also, information that is in conflict with other data is identified. The missing and conflicting information must be reconstituted in order to adequately document the design bases of the plant. For these operating facilities, the identification, tracking, and resolution of missing or conflicting information is very important when the reporting requirements stipulated by 10CFR21, 10CFR50.72, and 10CFR50.73 are considered. Additionally, controlled documentation (calculations, drawings, etc.) used to develop the design basis documents may contain conflicting data. In some cases, conflicts between the as-built design and licensing or design basis requirements established in specific commitments to the U.S. Nuclear Regulatory Commission may be identified. Furthermore, concerns regarding the adequacy of safety-related systems or components to perform their required function may be identified that would warrant prompt action by the licensee. The approach discussed in this paper was used by Omaha Public Power District for the ongoing design basis reconstitution effort at the Fort Calhoun nuclear plant

Documentation: Records and Reports.

Science.gov (United States)

Akers, Michael J

2017-01-01

This article deals with documentation to include the beginning of documentation, the requirements of Good Manufacturing Practice reports and records, and the steps that can be taken to minimize Good Manufacturing Practice documentation problems. It is important to remember that documentation for 503a compounding involves the Formulation Record, Compounding Record, Standard Operating Procedures, Safety Data Sheets, etc. For 503b outsourcing facilities, compliance with Current Good Manufacturing Practices is required, so this article is applicable to them. For 503a pharmacies, one can see the development and modification of Good Manufacturing Practice and even observe changes as they are occurring in 503a documentation requirements and anticipate that changes will probably continue to occur. Copyright© by International Journal of Pharmaceutical Compounding, Inc.

Light Duty Utility Arm interface control document plan

Energy Technology Data Exchange (ETDEWEB)

Engstrom, J.W.

1994-12-27

This document describes the interface control documents that will be used to identify and control interface features throughout all phases of the Light Duty Utility Arm (LDUA) development and design. After the system is built, delivered and installed in the Cold Test Facility and later at the tank farm, the Interface Control Documents can be used in maintaining the configuration control process. The Interface Control Document will consist of Interface Control Drawings and a data base directly tied to the Interface Control Drawings. The data base can be used as an index to conveniently find interface information. Design drawings and other text documents that contain interface information will appear in the database. The Interface Control Drawings will be used to document and control the data and information that define the interface boundaries between systems, subsystems and equipment. Also, the interface boundaries will define the areas of responsibility for systems and subsystems. The drawing will delineate and identify all the physical and functional interfaces that required coordination to establish and maintain compatibility between the co-functioning equipment, computer software, and the tank farm facilities. An appendix contains the Engineering interface control database system riser manual.

Light Duty Utility Arm interface control document plan

International Nuclear Information System (INIS)

Engstrom, J.W.

1994-01-01

This document describes the interface control documents that will be used to identify and control interface features throughout all phases of the Light Duty Utility Arm (LDUA) development and design. After the system is built, delivered and installed in the Cold Test Facility and later at the tank farm, the Interface Control Documents can be used in maintaining the configuration control process. The Interface Control Document will consist of Interface Control Drawings and a data base directly tied to the Interface Control Drawings. The data base can be used as an index to conveniently find interface information. Design drawings and other text documents that contain interface information will appear in the database. The Interface Control Drawings will be used to document and control the data and information that define the interface boundaries between systems, subsystems and equipment. Also, the interface boundaries will define the areas of responsibility for systems and subsystems. The drawing will delineate and identify all the physical and functional interfaces that required coordination to establish and maintain compatibility between the co-functioning equipment, computer software, and the tank farm facilities. An appendix contains the Engineering interface control database system riser manual

Criteria Document for B-plant's Surveillance and Maintenance Phase Safety Basis Document

International Nuclear Information System (INIS)

SCHWEHR, B.A.

1999-01-01

This document is required by the Project Hanford Managing Contractor (PHMC) procedure, HNF-PRO-705, Safety Basis Planning, Documentation, Review, and Approval. This document specifies the criteria that shall be in the B Plant surveillance and maintenance phase safety basis in order to obtain approval of the DOE-RL. This CD describes the criteria to be addressed in the S and M Phase safety basis for the deactivated Waste Fractionization Facility (B Plant) on the Hanford Site in Washington state. This criteria document describes: the document type and format that will be used for the S and M Phase safety basis, the requirements documents that will be invoked for the document development, the deactivated condition of the B Plant facility, and the scope of issues to be addressed in the S and M Phase safety basis document

Specifying Functional Requirements Dependency in the REWiki

OpenAIRE

ZHANG, ZHANG

2013-01-01

Most of the individual requirements cannot be treated in isolation. Requirements may affect each other in various ways. The dependency between requirements impacts a number of software development aspects and activities. How to classify and specify requirements dependency remains a classic research topic. This research aims at providing an approach of specifying functional requirements dependency. In this thesis we generalize a classification of functional requirements dependency. We also pro...

High-Level Functional and Operational Requirements for the Advanced Fuel Cycle Facility

International Nuclear Information System (INIS)

Charles Park

2006-01-01

This document describes the principal functional and operational requirements for the proposed Advanced Fuel Cycle Facility (AFCF). The AFCF is intended to be the world's foremost facility for nuclear fuel cycle research, technology development, and demonstration. The facility will also support the near-term mission to develop and demonstrate technology in support of fuel cycle needs identified by industry, and the long-term mission to retain and retain U.S. leadership in fuel cycle operations. The AFCF is essential to demonstrate a more proliferation-resistant fuel cycle and make long-term improvements in fuel cycle effectiveness, performance and economy

Applications for electronic documents

International Nuclear Information System (INIS)

Beitel, G.A.

1995-01-01

This paper discusses the application of electronic media to documents, specifically Safety Analysis Reports (SARs), prepared for Environmental Restoration and Waste Management (ER ampersand WM) programs being conducted for the Department of Energy (DOE) at the Idaho National Engineering Laboratory (INEL). Efforts are underway to upgrade our document system using electronic format. To satisfy external requirements (DOE, State, and Federal), ER ampersand WM programs generate a complement of internal requirements documents including a SAR and Technical Safety Requirements along with procedures and training materials. Of interest, is the volume of information and the difficulty in handling it. A recently prepared ER ampersand WM SAR consists of 1,000 pages of text and graphics; supporting references add 10,000 pages. Other programmatic requirements documents consist of an estimated 5,000 pages plus references

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

Energy Technology Data Exchange (ETDEWEB)

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

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

Science.gov (United States)

2014-01-01

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

Performance Requirements for the Double Shell Tank (DST) System

International Nuclear Information System (INIS)

SMITH, D.F.

2001-01-01

This document identifies the upper-level Double-Shell Tank (DST) System functions and bounds the associated performance requirements. The functions and requirements are provided along with supporting bases. These functions and requirements, in turn, will be incorporated into specifications for the DST System

Transient and accident analyses topical design basis documents

International Nuclear Information System (INIS)

Chi, Larry; Eckert, Eugene; Grim, Brit

2004-01-01

The designers and operators of nuclear power plants have extensively documented system functions, licensing performance, and operating procedures for all conditions. This paper presents a complementary, systematic approach for the documentation of all requirements that are based on the analysis of operational transients, abnormal transients, accidents, and other events which are included in the design and licensing basis for the plant. Up to now, application of the approach has focused on required mitigation actions (automatic or manual). All mitigation actions are directly identified with all applicable reactor events, as well as the plant-unique systems that work together to perform each function. The approach is also applicable to all operational functions. The approach makes extensive use of data base methods, thereby providing effective ways to interrogate the information for the varied users of this information. Examples of use include: evaluations of system design changes and equipment modifications, safety evaluations of any plant change (e.g., USNRC 10CFR50.59 review), plant operations (e.g., manual actions during unplanned events), system interactions, classification of safety-related equipment, environmental qualification of equipment, and mitigation requirements for different reactor operating states. This approach has been applied in customized ways to several boiling water reactor (BWR) units, based on the desires and needs of the specific utility. (author)

Requirements in Functional IT Management

NARCIS (Netherlands)

Blaauboer, F.A.; Blaauboer, F.A.

Requirements engineering and functional IT management have never been researched as to containing similar activities. This paper describes and compares both disciplines, where the BiSL-framework is used for functional IT management. The similarities and differences between the two disciplines are

Tabular map of bank mining in North Czech and photo-documentation

International Nuclear Information System (INIS)

Svec, J.; Jenista, J.

2003-01-01

Quarry coal mining in North Bohemian coal territory represents actual problem that resulted in destabilisation up to devastation of land. Mining activities represent total area about 300 square kilometres. It is documented by tabular map with photo-documentation. Anthropogenic land degradation requires restoration actions in land in this range that will return its stability and natural functions

A fully updated version of the European utility requirement (EUR) documents is to be available

International Nuclear Information System (INIS)

Chatry, J.P.; Berbey, P.

2001-01-01

The major European electricity producers have worked on a common requirement document for future LWR plants since 1992 to get specifications acceptable together by the owners, the public and the authorities. Thus the designers can develop standard LWR designs that could be acceptable everywhere in Europe and the utilities can open their consultations to vendors on common bases. Public and authority's acceptance should be improved as well. Significant savings are expected in development and construction costs. Since the release of the last versions of the EUR texts in 1996, a lot of work has been carried out: reviews by the regulators and other external organisations, comparisons, assessment of compliance of designs vs. EUR and clarification works on the controversial topics that deserved changes or clarification. At the beginning of 1999 enough material was available to start a complete revision of the EUR document. Volumes 1 and 2 of the EUR document list generic nuclear island requirements. The main NPP vendors are developing advanced LWR designs for the European market, with reference to the EUR document. Volume 3 deals with the application of EUR to those designs. The EUR utilities -with contributions of the vendors- are writing specific parts of the EUR document that address some of these designs. Each part includes a plant description and an assessment of its level of compliance with EUR. The first three parts deal with EPR (1500 MW PWR developed by NPI, Framatome and Siemens), EPP (1000 MW PWR with passive safety features developed by Westinghouse and Ansaldo) and BWR 90 (1300 MW BWR developed by ABB Atom). Two other subsets are: one for ABWR (1300 MW BWR developed by GE), the other one for SWR 1000 (1000 MW BWR with passive safety features developed by Siemens). This large and diverse set of designs actually gives the EUR document a very strong base. Revision B of Volume 4 incorporates responses to the comments collected on revision A. Considering all that

The control of documents maintained in the electronic media and the requirements of NBR ISO/IEC 17025 and adequacy for PNQ

Directory of Open Access Journals (Sweden)

Anselmo Ferreira de Castro

2006-01-01

Full Text Available During the assessments carried out by the authors at the diverse laboratories pertaining to the network of accredited laboratories - known as the Brazilian Calibration Network (RBC - the authors verified the difficulties that these laboratories had in meeting the requirements of NBR ISO/IEC 17025:2001 (Standard, related to the maintenance of documents in the electronic media. More and more laboratories are substituting traditional control with electronic document control, which allows for more agility in the recovery of information. These laboratories implement policies and procedures; however, they still feel insecure, in some way, as to how to meet all of these requirements, thereby giving rise to difficulties in the implementation of such. The aim of this paper is to discuss the control of documents stored in the electronic media, adopting requirement 4.3 of the Standard as the reference, and aiming, in this manner, to harmonize the assessment process of the procedures of document management in the electronic media, and to assist the laboratories in the interpretation of the Standard, so that they may implement systems that are adequate to their actual necessities and to their structural size, while at the same time complying with the referred to requirement. This work will not broach the treatment given to the records (requirement 4.12 of the Standard, facts (requirement 5.4.7 nor to the electronic transmission of results (requirement 5.10.7, leaving these subjects for posterior discussions.

National Ignition Facility system design requirements NIF integrated computer controls SDR004

International Nuclear Information System (INIS)

Bliss, E.

1996-01-01

This System Design Requirement document establishes the performance, design, development, and test requirements for the NIF Integrated Computer Control System. The Integrated Computer Control System (ICCS) is covered in NIF WBS element 1.5. This document responds directly to the requirements detailed in the NIF Functional Requirements/Primary Criteria, and is supported by subsystem design requirements documents for each major ICCS Subsystem

Functional requirements of the borrow area and haul route for the Waste Area Grouping projects at Oak Ridge National Laboratory, Oak Ridge, Tennessee

International Nuclear Information System (INIS)

Miller, D.G.

1992-09-01

This report describes the mission and functional requirements for the development of a borrow area and the associated haul route to support closure and/or remediation of Waste Area Grouping (WAG) 6 and other WAGs at Oak Ridge National Laboratory. This document specifies the basic functional requirements that must be met by the borrow area and haul route developed to produce low-permeability soil for the covers or caps at WAG 6

Spent Nuclear Fuel project stage and store K basin SNF in canister storage building functions and requirements. Revision 1

International Nuclear Information System (INIS)

Womack, J.C.

1995-01-01

This document establishes the functions and requirements baseline for the implementation of the Canister Storage Building Subproject. The mission allocated to the Canister Storage Building Subproject is to provide safe, environmentally sound staging and storage of K Basin SNF until a decision on the final disposition is reached and implemented

H2FIRST Hydrogen Contaminant Detector Task: Requirements Document and Market Survey

Energy Technology Data Exchange (ETDEWEB)

Terlip, Danny [National Renewable Energy Laboratory (NREL), Golden, CO (United States); Ainscough, Chris [National Renewable Energy Laboratory (NREL), Golden, CO (United States); Buttner, William [National Renewable Energy Laboratory (NREL), Golden, CO (United States); McWhorter, Scott [Savannah River Site (SRS), Aiken, SC (United States). Savannah River National Lab. (SRNL)

2015-04-20

The rollout of hydrogen fueling stations, and the fuel cell electric vehicles (FCEV) they support, requires the assurance of high quality hydrogen at the dispensing point. Automotive fuel cells are sensitive to a number of chemicals that can be introduced into the dispensed fuel at multiple points. Quality assurance and quality control methods are employed by the industry to ensure product quality, but they are not completely comprehensive and can fail at various points in the hydrogen pathway from production to dispensing. This reality leaves open the possibility of a station unknowingly dispensing harmful contaminants to a FCEV which, depending on the contaminant, may not be discovered until the FCEV is irreparably damaged. This situation is unacceptable. A hydrogen contaminant detector (HCD), defined as a combination of a gas analyzer and the components necessary for fuel stream integration, installed at hydrogen stations is one method for preventing poor quality gas from reaching an FCEV. This document identifies the characteristics required of such a device by industry and compares those requirements with the current state of commercially available gas analysis technology.

Waste Management Systems Requirements and Descriptions (SRD)

International Nuclear Information System (INIS)

Conner, C.W.

1986-01-01

The Department of Energy (DOE), Office of Civilian Radioactive Waste Management (OCRWM) is responsible for the development of a system for the management of high-level radioactive waste and spent fuel in accordance with the Nuclear Waste Policy Act of 1982. The Waste Management system requirements and description document is the program-level technical baseline document. The requirements include the functions that must be performed in order to achieve the system mission and performance criteria for those functions. This document covers only the functional requirements of the system; it does not cover programmatic or procedural requirements pertaining to the processes of designing, siting and licensing. The requirements are largely based on the Nuclear Waste Policy Act of 1982, Environmental Protection Agency standards, Nuclear Regulatory Commission regulations, and DOE orders and guidance. However, nothing in this document should be construed as to relieve the DOE or its contractors from their responsibilities to comply with applicable statutes, regulations, and standards. This document also provides a brief description of the system being developed to meet the requirements. In addition to the described ''authorized system,'' a system description is provided for an ''improved-performance system'' which would include a monitored retrievable storage (MRS) facility. In the event that an MRS facility is approved by Congress, the improved-performance system will become the reference system. Neither system description includes Federal Interim Storage (FIS) capabilities. Should the need for FIS be identified, it will be included as an additional system element. The descriptions are focused on the interfaces between the system elements, rather than on the detail of the system elements themselves

Functional requirements regarding medical registries--preliminary results.

Science.gov (United States)

Oberbichler, Stefan; Hörbst, Alexander

2013-01-01

The term medical registry is used to reference tools and processes to support clinical or epidemiologic research or provide a data basis for decisions regarding health care policies. In spite of this wide range of applications the term registry and the functional requirements which a registry should support are not clearly defined. This work presents preliminary results of a literature review to discover functional requirements which form a registry. To extract these requirements a set of peer reviewed articles was collected. These set of articles was screened by using methods from qualitative research. Up to now most discovered functional requirements focus on data quality (e. g. prevent transcription error by conducting automatic domain checks).

Functional Requirements and the Theory of Action.

Science.gov (United States)

Hills, R. Jean

1982-01-01

Responding to Willower's earlier questioning of the concept of systems' functional requirements, the author outlines the Parsonian theory of action, discussing action systems' components (values, norms, organizations, and facilities) and their functional imperatives or requirements (pattern maintenance, integration, goal attainment, and…

NGSI: Function Requirements for a Cylinder Tracking System

International Nuclear Information System (INIS)

Branney, S.

2012-01-01

While nuclear suppliers currently track uranium hexafluoride (UF 6 ) cylinders in various ways, for their own purposes, industry practices vary significantly. The NNSA Office of Nonproliferation and International Security's Next Generation Safeguards Initiative (NGSI) has begun a 5-year program to investigate the concept of a global monitoring scheme that uniquely identifies and tracks UF 6 cylinders. As part of this effort, NGSI's multi-laboratory team has documented the 'life of a UF 6 cylinder' and reviewed IAEA practices related to UF 6 cylinders. Based on this foundation, this paper examines the functional requirements of a system that would uniquely identify and track UF 6 cylinders. There are many considerations for establishing a potential tracking system. Some of these factors include the environmental conditions a cylinder may be expected to be exposed to, where cylinders may be particularly vulnerable to diversion, how such a system may be integrated into the existing flow of commerce, how proprietary data generated in the process may be protected, what a system may require in terms of the existing standard for UF 6 cylinder manufacture or modifications to it and what the limiting technology factors may be. It is desirable that a tracking system should provide benefit to industry while imposing as few additional constraints as possible and still meeting IAEA safeguards objectives. This paper includes recommendations for this system and the analysis that generated them.

IDC System Specification Document.

Energy Technology Data Exchange (ETDEWEB)

Clifford, David J.

2014-12-01

This document contains the system specifications derived to satisfy the system requirements found in the IDC System Requirements Document for the IDC Reengineering Phase 2 project. Revisions Version Date Author/Team Revision Description Authorized by V1.0 12/2014 IDC Reengineering Project Team Initial delivery M. Harris

Requirements Analysis Study for Master Pump Shutdown System Project Development Specification

International Nuclear Information System (INIS)

BEVINS, R.R.

2000-01-01

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 during the second phase of the W314 Project to cover the second phase of the project's scope

Supplemental design requirements document enhanced radioactive and mixed waste storage Phase V Project W-112

International Nuclear Information System (INIS)

Ocampo, V.P.; Boothe, G.F.; Greager, T.M.; Johnson, K.D.; Kooiker, S.L.; Martin, J.D.

1994-11-01

This document provides additional and supplemental information to WHC-SD-W112-FDC-001, Project W-112 for radioactive and mixed waste storage. It provides additional requirements for the design and summarizes Westinghouse Hanford Company key design guidance and establishes the technical baseline agreements to be used for definitive design of the Project W-112 facilities

Enterprise Document Management

Data.gov (United States)

US Agency for International Development — The function of the operation is to provide e-Signature and document management support for Acquisition and Assisitance (A&A) documents including vouchers in...

Recommended HSE-7 documents hierarchy

International Nuclear Information System (INIS)

Klein, R.B.; Jennrich, E.A.; Lund, D.M.; Danna, J.G.; Davis, K.D.; Rutz, A.C.

1990-01-01

This report recommends a hierarchy of waste management documents at Los Alamos National Laboratory (LANL or ''Laboratory''). The hierarchy addresses documents that are required to plan, implement, and document waste management programs at Los Alamos. These documents will enable the waste management group and the six sections contained within that group to satisfy requirements that are imposed upon them by the US Department of Energy (DOE), DOE Albuquerque Operations, US Environmental Protection Agency, various State of New Mexico agencies, and Laboratory management

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

Science.gov (United States)

Dodson, D. B.

1975-01-01

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

Subsurface Contamination Focus Area technical requirements. Volume 1: Requirements summary

International Nuclear Information System (INIS)

Nickelson, D.; Nonte, J.; Richardson, J.

1996-10-01

This document summarizes functions and requirements for remediation of source term and plume sites identified by the Subsurface Contamination Focus Area. Included are detailed requirements and supporting information for source term and plume containment, stabilization, retrieval, and selective retrieval remedial activities. This information will be useful both to the decision-makers within the Subsurface Contamination Focus Area (SCFA) and to the technology providers who are developing and demonstrating technologies and systems. Requirements are often expressed as graphs or charts, which reflect the site-specific nature of the functions that must be performed. Many of the tradeoff studies associated with cost savings are identified in the text

PFP functional development planning guide

International Nuclear Information System (INIS)

SINCLAIR, J.C.

1999-01-01

The PFP Functional Development Planning Guide presents the strategy and process used for the identification, development, and analysis of functions (activities) necessary to satisfy the requirements within the Plutonium Finishing Plant (PFP) integrated project baseline. The functional analysis will provide the basis for the development of a function driven work breakdown structure. Future revisions to this document will include as attachments the results of the PFP Functional Analysis resulting from this approach. This document is intended be a Project-owned management tool. As such, the guide will periodically require revisions resulting from improvements of the information, processes, and techniques as now described

22 CFR 203.7 - IPVO initial documentation requirements.

Science.gov (United States)

2010-04-01

... structure; (4) Statement of tax exemption or a comparable document from the country of its origin; (5... IPVO's country of domicile by an independent certified public accountant (CPA) and in U.S. dollars; (6...

Extremely secure identification documents

International Nuclear Information System (INIS)

Tolk, K.M.; Bell, M.

1997-09-01

The technology developed in this project uses biometric information printed on the document and public key cryptography to ensure that an adversary cannot issue identification documents to unauthorized individuals or alter existing documents to allow their use by unauthorized individuals. This process can be used to produce many types of identification documents with much higher security than any currently in use. The system is demonstrated using a security badge as an example. This project focused on the technologies requiring development in order to make the approach viable with existing badge printing and laminating technologies. By far the most difficult was the image processing required to verify that the picture on the badge had not been altered. Another area that required considerable work was the high density printed data storage required to get sufficient data on the badge for verification of the picture. The image processing process was successfully tested, and recommendations are included to refine the badge system to ensure high reliability. A two dimensional data array suitable for printing the required data on the badge was proposed, but testing of the readability of the array had to be abandoned due to reallocation of the budgeted funds by the LDRD office

Functional Foods Baseline and Requirements Analysis

Science.gov (United States)

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

2015-01-01

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

Health physics documentation

International Nuclear Information System (INIS)

Stablein, G.

1980-01-01

When dealing with radioactive material the health physicist receives innumerable papers and documents within the fields of researching, prosecuting, organizing and justifying radiation protection. Some of these papers are requested by the health physicist and some are required by law. The scope, quantity and deposit periods of the health physics documentation at the Karlsruhe Nuclear Research Center are presented and rationalizing methods discussed. The aim of this documentation should be the application of physics to accident prevention, i.e. documentation should protect those concerned and not the health physicist. (H.K.)

Functional analysis of the exploratory studies facility

International Nuclear Information System (INIS)

Duffy, M.A.; Mozhi, T.A.; Kumar, P.N.; Senderling, M.S.; Lemeshewsky, W.A.

1993-01-01

The 'Physical System Requirements - Exploratory Studies Facility' (PSR-ESF) was developed as part of an improved management structure and procedure initiative by the OCRWM for managing the disposal of spent nuclear fuel and high-level radioactive wastes. This paper discusses the development of the PSR-EF document. Based on a functional analysis approach, this document includes results in the form of boundary diagrams, function hierarchy trees, function description tables containing a compilation of requirements, architecture tree and tables, and functional flow diagrams. The approach used ensures the flowdown and traceability of relevant requirements for the ESF design process

Utility requirements for advanced LWR passive plants

International Nuclear Information System (INIS)

Yedidia, J.M.; Sugnet, W.R.

1992-01-01

LWR Passive Plants are becoming an increasingly attractive and prominent option for future electric generating capacity for U.S. utilities. Conceptual designs for ALWR Passive Plants are currently being developed by U.S. suppliers. EPRI-sponsored work beginning in 1985 developed preliminary conceptual designs for a passive BWR and PWR. DOE-sponsored work from 1986 to the present in conjunction with further EPRI-sponsored studies has continued this development to the point of mature conceptual designs. The success to date in developing the ALWR Passive Plant concepts has substantially increased utility interest. The EPRI ALWR Program has responded by augmenting its initial scope to develop a Utility Requirements Document for ALWR Passive Plants. These requirements will be largely based on the ALWR Utility Requirements Document for Evolutionary Plants, but with significant changes in areas related to the passive safety functions and system configurations. This work was begun in late 1988, and the thirteen-chapter Passive Plant Utility Requirements Document will be completed in 1990. This paper discusses the progress to date in developing the Passive Plant requirements, reviews the top-level requirements, and discusses key issues related to adaptation of the utility requirements to passive safety functions and system configurations. (orig.)

Documenting pharmacist interventions on an intranet.

Science.gov (United States)

Simonian, Armen I

2003-01-15

The process of developing and implementing an intranet Web site for clinical intervention documentation is described. An inpatient pharmacy department initiated an organizationwide effort to improve documentation of interventions by pharmacists at its seven hospitals to achieve real-time capture of meaningful benchmarking data. Standardization of intervention types would allow the health system to contrast and compare medication use, process improvement, and patient care initiatives among its hospitals. After completing a needs assessment and reviewing current methodologies, a computerized tracking tool was developed in-house and integrated with the organization's intranet. Representatives from all hospitals agreed on content and functionality requirements for the Web site. The site was completed and activated in February 2002. Before this Web site was established, the most documented intervention types were Renal Adjustment and Clarify Dose, with a daily average of four and three, respectively. After site activation, daily averages for Renal Adjustment remained unchanged, but Clarify Dose is now documented nine times per day. Drug Information and i.v.-to-p.o. intervention types, which previously averaged less than one intervention per day, are now documented an average of four times daily. Approximately 91% of staff pharmacists are using this site. Future plans for this site include enhanced accessibility to the site with wireless personal digital assistants. The design and implementation of an intranet Web site to document pharmacists' interventions doubled the rate of intervention documentation and standardized the intervention types among hospitals in the health system.

Integrated Management System, Configuration and Document Control for Research Reactors

International Nuclear Information System (INIS)

Steynberg, B.J.; Bruyn, J.F. du

2017-01-01

An integrated management system is a single management framework establishing all the processes necessary for the organisation to address all its goals and objectives. Very often only quality, environment and health & safety goals are included when referred to an integrated management system. However, within the research reactor environment such system should include goals pertinent to economic, environmental, health, operational, quality, safeguards, safety, security, and social considerations. One of the important objectives of an integrated management is to create the environment for a healthy safety culture. Configuration management is a disciplined process that involves both management and technical direction to establish and document the design requirements and the physical configuration of the research reactor and to ensure that they remain consistent with each other and the documentation. Configuration is the combination of the physical, functional, and operational characteristics of the structures, systems, and components (SSCs) or parts of the research reactor, operation, or activity. The basic objectives and general principles of configuration management are the same for all research reactors. The objectives of configuration management are to: a) Establish consistency among design requirements, physical configuration, and documentation (including analyses, drawings, and procedures) for the research reactor; b) Maintain this consistency throughout the life of the research reactor, particularly as changes are being made; and c) Retain confidence in the safety of the research reactor. The key elements needed to manage the configuration of research reactors are design requirements, work control, change control, document control, and configuration management assessments. The objective of document control is to ensure that only the most recently approved versions of documents are used in the process of operating, maintaining, and modifying the research reactor

LHCb electronics - requirements, specifications and implementation

CERN Document Server

Bibby, J

2001-01-01

This document is intended to serve as a requirements document, a design manual and an implementation reference for the RICH electronics systems. At the current time, the electronics design is under active consideration and this is reflected in this document which represents a working proposal as regards both the functional model and physical implementation. Comments on installation, commissioning, and maintenance are included. For convenience a description of the proposed RICH data formats is appended.

Station set requirements document. Volume 82: Fire support. Book 2: Preliminary functional fire plan

Science.gov (United States)

Gray, N. C.

1974-01-01

The fire prevention/protection requirements for all shuttle facility and ground support equipment are presented for the hazardous operations. These include: preparing the orbiter for launch, launch operations, landing operations, safing operations, and associated off-line activities.

A fully updated version of the european utility requirement (EUR) document is available

International Nuclear Information System (INIS)

Berbey, P.

2001-01-01

The major European electricity producers have worked on a common requirement document for future LWR plants since 1992 to get specifications acceptable together by the owners, the public and the authorities. Thus the designers can develop standard LWR designs that could be acceptable everywhere in Europe and the utilities can open their consultations to vendors on common bases. Public and authority's acceptance should be improved as well. Significant savings are expected in development and construction costs. Since the release of the last versions of the EUR texts in 1996, a lot of work has been carried out: reviews by the regulators and other external organisations, comparisons, assessment of compliance of designs vs. EUR and clarification works on the controversial topics that deserved changes or clarification. At the beginning of 1999 enough material was available to start a complete revision of the EUR document. In-depth works have been carried out during the last couple of year to develop this revision. The European utilities and the vendors have now an updated and well-tuned tool that allow them to develop, to assess and eventually to order modern LWR designs well fitted to their actual needs. (author)

Technical support document for proposed 1994 revision of the MEC thermal envelope requirements

Energy Technology Data Exchange (ETDEWEB)

Conner, C.C.; Lucas, R.G.

1994-03-01

This report documents the development of the proposed revision of the Council of American Building Officials` (CABO) 1994 supplement to the 1993 Model Energy Code (MEC) building thermal envelope requirements for maximum component U{sub 0}-value. The 1994 amendments to the 1993 MEC were established in last year`s code change cycle and did not change the envelope requirements. The research underlying the proposed MEC revision was conducted by Pacific Northwest Laboratory (PNL) for the US Department of Energy (DOE) Building Energy Standards program. The goal of this research was to develop revised guidelines based on an objective methodology that determines the most cost-effective (least total cost) combination of energy conservation measures (ECMs) (insulation levels and window types) for residential buildings. This least-cost set of ECMs was used as a basis for proposing revised MEC maximum U{sub 0}-values (thermal transmittances). ECMs include window types (for example, double-pane vinyl) and insulation levels (for example, R-19) for ceilings, walls, and floors.

1994 report on Tasks 4.3.1 and 4.3.2: Survey of anticipated requirements and qualification requirements for OSS

International Nuclear Information System (INIS)

Silvani, V.

1995-01-01

This is a preliminary report summarizing some topics related to the survey on functional and qualification requirements of Operator Support Systems (OSS's) in NPP's. This document has been prepared on the basis of the information presented in the previous meetings of this CRP working group. Additional information are expected when the answers to the working group questionnaire will be available. Functionalities examined are those referring to system functions and user's needs; technology trends are also considered. For practical purposes this document is divided in the followings: Summary of major OSS requirements and related problems as derived from the existing literature; appendix 1 reporting a summary of major functions performed by the OSS's presently in operation or under development in laboratories; appendix 2 reporting the list of standards for critical software. 18 refs, tabs

Molten Salt Reactor Experiment Facility (Building 7503) standards/requirements identification document adherence assessment plan at Oak Ridge National Laboratory, Oak Ridge, Tennessee

International Nuclear Information System (INIS)

1996-02-01

This is the Phase 2 (adherence) assessment plan for the Building 7503 Molten Salt Reactor Experiment (MSRE) Facility standards/requirements identification document (S/RID). This document outlines the activities to be conducted from FY 1996 through FY 1998 to ensure that the standards and requirements identified in the MSRE S/RID are being implemented properly. This plan is required in accordance with the Department of Energy Implementation Plan for Defense Nuclear Facilities Safety Board Recommendation 90-2, November 9, 1994, Attachment 1A. This plan addresses the major aspects of the adherence assessment and will be consistent with Energy Systems procedure QA-2. 7 ''Surveillances.''

Summary of functional and performance test procedures

DEFF Research Database (Denmark)

Mitzel, Jens; Gülzow, Erich; Friedrich, K. Andreas

Different Test Modules (TM) are defined for the functional and performance characterization of a PEMFC stack. The master document TM2.00 defines requirements and methodology for parameter variation, stability and data acquisition.......Different Test Modules (TM) are defined for the functional and performance characterization of a PEMFC stack. The master document TM2.00 defines requirements and methodology for parameter variation, stability and data acquisition....

Non-Functional Requirements Elicitation and Incorporation into Class Diagrams

OpenAIRE

Song , Xiaoyu; Duan , Zhenhua; Tian , Cong

2010-01-01

International audience; Top-quality software architecture should consider both functional and non-functional aspects of systems and their association. In the the existing literature, considerable efforts have been directed at functional requirement analysis and design, regardless of the non-functional aspects. This disassociation makes architecture comprehension and evolution hard. This paper proposes a strategy on how to elicit non-functional requirements and incorporate them into the design...

TA-55 facility control system upgrade project - human-system interface functional requirements

International Nuclear Information System (INIS)

Atkins, W.H.; Pope, N.G.; Turner, W.J.; Brown, R.E.

1995-11-01

The functional requirements for that part of the Technical Area (TA)-55 Operations Center Upgrade Project that involves the human-system interface (HSI) are described in this document. The upgrade project seeks to replace completely the center's existing computerized data acquisition and display system, which consists of the field multiplexer units, Data General computer systems, and associated peripherals and software. The upgrade project has two parts-the Facility Data Acquisition Interface System (FDAIS) and the HSI. The HSI comprises software and hardware to provide a high-level graphical operator interface to the data acquisition system, as well as data archiving, alarm annunciation, and logging. The new system will be built with modern, commercially available components; it will improve reliability and maintainability, and it can be expanded for future needs

Regulatory document R-104, Regulatory objectives, requirements and guidelines for the disposal of radioactive wastes - long-term aspects

International Nuclear Information System (INIS)

1987-01-01

The purpose and scope of this document is to present the regulatory basis for judging the long-term acceptability of radioactive waste disposal options. The basic objectives of radioactive waste disposal are given as are the regulatory requirements to be satisfied. (NEA)

Documentation of medical findings in radiation workers in the GDR to meet the requirements of ICRP publication 26

International Nuclear Information System (INIS)

Wolff, H.R.; Neumeister, K.

1979-01-01

Based on ICRP Publication 26, the future organization of the medical surveillance system for radiation workers in the GDR is considered in this paper. These radiation workers will also in future be medically supervised by means of pre-employment and routine examinations. It is considered necessary to have as extensive a registration as possible of information on medical examinations, working place analyses and incidents. Such data have to be collected and stored to be compared with other national and international projects (e.g. in the field of occupational health). In addition, they should permit epidemiological studies to be internationally co-ordinated. For this purpose, a documentation system has been prepared in the German Democratic Republic which is based on GDR experiences and makes it possible to specify the requirements of ICRP Publication 26. This system forms a new basis for mass examinations of occupationally exposed persons. Uniform examination methods tailored to meet the task of assuring occupational health in the GDR will be introduced. The documentation cards are meant to be used as clear-text cards suited for automatic reading by optical character recognition. The examination form consists of ten parts and comprises all details from working place situation to medical findings to laboratory results. It is felt that this new documentation system permits registration of all relevant data required for the effective radiation protection of man. On the basis of this documentation of findings, participation is scheduled in the respective international IAEA programmes and the studies proposed by the ICRP for problems of radiation-induced carcinogenesis and radiogenetics

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 4

Energy Technology Data Exchange (ETDEWEB)

1994-04-01

Radiation protection of personnel and the public is accomplished by establishing a well defined Radiation Protection Organization to ensure that appropriate controls on radioactive materials and radiation sources are implemented and documented. This Requirements Identification Document (RID) applies to the activities, personnel, structures, systems, components, and programs involved in executing the mission of the Tank Farms. The physical boundaries within which the requirements of this RID apply are the Single Shell Tank Farms, Double Shell Tank Farms, 242-A Evaporator-Crystallizer, 242-S, T Evaporators, Liquid Effluent Retention Facility (LERF), Purgewater Storage Facility (PWSF), and all interconnecting piping, valves, instrumentation, and controls. Also included is all piping, valves, instrumentation, and controls up to and including the most remote valve under Tank Farms control at any other Hanford Facility having an interconnection with Tank Farms. The boundary of the structures, systems, components, and programs to which this RID applies, is defined by those that are dedicated to and/or under the control of the Tank Farms Operations Department and are specifically implemented at the Tank Farms.

High-level waste storage tank farms/242-A evaporator standards/requirements identification document (S/RID), Vol. 4

International Nuclear Information System (INIS)

1994-04-01

Radiation protection of personnel and the public is accomplished by establishing a well defined Radiation Protection Organization to ensure that appropriate controls on radioactive materials and radiation sources are implemented and documented. This Requirements Identification Document (RID) applies to the activities, personnel, structures, systems, components, and programs involved in executing the mission of the Tank Farms. The physical boundaries within which the requirements of this RID apply are the Single Shell Tank Farms, Double Shell Tank Farms, 242-A Evaporator-Crystallizer, 242-S, T Evaporators, Liquid Effluent Retention Facility (LERF), Purgewater Storage Facility (PWSF), and all interconnecting piping, valves, instrumentation, and controls. Also included is all piping, valves, instrumentation, and controls up to and including the most remote valve under Tank Farms control at any other Hanford Facility having an interconnection with Tank Farms. The boundary of the structures, systems, components, and programs to which this RID applies, is defined by those that are dedicated to and/or under the control of the Tank Farms Operations Department and are specifically implemented at the Tank Farms

Assembling Components using SysML with Non-Functional Requirements

OpenAIRE

Chouali , Samir; Hammad , Ahmed; Mountassir , Hassan

2013-01-01

International audience; Non-functional requirements of component based systems are important as their functional requirements, therefore they must be considered in components assembly. These properties are beforehand specified with SysML requirement diagram. We specify component based system architecture with SysML block definition diagram, and component behaviors with sequence diagrams. We propose to specify formally component interfaces with interface automata, obtained from requirement and...

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

Science.gov (United States)

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

TECHNICAL BASIS FOR VENTILATION REQUIREMENTS IN TANK FARMS OPERATING SPECIFICATIONS DOCUMENTS

Energy Technology Data Exchange (ETDEWEB)

BERGLIN, E J

2003-06-23

This report provides the technical basis for high efficiency particulate air filter (HEPA) for Hanford tank farm ventilation systems (sometimes known as heating, ventilation and air conditioning [HVAC]) to support limits defined in Process Engineering Operating Specification Documents (OSDs). This technical basis included a review of older technical basis and provides clarifications, as necessary, to technical basis limit revisions or justification. This document provides an updated technical basis for tank farm ventilation systems related to Operation Specification Documents (OSDs) for double-shell tanks (DSTs), single-shell tanks (SSTs), double-contained receiver tanks (DCRTs), catch tanks, and various other miscellaneous facilities.

NASA software documentation standard software engineering program

Science.gov (United States)

1991-01-01

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

Towards an Early Software Effort Estimation Based on Functional and Non-Functional Requirements

Science.gov (United States)

Kassab, Mohamed; Daneva, Maya; Ormandjieva, Olga

The increased awareness of the non-functional requirements as a key to software project and product success makes explicit the need to include them in any software project effort estimation activity. However, the existing approaches to defining size-based effort relationships still pay insufficient attention to this need. This paper presents a flexible, yet systematic approach to the early requirements-based effort estimation, based on Non-Functional Requirements ontology. It complementarily uses one standard functional size measurement model and a linear regression technique. We report on a case study which illustrates the application of our solution approach in context and also helps evaluate our experiences in using it.

National Ignition Facility site requirements

International Nuclear Information System (INIS)

1996-07-01

The Site Requirements (SR) provide bases for identification of candidate host sites for the National Ignition Facility (NIF) and for the generation of data regarding potential actual locations for the facilities. The SR supplements the NIF Functional Requirements (FR) with information needed for preparation of responses to queries for input to HQ DOE site evaluation. The queries are to include both documents and explicit requirements for the potential host site responses. The Sr includes information extracted from the NIF FR (for convenience), data based on design approaches, and needs for physical and organization infrastructure for a fully operational NIF. The FR and SR describe requirements that may require new construction or may be met by use or modification of existing facilities. The SR do not establish requirements for NIF design or construction project planning. The SR document does not constitute an element of the NIF technical baseline

Semantic Metadata for Heterogeneous Spatial Planning Documents

Science.gov (United States)

Iwaniak, A.; Kaczmarek, I.; Łukowicz, J.; Strzelecki, M.; Coetzee, S.; Paluszyński, W.

2016-09-01

Spatial planning documents contain information about the principles and rights of land use in different zones of a local authority. They are the basis for administrative decision making in support of sustainable development. In Poland these documents are published on the Web according to a prescribed non-extendable XML schema, designed for optimum presentation to humans in HTML web pages. There is no document standard, and limited functionality exists for adding references to external resources. The text in these documents is discoverable and searchable by general-purpose web search engines, but the semantics of the content cannot be discovered or queried. The spatial information in these documents is geographically referenced but not machine-readable. Major manual efforts are required to integrate such heterogeneous spatial planning documents from various local authorities for analysis, scenario planning and decision support. This article presents results of an implementation using machine-readable semantic metadata to identify relationships among regulations in the text, spatial objects in the drawings and links to external resources. A spatial planning ontology was used to annotate different sections of spatial planning documents with semantic metadata in the Resource Description Framework in Attributes (RDFa). The semantic interpretation of the content, links between document elements and links to external resources were embedded in XHTML pages. An example and use case from the spatial planning domain in Poland is presented to evaluate its efficiency and applicability. The solution enables the automated integration of spatial planning documents from multiple local authorities to assist decision makers with understanding and interpreting spatial planning information. The approach is equally applicable to legal documents from other countries and domains, such as cultural heritage and environmental management.

Getting the balance right between functional and non-functional requirements: the case of requirement specification in IT procurement

Directory of Open Access Journals (Sweden)

Björn Johansson

2013-01-01

Full Text Available IT procurement represents a business process of high importance, including the ability to articulate requirements that the procurement deals with. Furthermore, specifying requirements is of importance for both procurer and potential supplier, as it functions as central contractual element between the two. The purpose of this article is two-fold: (i to show how established terminology for requirement specification is represented in current call for bids for the procurement of IT; and (ii to introduce an organizing framework that may assist procurers in actively addressing functional requirements and business requirements. Ten “call for bids” were examined from a Swedish national procurement database. From the analysis of the bids, it can be concluded that: (i the call for bids displays a high degree of precision regarding hardware aspects, but less precision regarding software; (ii supplier experience and competence is stressed, but rarely elaborated on in detail; and (iii call for bids vagueness may be used as a lock-in opportunity for suppliers. From the discussion on this, a tentative procurement framework is suggested, aiming on increasing the logical transparency for the procurement of IT.

Buddy Tag CONOPS and Requirements.

Energy Technology Data Exchange (ETDEWEB)

Brotz, Jay Kristoffer [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Deland, Sharon M. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States)

2015-12-01

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

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

Science.gov (United States)

2010-10-01

... of presenting entry documentation for clearance by customs authorities (e.g., CBP Forms 7533 or 3461... apply to all imports of fish or fish products regulated under this subpart, into the Customs territory... landed overseas (HTS heading 9815). For insular possessions with customs territories separate from the...

System requirements specification for waste information and control system

International Nuclear Information System (INIS)

Harris, R.R.

1994-09-01

This document defines the requirements for the Waste Information and Control System (WICS). The document defines the functions, constraints, and objectives that pertain to WICS. This shall serve as the baseline document to ensure the needs of the Hazardous Material Control group (HMC) at 222-S Laboratory are met with regard to assurance of accuracy and quality of data taken with WICS

How to understand requirements of nuclear and defense welding contracts

International Nuclear Information System (INIS)

Dickinson, O.D.

1986-01-01

This paper presents a basic requirements control plan for contract documentation and software validation and maintenance for nuclear operation. The objective is designing an integrated configuration control plan of both old, new, large or small, critical and noncritical software programs. There are positive advantages to managing a planned requirements program for product delivery or business operations. A requirements baseline like this is preferable to many iterations of design effort in the maintenance of nonbaselined programs, documentation and software. The plan that applies program requirements needs to address different levels of criticality and define matching program requirements for those levels. The plan needs to describe old vs. new requirements and define scope/responsibility that is needed to support the design, development and completion of these program requirements. Presented are management goals, relative costs, quality assurance goals, and program assessment plans. Outlined is a set of program QA requirements and document/software functional requirements for planning of program; also presented are some criteria for criticality assessment to establish levels of contract documentation or software activity. The paper shows two examples of planning work on this configuration control plan. The integrated configuration control requirements plan can be computer based or paper based for activity. It is designed to cover existing or new requirements and to cover either no documentation or all documentation

Document management in engineering construction

International Nuclear Information System (INIS)

Liao Bing

2008-01-01

Document management is one important part of systematic quality management, which is one of the key factors to ensure the construction quality. In the engineering construction, quality management and document management shall interwork all the time, to ensure the construction quality. Quality management ensures that the document is correctly generated and adopted, and thus the completeness, accuracy and systematicness of the document satisfy the filing requirements. Document management ensures that the document is correctly transferred during the construction, and various testimonies such as files and records are kept for the engineering construction and its quality management. This paper addresses the document management in the engineering construction based on the interwork of the quality management and document management. (author)

Feasibility study and functional requirements for a digital non-conventional literature system at INIS and Member Sites

International Nuclear Information System (INIS)

Hendley, T.; Dixon, R.

1993-03-01

The aim of any Non-Conventional Literature (NCL) system will be to improve the service INIS provides to members, reducing the operational cost of administering the NCL service by the streamlining of procedures, allowing INIS to provide NCL to members using media relevant to the needs of members and positioning INIS so that as a member's needs change these needs can be catered for. Specific functional requirements include the receipt and checking of NCL documents and bibliographic data, conversion of received NCL into digital image form accessed by an image index database referenced alongside the existing bibliographic database and output of NCL to digital interchange/distribution media in addition to microfiche and possibly paper. The quality of service to members in terms of document quality and turn around time must be at least maintained. The study was undertaken by Cimtech consultants between December 1992 and March 1993. Approximate costs and benefits of implementing a digital NCL system were identified. Some outstanding issues need to be resolved. This could include a pilot system being introduced which would allow requirements to be defined more fully and operational experience to be gained. (Author)

National Ignition Facility system design requirements conventional facilities SDR001

International Nuclear Information System (INIS)

Hands, J.

1996-01-01

This System Design Requirements (SDR) document specifies the functions to be performed and the minimum design requirements for the National Ignition Facility (NIF) site infrastructure and conventional facilities. These consist of the physical site and buildings necessary to house the laser, target chamber, target preparation areas, optics support and ancillary functions

SEMANTIC METADATA FOR HETEROGENEOUS SPATIAL PLANNING DOCUMENTS

Directory of Open Access Journals (Sweden)

A. Iwaniak

2016-09-01

Full Text Available Spatial planning documents contain information about the principles and rights of land use in different zones of a local authority. They are the basis for administrative decision making in support of sustainable development. In Poland these documents are published on the Web according to a prescribed non-extendable XML schema, designed for optimum presentation to humans in HTML web pages. There is no document standard, and limited functionality exists for adding references to external resources. The text in these documents is discoverable and searchable by general-purpose web search engines, but the semantics of the content cannot be discovered or queried. The spatial information in these documents is geographically referenced but not machine-readable. Major manual efforts are required to integrate such heterogeneous spatial planning documents from various local authorities for analysis, scenario planning and decision support. This article presents results of an implementation using machine-readable semantic metadata to identify relationships among regulations in the text, spatial objects in the drawings and links to external resources. A spatial planning ontology was used to annotate different sections of spatial planning documents with semantic metadata in the Resource Description Framework in Attributes (RDFa. The semantic interpretation of the content, links between document elements and links to external resources were embedded in XHTML pages. An example and use case from the spatial planning domain in Poland is presented to evaluate its efficiency and applicability. The solution enables the automated integration of spatial planning documents from multiple local authorities to assist decision makers with understanding and interpreting spatial planning information. The approach is equally applicable to legal documents from other countries and domains, such as cultural heritage and environmental management.

FLAMMABLE GAS TECHNICAL BASIS DOCUMENT

Energy Technology Data Exchange (ETDEWEB)

KRIPPS, L.J.

2005-03-03

This document describes the qualitative evaluation of frequency and consequences for DST and SST representative flammable gas accidents and associated hazardous conditions without controls. The evaluation indicated that safety-significant structures, systems and components (SSCs) and/or technical safety requirements (TSRs) were required to prevent or mitigate flammable gas accidents. Discussion on the resulting control decisions is included. This technical basis document was developed to support WP-13033, Tank Farms Documented Safety Analysis (DSA), and describes the risk binning process for the flammable gas representative accidents and associated represented hazardous conditions. The purpose of the risk binning process is to determine the need for safety-significant structures, systems, and components (SSC) and technical safety requirement (TSR)-level controls for a given representative accident or represented hazardous condition based on an evaluation of the event frequency and consequence.

Documentation of spectrom-32

International Nuclear Information System (INIS)

Callahan, G.D.; Fossum, A.F.; Svalstad, D.K.

1989-01-01

SPECTROM-32 is a finite element program for analyzing two-dimensional and axisymmetric inelastic thermomechanical problems related to the geological disposal of nuclear waste. The code is part of the SPECTROM series of special-purpose computer programs that are being developed by RE/SPEC Inc. to address many unique rock mechanics problems encountered in analyzing radioactive wastes stored in geologic formations. This document presents the theoretical basis for the mathematical models, the finite element formulation and solution procedure of the program, a description of the input data for the program, verification problems, and details about program support and continuing documentation. The computer code documentation is intended to satisfy the requirements and guidelines outlined in the document entitled Final Technical Position on Documentation of Computer Codes for High-Level Waste Management. The principal component models used in the program involve thermoelastic, thermoviscoelastic, thermoelastic-plastic, and thermoviscoplastic types of material behavior. Special material considerations provide for the incorporation of limited-tension material behavior and consideration of jointed material behavior. Numerous program options provide the capabilities for various boundary conditions, sliding interfaces, excavation, backfill, arbitrary initial stresses, multiple material domains, load incrementation, plotting database storage and access of results, and other features unique to the geologic disposal of radioactive wastes. Numerous verification problems that exercise many of the program options and illustrate the required data input and printed results are included in the documentation

Scheme Program Documentation Tools

DEFF Research Database (Denmark)

Nørmark, Kurt

2004-01-01

are separate and intended for different documentation purposes they are related to each other in several ways. Both tools are based on XML languages for tool setup and for documentation authoring. In addition, both tools rely on the LAML framework which---in a systematic way---makes an XML language available...... as named functions in Scheme. Finally, the Scheme Elucidator is able to integrate SchemeDoc resources as part of an internal documentation resource....

Department of Energy Emergency Management Functional Requirements Study

International Nuclear Information System (INIS)

1987-05-01

This Study, the Emergency Management Functional Requirements Study (EMFRS), identifies the physical environment, information resources, and equipment required in the DOE Headquarters Emergency Operations Center (EOC) to support the DOE staff in managing an emergency. It is the first step toward converting the present Forrestal EOC into a practical facility that will function well in each of the highly diverse types of emergencies in which the Department could be involved. 2 figs

33 CFR 157.12f - Workshop functional test requirements.

Science.gov (United States)

2010-07-01

... CARRYING OIL IN BULK Design, Equipment, and Installation § 157.12f Workshop functional test requirements... 33 Navigation and Navigable Waters 2 2010-07-01 2010-07-01 false Workshop functional test requirements. 157.12f Section 157.12f Navigation and Navigable Waters COAST GUARD, DEPARTMENT OF HOMELAND...

Securing XML Documents

Directory of Open Access Journals (Sweden)

Charles Shoniregun

2004-11-01

Full Text Available XML (extensible markup language is becoming the current standard for establishing interoperability on the Web. XML data are self-descriptive and syntax-extensible; this makes it very suitable for representation and exchange of semi-structured data, and allows users to define new elements for their specific applications. As a result, the number of documents incorporating this standard is continuously increasing over the Web. The processing of XML documents may require a traversal of all document structure and therefore, the cost could be very high. A strong demand for a means of efficient and effective XML processing has posed a new challenge for the database world. This paper discusses a fast and efficient indexing technique for XML documents, and introduces the XML graph numbering scheme. It can be used for indexing and securing graph structure of XML documents. This technique provides an efficient method to speed up XML data processing. Furthermore, the paper explores the classification of existing methods impact of query processing, and indexing.

The Effects of Information Technology on Library and Documentation Centers: A Review of Social, Structural, Managerial and Functional Aspects

Directory of Open Access Journals (Sweden)

Mesut Kurulgan

2013-11-01

Full Text Available In the context of protecting academic and cultural heritage, the purpose of libraries and information and documentation centers is to research, document, and archive and to transfer to future generations, domestically and internationally, a society ’s culture. This study examines the structural, functional and administrative innovations that have resulted from the implementation of information technology (IT in libraries since the 1990 ’s. The study also mentions how IT can be used in an efficient way in libraries and information and documentation centers.

ATLAS TDAQ/DCS Event filter : Supervision Requirements

CERN Document Server

Bee, C P; Meessen, C; Qian, Z; Touchard, F; Green, P; Pinfold, J L; Wheeler, S; Negri, A; Scannicchio, D A; Vercesi, V

2002-01-01

The second iteration of the Software Development Process of the ATLAS Event Filter has been launched. A summary of the design phase of the first iteration is given in the introduction. The document gives constraints, use cases, functional and non-functional requirements for the Supervision sub-system of the Event Filter.

Structure and drafting of safeguards regulatory documents

International Nuclear Information System (INIS)

Cole, R.J.; Bennett, C.A.; Edelhertz, H.; Wood, M.T.; Brown, R.J.; Roberts, F.P.

1977-09-01

This study develops hypothesis about the relation between the structure and drafting of safeguards regulatory documents and the ability of document users to understand and implement them in a way that reflects the intent and requirements of the NRC. Four decisions are needed to improve communication: (1) Should improvement of safeguards regulatory documents as communication instruments be an explicit NRC program. (2) What specific methods of communication should be the focus of improvement efforts. (3) What actions to improve communications are feasible and desirable. (4) How should the NRC divide its available effort and resources among desirable actions in order to provide the most effective communication through regulatory documents. This volume contains: introduction, conceptual bases, legal requirements, targets, choice of documents, preparation of documents, readability, and further study of recommended changes in structure and drafting

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

Science.gov (United States)

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

1981-01-01

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

Identifying environmental safety and health requirements for an Environmental Restoration Management Contractor

International Nuclear Information System (INIS)

Beckman, W.H.; Cossel, S.C.; Alhadeff, N.; Lindamood, S.B.; Beers, J.A.

1993-10-01

The purpose of the Standards/Requirements Identification Program, developed partially in response to the Defense Nuclear Facilities Safety Board Recommendation 90-2, was to identify applicable requirements that established the Environmental Restoration Management Contractor's (ERMC) responsibilities and authorities under the Environmental Restoration Management Contract, determine the adequacy of these requirements, ascertain a baseline level of compliance with them, and implement a maintenance program that would keep the program current as requirements or compliance levels change. The resultant Standards/Requirements Identification Documents (S/RIDs) consolidate the applicable requirements. These documents govern the development of procedures and manuals to ensure compliance with the requirements. Twenty-four such documents, corresponding with each functional area identified at the site, are to be issued. These requirements are included in the contractor's management plan

Radionuclide assessment of left ventricular function in patients requiring intraoperative balloon pump assistance

International Nuclear Information System (INIS)

Davies, R.A.; Laks, H.; Wackers, F.J.; Berger, H.J.; Williams, B.; Hammond, G.L.; Geha, A.S.; Gottschalk, A.; Zaret, B.L.

1982-01-01

Twenty-three surviving patients who were weaned from cardiopulmonary bypass with intraaortic balloon pump assistance returned for follow-up radionuclide left ventricular (LV) function and thallium 201 perfusion studies at a mean of 23 +/- 3 months following operation. It was found that despite profound intraoperative myocardial depression requiring intraaortic balloon assistance, 13 patients had no change (within 10%) in the resting LV ejection fraction compared with the preoperative measurement. Among all 23 patients, there was no difference between mean (+/- standard error of the mean) preoperative and postoperative resting LV ejection fraction (48 +/- 4 vs 46 +/- 4%, p . not significant [NS]). Only 11 patients had perioperative myocardial infarction documented by new Q waves in the electrocardiogram, by elevation of creatine kinase-MB fraction, or by defects on thallium 201 imaging not explained by documented myocardial infarction before operation. Overall, postoperative resting LV ejection fraction was not different from the preoperative value in patients with perioperative myocardial infarction (44 +/- 7 vs 47 +/- 5%, p . NS). Postoperative resting LV ejection fraction rose by greater than 10% compared with preoperative values in 4 patients (3 with aortic valve replacement), remained within the 10% limit in 9 patients, and fell by greater than 10% in 10 patients (7 with perioperative myocardial infarction). Only 4 out of 16 patients studied at follow-up with exercise radionuclide studies demonstrated a normal LV response to exercise (greater than 5% increase in LV ejection fraction). Thus, among survivors requiring intraaortic balloon pump assistance for weaning from cardiopulmonary bypass, LV performance at rest is frequently preserved. In addition, 11 of the 23 patients had evidence of perioperative myocardial infarction, indicating a component of reversible intraoperative LV dysfunction

Documentation assessment, Project C-018H, 200-E area effluent treatment facility

International Nuclear Information System (INIS)

Peres, M.W.; Connor, M.D.; Mertelendy, J.I.

1994-01-01

Project C-018H is one of the fourteen subprojects to the Hanford Environmental Compliance (HEC) Project. Project C-018H provides treatment and disposal for the 242-A Evaporator and PUREX plant process condensate waste streams. This project used the Integrated Management Team (IMT) approach proposed by RL. The IMT approach included all affected organizations on the project team to coordinate and execute all required project tasks, while striving to integrate and satisfy all technical, operational, functional, and organizational objectives. The HEC Projects were initiated in 1989. Project C-018H began in early 1990, with completion of construction currently targeted for mid-1995. This assessment was performed to evaluate the effectiveness of the management control on design documents and quality assurance records developed and submitted for processing, use, and retention for the Project. The assessment focused primarily on the overall adequacy and quality of the design documentation currently being submitted to the project document control function

Schwann cell myelination requires Dynein function

Directory of Open Access Journals (Sweden)

Langworthy Melissa M

2012-11-01

Full Text Available Abstract Background Interaction of Schwann cells with axons triggers signal transduction that drives expression of Pou3f1 and Egr2 transcription factors, which in turn promote myelination. Signal transduction appears to be mediated, at least in part, by cyclic adenosine monophosphate (cAMP because elevation of cAMP levels can stimulate myelination in the absence of axon contact. The mechanisms by which the myelinating signal is conveyed remain unclear. Results By analyzing mutations that disrupt myelination in zebrafish, we learned that Dynein cytoplasmic 1 heavy chain 1 (Dync1h1, which functions as a motor for intracellular molecular trafficking, is required for peripheral myelination. In dync1h1 mutants, Schwann cell progenitors migrated to peripheral nerves but then failed to express Pou3f1 and Egr2 or make myelin membrane. Genetic mosaic experiments revealed that robust Myelin Basic Protein expression required Dync1h1 function within both Schwann cells and axons. Finally, treatment of dync1h1 mutants with a drug to elevate cAMP levels stimulated myelin gene expression. Conclusion Dync1h1 is required for retrograde transport in axons and mutations of Dync1h1 have been implicated in axon disease. Our data now provide evidence that Dync1h1 is also required for efficient myelination of peripheral axons by Schwann cells, perhaps by facilitating signal transduction necessary for myelination.

Documentation of Cultural Heritage Objects

Directory of Open Access Journals (Sweden)

Jon Grobovšek

2013-09-01

Full Text Available EXTENDED ABSTRACT:The first and important phase of documentation of cultural heritage objects is to understand which objects need to be documented. The entire documentation process is determined by the characteristics and scope of the cultural heritage object. The next question to be considered is the expected outcome of the documentation process and the purpose for which it will be used. These two essential guidelines determine each stage of the documentation workflow: the choice of the most appropriate data capturing technology and data processing method, how detailed should the documentation be, what problems may occur, what the expected outcome is, what it will be used for, and the plan for storing data and results. Cultural heritage objects require diverse data capturing and data processing methods. It is important that even the first stages of raw data capturing are oriented towards the applicability of results. The selection of the appropriate working method can facilitate the data processing and the preparation of final documentation. Documentation of paintings requires different data capturing method than documentation of buildings or building areas. The purpose of documentation can also be the preservation of the contemporary cultural heritage to posterity or the basis for future projects and activities on threatened objects. Documentation procedures should be adapted to our needs and capabilities. Captured and unprocessed data are lost unless accompanied by additional analyses and interpretations. Information on tools, procedures and outcomes must be included into documentation. A thorough analysis of unprocessed but accessible documentation, if adequately stored and accompanied by additional information, enables us to gather useful data. In this way it is possible to upgrade the existing documentation and to avoid data duplication or unintentional misleading of users. The documentation should be archived safely and in a way to meet

National Ingition Facility subsystem design requirements optics subsystems SSDR 1.6

International Nuclear Information System (INIS)

English, R.E.

1996-01-01

This Subsystems Design Requirement (SSDR) document specifies the functions to be performed and the subsystems design requirements for the major optical components. These optical components comprise those custom designed and fabricated for amplification and transport of the full aperture NIF beam and does not include those off-the-shelf components that may be part of other optical sub-systems (i.e. alignment or diagnostic systems). This document also describes the optical component processing requirements and the QA/damage testing necessary to ensure that the optical components meet or exceed the requirements

Revk - a Tool for the Fulfilment of Requirements from National Rules for Tracking and Documentation of Radioactive Residual Material and Radioactive Waste

International Nuclear Information System (INIS)

Hartmann, B.; Haeger, M.; Gruendler, D.

2006-01-01

According to the German Radiation Protection Ordinance treatment, storage, whereabouts of radioactive material etc. have to be documented. Due to legal requirements an electronic documentation system for radioactive waste has to be installed. Within the framework of the currently largest decommissioning project of nuclear facilities by Energiewerke Nord GmbH, a material flow-waste tracking and control system (ReVK) has been developed, tailored to the special needs of the decommissioning of nuclear facilities. With this system it is possible to record radioactive materials which can be released after treatment or decay storage for restricted and unrestricted utilization. Radioactive waste meant for final storage can be registered and documented as well. Based on ORACLE, ReVK is a client/server data base system with the following modules: 1. data registration, 2. transport management, 3. waste tracking, 4. storage management, 5. container management, 6. reporting, 7. activity calculation, 8. examination of technical acceptance criteria for storages and final repositories. Furthermore ReVK provides a multitude of add-ons to meet special user needs, which enlarge the spectrum of application enormously. ReVK is validated and qualified, accepted by experts and authorities and fulfils the requirements for a radioactive waste documentation system. (authors)

The Advancement of Public Awareness, Concerning TRU Waste Characterization, Using a Virtual Document

International Nuclear Information System (INIS)

West, T. B.; Burns, T. P.; Estill, W. G.; Riggs, M. J.; Taggart, D. P.; Punjak, W. A.

2002-01-01

Building public trust and confidence through openness is a goal of the DOE Carlsbad Field Office for the Waste Isolation Pilot Plant (WIPP). The objective of the virtual document described in this paper is to give the public an overview of the waste characterization steps, an understanding of how waste characterization instrumentation works, and the type and amount of data generated from a batch of drums. The document is intended to be published on a web page and/or distributed at public meetings on CDs. Users may gain as much information as they desire regarding the transuranic (TRU) waste characterization program, starting at the highest level requirements (drivers) and progressing to more and more detail regarding how the requirements are met. Included are links to: drivers (which include laws, permits and DOE Orders); various characterization steps required for transportation and disposal under WIPP's Hazardous Waste Facility Permit; physical/chemical basis for each characterization method; types of data produced; and quality assurance process that accompanies each measurement. Examples of each type of characterization method in use across the DOE complex are included. The original skeleton of the document was constructed in a PowerPoint presentation and included descriptions of each section of the waste characterization program. This original document had a brief overview of Acceptable Knowledge, Non-Destructive Examination, Non-Destructive Assay, Small Quantity sites, and the National Certification Team. A student intern was assigned the project of converting the document to a virtual format and to discuss each subject in depth. The resulting product is a fully functional virtual document that works in a web browser and functions like a web page. All documents that were referenced, linked to, or associated, are included on the virtual document's CD. WIPP has been engaged in a variety of Hazardous Waste Facility Permit modification activities. During the

Joint Service Common Operating Environment (COE) Common Geographic Information System functional requirements

Energy Technology Data Exchange (ETDEWEB)

Meitzler, W.D.

1992-06-01

In the context of this document and COE, the Geographic Information Systems (GIS) are decision support systems involving the integration of spatially referenced data in a problem solving environment. They are digital computer systems for capturing, processing, managing, displaying, modeling, and analyzing geographically referenced spatial data which are described by attribute data and location. The ability to perform spatial analysis and the ability to combine two or more data sets to create new spatial information differentiates a GIS from other computer mapping systems. While the CCGIS allows for data editing and input, its primary purpose is not to prepare data, but rather to manipulate, analyte, and clarify it. The CCGIS defined herein provides GIS services and resources including the spatial and map related functionality common to all subsystems contained within the COE suite of C4I systems. The CCGIS, which is an integral component of the COE concept, relies on the other COE standard components to provide the definition for other support computing services required.

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

International Nuclear Information System (INIS)

BEVINS, R.R.

2000-01-01

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, operations input or engineering judgment

Regulatory systems-based licensing guidance documentation

International Nuclear Information System (INIS)

Delligatti, M.S.

1991-01-01

The US Nuclear Regulatory Commission (NRC) has developed a series of licensing guidance documents based on the regulatory requirements in Part 60 of Title 10 of the Code of Federal Regulations (10 CFR Part 60). This regulatory systems-based approach to licensing guidance documentation relies on the definition of the high-level waste repository in 10 CFR Part 60. A document which is important for the frame-work it gives to other programmatic licensing guidance is the Draft Regulatory Guide open-quotes Format and Content for the License Application for the High-Level Waste Repositoryclose quotes (FCRG). The FCRG describes a format and content acceptable to NRC for a high-level waste repository license application pursuant to the requirements of 10 CFR Part 60. Other licensing guidance documents will be compatible with the FCRG

DOE evaluation document for DOT 7A Type A packaging

International Nuclear Information System (INIS)

Edling, D.A.; Hopkins, D.R.; Williams, R.L.

1987-03-01

This document is a support document for the ''DOE Evaluation Document for DOT 7A Type A Packaging,'' MLM-3245, March 1987. Provided herein are details concerning the performance requirements specified in 178.350 Specification 7A, General Packaging, Type A. MLM-3245 references appropriate sections in this document. This document does not by itself meet the documentation requirements specified in 49 CFR 173.415 and has compliance value only when used in conjunction with MLM-3245

Innovative tool for specifying customer requirements

NARCIS (Netherlands)

Ellman, A.; Wendrich, Robert E.; Tiainen, T.

2014-01-01

This paper presents the design and development of an App based tool for specification of customer requirements (CR) for product development. The most Quality Function Deployment (QFD) tools and methods are system based or used as an Excel document for specification and evaluation. Nowadays tool

An Approach for Integrating the Prioritization of Functional and Nonfunctional Requirements

Directory of Open Access Journals (Sweden)

Mohammad Dabbagh

2014-01-01

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

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

Science.gov (United States)

Dabbagh, Mohammad; Lee, Sai Peck

2014-01-01

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

Fuel Handling Facility Description Document

International Nuclear Information System (INIS)

M.A. LaFountain

2005-01-01

The purpose of the facility description document (FDD) is to establish the requirements and their bases that drive the design of the Fuel Handling Facility (FHF) to allow the design effort to proceed to license application. This FDD is a living document that will be revised at strategic points as the design matures. It identifies the requirements and describes the facility design as it currently exists, with emphasis on design attributes provided to meet the requirements. This FDD was developed as an engineering tool for design control. Accordingly, the primary audience and users are design engineers. It leads the design process with regard to the flow down of upper tier requirements onto the facility. Knowledge of these requirements is essential to performing the design process. It trails the design with regard to the description of the facility. This description is a reflection of the results of the design process to date

ATLAS TDAQ/DCS Event Filter Event Handler Requirements

CERN Document Server

Bee, C P; Meessen, C; Qian, Z; Touchard, F; Green, P; Pinfold, J L; Wheeler, S; Negri, A; Scannicchio, D A; Vercesi, V

2002-01-01

The second iteration of the Software Development Process of the ATLAS Event Filter has been launched. A summary of the design phase of the first iteration is given in the introduction. The document gives constraints, use cases, functional and non-functional requirements for the Event Handler sub-system of the Event Filter.

Lifecycle management for nuclear engineering project documents

International Nuclear Information System (INIS)

Zhang Li; Zhang Ming; Zhang Ling

2010-01-01

The nuclear engineering project documents with great quantity and various types of data, in which the relationships of each document are complex, the edition of document update frequently, are managed difficultly. While the safety of project even the nuclear safety is threatened seriously by the false documents and mistakes. In order to ensure the integrality, veracity and validity of project documents, the lifecycle theory of document is applied to build documents center, record center, structure and database of document lifecycle management system. And the lifecycle management is used to the documents of nuclear engineering projects from the production to pigeonhole, to satisfy the quality requirement of nuclear engineering projects. (authors)

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

Directory of Open Access Journals (Sweden)

L. Ferrer

2018-04-01

Full Text Available 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.

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

Science.gov (United States)

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.

Systems engineering functions and requirements for the Hanford cleanup mission. First issue, Addendum 2

Energy Technology Data Exchange (ETDEWEB)

Holmes, J.J.

1994-01-01

This addendum provides the technical detail of a systems engineering functional analysis for the Hanford cleanup mission. Details of the mission analysis including mission statement, scope, problem statement, initial state definition, and final state definition are provided in the parent document. The functional analysis consists of Input Computer Automated Manufacturing Definition (IDEFO) diagrams an definitions, which will be understood by systems engineers, but which may be difficult for others to comprehend. For a more complete explanation of this work, refer to the parent document. The analysis covers the total Hanford cleanup mission including the decomposition levels at which the various Hanford programs or integrated activities are encountered.

Goals, requirements and prerequisites for teleradiology

International Nuclear Information System (INIS)

Walz, M.; Wein, B.; Lehmann, K.J.; Bolte, R.; Kilbinger, M.; Loose, R.; Guenther, R.W.; Georgi, M.

1997-01-01

Specific radiological requirements have to be considered for the realization of telemedicine. In this article the goals and requirements for an extensive introduction of teleradiology will be defined from the radiological user's point of view. Necessary medical, legal and professional prerequisites for teleradiology are presented. Essential requirements, such as data security maintenance of personal rights and standardization, must be realized. Application-specific requirements, e.g. quality and extent of teleradiological functions, as well as technological alternatives, are discussed. Each project must be carefully planned in relation to one's own needs, extent of functions and system selection. Topics, such as acknowledgement of electronic documentation, reimbursement of teleradiology and liability, must be clarified. Legal advice and the observance of quality guidelines are recommended. (orig.) [de

Waste management system functional requirements for Interim Waste Management Facilities (IWMFs) and technology demonstrations, LLWDDD [Low-Level Disposal Development and Demonstration] Program

International Nuclear Information System (INIS)

1988-03-01

The purpose of this report is to build upon the preceding decisions and body of information to prepare draft system functional requirements for each classification of waste disposal currently proposed for Low-Level Waste Disposal Development Demonstration (LLWDDD) projects. Functional requirements identify specific information and data needs necessary to satisfy engineering design criteria/objectives for Interim Waste Management Facilities. This draft will suppor the alternatives evaluation process and will continue to evolve as strategy is implemented, regulatory limits are established, technical and economic uncertainties are resolved, and waste management plans are being implemented. This document will become the planning basis for the new generation of solid LLW management facilities on new sites on the Reservation. Eighteen (18) general system requirements are identified which are applicable to all four Low-Level Waste (LLW) disposal classifications. Each classification of LLW disposal is individually addressed with respect ot waste characteristics, site considerations, facility operations, facility closure/post-closure, intruder barriers, institutional control, and performance monitoring requirements. Three initial LLW disposal sites have been proposed as locations on the ORR for the first demonstrations

FLAMMABLE GAS TECHNICAL BASIS DOCUMENT

Energy Technology Data Exchange (ETDEWEB)

KRIPPS, L.J.

2005-02-18

This document describes the qualitative evaluation of frequency and consequences for double shell tank (DST) and single shell tank (SST) representative flammable gas accidents and associated hazardous conditions without controls. The evaluation indicated that safety-significant SSCs and/or TSRS were required to prevent or mitigate flammable gas accidents. Discussion on the resulting control decisions is included. This technical basis document was developed to support of the Tank Farms Documented Safety Analysis (DSA) and describes the risk binning process for the flammable gas representative accidents and associated represented hazardous conditions. The purpose of the risk binning process is to determine the need for safety-significant structures, systems, and components (SSC) and technical safety requirement (TSR)-level controls for a given representative accident or represented hazardous condition based on an evaluation of the event frequency and consequence.

NON FUNCTIONAL REQUIREMENT TRACEABILITY AUTOMATION-AN MOBILE MULTIMEDIA APPROACH

OpenAIRE

J. Selvakumar; M. Rajaram

2012-01-01

Requirements Engineering (RE) is the area of software engineering that deals with the discovery and specification of the objectives for the system under development and the environment in which it is used including the human activities it supports. Requirement Elicitation is process of gathering requirements from stakeholders. Incorporating RE to identify non Functional Requirements (NFR) in early stages of design and implementation avoids ambiguities, conflicting requirement and other defect...

Safety of magnetic fusion facilities: Requirements

International Nuclear Information System (INIS)

1996-05-01

This Standard identifies safety requirements for magnetic fusion facilities. Safety functions are used to define outcomes that must be achieved to ensure that exposures to radiation, hazardous materials, or other hazards are maintained within acceptable limits. Requirements applicable to magnetic fusion facilities have been derived from Federal law, policy, and other documents. In addition to specific safety requirements, broad direction is given in the form of safety principles that are to be implemented and within which safety can be achieved

ITK optical links backup document

CERN Document Server

Huffman, B T; The ATLAS collaboration; Flick, T; Ye, J

2013-01-01

This document describes the proposed optical links to be used for the ITK in the phase II upgrade. The current R&D for optical links pursued in the Versatile Link group is reviewed. In particular the results demonstrating the radiation tolerance of all the on-detector components are documented. The bandwidth requirements and the resulting numerology are given.

Automatic document retrieval by the FAIRS

International Nuclear Information System (INIS)

Sasaki, Yoshio

1983-01-01

The algorithm proposed by C. Vernimb is constructed by means of two commands of ''CALL'' and ''INCLUDE'' for the FACOM Advanced Information Retrieval System (FAIRS). And its functions are demonstrated by the use of an experimental datafile containing 76,000 items in the International Nuclear Information System cumulated for a year in 1980. The experiment is conducted for a search topic ''possible migration of radionuclides leached from radioactive waste stored in underground'' for which the datafile contains many relevant documents. Four sets of relevant documents (hits) are prepared to input as original samples at the beginning of on-line search. The sets consist of three hits respectively and are different from each other in indexing pattern. By the experiment, the recall ratio of 80% is obtained with the precision ratio of more than 50%, but these is difference in both seach time spent and the number of operational steps among the sets. Following detailed analysis of the results, discussions are made on the subjects to require further studies. (author)

The significance of radiological control documentation in litigation

International Nuclear Information System (INIS)

Lodde, G.M.; Murphy, T.D.

1988-01-01

Commercial nuclear facilities accumulate radiological control program data and documents generated and retained pursuant to regulatory, license, and technical specification requirements. During and following the Three Mile Island Unit 2 (TMI-2) accident, many documents were produced that would not normally have been produced. Shortly after the accident, the US Nuclear Regulatory Commission (NRC) issued an order requiring the retention of all data, including documentary material and physical samples relating to the TMI-2 accident (44 Fed. Reg. 30788, May 29, 1979). Three years later, the NRC vacated the requirement to retain catalogued physical samples, provided the radioactivity data had been properly recorded, allowing disposal of many samples. After the TMI-2 accident, GPU Nuclear Corporation (GPU) designed and implemented an effective and efficient record management program for TMI. This Computer-Assisted Records and Information Retrieval System (CARIRS) was developed to assess the official record for TMI, which is maintained as a microform. GPU also retains hard copies of selected radiological control documents for potential litigation. This paper describes the use of radiological control documentation in the postaccident litigation and the magnitude of document production required to support that litigation

Assessing the Effect of an Educational Intervention on Nurses' and Patient Care Assistants' Comprehension and Documentation of Functional Ability in Pediatric Patients with Sickle Cell Disease.

Science.gov (United States)

Bernier, Katherine M; Strobel, Megan; Lucas, Ruth

2018-04-13

In 2014, the Youth Acute Pain Functional Ability Questionnaire (YAPFAQ) was developed to investigate patient's self-rated functional ability during times of acute pain in the inpatient clinical setting. Although it has great potential, the application of this tool has not been made a standard of care. The purpose of this multiple methods study was to determine if, through an educational intervention, hospital staff could consistently document the YAPFAQ in children with sickle cell disease (SCD) during a vaso-occlusive episode. Twenty-two staff members participated in an educational intervention and semi-structured group discussions. Pre/post surveys measured knowledge of the YAPFAQ before and after the intervention. Group discussions were recorded, transcribed verbatim, and analyzed for thematic clusters. Retrospective chart reviews of children with SCD were reviewed for YAPFAQ documentation frequency before and after the intervention. Staff knowledge of who completes the YAPFAQ increased after the intervention, (pcontinues to hold high potential for directing nursing care, but requires staff investment for clinical practice change. A seamless integration between nursing education and translation through EHR is recommended as technology continues to integrate into nursing practice. Copyright © 2018 Elsevier Inc. All rights reserved.

Spent Nuclear Fuel Project document control and Records Management Program Description

International Nuclear Information System (INIS)

MARTIN, B.M.

2000-01-01

The Spent Nuclear Fuel (SNF) Project document control and records management program, as defined within this document, is based on a broad spectrum of regulatory requirements, Department of Energy (DOE) and Project Hanford and SNF Project-specific direction and guidance. The SNF Project Execution Plan, HNF-3552, requires the control of documents and management of records under the auspices of configuration control, conduct of operations, training, quality assurance, work control, records management, data management, engineering and design control, operational readiness review, and project management and turnover. Implementation of the controls, systems, and processes necessary to ensure compliance with applicable requirements is facilitated through plans, directives, and procedures within the Project Hanford Management System (PHMS) and the SNF Project internal technical and administrative procedures systems. The documents cited within this document are those which directly establish or define the SNF Project document control and records management program. There are many peripheral documents that establish requirements and provide direction pertinent to managing specific types of documents that, for the sake of brevity and clarity, are not cited within this document

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

Science.gov (United States)

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

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

Embedding the shapes of regions of interest into a Clinical Document Architecture document.

Science.gov (United States)

Minh, Nguyen Hai; Yi, Byoung-Kee; Kim, Il Kon; Song, Joon Hyun; Binh, Pham Viet

2015-03-01

Sharing a medical image visually annotated by a region of interest with a remotely located specialist for consultation is a good practice. It may, however, require a special-purpose (and most likely expensive) system to send and view them, which is an unfeasible solution in developing countries such as Vietnam. In this study, we design and implement interoperable methods based on the HL7 Clinical Document Architecture and the eXtensible Markup Language Stylesheet Language for Transformation standards to seamlessly exchange and visually present the shapes of regions of interest using web browsers. We also propose a new integration architecture for a Clinical Document Architecture generator that enables embedding of regions of interest and simultaneous auto-generation of corresponding style sheets. Using the Clinical Document Architecture document and style sheet, a sender can transmit clinical documents and medical images together with coordinate values of regions of interest to recipients. Recipients can easily view the documents and display embedded regions of interest by rendering them in their web browser of choice. © The Author(s) 2014.

Lessons learned using HAMMLAB experimenter systems: Input for HAMMLAB 2000 functional requirements

International Nuclear Information System (INIS)

Sebok, Angelia L.

1998-02-01

To design a usable HAMMLAB 2000, lessons learned from use of the existing HAMMLAB must be documented. User suggestions are important and must be taken into account. Different roles in HAMMLAB experimental sessions are identified, and major functions of each role were specified. A series of questionnaires were developed and administered to different users of HAMMLAB, each tailored to the individual job description. The results of those questionnaires are included in this report. Previous HAMMLAB modification recommendations were also reviewed, to provide input to this document. A trial experimental session was also conducted, to give an overview of the tasks in HAMMLAB. (author)

Information Technology Act 2000 in India - Authentication of E-Documents

Directory of Open Access Journals (Sweden)

R. G. Pawar

2007-06-01

Full Text Available The Information Technology Act 2000 has enacted in India on 9th June 2000. This Act has mentioned provision of authentication of electronic document. It is the need of hour at that time that such provision is needed in the Indian Law system, especially for electronic commerce and electronic governance. Electronic commerce”, which involve the use of alternatives to paper based methods of communication and storage information. To do electronic commerce there should be authentication of particular document. The working of internet is the documents are traveling in terms of bits from one destination to other destination, through various media like – Co-axial cable, fiber optic, satellite etc. While traveling this document there is probability of making changes in that document by any third party is high or some document may get changed due to noise/disturbance in communication media. This Act required to provide legal recognition carried out by means of electronic data interchange and other means of electronic communication.In this paper researchers studied technological aspects of Information Technology Act 2000 like hash function, encryption, decryption, public key, private key etc. and its process. This paper gives details about certifying authority in detail. There should be some mechanism that will take care of document, that what ever the document is received should be the authentic one and it would not get changed in any manner due to any cause.

IDC System Specification Document Version 1.1.

Energy Technology Data Exchange (ETDEWEB)

Harris, James M. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Lober, Randall R. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States)

2015-02-01

This document contains the system specifications derived to satisfy the system requirements found in the IDC System Requirements Document for the IDC Reengineering Phase 2 project. Revisions Version Date Author/Team Revision Description Authorized by V1.0 12/2014 IDC Reengineering Project Team Initial delivery M. Harris V1.1 2/2015 IDC Reengineering Project Team Iteration I2 Review Comments M. Harris

IDC Re-Engineering Phase 2 System Specification Document Version 1.5

Energy Technology Data Exchange (ETDEWEB)

Satpathi, Meara Allena [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Burns, John F. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Harris, James M. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States)

2017-01-01

This document contains the system specifications derived to satisfy the system requirements found in the IDC System Requirements Document for the IDC Re-Engineering Phase 2 project. This System Specification Document (SSD) defines waveform data processing requirements for the International Data Centre (IDC) of the Comprehensive Nuclear Test Ban Treaty Organization (CTBTO). The routine processing includes characterization of events with the objective of screening out events considered to be consistent with natural phenomena or non-nuclear, man-made phenomena. This document does not address requirements concerning acquisition, processing and analysis of radionuclide data but does include requirements for the dissemination of radionuclide data and products.

WRAP module 1 DMS/PCS interface definition document

International Nuclear Information System (INIS)

Weidert, J.R.

1994-01-01

This document has been developed to define the computer software interfaces between Waste Receiving ampersand Processing Module 1 (WRAP 1) computer systems. The interfaces include those data interfaces which exist between the Plant Control System (PCS) and Data Management System (DMS), between the DMS and Non-Destructive Assay (NDA) equipment, and between the DMS and Boxed Waste Assay System (BWAS) equipment. In addition to the data interfaces between the various WRAP computer systems; there are also a number of control functions between WRAP 1 equipment. These control function interfaces have been specified in WRAP Construction specification 13462 and the associated equipment specifications. The PCS vendor has been listed in the equipment specifications as the responsible party for establishing the final control system interface between the PCS and Non-Destructive Examination (NDE) Equipment, the PCS and Non-Destructive Assay (NDA) Equipment, and the PCS and BWAS equipment. The primary interface requirements between these systems are addressed in Specification Sections 13462, 13532, 13533, 13026, 13537, and 13538. Additional requirements may be found in other specification sections such as the Automatic Stacker Retriever System (AS/RS) Technical Specification 14520 and the WRAP 1 Data Management System Software Requirements Specification

Exploration on Automated Software Requirement Document Readability Approaches

OpenAIRE

Chen, Mingda; He, Yao

2017-01-01

Context. The requirements analysis phase, as the very beginning of software development process, has been identified as a quite important phase in the software development lifecycle. Software Requirement Specification (SRS) is the output of requirements analysis phase, whose quality factors play an important role in the evaluation work. Readability is a quite important SRS quality factor, but there are few available automated approaches for readability measurement, because of the tight depend...

200 Area TEDF interface control document

Energy Technology Data Exchange (ETDEWEB)

Brown, M.J.; Hildebrand, R.A.

1994-11-15

Because the TEDF does not have any treatment or retention capacity, strict control at the generator interface is essential to operate the TEDF in compliance with good engineering practices, Hanford site requirements, and the 216 Discharge Permit. The information in the Interface Control Document (ICD) forms the basis of understanding between all parties involved in the TEDF; DOE, WHC, and the generating facilities. The ICD defines the controlling document hierarchy; LEF, and generator responsibilities; monitoring and sampling requirements; and specifies the TEDF/Generator Interface points.

200 Area TEDF interface control document

International Nuclear Information System (INIS)

Brown, M.J.; Hildebrand, R.A.

1994-01-01

Because the TEDF does not have any treatment or retention capacity, strict control at the generator interface is essential to operate the TEDF in compliance with good engineering practices, Hanford site requirements, and the 216 Discharge Permit. The information in the Interface Control Document (ICD) forms the basis of understanding between all parties involved in the TEDF; DOE, WHC, and the generating facilities. The ICD defines the controlling document hierarchy; LEF, and generator responsibilities; monitoring and sampling requirements; and specifies the TEDF/Generator Interface points

An analysis of electronic document management in oncology care.

Science.gov (United States)

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

2012-06-01

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

Document organization by means of graphs

Directory of Open Access Journals (Sweden)

Santa Vallejo Figueroa

2016-12-01

Full Text Available Nowadays documents are the main way to represent information and knowledge in several domains. Continuously users store documents in hard disk or online media according to some personal organization based on topics, but such documents can contain one or more topics. This situation makes hard to access documents when is required. The current search engines are based on the name of file or content, but where the desired term or terms must match exactly as are in the content. In this paper, a method for organize documents by means of graphs is proposed, taking into account the topics of the documents. For this a graph for each document is generated taking into account synonyms, semantic related terms, hyponyms, and hypernyms of nouns and verbs contained in documents. The proposal have been compares against Google Desktop and LogicalDoc with interesting results.

Research on Generating Method of Embedded Software Test Document Based on Dynamic Model

Science.gov (United States)

Qu, MingCheng; Wu, XiangHu; Tao, YongChao; Liu, Ying

2018-03-01

This paper provides a dynamic model-based test document generation method for embedded software that provides automatic generation of two documents: test requirements specification documentation and configuration item test documentation. This method enables dynamic test requirements to be implemented in dynamic models, enabling dynamic test demand tracking to be easily generated; able to automatically generate standardized, standardized test requirements and test documentation, improved document-related content inconsistency and lack of integrity And other issues, improve the efficiency.

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

Science.gov (United States)

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

1982-01-01

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

Technical Basis Document (TBD) and user guides

International Nuclear Information System (INIS)

Chiaro, P.J. Jr.

1998-09-01

A Technical Basis Document (TBD) should provide the background information for establishment of an instrument's operational requirements. Due to the amount and location of DOE facilities, no one set of requirements is possible. Operational requirements will vary based on the local environments and missions at each facility. Environmental conditions that can affect an instrument's operations are ambient temperature, humidity, and radio frequency, and to a lesser extent, magnetic fields, and interfering ionizing radiations. Consideration should also be made regarding how an instrument is to be used. If an instrument will be transported around the facility, vibration and shock can cause problems if they are not addressed in the TBD. This document provides guidance for the development of a TBD. This document applies to radiation instruments used for personnel and equipment contamination monitoring, dose rate monitoring, and air monitoring

7 CFR 1710.407 - Loan documents.

Science.gov (United States)

2010-01-01

... 7 Agriculture 11 2010-01-01 2010-01-01 false Loan documents. 1710.407 Section 1710.407 Agriculture... GENERAL AND PRE-LOAN POLICIES AND PROCEDURES COMMON TO ELECTRIC LOANS AND GUARANTEES Application Requirements and Procedures for Loans § 1710.407 Loan documents. Following approval of a loan, RUS will forward...

Multiple sclerosis documentation system (MSDS): moving from documentation to management of MS patients.

Science.gov (United States)

Ziemssen, Tjalf; Kempcke, Raimar; Eulitz, Marco; Großmann, Lars; Suhrbier, Alexander; Thomas, Katja; Schultheiss, Thorsten

2013-09-01

The long disease duration of multiple sclerosis and the increasing therapeutic options require a individualized therapeutic approach which should be carefully documented over years of observation. To switch from MS documentation to an innovative MS management, new computer- and internet-based tools could be implemented as we could demonstrate with the novel computer-based patient management system "multiple sclerosis management system 3D" (MSDS 3D). MSDS 3D allows documentation and management of visit schedules and mandatory examinations via defined study modules by integration of data input from various sources (patients, attending physicians and MS nurses). It provides forms for the documentation of patient visits as well as clinical and diagnostic findings. Information can be collected via interactive touch screens. Specific modules allow the management of highly efficacious treatments as natalizumab or fingolimod. MSDS can be used to transfer the documented data to databases as, e.g. the registry of the German MS society or REGIMS. MSDS has already been implemented successfully in clinical practice and is currently being evaluated in a multicenter setting. High-quality management and documentation are crucial for improvements in clinical practice and research work.

Early Quantitative Assessment of Non-Functional Requirements

NARCIS (Netherlands)

Kassab, M.; Daneva, Maia; Ormandjieva, O.

2007-01-01

Non-functional requirements (NFRs) of software systems are a well known source of uncertainty in effort estimation. Yet, quantitatively approaching NFR early in a project is hard. This paper makes a step towards reducing the impact of uncertainty due to NRF. It offers a solution that incorporates

Thermal conditions and functional requirements for molten fuel containment

International Nuclear Information System (INIS)

Kang, C.S.; Torri, A.

1980-05-01

This paper discusses the configuration and functional requirements for the molten fuel containment system (MFCS) in the GCFR demonstration plant design. Meltdown conditions following a loss of shutdown cooling (LOSC) accident were studied to define the core debris volume for a realistic meltdown case. Materials and thicknesses of the molten fuel container were defined. Stainless steel was chosen as the sacrificial material and magnesium oxide was chosen as the crucible material. Thermal conditions for an expected quasi-steady state were analyzed. Highlights of the functional requirements which directly affect the MFCS design are discussed

Model Penentuan Nilai Target Functional Requirement Berbasis Utilitas

Directory of Open Access Journals (Sweden)

Cucuk Nur Rosyidi

2012-01-01

Full Text Available In a product design and development process, a designer faces a problem to decide functional requirement (FR target values. That decision is made under a risk since it is conducted in the early design phase using incomplete information. Utility function can be used to reflect the decision maker attitude towards the risk in making such decision. In this research, we develop a utility-based model to determine FR target values using quadratic utility function and information from Quality Function Deployment (QFD. A pencil design is used as a numerical example using quadratic utility function for each FR. The model can be applied for balancing customer and designer interest in determining FR target values.

The development of functional requirement for integrated test facility

International Nuclear Information System (INIS)

Sim, B.S.; Oh, I.S.; Cha, K.H.; Lee, H.C.

1994-01-01

An Integrated Test Facility (ITF) is a human factors experimental environment comprised of a nuclear power plant function simulator, man-machine interfaces (MMI), human performance recording systems, and signal control and data analysis systems. In this study, we are going to describe how the functional requirements are developed by identification of both the characteristics of generic advanced control rooms and the research topics of world-wide research interest in human factors community. The functional requirements of user interface developed in this paper together with those of the other elements will be used for the design and implementation of the ITF which will serve as the basis for experimental research on a line of human factors topics. (author). 15 refs, 1 fig

10 CFR 850 Implementation of Requirements

Energy Technology Data Exchange (ETDEWEB)

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

System requirements and design description for the environmental requirements management interface (ERMI)

International Nuclear Information System (INIS)

Biebesheimer, E.

1997-01-01

This document describes system requirements and the design description for the Environmental Requirements Management Interface (ERMI). The ERMI database assists Tank Farm personnel with scheduling, planning, and documenting procedure compliance, performance verification, and selected corrective action tracking activities for Tank Farm S/RID requirements. The ERMI database was developed by Science Applications International Corporation (SAIC). This document was prepared by SAIC and edited by LMHC

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

Science.gov (United States)

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

Performance requirements for the single-shell tank

International Nuclear Information System (INIS)

GRENARD, C.E.

1999-01-01

This document provides performance requirements for the waste storage and waste feed delivery functions of the Single-Shell Tank (SST) System. The requirements presented here in will be used as a basis for evaluating the ability of the system to complete the single-shell tank waste feed delivery mission. They will also be used to select the technology or technologies for retrieving waste from the tanks selected for the single-shell tank waste feed delivery mission, assumed to be 241-C-102 and 241-C-104. This revision of the Performance Requirements for the SST is based on the findings of the SST Functional Analysis, and are reflected in the current System Specification for the SST System

Simplifying documentation while approaching site closure: integrated health and safety plans as documented safety analysis

International Nuclear Information System (INIS)

Brown, Tulanda

2003-01-01

At the Fernald Closure Project (FCP) near Cincinnati, Ohio, environmental restoration activities are supported by Documented Safety Analyses (DSAs) that combine the required project-specific Health and Safety Plans, Safety Basis Requirements (SBRs), and Process Requirements (PRs) into single Integrated Health and Safety Plans (I-HASPs). By isolating any remediation activities that deal with Enriched Restricted Materials, the SBRs and PRs assure that the hazard categories of former nuclear facilities undergoing remediation remain less than Nuclear. These integrated DSAs employ Integrated Safety Management methodology in support of simplified restoration and remediation activities that, so far, have resulted in the decontamination and demolition (D and D) of over 150 structures, including six major nuclear production plants. This paper presents the FCP method for maintaining safety basis documentation, using the D and D I-HASP as an example

Preparation of plant and system design description documents

International Nuclear Information System (INIS)

1989-01-01

This standard prescribes the purpose, scope, organization, and content of plant design requirements (PDR) documents and system design descriptions (SDDs), to provide a unified approach to their preparation and use by a project as the principal means to establish the plant design requirements and to establish, describe, and control the individual system designs from conception and throughout the lifetime of the plant. The Electric Power Research Institute's Advanced Light Water Reactor (LWR) Requirements Document should be considered for LWR plants

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

Science.gov (United States)

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

2008-01-01

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

Documentation Panels Enhance Teacher Education Programs

Science.gov (United States)

Warash, Bobbie Gibson

2005-01-01

Documentation of children's projects is advantageous to their learning process and is also a good method for student teachers to observe the process of learning. Documentation panels are a unique way to help student teachers understand how children learn. Completing a panel requires a student teacher to think through a process. Teachers must learn…

Development of requirements tracking and verification system for the software design of distributed control system

Energy Technology Data Exchange (ETDEWEB)

Jung, Chul Hwan; Kim, Jang Yeol; Kim, Jung Tack; Lee, Jang Soo; Ham, Chang Shik [Korea Atomic Energy Research Institute, Taejon (Korea, Republic of)

1999-12-31

In this paper a prototype of Requirement Tracking and Verification System(RTVS) for a Distributed Control System was implemented and tested. The RTVS is a software design and verification tool. The main functions required by the RTVS are managing, tracking and verification of the software requirements listed in the documentation of the DCS. The analysis of DCS software design procedures and interfaces with documents were performed to define the user of the RTVS, and the design requirements for RTVS were developed. 4 refs., 3 figs. (Author)

Development of requirements tracking and verification system for the software design of distributed control system

Energy Technology Data Exchange (ETDEWEB)

Jung, Chul Hwan; Kim, Jang Yeol; Kim, Jung Tack; Lee, Jang Soo; Ham, Chang Shik [Korea Atomic Energy Research Institute, Taejon (Korea, Republic of)

1998-12-31

In this paper a prototype of Requirement Tracking and Verification System(RTVS) for a Distributed Control System was implemented and tested. The RTVS is a software design and verification tool. The main functions required by the RTVS are managing, tracking and verification of the software requirements listed in the documentation of the DCS. The analysis of DCS software design procedures and interfaces with documents were performed to define the user of the RTVS, and the design requirements for RTVS were developed. 4 refs., 3 figs. (Author)

Functional Size Measurement applied to UML-based user requirements

NARCIS (Netherlands)

van den Berg, Klaas; Dekkers, Ton; Oudshoorn, Rogier; Dekkers, T.

There is a growing interest in applying standardized methods for Functional Size Measurement (FSM) to Functional User Requirements (FUR) based on models in the Unified Modelling Language (UML). No consensus exists on this issue. We analyzed the demands that FSM places on FURs. We propose a

Modeling the Non-functional Requirements in the Context of Usability, Performance, Safety and Security

OpenAIRE

Sadiq, Mazhar

2007-01-01

Requirement engineering is the most significant part of the software development life cycle. Until now great emphasis has been put on the maturity of the functional requirements. But with the passage of time it reveals that the success of software development does not only pertain to the functional requirements rather non-functional requirements should also be taken into consideration. Among the non-functional requirements usability, performance, safety and security are considered important. ...

45 CFR 641.16 - Preparation of environmental documents, generally.

Science.gov (United States)

2010-10-01

... affect climate and weather patterns; (3) May adversely affect air or water quality; (4) May affect... knowledge and expertise. (e) Type of environmental document. The type of environmental document required... bases for much of the year, and the need to obtain items or materials requiring long lead times), it may...

Document development, management and transmission

International Nuclear Information System (INIS)

Meister, K.

1998-01-01

Environmental monitoring can only be carried out by means of cartographic outputs allowing the representation of information in a compressed way and with a local reference. On account of this requirement and the continuously growing importance of international data exchange the development of a universal tool for the combination of data to so-called documents has been started for the management and for the exchange of these documents with other systems. (R.P.)

Transforming User Needs into Functional Requirements for an Antibiotic Clinical Decision Support System

Science.gov (United States)

Bright, T.J.

2013-01-01

Summary Background Many informatics studies use content analysis to generate functional requirements for system development. Explication of this translational process from qualitative data to functional requirements can strengthen the understanding and scientific rigor when applying content analysis in informatics studies. Objective To describe a user-centered approach transforming emergent themes derived from focus group data into functional requirements for informatics solutions and to illustrate these methods to the development of an antibiotic clinical decision support system (CDS). Methods The approach consisted of five steps: 1) identify unmet therapeutic planning information needs via Focus Group Study-I, 2) develop a coding framework of therapeutic planning themes to refine the domain scope to antibiotic therapeutic planning, 3) identify functional requirements of an antibiotic CDS system via Focus Group Study-II, 4) discover informatics solutions and functional requirements from coded data, and 5) determine the types of information needed to support the antibiotic CDS system and link with the identified informatics solutions and functional requirements. Results The coding framework for Focus Group Study-I revealed unmet therapeutic planning needs. Twelve subthemes emerged and were clustered into four themes; analysis indicated a need for an antibiotic CDS intervention. Focus Group Study-II included five types of information needs. Comments from the Barrier/Challenge to information access and Function/Feature themes produced three informatics solutions and 13 functional requirements of an antibiotic CDS system. Comments from the Patient, Institution, and Domain themes generated required data elements for each informatics solution. Conclusion This study presents one example explicating content analysis of focus group data and the analysis process to functional requirements from narrative data. Illustration of this 5-step method was used to develop an

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

Science.gov (United States)

1992-01-01

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

Feed tank transfer requirements

International Nuclear Information System (INIS)

Freeman-Pollard, J.R.

1998-01-01

This document presents a definition of tank turnover; DOE responsibilities; TWRS DST permitting requirements; TWRS Authorization Basis (AB) requirements; TWRS AP Tank Farm operational requirements; unreviewed safety question (USQ) requirements; records and reporting requirements, and documentation which will require revision in support of transferring a DST in AP Tank Farm to a privatization contractor for use during Phase 1B

Center-TRACON Automation System (CTAS) En Route Trajectory Predictor Requirements and Capabilities

Science.gov (United States)

Vivona, Robert; Cate, Karen Tung

2013-01-01

This requirements framework document is designed to support the capture of requirements and capabilities for state-of-the-art trajectory predictors (TPs). This framework has been developed to assist TP experts in capturing a clear, consistent, and cross-comparable set of requirements and capabilities. The goal is to capture capabilities (types of trajectories that can be built), functional requirements (including inputs and outputs), non-functional requirements (including prediction accuracy and computational performance), approaches for constraint relaxation, and input uncertainties. The sections of this framework are based on the Common Trajectory Predictor structure developed by the FAA/Eurocontrol Cooperative R&D Action Plan 16 Committee on Common Trajectory Prediction. It is assumed that the reader is familiar with the Common TP Structure.1 This initial draft is intended as a first cut capture of the En Route TS Capabilities and Requirements. As such, it contains many annotations indicating possible logic errors in the CTAS code or in the description provided. It is intended to work out the details of the annotations with NASA and to update this document at a later time.

49 CFR 237.155 - Documents and records.

Science.gov (United States)

2010-10-01

..., DEPARTMENT OF TRANSPORTATION BRIDGE SAFETY STANDARDS Documentation, Records, and Audits of Bridge Management Programs § 237.155 Documents and records. Each track owner required to implement a bridge management... protected by a security system that incorporates a user identity and password, or a comparable method, to...

NWTS program criteria for mined geologic disposal of nuclear waste: functional requirements and performance criteria for waste packages for solidified high-level waste and spent fuel

International Nuclear Information System (INIS)

1982-07-01

The Department of Energy (DOE) has primary federal responsibility for the development and implementation of safe and environmentally acceptable nuclear waste disposal methods. Currently, the principal emphasis in the program is on emplacement of nuclear wastes in mined geologic repositories well beneath the earth's surface. A brief description of the mined geologic disposal system is provided. The National Waste Terminal Storage (NWTS) program was established under DOE's predecessor, the Energy Research and Development Administration, to provide facilities for the mined geologic disposal of radioactive wastes. The NWTS program includes both the development and the implementation of the technology necessary for designing, constructing, licensing, and operating repositories. The program does not include the management of processing radioactive wastes or of transporting the wastes to repositories. The NWTS-33 series, of which this document is a part, provides guidance for the NWTS program in the development and implementation of licensed mined geologic disposal systems for solidified high-level and transuranic (TRU) wastes. This document presents the functional requirements and performance criteria for waste packages for solidified high-level waste and spent fuel. A separate document to be developed, NWTS-33(4b), will present the requirements and criteria for waste packages for TRU wastes. The hierarchy and application of these requirements and criteria are discussed in Section 2.2

From Medieval Philosophy to the Virtual Library: a descriptive framework for scientific knowledge and documentation as basis for document retrieval

Directory of Open Access Journals (Sweden)

Frances Morrissey

2001-11-01

Full Text Available This paper examines the conceptual basis of document retrieval systems for the Virtual Library in science and technology. It does so through analysing some cognitive models for scientific knowledge, drawing on philosophy, sociology and linguistics. It is important to consider improvements in search/ retrieval functionalities for scientific documents because knowledge creation and transfer are integral to the functioning of scientific communities, and on a larger scale, science and technology are central to the knowledge economy. This paper proposes four new and innovative understandings. Firstly, it is proposed that formal scientific communication constitutes the documentation and dissemination of concepts, and that conceptualism is a useful philosophical basis for study. Second, it is proposed that the scientific document is a dyadic con-struct, being both the physical manifestation as an encoded medium, and also being the associated knowledge, or intangible ideation, that is carried within the document. Third, it is shown that major philosophers of science divide science into three main activities, dealing with data, derived or inferred laws, and the axioms or the paradigm. Fourth, it is demonstrated that the data, information and conceptual frameworks carried by a scientific document, as different levels of signification or semiotic systems, can each be characterised in ways assisting in search and retrieval functionalities for the Virtual Library.

Experimentation on accuracy of non functional requirement prioritization approaches for different complexity projects

OpenAIRE

Raj Kumar Chopra; Varun Gupta; Durg Singh Chauhan

2016-01-01

Non functional requirements must be selected for implementation together with functional requirements to enhance the success of software projects. Three approaches exist for performing the prioritization of non functional requirements using the suitable prioritization technique. This paper performs experimentation on three different complexity versions of the industrial software project using cost-value prioritization technique employing three approaches. Experimentation is conducted to analy...

Specifications for human factors guiding documents

Energy Technology Data Exchange (ETDEWEB)

Rhodes, W; Szlapetis, I; MacGregor, C [Rhodes and Associates Inc., Toronto, ON (Canada)

1995-04-01

This report specifies the content, function and appearance of three proposed human factors guiding documents to be used by the Atomic Energy Control board and its licensees. These three guiding documents, to be developed at a later date, are: (a) Human Factors Process Guide; (b) Human Factors Activities Guide; and (c) Human Factors Design Integration Guide. The specifications were developed by examining the best documents as identified in a previous contract with the AECB (Review of Human Factors Guidelines and Methods by W. Rhodes, I. Szlapetis et al. 1992), and a brief literature review. The best features and content were selected from existing documents and used to develop specifications for the guiding documents. The developer of the actual guides would use these specifications to produce comprehensive and consolidated documents at a later date. (author). 128 ref., 7 figs.

Specifications for human factors guiding documents

International Nuclear Information System (INIS)

Rhodes, W.; Szlapetis, I.; MacGregor, C.

1995-04-01

This report specifies the content, function and appearance of three proposed human factors guiding documents to be used by the Atomic Energy Control board and its licensees. These three guiding documents, to be developed at a later date, are: (a) Human Factors Process Guide; (b) Human Factors Activities Guide; and (c) Human Factors Design Integration Guide. The specifications were developed by examining the best documents as identified in a previous contract with the AECB (Review of Human Factors Guidelines and Methods by W. Rhodes, I. Szlapetis et al. 1992), and a brief literature review. The best features and content were selected from existing documents and used to develop specifications for the guiding documents. The developer of the actual guides would use these specifications to produce comprehensive and consolidated documents at a later date. (author). 128 ref., 7 figs

Upon e-Documents: Evolution or Involution on GED Market

Directory of Open Access Journals (Sweden)

Mircea GEORGESCU

2006-01-01

Full Text Available In many organizations, vital information is trapped within individual desktops and fragmented in server silos across the enterprise. Manual, ad-hoc processes create inefficiencies, confusion and delays as employees waste time searching for important information. Organizations must find safer and easier ways to access, manage and share their content. Document and file management solutions designed to be used across the organization can help achieve these goals and reduce the total cost of managing content throughout the organization. If you decide to use an EDMS, your selection requires a careful, considered balance between your legal requirements and your technological options. The decision to use an EDMS requires significant planning and analysis. Managing documents more effectively, controlling costs associated with documents and document processes, and using resources more efficiently has become and will continue to be increasingly important to businesses and IT organizations.

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

Science.gov (United States)

1975-01-01

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

Experimentation on accuracy of non functional requirement prioritization approaches for different complexity projects

Directory of Open Access Journals (Sweden)

Raj Kumar Chopra

2016-09-01

Full Text Available Non functional requirements must be selected for implementation together with functional requirements to enhance the success of software projects. Three approaches exist for performing the prioritization of non functional requirements using the suitable prioritization technique. This paper performs experimentation on three different complexity versions of the industrial software project using cost-value prioritization technique employing three approaches. Experimentation is conducted to analyze the accuracy of individual approaches and the variation of accuracy with the complexity of the software project. The results indicate that selecting non functional requirements separately, but in accordance with functionality has higher accuracy amongst the other two approaches. Further, likewise other approaches, it witnesses the decrease in accuracy with increase in software complexity but the decrease is minimal.

Understanding the technical content of requirements in specification document

DEFF Research Database (Denmark)

Sudin, Mohd Nizam Bin; Ahmed-Kristensen, Saeema

2011-01-01

development process, is essential to be devised in advance. To achieve this aim, understanding how to formulate a good requirement is necessary and it is only possible if design engineers understand the technical content of a requirement. In aiming to understand the technical content of a requirement...

Tank Waste Remediation System Projects Document Control Plan

International Nuclear Information System (INIS)

Slater, G.D.; Halverson, T.G.

1994-01-01

The purpose of this Tank Waste Remediation System Projects Document Control Plan is to provide requirements and responsibilities for document control for the Hanford Waste Vitrification Plant (HWVP) Project and the Initial Pretreatment Module (IPM) Project

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

Science.gov (United States)

2005-01-01

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

Quantifying Functional Reuse from Object Oriented Requirements Specifications

NARCIS (Netherlands)

Condori-Fernandez, Nelly; Condori-Fernández, N.; Pastor, O; Daneva, Maia; Abran, A.; Castro, J.; Quer, C.; Carvallo, J. B.; Fernandes da Silva, L.

2008-01-01

Software reuse is essential in improving efficiency and productivity in the software development process. This paper analyses reuse within requirements engineering phase by taking and adapting a standard functional size measurement method, COSMIC FFP. Our proposal attempts to quantify reusability

Virtual Library Design Document; TOPICAL

International Nuclear Information System (INIS)

M. A. deLamare

2001-01-01

The objective of this document is to establish a design for the virtual library user and administrative layers that complies with the requirements of the virtual library software specification and subordinate module specification

Piles, tabs and overlaps in navigation among documents

DEFF Research Database (Denmark)

Jakobsen, Mikkel Rønne; Hornbæk, Kasper

2010-01-01

Navigation among documents is a frequent, but ill supported activity. Overlapping or tabbed documents are widespread, but they offer limited visibility of their content. We explore variations on navigation support: arranging documents with tabs, as overlapping windows, and in piles. In an experim......Navigation among documents is a frequent, but ill supported activity. Overlapping or tabbed documents are widespread, but they offer limited visibility of their content. We explore variations on navigation support: arranging documents with tabs, as overlapping windows, and in piles....... In an experiment we compared 11 participants’ navigation with these variations and found strong task effects. Overall, overlapping windows were preferred and their structured layout worked well with some tasks. Surprisingly, tabbed documents were efficient in tasks requiring simply finding a document. Piled...... on document navigation and its support by piling....

AUDIT plan documenting method

International Nuclear Information System (INIS)

Cornecsu, M.

1995-01-01

The work describes a method of documenting the AUDIT plan upon the basis of two quantitative elements resulting from quality assurance program appraisal system function implementation degree as established from the latest AUDIT performed an system function weight in QAP, respectively, appraised by taking into account their significance for the activities that are to be performed in the period for which the AUDITs are planned. (Author) 3 Figs., 2 Refs

L-Band Digital Aeronautical Communications System Engineering - Concepts of Use, Systems Performance, Requirements, and Architectures

Science.gov (United States)

Zelkin, Natalie; Henriksen, Stephen

2010-01-01

This NASA Contractor Report summarizes and documents the work performed to develop concepts of use (ConUse) and high-level system requirements and architecture for the proposed L-band (960 to 1164 MHz) terrestrial en route communications system. This work was completed as a follow-on to the technology assessment conducted by NASA Glenn Research Center and ITT for the Future Communications Study (FCS). ITT assessed air-to-ground (A/G) communications concepts of use and operations presented in relevant NAS-level, international, and NAS-system-level documents to derive the appropriate ConUse relevant to potential A/G communications applications and services for domestic continental airspace. ITT also leveraged prior concepts of use developed during the earlier phases of the FCS. A middle-out functional architecture was adopted by merging the functional system requirements identified in the bottom-up assessment of existing requirements with those derived as a result of the top-down analysis of ConUse and higher level functional requirements. Initial end-to-end system performance requirements were derived to define system capabilities based on the functional requirements and on NAS-SR-1000 and the Operational Performance Assessment conducted as part of the COCR. A high-level notional architecture of the L-DACS supporting A/G communication was derived from the functional architecture and requirements.

Managing the consistency of distributed documents

OpenAIRE

Nentwich, C.

2005-01-01

Many businesses produce documents as part of their daily activities: software engineers produce requirements specifications, design models, source code, build scripts and more; business analysts produce glossaries, use cases, organisation charts, and domain ontology models; service providers and retailers produce catalogues, customer data, purchase orders, invoices and web pages. What these examples have in common is that the content of documents is often semantically relate...

Functional requirements for the Automated Transportation Management System: TTP number: RL 439002

Energy Technology Data Exchange (ETDEWEB)

Portsmouth, J.H. [Westinghouse Hanford Co., Richland, WA (United States)

1992-12-31

This requirements analysis, documents Department of Energy (DOE) transportation management procedures for the purpose of providing a clear and mutual understanding between users and designers of the proposed Automated Transportation Management System (ATMS). It is imperative that one understand precisely how DOE currently performs traffic management tasks; only then can an integrated system be proposed that successfully satisfies the major requirements of transportation managers and other system users. Accordingly, this report describes the current workings of DOE transportation organizations and then proposes a new system which represents a synthesis of procedures (both current and desired) which forms the basis for further systems development activities.

Quality functions for requirements engineering in system development methods.

Science.gov (United States)

Johansson, M; Timpka, T

1996-01-01

Based on a grounded theory framework, this paper analyses the quality characteristics for methods to be used for requirements engineering in the development of medical decision support systems (MDSS). The results from a Quality Function Deployment (QFD) used to rank functions connected to user value and a focus group study were presented to a validation focus group. The focus group studies take advantage of a group process to collect data for further analyses. The results describe factors considered by the participants as important in the development of methods for requirements engineering in health care. Based on the findings, the content which, according to the user a MDSS method should support is established.

Financial effect of instituting Deficit Reduction Act documentation requirements in family planning clinics in Oregon.

Science.gov (United States)

Rodriguez, Maria Isabel; Angus, Lisa; Elman, Emily; Darney, Philip D; Caughey, Aaron B

2011-06-01

The study was conducted to estimate the long-term costs for implementing citizenship documentation requirements in a Medicaid expansion program for family planning services in Oregon. A decision-analytic model was developed using two perspectives: the state and society. Our primary outcome was future reproductive health care costs due to pregnancy in the next 5 years. A Markov structure was utilized to capture multiple future pregnancies. Model inputs were retrieved from the existing literature and local hospital and Medicaid data related to reimbursements. One-way and multi-way sensitivity analyses were conducted. A Monte Carlo simulation was performed to simultaneously incorporate uncertainty from all of the model inputs. Screening for citizenship results in a loss of $3119 over 5 years ($39,382 vs. $42,501) for the state and $4209 for society ($63,391 compared to $59,182) for adult women. Among adolescents, requiring proof of identity and citizenship results in a loss of $3123 for the state ($39,378 versus $42,501) and $4214 for society ($63,391 instead of $59,177). Screening for citizenship status in publicly funded family planning clinics leads to financial losses for the state and society. Copyright © 2011 Elsevier Inc. All rights reserved.

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

Science.gov (United States)

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.

Low-Level Burial Grounds Dangerous Waste Permit Application design documents

International Nuclear Information System (INIS)

1990-01-01

This document presents the Functional Design Criteria for trenches to be constructed to receive solid radioactive mixed waste (RMW) from on and offsite generators. The new RMW disposal facilities are considered modifications to or lateral expansion of the existing low-level waste burial grounds. The new facilities upgrade the existing disposal practice for RMW to the minimum technology requirements of the Resource Conservation and Recovery Act. The proposed locations for the two facilities are: 218-E-10 for drag-off-waste packages and, 218-W-4C for non drag-off waste packages

CERN Document Server (CDS): Introduction

CERN Multimedia

CERN. Geneva; Costa, Flavio

2017-01-01

A short online tutorial introducing the CERN Document Server (CDS). Basic functionality description, the notion of Revisions and the CDS test environment. Links: CDS Production environment CDS Test environment  

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

Science.gov (United States)

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

1986-01-01

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

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

Science.gov (United States)

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

1972-01-01

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

Functional requirement specification in the packaging development chain

NARCIS (Netherlands)

Lutters, Diederick; ten Klooster, Roland

2008-01-01

As it is clear that the full packaging life cycle – at least partially – coincides with the product life cycle, both cycles are interwoven. Each has a network of functional requirements, with specific hierarchic propensities. These networks overlap, with prevailing hierarchies playing important

Functional requirements for a central research imaging data repository.

Science.gov (United States)

Franke, Thomas; Gruetz, Romanus; Dickmann, Frank

2013-01-01

The current situation at many university medical centers regarding the management of biomedical research imaging data leaves much to be desired. In contrast to the recommendations of the German Research Foundation (DFG) and the German Council of Sciences and Humanities regarding the professional management of research data, there are commonly many individual data pools for research data in each institute and the management remains the responsibility of the researcher. A possible solution for this situation would be to install local central repositories for biomedical research imaging data. In this paper, we developed a scenario based on abstracted use-cases for institutional research undertakings as well as collaborative biomedical research projects and analyzed the functional requirements that a local repository would have to fulfill. We determined eight generic categories of functional requirements, which can be viewed as a basic guideline for the minimum functionality of a central repository for biomedical research imaging data.

Environment, Health, and Safety - Construction Subcontractors Documents |

Science.gov (United States)

NREL Environment, Health, and Safety - Construction Subcontractors Documents Environment Environment, Health and Safety (EH&S) requirements are understood by construction subcontractors and with these requirements before submitting proposals and/or environment, health and safety plans for the

Design requirement on HYPER blanket fuel assembly

International Nuclear Information System (INIS)

Hwang, Woan; Lee, B. O.; Nam, C.; Ryu, W. S.; Lee, B. S.; Park, W. S.

2000-07-01

This document describes design requirements which are needed for designing the blanket assembly of the HYPER as design guidance. The blanket assembly of the HYPER consists of blanket fuel rods, mounting rail, spacer, upper nozzle with handling socket, bottom nozzle with mounting rail and skeleton structure. The blanket fuel rod consists of top end plug, bottom end plug with key way, blanket fuel slug, and cladding. In the assembly, the rods are in a triangular pitch array. This report contains functional requirements, performance and operational requirements, interfacing systems requirements, core restraint and interface requirements, design limits and strength requirements, system configuration and essential feature requirements, seismic requirements, structural requirements, environmental requirements, reliability and safety requirements, standard and codes, QA programs, and other requirements for the blanket fuel assembly of the HYPER

Identifying Similarities in Cognitive Subtest Functional Requirements: An Empirical Approach

Science.gov (United States)

Frisby, Craig L.; Parkin, Jason R.

2007-01-01

In the cognitive test interpretation literature, a Rational/Intuitive, Indirect Empirical, or Combined approach is typically used to construct conceptual taxonomies of the functional (behavioral) similarities between subtests. To address shortcomings of these approaches, the functional requirements for 49 subtests from six individually…

Guideline on radiation protection in medicine requires documentation of radioiodine therapy and follow-up. What are the benefits of an electronic database?

International Nuclear Information System (INIS)

Koch, W.; Rosa, F.; Knesewitsch, P.; Hahn, K.

2005-01-01

The lately updated German guideline on radiation protection in medicine (Richtlinie Strahlenschutz in der Medizin) requires the physician who administers radioactive substances for therapy, to perform and document follows-up. In order to decrease the administrative burden, an electronic database was developed that interfaces with a word processing software to generate written reports and statistic analysis. Methods: Based on Microsoft registered Access and Microsoft registered Visual Basic a database was created to monitor patients with benign and malignant thyroid disorders after radioiodine therapy. It permits automatic creation of therapy documents and necessary patient reports in Microsoft registered Word. Intuitive handling, third level of normalization in database architecture and automatic plausibility checks guarantee integrity of the data and the efficacy of the database. Results, conclusion: The new software has been a success in over 1500 patients and over 3800 in- and outpatient therapies and visits. The effort of data entry is easily offset by the automatic generation of the necessary patient reports. The required supervision of the follow-up appointments is now also user-friendly and efficient. (orig.)

43 CFR 422.8 - Requirements for law enforcement functions and programs.

Science.gov (United States)

2010-10-01

..., and clear lines of authority and communication. This organizational structure must apply both within... PROJECTS Program Requirements § 422.8 Requirements for law enforcement functions and programs. The...

Born Broken: Fonts and Information Loss in Legacy Digital Documents

Directory of Open Access Journals (Sweden)

Geoffrey Brown

2011-03-01

Full Text Available For millions of legacy documents, correct rendering depends upon resources such as fonts that are not generally embedded within the document structure. Yet there is a significant risk of information loss due to missing or incorrectly substituted fonts. Large document collections depend on thousands of unique fonts not available on a common desktop workstation, which typically has between 100 and 200 fonts. Silent substitution of fonts, performed by applications such as Microsoft Office, can yield poorly rendered documents. In this paper we use a collection of 230,000 Word documents to assess the difficulty of matching font requirements with a database of fonts. We describe the identifying information contained in common font formats, font requirements stored in Word documents, the API provided by Windows to support font requests by applications, the documented substitution algorithms used by Windows when requested fonts are not available, and the ways in which support software might be used to control font substitution in a preservation environment.

The Algorithm Theoretical Basis Document for Level 1A Processing

Science.gov (United States)

Jester, Peggy L.; Hancock, David W., III

2012-01-01

The first process of the Geoscience Laser Altimeter System (GLAS) Science Algorithm Software converts the Level 0 data into the Level 1A Data Products. The Level 1A Data Products are the time ordered instrument data converted from counts to engineering units. This document defines the equations that convert the raw instrument data into engineering units. Required scale factors, bias values, and coefficients are defined in this document. Additionally, required quality assurance and browse products are defined in this document.

Quality documentation challenges for veterinary clinical pathology laboratories.

Science.gov (United States)

Sacchini, Federico; Freeman, Kathleen P

2008-05-01

An increasing number of veterinary laboratories worldwide have obtained or are seeking certification based on international standards, such as the International Organization for Standardization/International Electrotechnical Commission 17025. Compliance with any certification standard or quality management system requires quality documentation, an activity that may present several unique challenges in the case of veterinary laboratories. Research specifically addressing quality documentation is conspicuously absent in the veterinary literature. This article provides an overview of the quality system documentation needed to comply with a quality management system with an emphasis on preparing written standard operating procedures specific for veterinary laboratories. In addition, the quality documentation challenges that are unique to veterinary clinical pathology laboratories are critically evaluated against the existing quality standards and discussed with respect to possible solutions and/or recommended courses of action. Documentation challenges include the establishment of quality requirements for veterinary tests, the use or modification of human analytic methods for animal samples, the limited availability of quality control materials satisfactory for veterinary clinical pathology laboratories, the limited availability of veterinary proficiency programs, and the complications in establishing species-specific reference intervals.

National projections of forest and rangeland condition indicators: a supporting technical document for the 1999 RPA assessment.

Science.gov (United States)

John Hof; Curtis Flather; Tony Baltic; Stephen. Davies

1999-01-01

The 1999 forest and rangeland condition indicator model is a set of independent econometric production functions for environmental outputs (measured with condition indicators) at the national scale. This report documents the development of the database and the statistical estimation required by this particular production structure with emphasis on two special...

Making project documentation a positive tool for management

International Nuclear Information System (INIS)

Shirley, C.G.

1985-01-01

Since 1980, Sandia National Laboratory has been designing and constructing Particle Beam Fusion Accelerator II. One managerial challenge of a large project is the problem of handling information. The scope of the PBFA-II projet may be gauged by its cost: $19.4 million for the accelerator itself, $9.5 million for buildings and standard utilities, and $9.6 million for specialized utilities and support systems. The first need of the project at its outset, then, was communication, and this remains a chief function of the CPO. If the nature or magnitude of the risk changes in any one area, the entire project team must know. If a design is changed, persons working on interdependent efforts must know. Some of this communication takes place naturally and informally. But project procedures must guarantee that all important communication is received by all necessary people, that the communication creates accountability, and that management receives timely, accurate reports. To put it another way, important communication requires project documentation. Documentation is both a record of the project and a tool for management

Old TNX Seepage Basin: Environmental information document

International Nuclear Information System (INIS)

Dunaway, J.K.; Johnson, W.F.; Kingley, L.E.; Simmons, R.V.; Bledsoe, H.W.; Smith, J.A.

1986-12-01

This document provides environmental information on postulated closure options for the Old TNX Seepage Basin at the Savannah River Plant and was developed as background technical documentation for the Department of Energy's proposed Environmental Impact Statement (EIS) on waste management activities for groundwater protection at the plant. The results of groundwater and atmospheric pathway analyses, accident analysis, and other environmental assessments discussed in this document are based upon a conservative analysis of all foreseeable scenarios as defined by the National Environmental Policy Act (40 CFR 1500-1508). The scenarios do not necessarily represent actual environmental conditions. This document is not meant to be used as a regulatory closure plan or other regulatory document to comply with required federal or state environmental regulations

75 FR 14361 - Notification, Documentation, and Recordkeeping Requirements for Inspected Establishments

Science.gov (United States)

2010-03-25

... error. Table 3--Number of Establishments, and Total and Average Cost in Size (x $1,000) Recall Number of... Activities (2010) (2011) (2012) (2013) (2014) Total Very Small 2,856 Recall-Procedures 2,030 278 286 295 304... 461 Total All 6,300 Recall-Procedures 4,454 610 628 647 666 7,005 development & updating. Documenting...

Functional Requirements for Continuation Period Equipment and Drilling

International Nuclear Information System (INIS)

Sweeney, J.J.

2000-01-01

For geophysical measurements, creating a functional requirement based on finding a specific-sized target at a specific depth is difficult because of the wide variation of subsurface and surface geologic conditions that can be encountered. An alternative approach used in this paper is to specify functional requirements based on what is needed to search for the effects of a given target within a reasonable background of environmental or geological variation (noise). There is a gap between what the state-of-the-art expert with a large amount of experience can be expected to accomplish and what a non-expert inspector with limited experience can do. There are also limitations because of the Treaty environment (equipment certification, transparency, managed access, etc.); thus, for OSI, we must opt for pragmatic approach. Equipment must be easy to use, rugged, and functional over a wide range of environmental conditions. Equipment should consist of commercially available technology. Well-established operational procedures should be used for taking measurements, reducing data, and presenting data, with software mostly provided by the manufacturer along with the equipment. Equipment should be used in conjunction with WGB-approved position-finding equipment capable of relative position determinations pertinent to the type of equipment and measurement

LHCb Online Networking Requirements

CERN Document Server

Jost, B

2003-01-01

This document describes the networking requirements of the LHCb online installation. It lists both quantitative aspects such as the number of required switch ports, as well as some qualitative features of the equipment, such as minimum buffer sizes in switches. The document comprises both the data acquisition network and the controls/general-purpose network. While the numbers represent our best current knowledge and are intended to give (in particular) network equipment manufacturers an overview of our needs, this document should not be confused with a market survey questionnaire or a formal tendering document. However the information contained in this document will be the input of any such document. A preliminary schedule for procurement and installation is also given.

Electronic signature for medical documents--integration and evaluation of a public key infrastructure in hospitals.

Science.gov (United States)

Brandner, R; van der Haak, M; Hartmann, M; Haux, R; Schmücker, P

2002-01-01

Our objectives were to determine the user-oriented and legal requirements for a Public Key Infrastructure (PKI) for electronic signatures for medical documents, and to translate these requirements into a general model for a signature system. A prototype of this model was then implemented and evaluated in clinical routine use. Analyses of documents, processes, interviews, observations, and of the available literature supplied the foundations for the development of the signature system model. Eight participants of the Department of Dermatology of the Heidelberg University Medical Center evaluated the implemented prototype from December 2000 to January 2001, during the course of an intervention study. By means of questionnaires, interviews, observations and database analyses, the usefulness and user acceptance of the electronic signature and its integration into electronic discharge letters were established. Since the major part of medical documents generated in a hospital are signature-relevant, they will require electronic signatures in the future. A PKI must meet the multitude of responsibilities and security needs required in a hospital. Also, the signature functionality must be integrated directly into the workflow surrounding document creation. A developed signature model, fulfilling user-oriented and legal requirements, was implemented using hard and software components that conform to the German Signature Law. It was integrated into the existing hospital information system of the Heidelberg University Medical Center. At the end of the intervention study, the average acceptance scores achieved were mean = 3.90; SD = 0.42 on a scale of 1 (very negative attitude) to 5 (very positive attitude) for the electronic signature procedure. Acceptance of the integration into computer-supported discharge letter writing reached mean = 3.91; SD = 0.47. On average, the discharge letters were completed 7.18 days earlier. The electronic signature is indispensable for the

Design requirement on KALIMER blanket fuel assembly duct

International Nuclear Information System (INIS)

Hwang, Woan; Kang, H. Y.; Nam, C.; Kim, J. O.

1998-03-01

This document describes design requirements which are needed for designing the blanket fuel assembly duct of the KALIMER as design guidance. The blanket fuel assembly duct of the KALIMER consists of fuel rods, mounting rail, nosepiece, duct with pad, handling socket with pad. Blanket fuel rod consists of top end plug, bottom end plug with solid ferritic-martensitic steel rod and key way blanket fuel slug, cladding, and wire wrap. In the assembly, the rods are in a triangular pitch array, and the rod bundle is attached to the nosepiece with mounting rails. The bottom end of the assembly duct is formed by a long nosepiece which provides the lower restraint function and the paths for coolant inlet. This report contains functional requirements, performance and operational requirements, interfacing systems requirements, core restraint and interface requirements, design limits and strength requirements, system configuration and essential feature requirements, seismic requirements, structural requirements, environmental requirements, reliability and safety requirements, standard and codes, QA programs, and other requirements. (author). 20 refs., 4 figs

Project Documentation as a Risk for Public Projects

Directory of Open Access Journals (Sweden)

Vladěna Štěpánková

2015-08-01

Full Text Available Purpose of the article: The paper presents the different methodologies used for creating documentation and focuses on public projects and their requirements for this documentation. Since documentation is also incorporated in the overall planning of the project and its duration is estimated using expert qualified estimate, can any change in this documentation lead to project delays, or increase its cost as a result of consuming administration, and therefore the documentation is seen as a risk, which may threaten the project as a public contract by which a company trying to achieve and obtains it, and generally any project. Methodology/methods: There are used methods of obtaining information in this paper. These are mainly structured interviews in combination with a brainstorming, furthermore also been used questionnaire for companies dealing with public procurement. As a data processing program was used MS Excel and basic statistical methods based on regression analysis. Scientific aim: The article deals with the construction market in the Czech Republic and examines the impact of changes in project documentation of public projects on their turnover. Findings: In this paper we summarize the advantages and disadvantages of having project documentation. In the case of public contracts and changes in legislation it is necessary to focus on creating documentation in advance, follow the new requirements and try to reach them in the shortest possible time. Conclusions: The paper concludes with recommendations on how to proceed, if these changes and how to reduce costs, which may cause the risk of documentation.

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

Science.gov (United States)

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

2011-05-01

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

Towards an Early Software Effort Estimation Based on Functional and Non-Functional Requirements

NARCIS (Netherlands)

Kassab, M.; Daneva, Maia; Ormanjieva, Olga; Abran, A.; Braungarten, R.; Dumke, R.; Cuadrado-Gallego, J.; Brunekreef, J.

2009-01-01

The increased awareness of the non-functional requirements as a key to software project and product success makes explicit the need to include them in any software project effort estimation activity. However, the existing approaches to defining size-based effort relationships still pay insufficient

Report on functional requirements and software architecture for the IDTO prototype : phase I demonstration site (Columbus).

Science.gov (United States)

2013-08-01

This report documents the System Requirements and Architecture for the Phase I implementation of the Integrated Dynamic : Transit Operations (IDTO) Prototype bundle within the Dynamic Mobility Applications (DMA) portion of the Connected Vehicle : Pro...

Report on functional requirements and software architecture for the IDTO prototype phase 2 : central Florida demonstration.

Science.gov (United States)

2015-05-01

This report documents the System Requirements and Architecture for the Phase 2 implementation of the Integrated Dynamic : Transit Operations (IDTO) Prototype bundle within the Dynamic Mobility Applications (DMA) portion of the Connected Vehicle : Pro...

Authorization basis requirements comparison report

Energy Technology Data Exchange (ETDEWEB)

Brantley, W.M.

1997-08-18

The TWRS Authorization Basis (AB) consists of a set of documents identified by TWRS management with the concurrence of DOE-RL. Upon implementation of the TWRS Basis for Interim Operation (BIO) and Technical Safety Requirements (TSRs), the AB list will be revised to include the BIO and TSRs. Some documents that currently form part of the AB will be removed from the list. This SD identifies each - requirement from those documents, and recommends a disposition for each to ensure that necessary requirements are retained when the AB is revised to incorporate the BIO and TSRs. This SD also identifies documents that will remain part of the AB after the BIO and TSRs are implemented. This document does not change the AB, but provides guidance for the preparation of change documentation.

Authorization basis requirements comparison report

International Nuclear Information System (INIS)

Brantley, W.M.

1997-01-01

The TWRS Authorization Basis (AB) consists of a set of documents identified by TWRS management with the concurrence of DOE-RL. Upon implementation of the TWRS Basis for Interim Operation (BIO) and Technical Safety Requirements (TSRs), the AB list will be revised to include the BIO and TSRs. Some documents that currently form part of the AB will be removed from the list. This SD identifies each - requirement from those documents, and recommends a disposition for each to ensure that necessary requirements are retained when the AB is revised to incorporate the BIO and TSRs. This SD also identifies documents that will remain part of the AB after the BIO and TSRs are implemented. This document does not change the AB, but provides guidance for the preparation of change documentation