Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Draft Requirements”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 343 records · Page 19

Independent Orbiter Assessment (IOA): Assessment of the mechanical actuation subsystem, volume 2

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA approach features a top-down analysis of the hardware to determine draft failure modes, criticality, and potential critical items. To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. The IOA results were then compared to the proposed Post 51-L NASA FMEA/CIL baseline that was available. A resolution of each discrepancy from the comparison was provided through additional analysis as required. These discrepancies were flagged as issues, and recommendations were made based on the FMEA data available at the time. This report documents the results of that comparison for the Orbiter Mechanical Actuation System (MAS) hardware. Specifically, the MAS hardware consists of the following components: Air Data Probe (ADP); Elevon Seal Panel (ESP); External Tank Umbilical (ETU); Ku-Band Deploy (KBD); Payload Bay Doors (PBD); Payload Bay Radiators (PBR); Personnel Hatches (PH); Vent Door Mechanism (VDM); and Startracker Door Mechanism (SDM). Criticality was assigned based upon the severity of the effect for each failure mode. Volume 2 continues the presentation of IOA analysis worksheets and contains the potential critical items list, detailed analysis, and NASA FMEA/CIL to IOA worksheet cross reference and recommendations.

Bradway, M. W.↗

Goal-Function Tree Modeling for Systems Engineering and Fault Management

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

Patterson, Jonathan D.↗

Goal-Function Tree Modeling for Systems Engineering and Fault Management

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

Johnson, Stephen B.↗

Predictive Engineering Tools for Injection-Molded Long-Carbon-Fiber Thermoplastic Composites (Quarterly Report)

This quarterly report summarizes the status for the project planning to initiate all the legal and contract documents required for establishing the subcontracts needed and a Cooperative Research and Development Agreement (CRADA) with Autodesk, Inc., Toyota Motor Engineering and Manufacturing North America (Toyota), and Magna Exterior and Interiors Corporation (Magna). During the first quarter (10/1/2012 to 12/31/2012), the statements of work (SOW) for the subcontracts to Purdue University, University of Illinois, and PlastiComp, Inc. were completed. A draft of the CRADA SOW was sent to Autodesk, Toyota, and Magna for technical and legal reviews. PNNL Legal Services contacted project partners’ Legal counterparts for preparing legal documents for the project. A non-disclosure agreement was drafted and sent to all the parties for reviews.

compounding↗

The Effect of Cold Work on Properties of Alloy 617

Alloy 617 is approved for non-nuclear construction in the ASME Boiler and Pressure Vessel Code Section I and Section VIII, but is not currently qualified for nuclear use in ASME Code Section III. A draft Code Case was submitted in 1992 to qualify the alloy for nuclear service but efforts were stopped before the approval process was completed.1 Renewed interest in high temperature nuclear reactors has resulted in a new effort to qualify Alloy 617 for use in nuclear pressure vessels. The mechanical and physical properties of Alloy 617 were extensively characterized for the VHTR programs in the 1980’s and incorporated into the 1992 draft Code Case. Recently, the properties of modern heats of the alloy that incorporate an additional processing step, electro-slag re-melting, have been characterized both to confirm that the properties of contemporary material are consistent with those in the historical record and to increase the available database. A number of potential issues that were identified as requiring further consideration prior to the withdrawal of the 1992 Code Case are also being re-examined in the current R&D program. Code Cases are again being developed to allow use of Alloy 617 for nuclear design within the rules of the ASME Boiler and Pressure Vessel Code. In general the Code defines two temperature ranges for nuclear design with austenitic and nickel based alloys. Below 427°C (800°F) time dependent behavior is not considered, while above this temperature creep and creep-fatigue are considered to be the dominant life-limiting deformation modes. There is a corresponding differentiation in the treatment of the potential for effects associated with cold work. Below 427°C the principal issue is the relationship between the level of cold work and the propensity for stress corrosion cracking and above that temperature the primary concern is the impact of cold work on creep-rupture behavior.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

UPC++ as_eager Working Group Draft, Revision 2020.6.2

This draft proposes an extension for a new future-based completion variant that can be more effectively streamlined for RMA and atomic access operations that happen to be satisfied at runtime using purely node-local resources. Many such operations are most efficiently performed synchronously using load/store instructions on shared-memory mappings, where the actual access may only require a few CPU instructions. In such cases we believe it’s critical to minimize the overheads imposed by the UPC++ runtime and completion queues, in order to enable efficient operation on hierarchical node hardware using shared-memory bypass. The new upcxx::{source,operation}_cx::as_eager_future() completion variant accomplishes this goal by relaxing the current restriction that future-returning access operations must return a non-ready future whose completion is deferred until a subsequent explicit invocation of user-level progress. This relaxation allows access operations that are completed synchronously to instead return a ready future, thereby avoiding most or all of the runtime costs associated with deferment of future completion and subsequent mandatory entry into the progress engine. We additionally propose to make this new as_eager_future() completion variant the new default completion for communication operations that currently default to returning a future. This should encourage use of the streamlined variant, and may provide performance improvements to some codes without source changes. A mechanism is proposed to restore the legacy behavior on-demand for codes that might happen to rely on deferred completion for correctness. Finally, we propose a new as_eager_promise() completion variant that extends analogous improvements to promise-based completion, and corresponding changes to the default behavior of as_promise().

