Detail specification Surveyor system functional requirements, revision H
Functional requirement specifications for Surveyor spacecraft systems engineering
Source record↗
SEARCH · Search NASA
Results for “requirements specifications”
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.
Flight motor set 360L001 (STS-26R), volume 1
The NASA space shuttle flight STS-26R, launched at 11:37.00.009 a.m. EDT on 29 Sep. 1988, used the redesigned solid rocket motors (RSRM) 360LOO1A and 360LOO1B. Evaluation of the ground environment instrumentation (GEI) data recorded prior to flight showed: (1) no launch commit criteria violations, (2) that the field joint heater and aft skirt thermal conditioning systems performed adequately, and (3) that the GEI data showed good agreement with thermal model predictions. Evaluation of the developmental flight instrumentation (DFI) revealed excellent agreement with both the predicted and required ballistic specifications. All parameters were well within the CEI specification requirements including propellant burn rates, specific impulse values, and thrust imbalance. Recorded strain values also indicated satisfactory radial growth and stress levels, as well as verification of adequate safety factors. Postflight inspection of the insulation, seals, case, and nozzles showed overall excellent performance. Some thermal DFI protective cork was missing, and inoperative field joint vent valves on the thermal protection cork allowed water entry into the field joints upon splashdown. Evaluation of these anomalies, as well as complete evaluation of all RSRM components, is presented.
Ricks, Glen A.↗
Flight motor set 360L001 (STS-26R). Volume 1: System overview, revision A
The NASA space shuttle flight STS-26R, launched at 11:37.00.009 am, EDT on 29 Sep. 1988, used the redesigned solid rocket motors (RSRM) 360L001A and 360L001B. Evaluation of the ground environment instrumentation (GEI) data recorded prior to flight showed no launch commit criteria violations; that the field joint heater and aft skirt thermal conditioning systems performed adequately; and that the GEI data showed good agreement with thermal model predictions. Evaluation of the developmental flight instrumentation (DFI) revealed excellent agreement with both the predicted and required ballistic specifications. All parameters were well within the GEI specification requirements including propellant burn rates, specific impulse values, and thrust imbalance. Recorded strain values also indicated satisfactory radial growth and stress levels, as well as verification of adequate safety factors. Postflight inspection of the insulation, seals, case, and nozzles showed overall excellent performance. Some thermal DFI protective cork was missing, and inoperative field joint vent valves on the thermal protection cork allowed water entry into the field joints upon splashdown. Evaluation of these anomalies, as well as complete evaluation of all Redesigned Solid Rocket Motor components, is contained.
Garecht, Diane M.↗
IMCS reflight certification requirements and design specifications
The requirements for reflight certification are established. Software requirements encompass the software programs that are resident in the PCC, DEP, PDSS, EC, or any related GSE. A design approach for the reflight software packages is recommended. These designs will be of sufficient detail to permit the implementation of reflight software. The PDSS/IMC Reflight Certification system provides the tools and mechanisms for the user to perform the reflight certification test procedures, test data capture, test data display, and test data analysis. The system as defined will be structured to permit maximum automation of reflight certification procedures and test data analysis.
Source record↗
Methodology for the systems engineering process. Volume 2: Technical parameters
A scheme based on starting the logic networks from the development and mission factors that are of primary concern in an aerospace system is described. This approach required identifying the primary states (design, design verification, premission, mission, postmission), identifying the attributes within each state (performance capability, survival, evaluation, operation, etc), and then developing the generic relationships of variables for each branch. To illustrate this concept, a system was used that involved a launch vehicle and payload for an earth orbit mission. Examination showed that this example was sufficient to illustrate the concept. A more complicated mission would follow the same basic approach, but would have more extensive sets of generic trees and more correlation points between branches. It has been shown that in each system state (production, test, and use), a logic could be developed to order and classify the parameters involved in the translation from general requirements to specific requirements for system elements.
Nelson, J. H.↗
Megawatt Class Nuclear Space Power Systems (MCNSPS) conceptual design and evaluation report. Volume 1: Objectives, summary results and introduction
The objective was to determine which reactor, conversion, and radiator technologies would best fulfill future Megawatt Class Nuclear Space Power System Requirements. Specifically, the requirement was 10 megawatts for 5 years of full power operation and 10 years systems life on orbit. A variety of liquid metal and gas cooled reactors, static and dynamic conversion systems, and passive and dynamic radiators were considered. Four concepts were selected for more detailed study. The concepts are: a gas cooled reactor with closed cycle Brayton turbine-alternator conversion with heat pipe and pumped tube-fin heat rejection; a lithium cooled reactor with a free piston Stirling engine-linear alternator and a pumped tube-fin radiator; a lithium cooled reactor with potassium Rankine turbine-alternator and heat pipe radiator; and a lithium cooled incore thermionic static conversion reactor with a heat pipe radiator. The systems recommended for further development to meet a 10 megawatt long life requirement are the lithium cooled reactor with the K-Rankine conversion and heat pipe radiator, and the lithium cooled incore thermionic reactor with heat pipe radiator.
Wetch, J. R.↗
Pathfinder autonomous rendezvous and docking project
Capabilities are being developed and demonstrated to support manned and unmanned vehicle operations in lunar and planetary orbits. In this initial phase, primary emphasis is placed on definition of the system requirements for candidate Pathfinder mission applications and correlation of these system-level requirements with specific requirements. The FY-89 activities detailed are best characterized as foundation building. The majority of the efforts were dedicated to assessing the current state of the art, identifying desired elaborations and expansions to this level of development and charting a course that will realize the desired objectives in the future. Efforts are detailed across all work packages in developing those requirements and tools needed to test, refine, and validate basic autonomous rendezvous and docking elements.
Lamkin, Stephen↗
Quasi-Linear Circuit
This work involved developing spacequalifiable switch mode DC/DC power supplies that improve performance with fewer components, and result in elimination of digital components and reduction in magnetics. This design is for missions where systems may be operating under extreme conditions, especially at elevated temperature levels from 200 to 300 degC. Prior art for radiation-tolerant DC/DC converters has been accomplished utilizing classical magnetic-based switch mode converter topologies; however, this requires specific shielding and component de-rating to meet the high-reliability specifications. It requires complex measurement and feedback components, and will not enable automatic re-optimization for larger changes in voltage supply or electrical loading condition. The innovation is a switch mode DC/DC power supply that eliminates the need for processors and most magnetics. It can provide a well-regulated voltage supply with a gain of 1:100 step-up to 8:1 step down, tolerating an up to 30% fluctuation of the voltage supply parameters. The circuit incorporates a ceramic core transformer in a manner that enables it to provide a well-regulated voltage output without use of any processor components or magnetic transformers. The circuit adjusts its internal parameters to re-optimize its performance for changes in supply voltage, environmental conditions, or electrical loading at the output
Bradley, William↗
General specifications covering requirements of aeronautic instruments
Report includes specifications for the use and production of instruments used in the navigation and operation of aircraft. Specifications are included for the following instruments: barometer or altimeter, compass, air speed meter, inclinometer, drift meter, tachometer, oil gauge, oil pressure gauge, gasoline gauge, gasoline flow indicator, distance indicator, barograph, angle of attack indicator, radiator temperature indicator, gasoline feed system pressure indicator, sextant, airplane director.
Source record↗
Preliminary Concept, Specifications, and Requirements for a Zero-Gravity Combustion Facility for Spacelab
The preliminary concept, specifications, and requirements of a reusable zero gravity combustion facility (0-GCF) for use by experimenters aboard the spacelab payload of the space transportation system (STS) orbiter are described. The facility will be amenable to any mission of the STS orbiter in which a spacelab habitable segment and pallet segment are integral and for which orbital mission plans specify induced accelerations of 0.0001 g or less for sufficiently long periods so as not to impact experiment performance.
Dewitt, Richard L.↗
Software reuse issues affecting AdaNET
The AdaNet program is reviewing its long-term goals and strategies. A significant concern is whether current AdaNet plans adequately address the major strategic issues of software reuse technology. The major reuse issues of providing AdaNet services that should be addressed as part of future AdaNet development are identified and reviewed. Before significant development proceeds, a plan should be developed to resolve the aforementioned issues. This plan should also specify a detailed approach to develop AdaNet. A three phased strategy is recommended. The first phase would consist of requirements analysis and produce an AdaNet system requirements specification. It would consider the requirements of AdaNet in terms of mission needs, commercial realities, and administrative policies affecting development, and the experience of AdaNet and other projects promoting the transfer software engineering technology. Specifically, requirements analysis would be performed to better understand the requirements for AdaNet functions. The second phase would provide a detailed design of the system. The AdaNet should be designed with emphasis on the use of existing technology readily available to the AdaNet program. A number of reuse products are available upon which AdaNet could be based. This would significantly reduce the risk and cost of providing an AdaNet system. Once a design was developed, implementation would proceed in the third phase.
Mcbride, John G.↗
Systems Maintenance Automated Repair Tasks (SMART)
SMART is a uniform automated discrepancy analysis and repair-authoring platform that improves technical accuracy and timely delivery of repair procedures for a given discrepancy (see figure a). SMART will minimize data errors, create uniform repair processes, and enhance the existing knowledge base of engineering repair processes. This innovation is the first tool developed that links the hardware specification requirements with the actual repair methods, sequences, and required equipment. SMART is flexibly designed to be useable by multiple engineering groups requiring decision analysis, and by any work authorization and disposition platform (see figure b). The organizational logic creates the link between specification requirements of the hardware, and specific procedures required to repair discrepancies. The first segment in the SMART process uses a decision analysis tree to define all the permutations between component/ subcomponent/discrepancy/repair on the hardware. The second segment uses a repair matrix to define what the steps and sequences are for any repair defined in the decision tree. This segment also allows for the selection of specific steps from multivariable steps. SMART will also be able to interface with outside databases and to store information from them to be inserted into the repair-procedure document. Some of the steps will be identified as optional, and would only be used based on the location and the current configuration of the hardware. The output from this analysis would be sent to a work authoring system in the form of a predefined sequence of steps containing required actions, tools, parts, materials, certifications, and specific requirements controlling quality, functional requirements, and limitations.
Schuh, Joseph↗
Knowledge-based requirements analysis for automating software development
We present a new software development paradigm that automates the derivation of implementations from requirements. In this paradigm, informally-stated requirements are expressed in a domain-specific requirements specification language. This language is machine-understable and requirements expressed in it are captured in a knowledge base. Once the requirements are captured, more detailed specifications and eventually implementations are derived by the system using transformational synthesis. A key characteristic of the process is that the required human intervention is in the form of providing problem- and domain-specific engineering knowledge, not in writing detailed implementations. We describe a prototype system that applies the paradigm in the realm of communication engineering: the prototype automatically generates implementations of buffers following analysis of the requirements on each buffer.
Markosian, Lawrence Z.↗
Requirements and specifications of the space telescope for scientific operations
Requirements for the scientific operations of the Space Telescope and the Science Institute are used to develop operational interfaces between user scientists and the NASA ground system. General data systems are defined for observatory scheduling, daily science planning, and science data management. Hardware, software, manpower, and space are specified for several science institute locations and support options.
West, D. K.↗
End User Acceptance - Requirements or Specifications, Certification, Testing
NASA follows top level safety requirement of two-failure tolerance (t hree levels of controls or design for minimum risk) to all catastroph ic hazards in the design of safe li-ion batteries for space use. ? R igorous development testing at appropriate levels to credible offnominal conditions and review of test data. ? Implement robust design con trols based on test results and test again to confirm safety at the a ppropriate levels. ? Stringent testing of all (100%) flight batteries (from button cells to large batteries).
Jeevarajan, Judith↗
Precise time and time interval users, requirements and specifications
The functional areas of application of Precise Time and Time Interval (PTTI) were considered and expanded. A comprehensive overview of the PTTI requirements and applications would provide an opportunity for individuals working in a specific functional area. Mutual problems, requirements, applications or successes shared by those in other functional areas were studied. Based upon the results of a two year study a compendium of PTTI requirements, applications and the means of meeting the requirements among Department of Defense components, other government agencies and major commercial users was compiled and is presented. It was found that the planning process for PTTI support for new acquisitions or new programs was less than a well defined, coordinated process. The processes are described in general terms and a generic model for requirements determination and subsequent coordination which may enhance the planning process and introduce cost benefits to the program is also presented.
Bowser, J. R.↗
4D Dynamic RNP Annual Interim Report-Year 1
This Annual Interim Report summarizes the activities led by Raytheon, in collaboration with GE Aviation and SAIC, and presents the results obtained during the first year of this research effort to expand the RNP concept to 4 dimensions relative to a dynamic frame of reference. Joint Program Development Office (JPDO)Concepts of Operations for the Next Generation Air Transportation System (NextGen) considers 4 Dimension Trajectory (4DT) procedures a key enabler to Trajectory Based Operations (TBO). The JPDO defines 4DT as a precise description of an aircraft path in space and time . While NextGen assumes that this path is defined within an Earth-reference frame, many 4DT procedure implementations will require an aircraft to precisely navigate relative to a moving reference such as another aircraft to form aggregate flows or a weather cell to allow for flows to shift. Current methods of implementing routes and flight paths rely on aircraft meeting a Required Navigation Performance (RNP) specification and being equipped with a monitoring and alerting capability to annunciate when the aircraft system is unable to meet the performance specification required for the operation. Since all aircraft today operate within the NAS relative to fixed reference points, the current RNP definition is deemed satisfactory. However, it is not well understood how the current RNP construct will support NextGen 4DT procedures where aircraft operate relative to each other or to other dynamic frames of reference. The objective of this research effort is to analyze candidate 4DT procedures from both an Air Navigation Service Provider (ANSP) and aircraft perspective, to identify their specific navigational requirements, assess the shortcomings of the current RNP construct to meet these requirements, to propose an extended 4 Dimensional Dynamic RNP (4D Dynamic RNP) construct that accounts for the dynamic spatial and temporal nature of the selected 4DT procedures, and finally, to design an experiment using the Airspace and Traffic Operations Simulation (ATOS) system to validate the 4D Dynamic RNP construct. This Annual Interim Report summarizes the activities led by Raytheon, in collaboration with GE Aviation and SAIC, and presents the results obtained during the first year of this research effort to expand the RNP concept to 4 dimensions relative to a dynamic frame of reference. A comprehensive assessment of the state-of-the-art international implementation of current RNP was completed and presented in the Contractor Report RNP State-of-the-Art Assessment, Version 4, 17 December 2008 . The team defined in detail two 4DT operations, Airborne Precision Spacing and Self-Separation, that are ideally suited to be supported by 4D Dynamic RNP and developed their respective conceptual frameworks, Required Interval Management Performance (RIMP) Version 1.1, 13 April 2009 and Required Self Separation Performance (RSSP) Version 1.1, 13 April 2009 . Finally, the team started the development of a mathematical model and simulation tool for RIMP and RSSP scheduled to be delivered during the second year of this research effort.
Finkelsztein, Daniel M.↗
Revitalization of Space-Related Human Factors, Environmental and Habitability Data
The NASA Chief Health and Medical Officer (CHMO) recently directed that the agency establish crew health standards to aid in the development of requirements for future vehicles and habitats. Response to this direction includes development of a new NASA habitability and human factors standard and an accompanying design handbook. The new standard contains high-level, over-arching principles to assure its applicability and usability across all NASA development programs. The handbook will provide detailed design requirements and suggestions that will meet the standards. The information contained in NASA-STD-3000 will be updated and included in the new design handbook. In this approach, each new program will derive detailed program-specific requirements from the new standard using the handbook as a design guide and resource. With the completion of the standard, the focus of this year s effort is the development of the new handbook: Human Integration Design Handbook (HIDH). This is an opportunity for the space flight human factors and habitability community to consolidate up-to-date data for use by NASA programs and designers as well as outside researchers and policy makers looking for the next research focus. The goal of the handbook is to help NASA design and build human space flight systems which accommodate the capabilities and limitations of the crew so as to provide an environment where the crew can live and work effectively, safely, and comfortably. Handbook contents will address that primary goal, addressing unique aspects of space flight and habitation, including reduced gravity conditions, time lags, EVA systems and day/night cycles, not addressed in other standards or handbooks. The handbook will be divided into topics similar to NASA-STD-3000 (anthropometrics, architecture, workstations, etc.) and each topic area will contain elements for designers, human factors practitioners, program managers, operators, and researchers. The handbook will include the following elements: (1) Design considerations include a clear and concise summary of what is important to designers in space vehicle / habitat design, design information to translate Earth-base knowledge to the space environment, space issues and the data necessary to address those issues, and a consistent set of terminology. (2) Updates to Lessons Learned and example solutions from Shuttle and Station program experience will provide historical examples to help prevent repeating mistakes or reinvention of the wheel. (3) Requirements will aid in the translation of standards into program specific requirements. The scope of included requirements will define the pool that each program needs to consider and tailor for their specific program. (4) Requirements rationale will help understanding of the importance of these considerations. The HIDH development team at JSC is finalizing the format of the new handbook, prioritizing topic areas for expansion and update, and contacting subject matter experts within the scientific community to assist with this effort. Plans are also being made to continue handbook expansion and maintenance to assure it remains a valuable resource for human factors and human space flight programs.
Russo, Dane↗