97 MATHEMATICS AND COMPUTING↗

SPDB (science processing database): Quick reference guide

This contents of this draft copy include: how to log into the SPDB (Science Processing DataBase); how to navigate through menus; how to use ESC keys; how to get help; and how to quit the program. The Science Processing Database is an interactive, on-line system that provides updated information about Earth Observing System Project, including instruments, investigators, output data products, input requirements, retrieval algorithms, and VO datasets archived at DAAC's.

Source record↗

PLUTONIUM-URANIUM EXTRACTION (PUREX) FACILITY ALARACT DEMONSTRATION FOR FILTER HOUSING

This document presents an As Low As Reasonably Achievable Control Technology (ALARACT) demonstration for evaluating corrosion on the I-beam supporting filter housing No.9 for the 291-A-l emission unit of the Plutonium-Uranium Extraction (PUREX) Facility, located in the 200 East Area of the Hanford Site. The PUREX facility is currently in surveillance and maintenance mode. During a State of Washington, Department of Health (WDOH) 291-A-l emission unit inspection, a small amount of corrosion was observed at the base of a high-efficiency particulate air (HEPA) filter housing. A series of internal and external inspections identified the source of the corrosion material as oxidation of a small section of one of the carbon steel I-beams that provides support to the stainless steel filter housing. The inspections confirmed the corrosion is isolated to one I-beam support location and does not represent any compromise of the structural support or filter housing integrity. Further testing and inspections of the support beam corrosion and its cause were conducted but did not determine the cause. No definitive evidence was found to support any degradation of the housing. Although no degradation of the housing was found, a conservative approach will be implemented. The following actions will be taken: (1) The current operating filter housing No.9 will be removed from service. (2) The only remaining available filter housings (No.1, No.2, and No.3) will be placed in service. These filter housings have new HEPA filters fitted with stainless steel frames and faceguards which were installed in the spring of 2007. (3) Filter housings No.5 and No.10 will be put on standby as backups. To document the assessment of the unit, a draft ALARACT filter housing demonstration for the PUREX filter housing was prepared, and informally provided to WDOH on August 7, 2008. A follow up WDOH response to the draft ALARACT filter housing demonstration for the PUREX filter housing questioned whether deteriorated galvanized filter faceguards discovered during an internal filter housing inspection met American Society of Mechanical Engineers (ASME) AG-l or Military Specification (MIL) 51068 standards. The filter system was designed and installed prior to the issuance of AG-l, February 1986; however, MIL 51068 did require galvanized faceguards. The faceguards are not necessary for filtration or structural purposes; it is concluded that the system is in compliance with the intent of the applicable standard. Appendix B provides supporting information to address this issue.

36 MATERIALS SCIENCE↗

Independent Orbiter Assessment (IOA): Assessment of the rudder/speed brake subsystem FMEA/CIL

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA effort first completed an analysis of the Rudder/Speed Brake (RSB) hardware, generating draft failure modes and potential critical items. To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. The IOA results were then compared to the NASA FMEA/CIL baseline along with the proposed Post 51-L CIL updates included. A resolution of each discrepancy from the comparison was provided through additional analysis as required. This report documents the results of that comparison for the Orbiter RSB hardware. The IOA product for the RSB analysis consisted of 38 failure mode worksheets that resulted in 27 potential critical items being identified. Comparison was made to the NASA baseline which consisted of 34 FMEAs and 18 CIL items. This comparison produced agreement on all CIL items. Based on the Pre 51-L baseline, all non-CIL FMEAs were also in agreement.

Wilson, R. E.↗

Low-Level Waste Regulation: Putting Principles Into Practice - 13297 - The Richard S. Hodes, M.D., Honor Lecture Award

In carrying out its mission to ensure the safe use of radioactive materials for beneficial civilian purposes while protecting people and the environment, the U.S. Nuclear Regulatory Commission (NRC) adheres to its Principles of Good Regulation. The Principles-Independence, Openness, Efficiency, Clarity, and Reliability-apply to the agency as a whole in its decision-making and to the individual conduct of NRC employees. This paper describes the application of the Principles in a real-life staff activity, a guidance document used in the NRC's low-level radioactive waste (LLW) program, the Concentration Averaging and Encapsulation Branch Technical Position (CA BTP). The staff's process to revise the document, as well as the final content of the document, were influenced by following the Principles. For example, consistent with the Openness Principle, the staff conducted a number of outreach activities and received many comments on three drafts of the document. Stakeholder comments affected the final staff positions in some cases. The revised CA BTP, once implemented, is expected to improve management and disposal of LLW in the United States. Its positions have an improved nexus to health and safety; are more performance-based than previously, thus providing licensees with options for how they achieve the required outcome of protecting an inadvertent human intruder into a disposal facility; and provide for disposal of more sealed radioactive sources, which are a potential threat to national security. (author)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Draft ASME Section III Division 5 Code Cases to extend EPP strain limits and creep-fatigue design methods to Grade 91

This report describes the drafting of Code Cases extending the ASME Boiler and Pressure Vessel Code Section III, Division 5, Subsection HB, Subpart B design by elastic perfect-plastic (EPP) analysis methods to Grade 91 steel. The primary technical challenge is that Grade 91 steel is a cyclic softening material and so modifications to the current ASME design approach for austenitic stainless steel were required to produce conservative designs. Previous work established the technical basis required to support these modifications. This report provides the full package for balloting by ASME – both revised Code Case language and associated background documentation for two nuclear code cases: N-861 covering ratcheting strain limits and N-862 covering creep-fatigue damage. The completion of this work and successful balloting at ASME, currently underway, allows designers to apply the efficient EPP methods to Grade 91 high temperature structural components.

36 MATERIALS SCIENCE↗

Efficiencies in the Environmental Restoration Operations at Sandia National Laboratories, New Mexico - 12198

The mission of the Environmental Restoration Operations at Sandia National Laboratories - New Mexico is to complete all necessary corrective actions at 268 legacy release soil sites and three groundwater Areas of Concern. Additional scope impacted the anticipated 2009 completion of corrective action at the remaining 32 soil sites and the three groundwater Areas of Concern. This additional scope is base-lined to require 10 years (2011-2020) at an estimated cost of $34 M to $39 M. Efficiencies been proposed to reduce the impact of this recently realized additional corrective action scope: (1) Perform activities concurrently when possible to help reduce the length of the overall schedule; (2) Implement a 'high-performance, one-pass' concept based on an early resolution of deficiencies in draft documents and attempt to avoid multi-submission cycles with long turnaround review times, and (3) Assess the appropriateness of progressing 'at risk' from groundwater characterization to groundwater remediation using existing data, conceptual models and potential remedies. The ongoing promotion and implementation of these ideas with the New Mexico Environment Department will produce scope and cost saving -- without any reduction in the protection of public health and the environment. DOE/SSO developed and presented to the NMED three areas where efficiencies in ER Operations may be realized. The NMED has not formally responded to these proposals, but in discussions with NMED in the fall of 2011 the NMED is conceptually supportive of these proposals. NMED cannot commit to an outcome (such as no NOD), but NMED is very willing to seek efficiencies that will reduce the overall scope, while achieving regulatory compliance and considering public input. The challenge of finding efficiencies to reduce the new schedule and cost has become even more of a necessity due to shrinking budgets. A prioritization of remaining activities has been discussed with the regulatory authority. Efficiencies in the ER Operations at SNL have been proposed to reduce the impact of recently realized regulatory delays and additional corrective action scope. The ongoing promotion and implementation of these ideas with the NMED will produce scope and cost saving, without any reduction in the protection of public health and the environment. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

SG50 Data-format Specifications Document for the Automatically Readable, Comprehensive, and Curated Experimental Reaction Database MEDUSAL

The aim of this document is to lay out a first draft of the specifications for the MEDUSAL database (Machine-readable Experimental Data User App & Library) that is being described by OECD/NEA/WPEC SG-50. The EXFOR database (Otuka et al., 2014) has a format that is based on code-value pairs, and a significant portion of the information in the EXFOR entry is contained in free text sections. Several high-level requirements for the MEDUSAL database, as laid out in the Use Cases and Requirements Working Paper (citation), relate to the definition of the specifications

Nuclear Criticality Safety Program (NCSP)↗

PV-RPM V2.0 beta - SAM Implementation. DRAFT User Instructions

This user manual is intended to provide instructions to volunteer beta testers on how to use Sandia National Laboratories (SNL) PV Reliability Performance Model (PV-RPM) features in the National Renewable Energy Laboratory (NREL) System Advisor Model (SAM) version 2017.1.17 r4 (NREL, 2017). This new feature is provided in SAM to allow users with reliability data the ability to develop and run scenarios where PV performance and costs are impacted from components that can fail stochastically. This is intended to be an advanced user feature as it requires knowledge and data regarding different PV component failure modes. It also relies heavily on the SAM LK scripting language, which is not utilized by a majority of SAM users. NREL has published a SAM LK users guide (Dobos, 2017) and has multiple online help topics and videos to get users familiar with the scripting language and what it can do. This user instruction manual will provide some background on how data collected from a PV system can be used as inputs in the PV-RPM model, which will give data owners the ability to develop their own reliability and repair distributions outside of the example provided here.

14 SOLAR ENERGY↗

Using Third-Party Inspectors in Building Energy Codes Enforcement in India

India is experiencing fast income growth and urbanization, and this leads to unprecedented increases in demand for building energy services and resulting energy consumption. In response to rapid growth in building energy use, the Government of India issued the Energy Conservation Building Code (ECBC) in 2007, which is consistent with and based on the 2001 Energy Conservation Act. ECBC implementation has been voluntary since its enactment and a few states have started to make progress towards mandatory implementation. Rajasthan is the first state in India to adopt ECBC as a mandatory code. The State adopted ECBC with minor additions on March 28, 2011 through a stakeholder process; it became mandatory in Rajasthan on September 28, 2011. Tamil Nadu, Gujarat, and Andhra Pradesh have started to draft an implementation roadmap and build capacity for its implementation. The Bureau of Energy Efficiency (BEE) plans to encourage more states to adopt ECBC in the near future, including Haryana, Uttar Pradesh, Karnataka, Maharashtra, West Bengal, and Delhi. Since its inception, India has applied the code on a voluntary basis, but the Government of India is developing a strategy to mandate compliance. Implementing ECBC requires coordination between the Ministry of Power and the Ministry of Urban Development at the national level as well as interdepartmental coordination at the state level. One challenge is that the Urban Local Bodies (ULBs), the enforcement entities of building by-laws, lack capacity to implement ECBC effectively. For example, ULBs in some states might find the building permitting procedures to be too complex; in other cases, lack of awareness and technical knowledge on ECBC slows down the amendment of local building by-laws as well as ECBC implementation. The intent of this white paper is to share with Indian decision-makers code enforcement approaches: through code officials, third-party inspectors, or a hybrid approach. Given the limited capacity and human resources available in the state and local governments, involving third-party inspectors could rapidly expand the capacity for plan reviews and broad implementation. However, the procedures of involving third-parties need to be carefully designed in order to guarantee a fair process. For example, there should be multiple checks and certification requirements for third-party inspectors, and the government should have the final approval when third-party inspectors are used in a project. This paper discusses different approaches of involving third-parties in ECBC enforcement; the Indian states may choose the approaches that work best in their given circumstances.

Yu, Sha↗

Preliminary Shielding Analysis for the 1012 400 MeV Linac Building

EIC is planning to purchase a 400 MeV turnkey pre-injector linear accelerator (Linac) which will be in a new building at the end of an existing RHIC tunnel at 12 o’clock. The building will contain the Linac Tunnel and associated accelerating structures, Klystron Gallery and waveguides, laser, utility, and control rooms. This report only examines the radiation source term produced by operating the Linac and not supplemental shielding that may be required to shield the Klystrons or solid state amplifiers in the Klystron Gallery from the x rays they emit. Normal Portland concrete blocks are planned to provide shielding between the Linac vault and the occupiable portions of the building per the attached drawing. It is expected that this facility will not be routinely occupied during operations (post commissioning). The shielding design considers EIC’s draft Shielding Policy that states shielding and other controls for areas where access is controlled for radiological purposes will be designed so that an ambient dose of 100 mrem per year to a worker is not likely.

43 PARTICLE ACCELERATORS↗

Earth Observations and the Role of UAVs: A Capabilities Assessment

This three-volume document, based on the draft document located on the website given on page 6, presents the findings of a NASA-led capabilities assessment of Uninhabited Aerial Vehicles (UAVs) for civil (defined as non-DoD) use in Earth observations. Volume 1 is the report that presents the overall assessment and summarizes the data. The second volume contains the appendices and references to address the technologies and capabilities required for viable UAV missions. The third volume is the living portion of this effort and contains the outputs from each of the Technology Working Groups (TWGs) along with the reviews conducted by the Universities Space Research Association (USRA). The focus of this report, intended to complement the Office of the Secretary of Defense UAV Roadmap, is four-fold: 1) To determine and document desired future Earth observation missions for all UAVs based on user-defined needs; 2) To determine and document the technologies necessary to support those missions; 3) To discuss the present state of the art platform capabilities and required technologies, including identifying those in progress, those planned, and those for which no current plans exist; 4) Provide the foundations for development of a comprehensive civil UAV roadmap. It is expected that the content of this report will be updated periodically and used to assess the feasibility of future missions. In addition, this report will provide the foundation to help influence funding decisions to develop those technologies that are considered enabling or necessary but are not contained within approved funding plans. This document is written such that each section will be supported by an Appendix that will give the reader a more detailed discussion of that section's topical materials.

Cox, Timothy H.↗

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

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

Source record↗