Kinematic Modeling Of The Milky Way Using The RAVE And GCS Stellar Surveys

NASA Astrophysics Data System (ADS)

Sharma, Sanjib; Rave Collaboration

2014-01-01

We investigate the kinematic parameters of the Milky Way disc using the Radial Velocity (RAVE) and Geneva-Copenhagen (GCS) stellar surveys. We do this by fitting a kinematic model to the data. Using two distinct Markov Chain Monte Carlo (MCMC) techniques, we investigate the full posterior distributions of the parameters given the data. For RAVE, we restrict ourselves to angular position and radial velocity for each star since these quantities are determined to high accuracy. For GCS, the data consist of the full 6 dimensional phase space but, in contrast to RAVE, are confined to the Solar neighborhood only. We show results using the traditional Gaussian distribution function and compare to the Shu distribution function that handles non-circular orbits more accurately. We investigate the `age-velocity dispersion' relation (AVR) for the three kinematic components (σ_R,σ_φ, σ_z), the radial dependence of the velocity dispersions, the Solar peculiar motion (U_Sun,V_Sun, W_Sun) and the circular velocity (v_c) at the Sun. We investigate models with and without a thick disc. We find that the kinematic parameters derived from RAVE and GCS are in good agreement. The Shu model fits the RAVE data better than the Gaussian model, but a perfect fit could not be found for either model. Furthermore, the Gaussian model predicts a positive radial gradient for the velocity dispersion, while the Shu model does not. The measured Solar peculiar motion, U_Sun=10.5 ±0.13, V_Sun=10.27±0.11, and W_Sun=7.44± 0.09, is in good agreement with estimates of Schonrich et al (2010) but our values for (U_Sun, V_Sun) are slightly lower. We stress that V_Sun is a highly model-dependent quantity and claims of accuracy must be treated with caution. For RAVE, we find that v_c = 212 ±1.4 km/s ; this is a lower bound on the true value as the vertical dependence of asymmetric drift for an isothermal population has been ignored in our analysis.

Chemical gradients in the Milky Way from the RAVE data. I. Dwarf stars

NASA Astrophysics Data System (ADS)

Boeche, C.; Siebert, A.; Piffl, T.; Just, A.; Steinmetz, M.; Sharma, S.; Kordopatis, G.; Gilmore, G.; Chiappini, C.; Williams, M.; Grebel, E. K.; Bland-Hawthorn, J.; Gibson, B. K.; Munari, U.; Siviero, A.; Bienaymé, O.; Navarro, J. F.; Parker, Q. A.; Reid, W.; Seabroke, G. M.; Watson, F. G.; Wyse, R. F. G.; Zwitter, T.

2013-11-01

Aims: We aim at measuring the chemical gradients of the elements Mg, Al, Si, and Fe along the Galactic radius to provide new constraints on the chemical evolution models of the Galaxy and Galaxy models such as the Besançon model. Thanks to the large number of stars of our RAVE sample we can study how the gradients vary as function of the distance from the Galactic plane. Methods: We analysed three different samples selected from three independent datasets: a sample of 19 962 dwarf stars selected from the RAVE database, a sample of 10 616 dwarf stars selected from the Geneva-Copenhagen Survey (GCS) dataset, and a mock sample (equivalent to the RAVE sample) created by using the GALAXIA code, which is based on the Besançon model. The three samples were analysed by using the very same method for comparison purposes. We integrated the Galactic orbits and obtained the guiding radii (Rg) and the maximum distances from the Galactic plane reached by the stars along their orbits (Zmax). We measured the chemical gradients as functions of Rg at different Zmax. Results: We found that the chemical gradients of the RAVE and GCS samples are negative and show consistent trends, although they are not equal: at Zmax< 0.4 kpc and 4.5 RAVE sample is d [Fe/H] /dRg = -0.065 dex kpc-1, whereas for the GCS sample it is d [Fe/H] /dRg = -0.043 dex kpc-1 with internal errors of ±0.002 and ±0.004 dex kpc-1, respectively. The gradients of the RAVE and GCS samples become flatter at larger Zmax. Conversely, the mock sample has a positive iron gradient of d [Fe/H] /dRg = +0.053 ± 0.003 dex kpc-1 at Zmax< 0.4 kpc and remains positive at any Zmax. These positive and unrealistic values originate from the lack of correlation between metallicity and tangential velocity in the Besançon model. In addition, the low metallicity and asymmetric drift of the thick disc causes a shift of the stars towards lower Rg and metallicity which, together with the thin

The RAVE-on Catalog of Stellar Atmospheric Parameters and Chemical Abundances for Chemo-dynamic Studies in the Gaia Era

NASA Astrophysics Data System (ADS)

Casey, Andrew R.; Hawkins, Keith; Hogg, David W.; Ness, Melissa; Rix, Hans-Walter; Kordopatis, Georges; Kunder, Andrea; Steinmetz, Matthias; Koposov, Sergey; Enke, Harry; Sanders, Jason; Gilmore, Gerry; Zwitter, Tomaž; Freeman, Kenneth C.; Casagrande, Luca; Matijevič, Gal; Seabroke, George; Bienaymé, Olivier; Bland-Hawthorn, Joss; Gibson, Brad K.; Grebel, Eva K.; Helmi, Amina; Munari, Ulisse; Navarro, Julio F.; Reid, Warren; Siebert, Arnaud; Wyse, Rosemary

2017-05-01

The orbits, atmospheric parameters, chemical abundances, and ages of individual stars in the Milky Way provide the most comprehensive illustration of galaxy formation available. The Tycho-Gaia Astrometric Solution (TGAS) will deliver astrometric parameters for the largest ever sample of Milky Way stars, though its full potential cannot be realized without the addition of complementary spectroscopy. Among existing spectroscopic surveys, the RAdial Velocity Experiment (RAVE) has the largest overlap with TGAS (≳200,000 stars). We present a data-driven re-analysis of 520,781 RAVE spectra using The Cannon. For red giants, we build our model using high-fidelity APOGEE stellar parameters and abundances for stars that overlap with RAVE. For main sequence and sub-giant stars, our model uses stellar parameters from the K2/EPIC. We derive and validate effective temperature T eff, surface gravity log g, and chemical abundances of up to seven elements (O, Mg, Al, Si, Ca, Fe, and Ni). We report a total of 1,685,851 elemental abundances with a typical precision of 0.07 dex, a substantial improvement over previous RAVE data releases. The synthesis of RAVE-on and TGAS is the most powerful data set for chemo-dynamic analyses of the Milky Way ever produced.

Correlations between age, kinematics, and chemistry as seen by the RAVE survey

NASA Astrophysics Data System (ADS)

Wojno, Jennifer; Kordopatis, Georges; Steinmetz, Matthias; McMillan, Paul; Binney, James; Famaey, Benoit; Monari, Giacomo; Minchev, Ivan; Wyse, Rosemary F. G.; Antoja, Teresa; Siebert, Arnaud; Carrillo, Ismael; Bland-Hawthorn, Joss; K Grebel, Eva; Zwitter, Tomaž; Bienaymé, Olivier; Gibson, Brad; Kunder, Andrea; Munari, Ulisse; Navarro, Julio; Parker, Quentin; Reid, Warren; Seabroke, George

2018-04-01

We explore the connections between stellar age, chemistry, and kinematics across a Galactocentric distance of 7.5 < R (kpc) < 9.0, using a sample of ˜12 000 intermediate-mass (FGK) turnoff stars observed with the RAdial Velocity Experiment (RAVE) survey. The kinematics of this sample are determined using radial velocity measurements from RAVE, and parallax and proper motion measurements from the Tycho-Gaia Astrometric Solution (TGAS). In addition, ages for RAVE stars are determined using a Bayesian method, taking TGAS parallaxes as a prior. We divide our sample into young (0 < τ < 3 Gyr) and old (8 < τ < 13 Gyr) populations, and then consider different metallicity bins for each of these age groups. We find significant differences in kinematic trends of young and old, metal-poor and metal-rich, stellar populations. In particular, we find a strong metallicity dependence in the mean Galactocentric radial velocity as a function of radius (∂VR/∂R) for young stars, with metal-rich stars having a much steeper gradient than metal-poor stars. For ∂Vϕ/∂R, young, metal-rich stars significantly lag the LSR with a slightly positive gradient, while metal-poor stars show a negative gradient above the LSR. We interpret these findings as correlations between metallicity and the relative contributions of the non-axisymmetries in the Galactic gravitational potential (the spiral arms and the bar) to perturb stellar orbits.

An outbreak of mumps among young adults in Vancouver, British Columbia, associated with 'rave' parties.

PubMed

Buxton, J; Craig, C; Daly, P; Bigham, M; Bell, A; Fyfe, M

1999-01-01

In early 1997 an unexpectedly high number of cases of mumps was reported in Vancouver, British Columbia. A case control study was conducted to address four objectives: 1) Describe the outbreak and the population at risk, 2) examine the impact of mumps on this population, 3) identify personal risk factors for infection, and 4) test the hypothesis that social gatherings, 'rave' parties in particular, were a risk factor in this outbreak. Mumps infection was associated with: attending a rave party [OR = 17; 95% CI: 2.7-710], residing in Vancouver [OR = 3.7; 95% CI: 1.4-10], and contact with a person with mumps [OR = 13; 95% CI: 2-552], during the 'exposure' period. Vaccine effectiveness, ascertained by self-reported immunization status, was 80% [95% CI: 29%-96%]. Attendance at rave parties was associated with mumps infection during this outbreak. Many persons aged 17-40 may remain susceptible to mumps; in BC these persons are eligible for one dose of MMR and should be encouraged to be vaccinated.

Correlations between age, kinematics, and chemistry as seen by the RAVE survey

NASA Astrophysics Data System (ADS)

Wojno, Jennifer; Kordopatis, Georges; Steinmetz, Matthias; McMillan, Paul; Binney, James; Famaey, Benoit; Monari, Giacomo; Minchev, Ivan; Wyse, Rosemary F. G.; Antoja, Teresa; Siebert, Arnaud; Carrillo, Ismael; Bland-Hawthorn, Joss; Grebel, Eva K.; Zwitter, Tomaž; Bienaymé, Olivier; Gibson, Brad; Kunder, Andrea; Munari, Ulisse; Navarro, Julio; Parker, Quentin; Reid, Warren; Seabroke, George

2018-07-01

We explore the connections between stellar age, chemistry, and kinematics across a Galactocentric distance of 7.5 < R(kpc) < 9.0, using a sample of ˜12 000 intermediate-mass (FGK) turn-off stars observed with the RAdial Velocity Experiment (RAVE) survey. The kinematics of this sample are determined using radial velocity measurements from RAVE, and parallax and proper motion measurements from the Tycho-Gaia Astrometric Solution (TGAS). In addition, ages for RAVE stars are determined using a Bayesian method, taking TGAS parallaxes as a prior. We divide our sample into young (0 < τ < 3 Gyr) and old (8 < τ < 13 Gyr) populations, and then consider different metallicity bins for each of these age groups. We find significant differences in kinematic trends of young and old, metal-poor and metal-rich, stellar populations. In particular, we find a strong metallicity dependence in the mean Galactocentric radial velocity as a function of radius (partial {V_R}/partial R) for young stars, with metal-rich stars having a much steeper gradient than metal-poor stars. For partial {V_{φ }}/partial R, young, metal-rich stars significantly lag the LSR with a slightly positive gradient, while metal-poor stars show a negative gradient above the LSR. We interpret these findings as correlations between metallicity and the relative contributions of the non-axisymmetries in the Galactic gravitational potential (the spiral arms and the bar) to perturb stellar orbits.

The RAVE/VERTIGO vertex reconstruction toolkit and framework

NASA Astrophysics Data System (ADS)

Waltenberger, W.; Mitaroff, W.; Moser, F.; Pflugfelder, B.; Riedel, H. V.

2008-07-01

A detector-independent toolkit for vertex reconstruction (RAVE1) is being developed, along with a standalone framework (VERTIGO2) for testing, analyzing and debugging. The core algorithms represent state-of-the-art for geometric vertex finding and fitting by both linear (Kalman filter) and robust estimation methods. Main design goals are ease of use, flexibility for embedding into existing software frameworks, extensibility, and openness. The implementation is based on modern object-oriented techniques, is coded in C++ with interfaces for Java and Python, and follows an open-source approach. A beta release is available.

Retrieval, automaticity, vocabulary elaboration, orthography (RAVE-O): a comprehensive, fluency-based reading intervention program.

PubMed

Wolf, M; Miller, L; Donnelly, K

2000-01-01

The most important implication of the double-deficit hypothesis (Wolf & Bowers, in this issue) concerns a new emphasis on fluency and automaticity in intervention for children with developmental reading disabilities. The RAVE-O (Retrieval, Automaticity, Vocabulary Elaboration, Orthography) program is an experimental, fluency-based approach to reading intervention that is designed to accompany a phonological analysis program. In an effort to address multiple possible sources of dysfluency in readers with disabilities, the program involves comprehensive emphases both on fluency in word attack, word identification, and comprehension and on automaticity in underlying componential processes (e.g., phonological, orthographic, semantic, and lexical retrieval skills). The goals, theoretical principles, and applied activities of the RAVE-O curriculum are described with particular stress on facilitating the development of rapid orthographic pattern recognition and on changing children's attitudes toward language.

Spectroscopic Validation of Low-metallicity Stars from RAVE

NASA Astrophysics Data System (ADS)

Placco, Vinicius M.; Beers, Timothy C.; Santucci, Rafael M.; Chanamé, Julio; Sepúlveda, María Paz; Coronado, Johanna; Points, Sean D.; Kaleida, Catherine C.; Rossi, Silvia; Kordopatis, Georges; Lee, Young Sun; Matijevič, Gal; Frebel, Anna; Hansen, Terese T.; Holmbeck, Erika M.; Rasmussen, Kaitlin C.; Roederer, Ian U.; Sakari, Charli M.; Whitten, Devin D.

2018-06-01

We present results from a medium-resolution (R ∼ 2000) spectroscopic follow-up campaign of 1694 bright (V < 13.5), very metal-poor star candidates from the RAdial Velocity Experiment (RAVE). Initial selection of the low-metallicity targets was based on the stellar parameters published in RAVE Data Releases 4 and 5. Follow up was accomplished with the Gemini-N and Gemini-S, the ESO/NTT, the KPNO/Mayall, and the SOAR telescopes. The wavelength coverage for most of the observed spectra allows for the determination of carbon and α-element abundances, which are crucial for considering the nature and frequency of the carbon-enhanced metal-poor (CEMP) stars in this sample. We find that 88% of the observed stars have [{Fe}/{{H}}] ≤ ‑1.0, 61% have [{Fe}/{{H}}] ≤ ‑2.0, and 3% have [{Fe}/{{H}}] ≤ ‑3.0 (with four stars at [{Fe}/{{H}}] ≤ ‑3.5). There are 306 CEMP star candidates in this sample, and we identify 169 CEMP Group I, 131 CEMP Group II, and 6 CEMP Group III stars from the A(C) versus [Fe/H] diagram. Inspection of the [α /{{C}}] abundance ratios reveals that five of the CEMP Group II stars can be classified as “mono-enriched second-generation” stars. Gaia DR1 matches were found for 734 stars, and we show that transverse velocities can be used as a confirmatory selection criteria for low-metallicity candidates. Selected stars from our validated list are being followed-up with high-resolution spectroscopy to reveal their full chemical-abundance patterns for further studies.

Chromospherically Active Stars in the RAVE Survey. II. Young Dwarfs in the Solar Neighborhood

NASA Astrophysics Data System (ADS)

Žerjal, M.; Zwitter, T.; Matijevič, G.; Grebel, E. K.; Kordopatis, G.; Munari, U.; Seabroke, G.; Steinmetz, M.; Wojno, J.; Bienaymé, O.; Bland-Hawthorn, J.; Conrad, C.; Freeman, K. C.; Gibson, B. K.; Gilmore, G.; Kunder, A.; Navarro, J.; Parker, Q. A.; Reid, W.; Siviero, A.; Watson, F. G.; Wyse, R. F. G.

2017-01-01

A large sample of over 38,000 chromospherically active candidate solar-like stars and cooler dwarfs from the RAVE survey is addressed in this paper. An improved activity identification with respect to the previous study was introduced to build a catalog of field stars in the solar neighborhood with an excess emission flux in the calcium infrared triplet wavelength region. The central result of this work is the calibration of the age-activity relation for main-sequence dwarfs in a range from a few 10 {Myr} up to a few Gyr. It enabled an order of magnitude age estimation of the entire active sample. Almost 15,000 stars are shown to be younger than 1 {Gyr} and ˜2000 younger than 100 {Myr}. The young age of the most active stars is confirmed by their position off the main sequence in the J - K versus {N}{UV}-V diagram showing strong ultraviolet excess, mid-infrared excess in the J - K versus {W}1-{W}2 diagram, and very cool temperatures (J-K> 0.7). They overlap with the reference pre-main-sequence RAVE stars often displaying X-ray emission. The activity level increasing with the color reveals their different nature from the solar-like stars and probably represents an underlying dynamo-generating magnetic fields in cool stars. Of the RAVE objects from DR5, 50% are found in the TGAS catalog and supplemented with accurate parallaxes and proper motions by Gaia. This makes the database of a large number of young stars in a combination with RAVE’s radial velocities directly useful as a tracer of the very recent large-scale star formation history in the solar neighborhood. The data are available online in the Vizier database.

Optimizing Radiation Therapy Quality Assurance in Clinical Trials: A TROG 08.03 RAVES Substudy

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

Trada, Yuvnik, E-mail: yuvnik@gmail.com; Kneebone, Andrew; Paneghel, Andrea

2015-12-01

Purpose: To explore site- and clinician-level factors associated with protocol violations requiring real-time-review (RTR) resubmission in a multicenter clinical trial to help tailor future quality assurance (QA) protocols. Methods and Materials: RAVES (Radiation Therapy–Adjuvant vs Early Salvage) (Trans-Tasman Radiation Oncology Group 08.03) is a randomized trial comparing adjuvant with early salvage radiation therapy in men with positive surgical margins or pT3 disease after prostatectomy. Quality assurance in RAVES required each clinician and site to submit a credentialing dummy run (DR) and for each patient's radiation therapy plan to undergo external RTR before treatment. Prospectively defined major violations from trial protocol requiredmore » remedy and resubmission. Site and clinician factors associated with RTR resubmission were examined using hierarchical modeling. Results: Data were collected from 171 consecutive patients, treated by 46 clinicians at 32 hospitals. There were 47 RTR resubmissions (27%) due to 65 major violations. The relative rate of resubmission decreased by 29% per year as the study progressed (odds ratio OR. 0.71, P=.02). The majority of resubmissions were due to contouring violations (39 of 65) and dosimetric violations (22 of 65). For each additional patient accrued, significant decreases in RTR resubmission were seen at both clinician level (OR 0.75, P=.02) and site level (OR 0.72, P=.01). The rate of resubmission due to dosimetric violations was only 1.6% after the first 5 patients. Use of IMRT was associated with lower rates of resubmission compared with 3-dimensional conformal radiation therapy (OR 0.38, P=.05). Conclusion: Several low- and high-risk factors that may assist with tailoring future clinical trial QA were identified. Because the real-time resubmission rate was largely independent of the credentialing exercise, some form of RTR QA is recommended. The greatest benefit from QA was derived early in trial

Chromospherically Active Stars in the RAVE Survey

NASA Astrophysics Data System (ADS)

Žerjal, M.; Zwitter, T.; Matijevič, G.; Strassmeier, K. G.

2014-01-01

We present a qualitative characterization of activity levels of a large database of ~44,000 candidate RAVE stars (unbiased, magnitude limited medium resolution survey) that show chromospheric emission in the Ca II infrared triplet and this vastly enlarges previously known samples. Our main motivation to study these stars is the anti-correlation of chromospheric activity and stellar ages that could be calibrated using stellar clusters with known ages. Locally linear embedding used for a morphological classification of spectra revealed 53,347 cases with a suggested emission component in the calcium lines. We analyzed a subsample of ~44,000 stars with S/N>20 using a spectral subtraction technique where observed reference spectra of inactive stars were used as templates instead of synthetic ones. Both the equivalent width of the excess emission for each calcium line and their sum is derived for all candidate active stars with no respect to the origin of their emission flux. ~17,800 spectra show a detectable chromospheric flux with at least 2 σ confidence level. The overall distribution of activity levels shows a bimodal shape, with the first peak coinciding with inactive stars and the second with the pre-main-sequence cases.

Chromospherically Active Stars in the RAdial Velocity Experiment (RAVE) Survey. I. The Catalog

NASA Astrophysics Data System (ADS)

Žerjal, M.; Zwitter, T.; Matijevič, G.; Strassmeier, K. G.; Bienaymé, O.; Bland-Hawthorn, J.; Boeche, C.; Freeman, K. C.; Grebel, E. K.; Kordopatis, G.; Munari, U.; Navarro, J. F.; Parker, Q. A.; Reid, W.; Seabroke, G.; Siviero, A.; Steinmetz, M.; Wyse, R. F. G.

2013-10-01

RAVE, the unbiased magnitude limited survey of southern sky stars, contained 456,676 medium-resolution spectra at the time of our analysis. Spectra cover the Ca II infrared triplet (IRT) range, which is a known indicator of chromospheric activity. Our previous work classified all spectra using locally linear embedding. It identified 53,347 cases with a suggested emission component in calcium lines. Here, we use a spectral subtraction technique to measure the properties of this emission. Synthetic templates are replaced by the observed spectra of non-active stars to bypass the difficult computations of non-local thermal equilibrium profiles of the line cores and stellar parameter dependence. We derive both the equivalent width of the excess emission for each calcium line on a 5 Å wide interval and their sum EWIRT for ~44,000 candidate active dwarf stars with signal-to-noise ratio >20, with no cuts on the basis of the source of their emission flux. From these, ~14,000 show a detectable chromospheric flux with at least a 2σ confidence level. Our set of active stars vastly enlarges previously known samples. Atmospheric parameters and, in some cases, radial velocities of active stars derived from automatic pipelines suffer from systematic shifts due to their shallower calcium lines. We re-estimate the effective temperature, metallicity, and radial velocities for candidate active stars. The overall distribution of activity levels shows a bimodal shape, with the first peak coinciding with non-active stars and the second with the pre-main-sequence cases. The catalog will be made publicly available with the next RAVE public data releases.

Addicted to Democracy: "South Park" and the Salutary Effects of Agitation (Reflections of a Ranting and Raving "South Park" Junkie)

ERIC Educational Resources Information Center

Bruna, Katherine Richardson

2004-01-01

This article presents reflections of a ranting and raving "South Park" junkie. The church the author goes to is Unitarian Universalist (UU). UUism is the religion for people who don't believe in religion but somehow feel the need to regularly assemble in a religious tradition and affirm their nontraditional religiosity. From what the author can…

The local rotation curve of the Milky Way based on SEGUE and RAVE data

NASA Astrophysics Data System (ADS)

Sysoliatina, K.; Just, A.; Golubov, O.; Parker, Q. A.; Grebel, E. K.; Kordopatis, G.; Zwitter, T.; Bland-Hawthorn, J.; Gibson, B. K.; Kunder, A.; Munari, U.; Navarro, J.; Reid, W.; Seabroke, G.; Steinmetz, M.; Watson, F.

2018-06-01

Aims: We construct the rotation curve of the Milky Way in the extended solar neighbourhood using a sample of Sloan Extension for Galactic Understanding and Exploration (SEGUE) G-dwarfs. We investigate the rotation curve shape for the presence of any peculiarities just outside the solar radius as has been reported by some authors. Methods: Using the modified Strömberg relation and the most recent data from the RAdial Velocity Experiment (RAVE), we determine the solar peculiar velocity and the radial scale lengths for the three populations of different metallicities representing the Galactic thin disc. Subsequently, with the same binning in metallicity for the SEGUE G-dwarfs, we construct the rotation curve for a range of Galactocentric distances from 7 to 10 kpc. We approach this problem in a framework of classical Jeans analysis and derive the circular velocity by correcting the mean tangential velocity for the asymmetric drift in each distance bin. With SEGUE data we also calculate the radial scale length of the thick disc taking as known the derived peculiar motion of the Sun and the slope of the rotation curve. Results: The tangential component of the solar peculiar velocity is found to be V ⊙ = 4.47 ± 0.8 km s-1 and the corresponding scale lengths from the RAVE data are Rd(0 < [Fe/H] < 0.2) = 2.07 ± 0.2 kpc, Rd(-0.2 < [Fe/H] < 0) = 2.28 ± 0.26 kpc and Rd(-0.5 < [Fe/H] <-0.2) = 3.05 ± 0.43 kpc. In terms of the asymmetric drift, the thin disc SEGUE stars are demonstrated to have dynamics similar to the thin disc RAVE stars, therefore the scale lengths calculated from the SEGUE sample have close values: Rd(0 < [Fe/H] < 0.2) = 1.91 ± 0.23 kpc, Rd(-0.2 < [Fe/H] < 0) = 2.51 ± 0.25 kpc and Rd(-0.5 < [Fe/H] <-0.2) = 3.55 ± 0.42 kpc. The rotation curve constructed through SEGUE G-dwarfs appears to be smooth in the selected radial range 7 kpc < R < 10 kpc. The inferred power law index of the rotation curve is 0.033 ± 0.034, which corresponds to a local slope

"Partying" hard: party style, motives for and effects of MDMA use at rave parties.

PubMed

M ter Bogt, Tom F; Engels, Rutger C M E

2005-01-01

This study examines motives for and consequences of MDMA use at different types of dance parties in the Netherlands (2001 and 2002). Participants were 490 visitors of three different types of rave parties, "club/mellow," "trance/mainstream," and "hardcore" (34% female, mean age 22.3 years, 76.5% MDMA users). Partygoers are motivated primarily by the energetic and euphoric effects they expect from MDMA. Quantity of MDMA use is associated with hardcore and trance/mainstream party style, with the motives of euphoria, sexiness, self-insight, and sociability/flirtatiousness (negative), and with gender, educational level (negative), and MDMA use by friends. Women report more (acute) negative effects--depression, confusion, loss of control, suspiciousness, edginess, nausea, dizziness--than men; and in particular, women who are motivated to cope with their problems by using MDMA are at risk. Men's polydrug use and notably their motivation to conform to friends by using MDMA are associated with negative effects.

High incidence of mild hyponatraemia in females using ecstasy at a rave party.

PubMed

van Dijken, Geetruida D; Blom, Renske E; Hené, Ronald J; Boer, Walther H; NIGRAM Consortium

2013-09-01

Globally, millions of subjects regularly use ecstasy, a drug popular due to its empathogenic and entactogenic effects. Dilutional hyponatraemia, mainly caused by direct stimulation of antidiuretic hormone (ADH) secretion by ecstasy, is among the many side effects of the drug (active substance 3, 4-methylenedioxymethamphetamine, MDMA). Severe, symptomatic hyponatraemia related to the use of MDMA has been reported in more than 30 cases. The mortality of this complication is high and mainly females are involved. Dramatic cases that reach the literature probably represent the tip of the iceberg. We decided to study the incidence of hyponatraemia in subjects using MDMA at an indoor rave party. The study was performed at the indoor event 'Awakenings', held in Amsterdam in the fall of 2010. The plasma sodium concentration was measured at the party using a point of care method in 63 subjects using MDMA and 44 controls. The use of MDMA was confirmed by a urine test. The plasma sodium concentration in subjects using MDMA was significantly lower than in those not using the drug (138 ± 2 mmol/L versus 140 ± 2 mmol/L, respectively, P < 0.001). The overall incidence of hyponatraemia, defined as a plasma sodium concentration <136 mmol/L, was 14.3% in MDMA users (9/63 subjects). Most cases of hyponatraemia occurred in females, in whom the incidence was 26.7% (8 of 30 females), with lowest values of 133 mmol/L. The number of ecstasy pills ingested by the females developing hyponatraemia was not different from that ingested by those who did not develop this complication. Fluid intake in ecstasy users exceeded that of non-users, suggesting a dipsogenic effect of the drug. Only 3% of males, but no less than ∼25% of females attending a rave party and using MDMA developed mild hyponatraemia during the event. Especially females are therefore probably also at risk of developing severe symptomatic hyponatraemia. Not using MDMA is obviously the best option to prevent MDMA

The vertical metallicity gradients of mono-age stellar populations in the Milky Way with the RAVE and Gaia data

NASA Astrophysics Data System (ADS)

Ciucǎ, Ioana; Kawata, Daisuke; Lin, Jane; Casagrande, Luca; Seabroke, George; Cropper, Mark

2018-03-01

We investigate the vertical metallicity gradients of five mono-age stellar populations between 0 and 11 Gyr for a sample of 18 435 dwarf stars selected from the cross-matched Tycho-Gaia Astrometric Solution and Radial Velocity Experiment (RAVE) Data Release 5. We find a correlation between the vertical metallicity gradients and age, with no vertical metallicity gradient in the youngest population and an increasingly steeper negative vertical metallicity gradient for the older stellar populations. The metallicity at disc plane remains almost constant between 2 and 8 Gyr, and it becomes significantly lower for the 8 < τ ≤ 11 Gyr population. The current analysis also reveals that the intrinsic dispersion in metallicity increases steadily with age. We discuss that our results are consistent with a scenario that (thin) disc stars formed from a flaring (thin) star-forming disc.

Search for Stellar Streams Based on Data from the RAVE5 and Gaia TGAS Catalogues

NASA Astrophysics Data System (ADS)

Bajkova, A. T.; Bobylev, V. V.

2018-03-01

We have analyzed the space velocities of stars with the proper motions and trigonometric parallaxes from the Gaia TGAS catalogue in combination with the line-of-sight velocities from the RAVE5 catalogue. In the V, √ {{U^2} + 2{V^2}} velocity plane we have identified three clumps, BB17-1, BB17-2, and BB17-3, in the region of large velocities ( V<-150 km s-1). The stars of the BB17-1 and BB17-2 clumps are associated with the kinematic groups VelHel-6 and VelHel-7 detected previously by Helmi et al. We give the greatest attention to the BB17-3 clump. The latter is shown to be most closely linked with the debris of the globular cluster ω Cen. In the BB17-3 clump we have identified 28 stars with a low velocity dispersion with respect to the center of their distribution. All these stars have very close individual age estimates: log t ≈ 10. The distribution of metallicity indices in this sample is typical for the stars of the globular cluster ω Cen. In our opinion, the BB17-3 clump can be described as a homogeneous stream in the debris of the cluster ω Cen.

Who is 'Molly'? MDMA adulterants by product name and the impact of harm-reduction services at raves.

PubMed

Saleemi, Sarah; Pennybaker, Steven J; Wooldridge, Missi; Johnson, Matthew W

2017-08-01

Methylenedioxymethamphetamine (MDMA), often sold as 'Ecstasy' or 'Molly', is commonly used at music festivals and reported to be responsible for an increase in deaths over the last decade. Ecstasy is often adulterated and contains compounds that increase morbidity and mortality. While users and clinicians commonly assume that products sold as Molly are less-adulterated MDMA products, this has not been tested. Additionally, while pill-testing services are sometimes available at raves, the assumption that these services decrease risky drug use has not been studied. This study analyzed data collected by the pill-testing organization, DanceSafe, from events across the United States from 2010 to 2015. Colorimetric reagent assays identified MDMA in only 60% of the 529 samples collected. No significant difference in the percentage of samples testing positive for MDMA was determined between Ecstasy and Molly. Individuals were significantly less likely to report intent to use a product if testing did not identify MDMA (relative risk (RR) = 0.56, p = 0.01). Results suggest that Molly is not a less-adulterated substance, and that pill-testing services are a legitimate harm-reduction service that decreases intent to consume potentially dangerous substances and may warrant consideration by legislators for legal protection. Future research should further examine the direct effects of pill-testing services and include more extensive pill-testing methods.

Discovering system requirements

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

Bahill, A.T.; Bentz, B.; Dean, F.F.

1996-07-01

Cost and schedule overruns are often caused by poor requirements that are produced by people who do not understand the requirements process. This report provides a high-level overview of the system requirements process, explaining types, sources, and characteristics of good requirements. System requirements, however, are seldom stated by the customer. Therefore, this report shows ways to help you work with your customer to discover the system requirements. It also explains terminology commonly used in the requirements development field, such as verification, validation, technical performance measures, and the various design reviews.

Managing System of Systems Requirements with a Requirements Screening Group

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

Ronald R. Barden

2012-07-01

Figuring out an effective and efficient way to manage not only your Requirement’s Baseline, but also the development of all your individual requirements during a Program’s/Project’s Conceptual and Development Life Cycle Stages can be both daunting and difficult. This is especially so when you are dealing with a complex and large System of Systems (SoS) Program with potentially thousands and thousands of Top Level Requirements as well as an equal number of lower level System, Subsystem and Configuration Item requirements that need to be managed. This task is made even more overwhelming when you have to add in integration withmore » multiple requirements’ development teams (e.g., Integrated Product Development Teams (IPTs)) and/or numerous System/Subsystem Design Teams. One solution for tackling this difficult activity on a recent large System of Systems Program was to develop and make use of a Requirements Screening Group (RSG). This group is essentially a Team made up of co-chairs from the various Stakeholders with an interest in the Program of record that are enabled and accountable for Requirements Development on the Program/Project. The RSG co-chairs, often with the help of individual support team, work together as a Program Board to monitor, make decisions on, and provide guidance on all Requirements Development activities during the Conceptual and Development Life Cycle Stages of a Program/Project. In addition, the RSG can establish and maintain the Requirements Baseline, monitor and enforce requirements traceability across the entire Program, and work with other elements of the Program/Project to ensure integration and coordination.« less

Kinematic structures of the solar neighbourhood revealed by Gaia DR1/TGAS and RAVE

NASA Astrophysics Data System (ADS)

Kushniruk, I.; Schirmer, T.; Bensby, T.

2017-12-01

Context. The velocity distribution of stars in the solar neighbourhood is inhomogeneous and rich with stellar streams and kinematic structures. These may retain important clues regarding the formation and dynamical history of the Milky Way. However, the nature and origin of many of the streams and structures is unclear, hindering our understanding of how the Milky Way formed and evolved. Aims: We aim to study the velocity distribution of stars of the solar neighbourhood and investigate the properties of individual kinematic structures in order to improve our understanding of their origins. Methods: Using the astrometric data provided by Gaia DR1/TGAS and radial velocities from RAVE DR5 we perform a wavelet analysis with the à trous algorithm of 55 831 stars that have U and V velocity uncertainties less than 4 km s-1. An auto-convolution histogram method is used to filter the output data, and we then run Monte Carlo simulations to verify that the detected structures are real and are not caused by noise due to velocity uncertainties. Additionally we analysed our stellar sample by splitting all stars into a nearby sample (<300 pc) and a distant sample (>300 pc), and two chemically defined samples that to a first degree represent the thin and the thick disks. Results: We detect 19 kinematic structures in the solar neighbourhood in the range of scales 3-16 km s-1 at the 3σ confidence level. Among them we identified well-known groups (such as Hercules, Sirius, Coma Berenices, Pleiades, and Wolf 630), confirmed recently detected groups (such as Antoja12 and Bobylev16), and detected a new structure at (U,V) ≈ (37,8) km s-1. Another three new groups are tentatively detected, but require further confirmation. Some of the detected groups show clear dependence on distance in the sense that they are only present in the nearby sample (<300 pc), and others appear to be correlated with chemistry as they are only present in one of the chemically defined thin and thick disk

Advanced EVA system design requirements study: EVAS/space station system interface requirements

NASA Technical Reports Server (NTRS)

Woods, T. G.

1985-01-01

The definition of the Extravehicular Activity (EVA) systems interface requirements and accomodations for effective integration of a production EVA capability into the space station are contained. A description of the EVA systems for which the space station must provide the various interfaces and accomodations are provided. The discussion and analyses of the various space station areas in which the EVA interfaces are required and/or from which implications for EVA system design requirements are derived, are included. The rationale is provided for all EVAS mechanical, fluid, electrical, communications, and data system interfaces as well as exterior and interior requirements necessary to facilitate EVA operations. Results of the studies supporting these discussions are presented in the appendix.

The metal-poor stellar halo in RAVE-TGAS and its implications for the velocity distribution of dark matter

NASA Astrophysics Data System (ADS)

Herzog-Arbeitman, Jonah; Lisanti, Mariangela; Necib, Lina

2018-04-01

The local velocity distribution of dark matter plays an integral role in interpreting the results from direct detection experiments. We previously showed that metal-poor halo stars serve as excellent tracers of the virialized dark matter velocity distribution using a high-resolution hydrodynamic simulation of a Milky Way-like halo. In this paper, we take advantage of the first Gaia data release, coupled with spectroscopic measurements from the RAdial Velocity Experiment (RAVE), to study the kinematics of stars belonging to the metal-poor halo within an average distance of ~5 kpc of the Sun. We study stars with iron abundances [Fe/H] < ‑1.5 and ‑1.8 that are located more than 1.5 kpc from the Galactic plane. Using a Gaussian mixture model analysis, we identify the stars that belong to the halo population, as well as some kinematic outliers. We find that both metallicity samples have similar velocity distributions for the halo component, within uncertainties. Assuming that the stellar halo velocities adequately trace the virialized dark matter, we study the implications for direct detection experiments. The Standard Halo Model, which is typically assumed for dark matter, is discrepant with the empirical distribution by ~6σ, predicts fewer high-speed particles, and is anisotropic. As a result, the Standard Halo Model overpredicts the nuclear scattering rate for dark matter masses below ~10 GeV. The kinematic outliers that we identify may potentially be correlated with dark matter substructure, though further study is needed to establish this correspondence.

VizieR Online Data Catalog: RAVE open cluster pairs, groups and complexes (Conrad+, 2017)

NASA Astrophysics Data System (ADS)

Conrad, C.; Scholz, R.-D.; Kharchenko, N. V.; Piskunov, A. E.; Roeser, S.; Schilbach, E.; de Jong, R. S.; Schnurr, O.; Steinmetz, M.; Grebel, E. K.; Zwitter, T.; Bienayme, O.; Bland-Hawthorn, J.; Gibson, B. K.; Gilmore, G.; Kordopatis, G.; Kunder, A.; Navarro, J. F.; Parker, Q.; Reid, W.; Seabroke, G.; Siviero, A.; Watson, F.; Wyse, R.

2017-01-01

The presented tables summarize the parameters for the clusters and the mean values for the detected potential cluster groupings. The ages, distances and proper motions were taken from the Catalogue of Open Cluster Data (COCD; Kharchenko et al. 2005, Cat. J/A+A/438/1163, J/A+A/440/403), while additional radial velocities and metallicities were obtained from the Radial Velocity Experiment (RAVE; Kordopatis et al. 2013AJ....146..134K, Cat. III/272 ) and from the online compilation provided by Dias et al. (2002, See B/ocl). A description of the determination for the radial velocities and metallicities can be found in Conrad et al. 2014A&A...562A..54C. The potential groupings were identified using an adapted Friends-of-Friends algorithm with two sets of linking lengths, namely (100pc, 10km/s) and (100pc, 20km/s). The table clupar.dat (combining Tables A.1 and A.2 from the Appendix of our paper): Tables comprises the parameters collected for the final working sample of 432 clusters with available radial velocities, namely coordinates and proper motions in equatorial and galactic coordinates, distances, ages, metallicities, as well as Cartesian coordinates and velocities. The latter were computed through converting the spherical parameters to Cartesian space with the sun as point of origin. The tables grpar10.dat and grpar20.dat (listed as two parts in Table B.1 of the Appendix of our paper) contain the mean values for the identified potential open cluster groupings for two sets of linking lengths, 100pc and 10km/s (19 potential groupings) and 100pc and 20km/s (41 potential groupings), respectively. These were computed as simple mean, while the uncertainties were computed as simple rms. We list the counting number, the number of members, the COCD number and name for each member, The mean Cartesian coordinates and velocities, along with the uncertainties, the mean distances (with uncertainties), the mean logarithmic ages (with uncertainties) and the mean metallicities

A box full of chocolates: The rich structure of the nearby stellar halo revealed by Gaia and RAVE

NASA Astrophysics Data System (ADS)

Helmi, Amina; Veljanoski, Jovan; Breddels, Maarten A.; Tian, Hao; Sales, Laura V.

2017-02-01

Context. The hierarchical structure formation model predicts that stellar halos should form, at least partly, via mergers. If this was a predominant formation channel for the Milky Way's halo, imprints of this merger history in the form of moving groups or streams should also exist in the vicinity of the Sun. Aims: We study the kinematics of halo stars in the Solar neighbourhood using the very recent first data release from the Gaia mission, and in particular the TGAS dataset, in combination with data from the RAVE survey. Our aim is to determine the amount of substructure present in the phase-space distribution of halo stars that could be linked to merger debris. Methods: To characterise kinematic substructure, we measured the velocity correlation function in our sample of halo (low-metallicity) stars. We also studied the distribution of these stars in the space of energy and two components of the angular momentum, in what we call "integrals of motion" space. Results: The velocity correlation function reveals substructure in the form of an excess of pairs of stars with similar velocities, well above that expected for a smooth distribution. Comparison to cosmological simulations of the formation of stellar halos indicates that the levels found are consistent with the Galactic halo having been built solely via accretion. Similarly, the distribution of stars in the space of integrals of motion is highly complex. A strikingly high fraction (from 58% up to more than 73%) of the stars that are somewhat less bound than the Sun are on (highly) retrograde orbits. A simple comparison to Milky Way-mass galaxies in cosmological hydrodynamical simulations suggests that less than 1% have such prominently retrograde outer halos. We also identify several other statistically significant structures in integrals of motion space that could potentially be related to merger events.

Teleoperators - Manual/automatic system requirements.

NASA Technical Reports Server (NTRS)

Janow, C.; Malone, T. B.

1973-01-01

The teleoperator is defined as a remotely controlled, cybernetic, man-machine system designed to extend and augment man's sensory, manipulative, and cognitive capabilities. The teleoperator system incorporates the decision making, adaptive intelligence without requiring its presence. The man and the machine work as a team, each contributing unique and significant capabilities, and each depending on the other to achieve a common goal. Some of the more significant requirements associated with the development of teleoperator systems technology for space, industry, and medicine are examined. Emphasis is placed on the requirement to more effectively use the man and the machine in any man-machine system.

Advanced EVA system design requirements study

NASA Technical Reports Server (NTRS)

1986-01-01

Design requirements and criteria for the Space Station Advanced Extravehicular Activity System (EVAS) including crew enclosures, portable life support systems, maneuvering propulsion systems, and related extravehicular activity (EVA) support equipment were defined and established. The EVA mission requirements, environments, and medical and physiological requirements, as well as opertional, procedures, and training issues were considered.

Research on atmospheric volcanic emissions - An overview

NASA Technical Reports Server (NTRS)

Friend, J. P.; Bandy, A. R.; Moyers, J. L.; Zoller, W. H.; Stoiber, R. E.; Torres, A. L.; Rose, W. I., Jr.; Mccormick, M. P.; Woods, D. C.

1982-01-01

Atmospheric abundances and the geochemical cycle of certain volatile compounds and elements may be largely influenced or entirely controlled by magmatic sources. However, better estimates of the magnitude and variability of volcanic emissions are required if the importance of this natural source of atmospheric constituents and the resulting effect on atmospheric chemistry are to be elucidated. The project 'Research on Atmospheric Volcanic Emissions' (RAVE) is concerned with the improvement of knowledge of both geological and chemical phenomena attending these emissions by means of comprehensive instrumentation on board a research aircraft making simultaneous measurements of plume constituents. A description is presented of the equipment and the procedures used in the RAVE field study of Mt. St. Helens' plume. An overview of the results is also provided.

Maintainability Program Requirements for Space Systems

NASA Technical Reports Server (NTRS)

1987-01-01

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

Intelligent redundant actuation system requirements and preliminary system design

NASA Technical Reports Server (NTRS)

Defeo, P.; Geiger, L. J.; Harris, J.

1985-01-01

Several redundant actuation system configurations were designed and demonstrated to satisfy the stringent operational requirements of advanced flight control systems. However, this has been accomplished largely through brute force hardware redundancy, resulting in significantly increased computational requirements on the flight control computers which perform the failure analysis and reconfiguration management. Modern technology now provides powerful, low-cost microprocessors which are effective in performing failure isolation and configuration management at the local actuator level. One such concept, called an Intelligent Redundant Actuation System (IRAS), significantly reduces the flight control computer requirements and performs the local tasks more comprehensively than previously feasible. The requirements and preliminary design of an experimental laboratory system capable of demonstrating the concept and sufficiently flexible to explore a variety of configurations are discussed.

Requirements Analysis for Information-Intensive Systems

NASA Technical Reports Server (NTRS)

Callender, E. D.; Hartsough, C.; Morris, R. V.; Yamamoto, Y.

1986-01-01

Report discusses role of requirements analysis in development of information-intensive systems. System examined from variety of human viewpoints during design, development, and implementation. Such examination, called requirements analysis, ensures system simultaneously meets number of distinct but interacting needs. Viewpoints defined and integrated to help attain objectives.

Design requirements for SRB production control system. Volume 2: System requirements and conceptual description

NASA Technical Reports Server (NTRS)

1981-01-01

In the development of the business system for the SRB automated production control system, special attention had to be paid to the unique environment posed by the space shuttle. The issues posed by this environment, and the means by which they were addressed, are reviewed. The change in management philosphy which will be required as NASA switches from one-of-a-kind launches to multiple launches is discussed. The implications of the assembly process on the business system are described. These issues include multiple missions, multiple locations and facilities, maintenance and refurbishment, multiple sources, and multiple contractors. The implications of these aspects on the automated production control system are reviewed including an assessment of the six major subsystems, as well as four other subsystem. Some general system requirements which flow through the entire business system are described.

7 CFR 1770.11 - Accounting system requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 7 Agriculture 12 2010-01-01 2010-01-01 false Accounting system requirements. 1770.11 Section 1770..., DEPARTMENT OF AGRICULTURE (CONTINUED) ACCOUNTING REQUIREMENTS FOR RUS TELECOMMUNICATIONS BORROWERS Uniform System of Accounts § 1770.11 Accounting system requirements. (a) Each RUS borrower subject to the...

7 CFR 1767.12 - Accounting system requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 7 Agriculture 12 2010-01-01 2010-01-01 false Accounting system requirements. 1767.12 Section 1767..., DEPARTMENT OF AGRICULTURE (CONTINUED) ACCOUNTING REQUIREMENTS FOR RUS ELECTRIC BORROWERS Uniform System of Accounts § 1767.12 Accounting system requirements. (a) Each Rural Development electric borrower must...

Vehicle systems and payload requirements evaluation. [computer programs for identifying launch vehicle system requirements

NASA Technical Reports Server (NTRS)

Rea, F. G.; Pittenger, J. L.; Conlon, R. J.; Allen, J. D.

1975-01-01

Techniques developed for identifying launch vehicle system requirements for NASA automated space missions are discussed. Emphasis is placed on development of computer programs and investigation of astrionics for OSS missions and Scout. The Earth Orbit Mission Program - 1 which performs linear error analysis of launch vehicle dispersions for both vehicle and navigation system factors is described along with the Interactive Graphic Orbit Selection program which allows the user to select orbits which satisfy mission requirements and to evaluate the necessary injection accuracy.

Requirements based system risk modeling

NASA Technical Reports Server (NTRS)

Meshkat, Leila; Cornford, Steven; Feather, Martin

2004-01-01

The problem that we address in this paper is assessing the expected degree of success of the system or mission based on the degree to which each requirement is satisfied and the relative weight of the requirements. We assume a complete list of the requirements, the relevant risk elements and their probability of occurrence and the quantified effect of the risk elements on the requirements. In order to assess the degree to which each requirement is satisfied, we need to determine the effect of the various risk elements on the requirement.

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

Casey, Andrew R.; Hawkins, Keith; Koposov, Sergey

The orbits, atmospheric parameters, chemical abundances, and ages of individual stars in the Milky Way provide the most comprehensive illustration of galaxy formation available. The Tycho- Gaia Astrometric Solution (TGAS) will deliver astrometric parameters for the largest ever sample of Milky Way stars, though its full potential cannot be realized without the addition of complementary spectroscopy. Among existing spectroscopic surveys, the RAdial Velocity Experiment (RAVE) has the largest overlap with TGAS (≳200,000 stars). We present a data-driven re-analysis of 520,781 RAVE spectra using The Cannon . For red giants, we build our model using high-fidelity APOGEE stellar parameters and abundancesmore » for stars that overlap with RAVE. For main sequence and sub-giant stars, our model uses stellar parameters from the K2/EPIC . We derive and validate effective temperature T {sub eff}, surface gravity log g , and chemical abundances of up to seven elements (O, Mg, Al, Si, Ca, Fe, and Ni). We report a total of 1,685,851 elemental abundances with a typical precision of 0.07 dex, a substantial improvement over previous RAVE data releases. The synthesis of RAVE-on and TGAS is the most powerful data set for chemo-dynamic analyses of the Milky Way ever produced.« less

Advanced EVA system design requirements study

NASA Technical Reports Server (NTRS)

Woods, T. G.

1988-01-01

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

40 CFR 91.327 - Sampling system requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 40 Protection of Environment 20 2011-07-01 2011-07-01 false Sampling system requirements. 91.327....327 Sampling system requirements. (a) Sample component surface temperature. For sampling systems which..., sample line section, filters, and so forth) in the heated portion of the sampling system that has a...

40 CFR 91.327 - Sampling system requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... 40 Protection of Environment 20 2010-07-01 2010-07-01 false Sampling system requirements. 91.327....327 Sampling system requirements. (a) Sample component surface temperature. For sampling systems which..., sample line section, filters, and so forth) in the heated portion of the sampling system that has a...

49 CFR 228.313 - Electrical system requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 49 Transportation 4 2012-10-01 2012-10-01 false Electrical system requirements. 228.313 Section...; SLEEPING QUARTERS Safety and Health Requirements for Camp Cars Provided by Railroads as Sleeping Quarters § 228.313 Electrical system requirements. (a) All heating, cooking, ventilation, air conditioning, and...

49 CFR 228.313 - Electrical system requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 49 Transportation 4 2014-10-01 2014-10-01 false Electrical system requirements. 228.313 Section...; SLEEPING QUARTERS Safety and Health Requirements for Camp Cars Provided by Railroads as Sleeping Quarters § 228.313 Electrical system requirements. (a) All heating, cooking, ventilation, air conditioning, and...

49 CFR 228.313 - Electrical system requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 49 Transportation 4 2013-10-01 2013-10-01 false Electrical system requirements. 228.313 Section...; SLEEPING QUARTERS Safety and Health Requirements for Camp Cars Provided by Railroads as Sleeping Quarters § 228.313 Electrical system requirements. (a) All heating, cooking, ventilation, air conditioning, and...

The Requirements Generation System: A tool for managing mission requirements

NASA Technical Reports Server (NTRS)

Sheppard, Sylvia B.

1994-01-01

Historically, NASA's cost for developing mission requirements has been a significant part of a mission's budget. Large amounts of time have been allocated in mission schedules for the development and review of requirements by the many groups who are associated with a mission. Additionally, tracing requirements from a current document to a parent document has been time-consuming and costly. The Requirements Generation System (RGS) is a computer-supported cooperative-work tool that assists mission developers in the online creation, review, editing, tracing, and approval of mission requirements as well as in the production of requirements documents. This paper describes the RGS and discusses some lessons learned during its development.

Civilian Radioactive Waste Management System Requirements Document

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

C.A. Kouts

2006-05-10

The CRD addresses the requirements of Department of Energy (DOE) Order 413.3-Change 1, ''Program and Project Management for the Acquisition of Capital Assets'', by providing the Secretarial Acquisition Executive (Level 0) scope baseline and the Program-level (Level 1) technical baseline. The Secretarial Acquisition Executive approves the Office of Civilian Radioactive Waste Management's (OCRWM) critical decisions and changes against the Level 0 baseline; and in turn, the OCRWM Director approves all changes against the Level 1 baseline. This baseline establishes the top-level technical scope of the CRMWS and its three system elements, as described in section 1.3.2. The organizations responsible formore » design, development, and operation of system elements described in this document must therefore prepare subordinate project-level documents that are consistent with the CRD. Changes to requirements will be managed in accordance with established change and configuration control procedures. The CRD establishes requirements for the design, development, and operation of the CRWMS. It specifically addresses the top-level governing laws and regulations (e.g., ''Nuclear Waste Policy Act'' (NWPA), 10 Code of Federal Regulations (CFR) Part 63, 10 CFR Part 71, etc.) along with specific policy, performance requirements, interface requirements, and system architecture. The CRD shall be used as a vehicle to incorporate specific changes in technical scope or performance requirements that may have significant program implications. Such may include changes to the program mission, changes to operational capability, and high visibility stakeholder issues. The CRD uses a systems approach to: (1) identify key functions that the CRWMS must perform, (2) allocate top-level requirements derived from statutory, regulatory, and programmatic sources, and (3) define the basic elements of the system architecture and operational concept. Project-level documents address CRD requirements by

Organizing Performance Requirements For Dynamical Systems

NASA Technical Reports Server (NTRS)

Malchow, Harvey L.; Croopnick, Steven R.

1990-01-01

Paper describes methodology for establishing performance requirements for complicated dynamical systems. Uses top-down approach. In series of steps, makes connections between high-level mission requirements and lower-level functional performance requirements. Provides systematic delineation of elements accommodating design compromises.

Electrocardiogram Scanner-System Requirements

DOT National Transportation Integrated Search

1973-03-01

An experimental and analytical study has been conducted to establish the feasibility for scanning and digitizing electrocardiogram records. The technical requirements and relative costs for two systems are discussed herein. One is designed to automat...

Systems and context modeling approach to requirements analysis

NASA Astrophysics Data System (ADS)

Ahuja, Amrit; Muralikrishna, G.; Patwari, Puneet; Subhrojyoti, C.; Swaminathan, N.; Vin, Harrick

2014-08-01

Ensuring completeness and correctness of the requirements for a complex system such as the SKA is challenging. Current system engineering practice includes developing a stakeholder needs definition, a concept of operations, and defining system requirements in terms of use cases and requirements statements. We present a method that enhances this current practice into a collection of system models with mutual consistency relationships. These include stakeholder goals, needs definition and system-of-interest models, together with a context model that participates in the consistency relationships among these models. We illustrate this approach by using it to analyze the SKA system requirements.

40 CFR 90.327 - Sampling system requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 40 Protection of Environment 20 2011-07-01 2011-07-01 false Sampling system requirements. 90.327... Equipment Provisions § 90.327 Sampling system requirements. (a) Sample component surface temperature. For sampling systems which use heated components, use engineering judgment to locate the coolest portion of...

40 CFR 90.327 - Sampling system requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... 40 Protection of Environment 20 2010-07-01 2010-07-01 false Sampling system requirements. 90.327... Equipment Provisions § 90.327 Sampling system requirements. (a) Sample component surface temperature. For sampling systems which use heated components, use engineering judgment to locate the coolest portion of...

46 CFR 63.20-1 - Specific control system requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 2 2011-10-01 2011-10-01 false Specific control system requirements. 63.20-1 Section 63... AUXILIARY BOILERS Additional Control System Requirements § 63.20-1 Specific control system requirements. In... following requirements apply for specific control systems: (a) Primary safety control system. Following...

46 CFR 63.20-1 - Specific control system requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 2 2010-10-01 2010-10-01 false Specific control system requirements. 63.20-1 Section 63... AUXILIARY BOILERS Additional Control System Requirements § 63.20-1 Specific control system requirements. In... following requirements apply for specific control systems: (a) Primary safety control system. Following...

Requirements controlled design: A method for discovery of discontinuous system boundaries in the requirements hyperspace

NASA Astrophysics Data System (ADS)

Hollingsworth, Peter Michael

The drive toward robust systems design, especially with respect to system affordability throughout the system life-cycle, has led to the development of several advanced design methods. While these methods have been extremely successful in satisfying the needs for which they have been developed, they inherently leave a critical area unaddressed. None of them fully considers the effect of requirements on the selection of solution systems. The goal of all of current modern design methodologies is to bring knowledge forward in the design process to the regions where more design freedom is available and design changes cost less. Therefore, it seems reasonable to consider the point in the design process where the greatest restrictions are placed on the final design, the point in which the system level requirements are set. Historically the requirements have been treated as something handed down from above. However, neither the customer nor the solution provider completely understood all of the options that are available in the broader requirements space. If a method were developed that provided the ability to understand the full scope of the requirements space, it would allow for a better comparison of potential solution systems with respect to both the current and potential future requirements. The key to a requirements conscious method is to treat requirements differently from the traditional approach. The method proposed herein is known as Requirements Controlled Design (RCD). By treating the requirements as a set of variables that control the behavior of the system, instead of variables that only define the response of the system, it is possible to determine a-priori what portions of the requirements space that any given system is capable of satisfying. Additionally, it should be possible to identify which systems can satisfy a given set of requirements and the locations where a small change in one or more requirements poses a significant risk to a design program

Louisiana Threads the Needle on ED Reform: Launching a Coherent Curriculum in a Local-Control State

ERIC Educational Resources Information Center

Pondiscio, Robert

2017-01-01

Officials of state education agencies are not known for hyperbole. Maintaining data systems, drafting rules and regulations, and monitoring compliance are not the stuff of breathless raves--especially in Louisiana, whose education system ranks near the bottom nationwide on measures of student achievement and high-school graduation rates. Yet in…

Advanced EVA system design requirements study, executive summary

NASA Technical Reports Server (NTRS)

1986-01-01

Design requirements and criteria for the space station advanced Extravehicular Activity System (EVAS) including crew enclosures, portable life support systems, maneuvering propulsion systems, and related EVA support equipment were established. The EVA mission requirements, environments, and medical and physiological requirements, as well as operational, procedures and training issues were considered.

7 CFR 400.403 - Required system of records.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 7 Agriculture 6 2010-01-01 2010-01-01 false Required system of records. 400.403 Section 400.403... and Storage of Social Security Account Numbers and Employer Identification Numbers § 400.403 Required system of records. Insurance providers are required to implement a system of records for obtaining, using...

I-15 integrated corridor management : system requirements.

DOT National Transportation Integrated Search

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

Flight Guidance System Requirements Specification

NASA Technical Reports Server (NTRS)

Miller, Steven P.; Tribble, Alan C.; Carlson, Timothy M.; Danielson, Eric J.

2003-01-01

This report describes a requirements specification written in the RSML-e language for the mode logic of a Flight Guidance System of a typical regional jet aircraft. This model was created as one of the first steps in a five-year project sponsored by the NASA Langley Research Center, Rockwell Collins Inc., and the Critical Systems Research Group of the University of Minnesota to develop new methods and tools to improve the safety of avionics designs. This model will be used to demonstrate the application of a variety of methods and techniques, including safety analysis of system and subsystem requirements, verification of key properties using theorem provers and model checkers, identification of potential sources mode confusion in system designs, partitioning of applications based on the criticality of system hazards, and autogeneration of avionics quality code. While this model is representative of the mode logic of a typical regional jet aircraft, it does not describe an actual or planned product. Several aspects of a full Flight Guidance System, such as recovery from failed sensors, have been omitted, and no claims are made regarding the accuracy or completeness of this specification.

Teleoperator system man-machine interface requirements for satellite retrieval and satellite servicing. Volume 1: Requirements

NASA Technical Reports Server (NTRS)

Malone, T. B.

1972-01-01

Requirements were determined analytically for the man machine interface for a teleoperator system performing on-orbit satellite retrieval and servicing. Requirements are basically of two types; mission/system requirements, and design requirements or design criteria. Two types of teleoperator systems were considered: a free flying vehicle, and a shuttle attached manipulator. No attempt was made to evaluate the relative effectiveness or efficiency of the two system concepts. The methodology used entailed an application of the Essex Man-Systems analysis technique as well as a complete familiarization with relevant work being performed at government agencies and by private industry.

Exploration Planetary Surface Structural Systems: Design Requirements and Compliance

NASA Technical Reports Server (NTRS)

Dorsey, John T.

2011-01-01

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

Information System Requirements Determination: Factors Impeding Stakeholders from Reaching Common Understandings and Agreements on Requirements

ERIC Educational Resources Information Center

Gissel, Richard L.

2010-01-01

Information system implementations require developers to first know what they must create and then determine how best to create it. The requirements determination phase of the system development life cycle typically determines what functions a system must perform and how well it must accomplish required functions. Implementation success depends on…

Requirements based system level risk modeling

NASA Technical Reports Server (NTRS)

Meshkat, Leila; Cornford, Steven; Feather, Martin

2004-01-01

The problem that we address in this paper is assessing the expected degree of success of the system or mission based on the degree to which each requirement is satisfied and the relative weight of the requirements.

14 CFR 121.127 - Flight following system; requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 14 Aeronautics and Space 3 2010-01-01 2010-01-01 false Flight following system; requirements. 121... Supplemental Operations § 121.127 Flight following system; requirements. (a) Each certificate holder conducting supplemental operations using a flight following system must show that— (1) The system has adequate facilities...

14 CFR 121.127 - Flight following system; requirements.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 14 Aeronautics and Space 3 2013-01-01 2013-01-01 false Flight following system; requirements. 121... Supplemental Operations § 121.127 Flight following system; requirements. (a) Each certificate holder conducting supplemental operations using a flight following system must show that— (1) The system has adequate facilities...

14 CFR 121.127 - Flight following system; requirements.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 14 Aeronautics and Space 3 2014-01-01 2014-01-01 false Flight following system; requirements. 121... Supplemental Operations § 121.127 Flight following system; requirements. (a) Each certificate holder conducting supplemental operations using a flight following system must show that— (1) The system has adequate facilities...

14 CFR 121.127 - Flight following system; requirements.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 14 Aeronautics and Space 3 2012-01-01 2012-01-01 false Flight following system; requirements. 121... Supplemental Operations § 121.127 Flight following system; requirements. (a) Each certificate holder conducting supplemental operations using a flight following system must show that— (1) The system has adequate facilities...

14 CFR 121.127 - Flight following system; requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 14 Aeronautics and Space 3 2011-01-01 2011-01-01 false Flight following system; requirements. 121... Supplemental Operations § 121.127 Flight following system; requirements. (a) Each certificate holder conducting supplemental operations using a flight following system must show that— (1) The system has adequate facilities...

Automated Derivation of Complex System Constraints from User Requirements

NASA Technical Reports Server (NTRS)

Muery, Kim; Foshee, Mark; Marsh, Angela

2006-01-01

International Space Station (ISS) payload developers submit their payload science requirements for the development of on-board execution timelines. The ISS systems required to execute the payload science operations must be represented as constraints for the execution timeline. Payload developers use a software application, User Requirements Collection (URC), to submit their requirements by selecting a simplified representation of ISS system constraints. To fully represent the complex ISS systems, the constraints require a level of detail that is beyond the insight of the payload developer. To provide the complex representation of the ISS system constraints, HOSC operations personnel, specifically the Payload Activity Requirements Coordinators (PARC), manually translate the payload developers simplified constraints into detailed ISS system constraints used for scheduling the payload activities in the Consolidated Planning System (CPS). This paper describes the implementation for a software application, User Requirements Integration (URI), developed to automate the manual ISS constraint translation process.

46 CFR 16.500 - Management Information System requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 1 2010-10-01 2010-10-01 false Management Information System requirements. 16.500 Section 16.500 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY MERCHANT MARINE OFFICERS AND SEAMEN CHEMICAL TESTING Management Information System § 16.500 Management Information System requirements. (a...

46 CFR 16.500 - Management Information System requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 1 2013-10-01 2013-10-01 false Management Information System requirements. 16.500 Section 16.500 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY MERCHANT MARINE OFFICERS AND SEAMEN CHEMICAL TESTING Management Information System § 16.500 Management Information System requirements. (a...

46 CFR 16.500 - Management Information System requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 1 2011-10-01 2011-10-01 false Management Information System requirements. 16.500 Section 16.500 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY MERCHANT MARINE OFFICERS AND SEAMEN CHEMICAL TESTING Management Information System § 16.500 Management Information System requirements. (a...

46 CFR 16.500 - Management Information System requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 1 2014-10-01 2014-10-01 false Management Information System requirements. 16.500 Section 16.500 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY MERCHANT MARINE OFFICERS AND SEAMEN CHEMICAL TESTING Management Information System § 16.500 Management Information System requirements. (a...

46 CFR 16.500 - Management Information System requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 1 2012-10-01 2012-10-01 false Management Information System requirements. 16.500 Section 16.500 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY MERCHANT MARINE OFFICERS AND SEAMEN CHEMICAL TESTING Management Information System § 16.500 Management Information System requirements. (a...

Requirements for a Global Greenhouse Gas Information System

NASA Astrophysics Data System (ADS)

Duren, R.; Boland, S.; Lempert, R.; Miller, C.

2008-12-01

A global greenhouse gas information system will prove a critical component of any successful effort to mitigate climate change which relies on limiting the atmospheric concentration of greenhouse gases. The system will provide the situational awareness necessary to actively reduce emissions, influence land use change, and sequester carbon. The information from such a system will be subject to intense scrutiny. Therefore, an effective system must openly and transparently produce data of unassailable quality. A global greenhouse gas information system will likely require a combination of space-and air-based remote- sensing assets, ground-based measurements, carbon cycle modeling and self-reporting. The specific requirements on such a system will be shaped by the degree of international cooperation it enjoys and the needs of the policy regime it aims to support, which might range from verifying treaty obligations, to certifying the tradable permits and offsets underlying a market in greenhouse gas emission reductions, to providing a comprehensive inventory of high and low emitters that could be used by non-governmental organizations and other international actors. While some technical studies have examined particular system components in single scenarios, there remains a need for a comprehensive survey of the range of potential requirements, options, and strategies for the overall system. We have initiated such a survey and recently hosted a workshop which engaged a diverse community of stakeholders to begin synthesizing requirements for such a system, with an initial focus on carbon dioxide. In this paper we describe our plan for completing the definition of the requirements, options, and strategies for a global greenhouse gas monitoring system. We discuss our overall approach and provide a status on the initial requirements synthesis activity.

49 CFR 659.21 - System security plan: general requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 49 Transportation 7 2010-10-01 2010-10-01 false System security plan: general requirements. 659.21... State Oversight Agency § 659.21 System security plan: general requirements. (a) The oversight agency shall require the rail transit agency to implement a system security plan that, at a minimum, complies...

Satellite Power Systems (SPS) concept definition study. Volume 2: SPS system requirements

NASA Technical Reports Server (NTRS)

Hanley, G.

1978-01-01

Collected data reflected the level of definition resulting from the evaluation of a broad spectrum of SPS (satellite power systems) concepts. As the various concepts matured, these requirements were updated to reflect the requirements identified for the projected satellite system/subsystem point design(s). The study established several candidate concepts which were presented to provide a basis for the selection of one or two approaches that would be given a more comprehensive examination. The two selected concepts were expanded and constitute the selected system point designs. The identified system/subsystem requirements was emphasized and information on the selected point design was provided.

State analysis requirements database for engineering complex embedded systems

NASA Technical Reports Server (NTRS)

Bennett, Matthew B.; Rasmussen, Robert D.; Ingham, Michel D.

2004-01-01

It has become clear that spacecraft system complexity is reaching a threshold where customary methods of control are no longer affordable or sufficiently reliable. At the heart of this problem are the conventional approaches to systems and software engineering based on subsystem-level functional decomposition, which fail to scale in the tangled web of interactions typically encountered in complex spacecraft designs. Furthermore, there is a fundamental gap between the requirements on software specified by systems engineers and the implementation of these requirements by software engineers. Software engineers must perform the translation of requirements into software code, hoping to accurately capture the systems engineer's understanding of the system behavior, which is not always explicitly specified. This gap opens up the possibility for misinterpretation of the systems engineer's intent, potentially leading to software errors. This problem is addressed by a systems engineering tool called the State Analysis Database, which provides a tool for capturing system and software requirements in the form of explicit models. This paper describes how requirements for complex aerospace systems can be developed using the State Analysis Database.

Implementation Procedure for STS Payloads, System Safety Requirements

NASA Technical Reports Server (NTRS)

1979-01-01

Guidelines and instructions for the implementation of the SP&R system safety requirements applicable to STS payloads are provided. The initial contact meeting with the payload organization and the subsequent safety reviews necessary to comply with the system safety requirements of the SP&R document are described. Waiver instructions are included for the cases in which a safety requirement cannot be met.

Automated Orbit Determination System (AODS) requirements definition and analysis

NASA Technical Reports Server (NTRS)

Waligora, S. R.; Goorevich, C. E.; Teles, J.; Pajerski, R. S.

1980-01-01

The requirements definition for the prototype version of the automated orbit determination system (AODS) is presented including the AODS requirements at all levels, the functional model as determined through the structured analysis performed during requirements definition, and the results of the requirements analysis. Also specified are the implementation strategy for AODS and the AODS-required external support software system (ADEPT), input and output message formats, and procedures for modifying the requirements.

Investigation of Propulsion System Requirements for Spartan Lite

NASA Technical Reports Server (NTRS)

Urban, Mike; Gruner, Timothy; Morrissey, James; Sneiderman, Gary

1998-01-01

This paper discusses the (chemical or electric) propulsion system requirements necessary to increase the Spartan Lite science mission lifetime to over a year. Spartan Lite is an extremely low-cost (less than 10 M) spacecraft bus being developed at the NASA Goddard Space Flight Center to accommodate sounding rocket class (40 W, 45 kg, 35 cm dia by 1 m length) payloads. While Spartan Lite is compatible with expendable launch vehicles, most missions are expected to be tertiary payloads deployed by. the Space Shuttle. To achieve a one year or longer mission life from typical Shuttle orbits, some form of propulsion system is required. Chemical propulsion systems (characterized by high thrust impulsive maneuvers) and electrical propulsion systems (characterized by low-thrust long duration maneuvers and the additional requirement for electrical power) are discussed. The performance of the Spartan Lite attitude control system in the presence of large disturbance torques is evaluated using the Trectops(Tm) dynamic simulator. This paper discusses the performance goals and resource constraints for candidate Spartan Lite propulsion systems and uses them to specify quantitative requirements against which the systems are evaluated.

Towards Requirements in Systems Engineering for Aerospace IVHM Design

NASA Technical Reports Server (NTRS)

Saxena, Abhinav; Roychoudhury, Indranil; Lin, Wei; Goebel, Kai

2013-01-01

Health management (HM) technologies have been employed for safety critical system for decades, but a coherent systematic process to integrate HM into the system design is not yet clear. Consequently, in most cases, health management resorts to be an after-thought or 'band-aid' solution. Moreover, limited guidance exists for carrying out systems engineering (SE) on the subject of writing requirements for designs with integrated vehicle health management (IVHM). It is well accepted that requirements are key to developing a successful IVHM system right from the concept stage to development, verification, utilization, and support. However, writing requirements for systems with IVHM capability have unique challenges that require the designers to look beyond their own domains and consider the constraints and specifications of other interlinked systems. In this paper we look at various stages in the SE process and identify activities specific to IVHM design and development. More importantly, several relevant questions are posed that system engineers must address at various design and development stages. Addressing these questions should provide some guidance to systems engineers towards writing IVHM related requirements to ensure that appropriate IVHM functions are built into the system design.

Formal Specification of Information Systems Requirements.

ERIC Educational Resources Information Center

Kampfner, Roberto R.

1985-01-01

Presents a formal model for specification of logical requirements of computer-based information systems that incorporates structural and dynamic aspects based on two separate models: the Logical Information Processing Structure and the Logical Information Processing Network. The model's role in systems development is discussed. (MBR)

Engineered Barrier System performance requirements systems study report. Revision 02

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

Balady, M.A.

This study evaluates the current design concept for the Engineered Barrier System (EBS), in concert with the current understanding of the geologic setting to assess whether enhancements to the required performance of the EBS are necessary. The performance assessment calculations are performed by coupling the EBS with the geologic setting based on the models (some of which were updated for this study) and assumptions used for the 1995 Total System Performance Assessment (TSPA). The need for enhancements is determined by comparing the performance assessment results against the EBS related performance requirements. Subsystem quantitative performance requirements related to the EBS includemore » the requirement to allow no more than 1% of the waste packages (WPs) to fail before 1,000 years after permanent closure of the repository, as well as a requirement to control the release rate of radionuclides from the EBS. The EBS performance enhancements considered included additional engineered components as well as evaluating additional performance available from existing design features but for which no performance credit is currently being taken.« less

Requirements for a transformerless power conditioning system

NASA Technical Reports Server (NTRS)

Klein, J.; Koerner, T.; Rippel, W.; Kalbach, J.

1984-01-01

Requirements for development of a Transformerless Power Conditioning Subsystem (TPCS) that will meet utility, manufacturer, and customer needs are detailed. Issues analyzed include current utility guidelines, safety and grounding issues that appear as local codes, various kinds of TPCS connections that can be developed, dc injection, and a brief survey of TPCS circuit topologies that will meet requirements. The major result is that a finite time exists for control operation before dc injection into the distribution transformer causes customer outage (on the order of seconds). This time permits the control system to sense a dc injection condition and remove the TPCS from the utility system. Requirements for such a control system are specified. A three wire connection will ensure balanced operation for customer loads and two wire connections caused average value dc to be injected into single phase loads. This type of connection also allows for the lowest array voltage. The conclusion is that requirements for a TPCS can be determined and that there are not showstopping issues preventing implementation. The actual design and topology of the TPCS was left for further study.

47 CFR 73.317 - FM transmission system requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 4 2010-10-01 2010-10-01 false FM transmission system requirements. 73.317... RADIO BROADCAST SERVICES FM Broadcast Stations § 73.317 FM transmission system requirements. (a) FM... occupied by their emissions in accordance with the specification detailed below. FM broadcast stations...

47 CFR 73.317 - FM transmission system requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 47 Telecommunication 4 2011-10-01 2011-10-01 false FM transmission system requirements. 73.317... RADIO BROADCAST SERVICES FM Broadcast Stations § 73.317 FM transmission system requirements. (a) FM... occupied by their emissions in accordance with the specification detailed below. FM broadcast stations...

Facility Systems, Ground Support Systems, and Ground Support Equipment General Design Requirements

NASA Technical Reports Server (NTRS)

Thaxton, Eric A.

2014-01-01

KSC-DE-512-SM establishes overall requirements and best design practices to be used at the John F. Kennedy Space Center (KSC) for the development of ground systems (GS) in support of operations at launch, landing, and retrieval sites. These requirements apply to the design and development of hardware and software for ground support equipment (GSE), ground support systems (GSS), and facility ground support systems (F-GSS) used to support the KSC mission for transportation, receiving, handling, assembly, test, checkout, servicing, and launch of space vehicles and payloads and selected flight hardware items for retrieval. This standards manual supplements NASA-STD-5005 by including KSC-site-specific and local environment requirements. These requirements and practices are optional for equipment used at manufacturing, development, and test sites.

Advanced extravehicular activity systems requirements definition study

NASA Technical Reports Server (NTRS)

1988-01-01

A study to define the requirements for advanced extravehicular activities (AEVA) was conducted. The purpose of the study was to develop an understanding of the EVA technology requirements and to map a pathway from existing or developing technologies to an AEVA system capable of supporting long-duration missions on the lunar surface. The parameters of an AEVA system which must sustain the crewmembers and permit productive work for long periods in the lunar environment were examined. A design reference mission (DRM) was formulated and used as a tool to develop and analyze the EVA systems technology aspects. Many operational and infrastructure design issues which have a significant influence on the EVA system are identified.

47 CFR 73.33 - Antenna systems; showing required.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 47 Telecommunication 4 2013-10-01 2013-10-01 false Antenna systems; showing required. 73.33... RADIO BROADCAST SERVICES AM Broadcast Stations § 73.33 Antenna systems; showing required. (a) An application for authority to install a broadcast antenna shall specify a definite site and include full...

47 CFR 73.33 - Antenna systems; showing required.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 4 2010-10-01 2010-10-01 false Antenna systems; showing required. 73.33... RADIO BROADCAST SERVICES AM Broadcast Stations § 73.33 Antenna systems; showing required. (a) An application for authority to install a broadcast antenna shall specify a definite site and include full...

47 CFR 73.33 - Antenna systems; showing required.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 47 Telecommunication 4 2012-10-01 2012-10-01 false Antenna systems; showing required. 73.33... RADIO BROADCAST SERVICES AM Broadcast Stations § 73.33 Antenna systems; showing required. (a) An application for authority to install a broadcast antenna shall specify a definite site and include full...

47 CFR 73.33 - Antenna systems; showing required.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 47 Telecommunication 4 2011-10-01 2011-10-01 false Antenna systems; showing required. 73.33... RADIO BROADCAST SERVICES AM Broadcast Stations § 73.33 Antenna systems; showing required. (a) An application for authority to install a broadcast antenna shall specify a definite site and include full...

47 CFR 73.33 - Antenna systems; showing required.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 47 Telecommunication 4 2014-10-01 2014-10-01 false Antenna systems; showing required. 73.33... RADIO BROADCAST SERVICES AM Broadcast Stations § 73.33 Antenna systems; showing required. (a) An application for authority to install a broadcast antenna shall specify a definite site and include full...

Space station electric power system requirements and design

NASA Technical Reports Server (NTRS)

Teren, Fred

1987-01-01

An overview of the conceptual definition and design of the space station Electric Power System (EPS) is given. Responsibilities for the design and development of the EPS are defined. The EPS requirements are listed and discussed, including average and peak power requirements, contingency requirements, and fault tolerance. The most significant Phase B trade study results are summarized, and the design selections and rationale are given. Finally, the power management and distribution system architecture is presented.

Live, Model, Learn: Experiencing Information Systems Requirements through Simulation

ERIC Educational Resources Information Center

Hartzel, Kathleen S.; Pike, Jacqueline C.

2015-01-01

Information system professionals strive to determine requirements by interviewing clients, observing activities at the client's site, and studying existing system documentation. Still this often leads to vague and inaccurate requirements documentation. When teaching the skills needed to determine requirements, it is important to recreate a…

A Study on the Deriving Requirements of ARGO Operation System

NASA Astrophysics Data System (ADS)

Seo, Yoon-Kyung; Rew, Dong-Young; Lim, Hyung-Chul; Park, In-Kwan; Yim, Hong-Suh; Jo, Jung Hyun; Park, Jong-Uk

2009-12-01

Korea Astronomy and Space Science Institute (KASI) has been developing one mobile and one stationary SLR system since 2008 named as ARGO-M and ARGO-F, respectively. KASI finished the step of deriving the system requirements of ARGO. The requirements include definitions and scopes of various software and hardware components which are necessary for developing the ARGO-M operation system. And the requirements define function, performance, and interface requirements. The operation system consisting of ARGO-M site, ARGO-F site, and Remote Operation Center (ROC) inside KASI is designed for remote access and the automatic tracking and control system which are the main operation concept of ARGO system. To accomplish remote operation, we are considering remote access to ARGO-F and ARGO-M from ROC. The mobile-phone service allows us to access the ARGO-F remotely and to control the system in an emergency. To implement fully automatic tracking and control function in ARGO-F, we have investigated and described the requirements about the automatic aircraft detection system and the various meteorological sensors. This paper addresses the requirements of ARGO Operation System.

Relative navigation requirements for automatic rendezvous and capture systems

NASA Technical Reports Server (NTRS)

Kachmar, Peter M.; Polutchko, Robert J.; Chu, William; Montez, Moises

1991-01-01

This paper will discuss in detail the relative navigation system requirements and sensor trade-offs for Automatic Rendezvous and Capture. Rendezvous navigation filter development will be discussed in the context of navigation performance requirements for a 'Phase One' AR&C system capability. Navigation system architectures and the resulting relative navigation performance for both cooperative and uncooperative target vehicles will be assessed. Relative navigation performance using rendezvous radar, star tracker, radiometric, laser and GPS navigation sensors during appropriate phases of the trajectory will be presented. The effect of relative navigation performance on the Integrated AR&C system performance will be addressed. Linear covariance and deterministic simulation results will be used. Evaluation of relative navigation and IGN&C system performance for several representative relative approach profiles will be presented in order to demonstrate the full range of system capabilities. A summary of the sensor requirements and recommendations for AR&C system capabilities for several programs requiring AR&C will be presented.

Requirements for CEC POP Machine Protection System

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

Pinayev, I.

2015-02-18

The requirements of CEC POP machine protection system are meant to prevent damage to a vacuum chamber by a missteered electron beam. In this example, beam energy = 22 MeV, Maximal bunch charge = 5 nC, Maximal repetition rate = 78 kHz, Normalized emittance = 5 mm mrad, Minimal β-function = 1 m. From this information the requirements of the protection system can be calculated by factoring the information into equations to find beam densities and temperature excursions.

Clinical requirements for closed-loop control systems.

PubMed

Clarke, William L; Renard, Eric

2012-03-01

Closed-loop (CL) therapy systems should be safe, efficacious, and easily manageable for type 1 diabetes mellitus patient use. For the first two clinical requirements, noninferiority and superiority criteria must be determined based on current conventional and intensive therapy outcomes. Current frequencies of hypoglycemia and diabetic ketoacidosis are reviewed and safety expectations for CL therapy systems are proposed. Glycosylated hemoglobin levels lower than current American Diabetes Association recommendations for different age groups are proposed as superiority criteria. Measures of glycemic variability are described and the recording of blood glucose levels as percentages within, above, and below a target range are suggested as reasonable alternatives to sophisticated statistical analyses. It is also suggested that Diabetes Quality of Life and Fear of Hypoglycemia surveys should be used to track psychobehavioral outcomes. Manageability requirements for safe and effective clinical management of CL systems are worth being underscored. The weakest part of the infusion system remains the catheter, which is exposed to variable and under-delivery incidents. Detection methods are needed to warn both the system and the patient about altered insulin delivery, including internal pressure and flow alarms. Glucose monitor sensor accuracy is another requirement; it includes the definition of conditions that lead to capillary glucose measurement, eventually followed by sensor recalibration or replacement. The crucial clinical requirement will be a thorough definition of the situations when the patient needs to move from CL to manual management of insulin delivery, or inversely can switch back to CL after a requested interruption. Instructions about these actions will constitute a major part of the education process of the patients before using CL systems and contribute to the manageability of these systems. © 2012 Diabetes Technology Society.

“A Cool Little Buzz”: Alcohol intoxication in an Asian American nightlife scene

PubMed Central

Hunt, Geoffrey; Moloney, Molly; Fazio, Adam

2014-01-01

Intoxication a state of altered consciousness brought about by the ingestion of intoxicants. Nighttime economy The term refers to those nighttime activities primarily associated with bars and clubs that take place within commercialized spaces in inner urban areas. Raves Although the precise origin of the word rave is unclear, with some writers associating it with boheminian parties in London in 1950s and others suggesting that raves began in the 1960s in San Francisco, by the late 1980s raves referred primarily to a dance parties, often unlicensed, where electronic music including acid house and techno music, was the music of choice. Asian American The pan-ethnic category “Asian American” comprises a large, diverse group of ethnic groups in the United States, representing dozens of cultures, national backgrounds, and languages, including those of Chinese, Japanese, Korean, Filipino, Indian, and Vietnamese descent. Emerging adulthood This term was coined to capture a life-course phase experienced by young adults in many contemporary western societies who are post-adolescence, but who have not yet achieved many of the traditional (twentieth century) life course markers that were associated with adulthood, such as completion of education, beginning of career, marriage, and parenthood (Arnett 2000) PMID:24779496

Evolving Requirements for Magnetic Tape Data Storage Systems

NASA Technical Reports Server (NTRS)

Gniewek, John J.

1996-01-01

Magnetic tape data storage systems have evolved in an environment where the major applications have been back-up/restore, disaster recovery, and long term archive. Coincident with the rapidly improving price-performance of disk storage systems, the prime requirements for tape storage systems have remained: (1) low cost per MB, (2) a data rate balanced to the remaining system components. Little emphasis was given to configuring the technology components to optimize retrieval of the stored data. Emerging new applications such as network attached high speed memory (HSM), and digital libraries, place additional emphasis and requirements on the retrieval of the stored data. It is therefore desirable to consider the system to be defined both by STorage And Retrieval System (STARS) requirements. It is possible to provide comparative performance analysis of different STARS by incorporating parameters related to (1) device characteristics, and (2) application characteristics in combination with queuing theory analysis. Results of these analyses are presented here in the form of response time as a function of system configuration for two different types of devices and for a variety of applications.

47 CFR 15.511 - Technical requirements for surveillance systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 47 Telecommunication 1 2013-10-01 2013-10-01 false Technical requirements for surveillance systems... DEVICES Ultra-Wideband Operation § 15.511 Technical requirements for surveillance systems. (a) The UWB... surveillance systems operated by law enforcement, fire or emergency rescue organizations or by manufacturers...

47 CFR 15.511 - Technical requirements for surveillance systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 47 Telecommunication 1 2012-10-01 2012-10-01 false Technical requirements for surveillance systems... DEVICES Ultra-Wideband Operation § 15.511 Technical requirements for surveillance systems. (a) The UWB... surveillance systems operated by law enforcement, fire or emergency rescue organizations or by manufacturers...

47 CFR 15.511 - Technical requirements for surveillance systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 47 Telecommunication 1 2011-10-01 2011-10-01 false Technical requirements for surveillance systems... DEVICES Ultra-Wideband Operation § 15.511 Technical requirements for surveillance systems. (a) The UWB... surveillance systems operated by law enforcement, fire or emergency rescue organizations or by manufacturers...

47 CFR 15.511 - Technical requirements for surveillance systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 1 2010-10-01 2010-10-01 false Technical requirements for surveillance systems... DEVICES Ultra-Wideband Operation § 15.511 Technical requirements for surveillance systems. (a) The UWB... surveillance systems operated by law enforcement, fire or emergency rescue organizations or by manufacturers...

47 CFR 15.511 - Technical requirements for surveillance systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 47 Telecommunication 1 2014-10-01 2014-10-01 false Technical requirements for surveillance systems... DEVICES Ultra-Wideband Operation § 15.511 Technical requirements for surveillance systems. (a) The UWB... surveillance systems operated by law enforcement, fire or emergency rescue organizations or by manufacturers...

Energy requirements in pressure irrigation systems

NASA Astrophysics Data System (ADS)

Sánchez, R.; Rodríguez-Sinobas, L.; Juana, L.; Laguna, F. V.; Castañón, G.; Gil, M.; Benítez, J.

2012-04-01

Modernization of irrigation schemes, generally understood as transformation of surface irrigation systems into pressure -sprinkler and trickle- irrigation systems, aims at, among others, improving irrigation efficiency and reduction of operation and maintenance efforts made by the irrigators. However, pressure irrigation systems, in contrast, carry a serious energy cost. Energy requirements depend on decisions taken on management strategies during the operation phase, which are conditioned by previous decisions taken on the design project of the different elements which compose the irrigation system. Most of the countries where irrigation activity is significant bear in mind that modernization irrigation must play a key role in the agricultural infrastructure policies. The objective of this study is to characterize and estimate the mean and variation of the energy consumed by common types of irrigation systems and their management possibilities. The work includes all processes involved from the diversion of water into irrigation specific infrastructure to water discharge by the emitters installed on the crop fields. Simulation taking into account all elements comprising the irrigation system has been used to estimate the energy requirements of typical irrigation systems of several crop production systems. It has been applied to extensive and intensive crop systems, such us extensive winter crops, summer crops and olive trees, fruit trees and vineyards and intensive horticulture in greenhouses. The simulation of various types of irrigation systems and management strategies, in the framework imposed by particular cropping systems, would help to develop criteria for improving the energy balance in relation to the irrigation water supply productivity.

Engineering Safety- and Security-Related Requirements for Software-Intensive Systems

DTIC Science & Technology

2010-04-27

Requirements Negative (shall not) Requirements Hardware Requirements equ remen s System / Documentation Requirements eve oper Requirements Operational ...Validation Actual / Proposed Defensibility C li Operational Vulnerability Analysis VulnerabilityVulnerability Safety Vulnerability performs System ...including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson

Environmental Assessment: The Development of a Borrow Source Cape Canaveral Air Force Station to Provide Material for Future Emergency Renourishment Projects Patrick Air Force Base

DTIC Science & Technology

2007-07-01

donor and recipient site description, date, turtle ID, morphometrics, sex , general health, etc.). These reports will be kept on file in the CCAFS 45...target species captured, weather conditions, lost or missing traps, and moon phase. If population data is being collected, sex , age, and reproductive...typical of other beach mice as well (Rave and Holler 1992). Sex ratios in beach mouse populations are generally 1:1 (Extine 1980; Rave and Holler

Formal Requirements-Based Programming for Complex Systems

NASA Technical Reports Server (NTRS)

Rash, James L.; Hinchey, Michael G.; Rouff, Christopher A.; Gracanin, Denis

2005-01-01

Computer science as a field has not yet produced a general method to mechanically transform complex computer system requirements into a provably equivalent implementation. Such a method would be one major step towards dealing with complexity in computing, yet it remains the elusive holy grail of system development. Currently available tools and methods that start with a formal model of a system and mechanically produce a provably equivalent implementation are valuable but not sufficient. The gap that such tools and methods leave unfilled is that the formal models cannot be proven to be equivalent to the system requirements as originated by the customer For the classes of complex systems whose behavior can be described as a finite (but significant) set of scenarios, we offer a method for mechanically transforming requirements (expressed in restricted natural language, or appropriate graphical notations) into a provably equivalent formal model that can be used as the basis for code generation and other transformations. While other techniques are available, this method is unique in offering full mathematical tractability while using notations and techniques that are well known and well trusted. We illustrate the application of the method to an example procedure from the Hubble Robotic Servicing Mission currently under study and preliminary formulation at NASA Goddard Space Flight Center.

The Impact of a Reflective Thinking Intervention on Nursing Students in a Child and Family Nursing Course

ERIC Educational Resources Information Center

Becherer, Vicky H.

2011-01-01

With the ever-changing healthcare systems, nursing students need to think at a high level by applying their knowledge from theory to the clinical setting by prioritizing, delegating, and problem solving to provide safe, competent, quality nursing care. Using action research, nursing students participated in R.A.V.E. (Reflective Thinking Allows…

Health requirements for advanced coal extraction systems

NASA Technical Reports Server (NTRS)

Zimmerman, W. F.

1980-01-01

Health requirements were developed as long range goals for future advanced coal extraction systems which would be introduced into the market in the year 2000. The goal of the requirements is that underground coal miners work in an environment that is as close as possible to the working conditions of the general population, that they do not exceed mortality and morbidity rates resulting from lung diseases that are comparable to those of the general population, and that their working conditions comply as closely as possible to those of other industries as specified by OSHA regulations. A brief technique for evaluating whether proposed advanced systems meet these safety requirements is presented, as well as a discussion of the costs of respiratory disability compensation.

Traceability of Software Safety Requirements in Legacy Safety Critical Systems

NASA Technical Reports Server (NTRS)

Hill, Janice L.

2007-01-01

How can traceability of software safety requirements be created for legacy safety critical systems? Requirements in safety standards are imposed most times during contract negotiations. On the other hand, there are instances where safety standards are levied on legacy safety critical systems, some of which may be considered for reuse for new applications. Safety standards often specify that software development documentation include process-oriented and technical safety requirements, and also require that system and software safety analyses are performed supporting technical safety requirements implementation. So what can be done if the requisite documents for establishing and maintaining safety requirements traceability are not available?

40 CFR 280.41 - Requirements for petroleum UST systems.

Code of Federal Regulations, 2010 CFR

2010-07-01

... 40 Protection of Environment 26 2010-07-01 2010-07-01 false Requirements for petroleum UST systems... UNDERGROUND STORAGE TANKS (UST) Release Detection § 280.41 Requirements for petroleum UST systems. Owners and operators of petroleum UST systems must provide release detection for tanks and piping as follows: (a) Tanks...

40 CFR 280.41 - Requirements for petroleum UST systems.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 40 Protection of Environment 27 2011-07-01 2011-07-01 false Requirements for petroleum UST systems... UNDERGROUND STORAGE TANKS (UST) Release Detection § 280.41 Requirements for petroleum UST systems. Owners and operators of petroleum UST systems must provide release detection for tanks and piping as follows: (a) Tanks...

Analyzing Software Requirements Errors in Safety-Critical, Embedded Systems

NASA Technical Reports Server (NTRS)

Lutz, Robyn R.

1993-01-01

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

Wind Shear Requirements and Their Application to Laser Systems

DOT National Transportation Integrated Search

1978-02-01

The requirements for a ground-based wind shear sensing system are developed. System coverage, accuracy, resolution, and data update rate are treated in detail. The differing requirements for synoptic shear conditions and thunderstorm-associated shear...

Ground Systems Development Environment (GSDE) interface requirements analysis

NASA Technical Reports Server (NTRS)

Church, Victor E.; Philips, John; Hartenstein, Ray; Bassman, Mitchell; Ruskin, Leslie; Perez-Davila, Alfredo

1991-01-01

A set of procedural and functional requirements are presented for the interface between software development environments and software integration and test systems used for space station ground systems software. The requirements focus on the need for centralized configuration management of software as it is transitioned from development to formal, target based testing. This concludes the GSDE Interface Requirements study. A summary is presented of findings concerning the interface itself, possible interface and prototyping directions for further study, and results of the investigation of the Cronus distributed applications environment.

An airline study of advanced technology requirements for advanced high speed commercial engines. 3: Propulsion system requirements

NASA Technical Reports Server (NTRS)

Sallee, G. P.

1973-01-01

The advanced technology requirements for an advanced high speed commercial transport engine are presented. The results of the phase 3 effort cover the requirements and objectives for future aircraft propulsion systems. These requirements reflect the results of the Task 1 and 2 efforts and serve as a baseline for future evaluations, specification development efforts, contract/purchase agreements, and operational plans for future subsonic commercial engines. This report is divided into five major sections: (1) management objectives for commercial propulsion systems, (2) performance requirements for commercial transport propulsion systems, (3) design criteria for future transport engines, (4) design requirements for powerplant packages, and (5) testing.

The 30/20 GHz communications system functional requirements

NASA Technical Reports Server (NTRS)

Siperko, C. M.; Frankfort, M.; Markham, R.; Wall, M.

1981-01-01

The characteristics of 30/20 GHz usage in satellite systems to be used in support of projected communication requirements of the 1990's are defined. A requirements analysis which develops projected market demand for satellite services by general and specialized carriers and an analysis of the impact of propagation and system constraints on 30/20 GHz operation are included. A set of technical performance characteristics for the 30/20 GHz systems which can serve the resulting market demand and the experimental program necessary to verify technical and operational aspects of the proposed systems is also discussed.

Smart roadside initiative : system requirements specifications.

DOT National Transportation Integrated Search

2015-09-01

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

76 FR 76917 - Homeless Management Information Systems Requirements

Federal Register 2010, 2011, 2012, 2013, 2014

2011-12-09

...-P-01] Homeless Management Information Systems Requirements AGENCY: Office of the Assistant Secretary... for the establishment of regulations for Homeless Management Information Systems (HMIS), which are the... community development, Homeless, Information technology system, Management system, Nonprofit organizations...

Development and analysis of SCR requirements tables for system scenarios

NASA Technical Reports Server (NTRS)

Callahan, John R.; Morrison, Jeffery L.

1995-01-01

We describe the use of scenarios to develop and refine requirement tables for parts of the Earth Observing System Data and Information System (EOSDIS). The National Aeronautics and Space Administration (NASA) is developing EOSDIS as part of its Mission-To-Planet-Earth (MTPE) project to accept instrument/platform observation requests from end-user scientists, schedule and perform requested observations of the Earth from space, collect and process the observed data, and distribute data to scientists and archives. Current requirements for the system are managed with tools that allow developers to trace the relationships between requirements and other development artifacts, including other requirements. In addition, the user community (e.g., earth and atmospheric scientists), in conjunction with NASA, has generated scenarios describing the actions of EOSDIS subsystems in response to user requests and other system activities. As part of a research effort in verification and validation techniques, this paper describes our efforts to develop requirements tables from these scenarios for the EOSDIS Core System (ECS). The tables specify event-driven mode transitions based on techniques developed by the Naval Research Lab's (NRL) Software Cost Reduction (SCR) project. The SCR approach has proven effective in specifying requirements for large systems in an unambiguous, terse format that enhance identification of incomplete and inconsistent requirements. We describe development of SCR tables from user scenarios and identify the strengths and weaknesses of our approach in contrast to the requirements tracing approach. We also evaluate the capabilities of both approach to respond to the volatility of requirements in large, complex systems.

Networking and AI systems: Requirements and benefits

NASA Technical Reports Server (NTRS)

1988-01-01

The price performance benefits of network systems is well documented. The ability to share expensive resources sold timesharing for mainframes, department clusters of minicomputers, and now local area networks of workstations and servers. In the process, other fundamental system requirements emerged. These have now been generalized with open system requirements for hardware, software, applications and tools. The ability to interconnect a variety of vendor products has led to a specification of interfaces that allow new techniques to extend existing systems for new and exciting applications. As an example of the message passing system, local area networks provide a testbed for many of the issues addressed by future concurrent architectures: synchronization, load balancing, fault tolerance and scalability. Gold Hill has been working with a number of vendors on distributed architectures that range from a network of workstations to a hypercube of microprocessors with distributed memory. Results from early applications are promising both for performance and scalability.

A Methodological Framework for Enterprise Information System Requirements Derivation

NASA Astrophysics Data System (ADS)

Caplinskas, Albertas; Paškevičiūtė, Lina

Current information systems (IS) are enterprise-wide systems supporting strategic goals of the enterprise and meeting its operational business needs. They are supported by information and communication technologies (ICT) and other software that should be fully integrated. To develop software responding to real business needs, we need requirements engineering (RE) methodology that ensures the alignment of requirements for all levels of enterprise system. The main contribution of this chapter is a requirement-oriented methodological framework allowing to transform business requirements level by level into software ones. The structure of the proposed framework reflects the structure of Zachman's framework. However, it has other intentions and is purposed to support not the design but the RE issues.

Freight advanced traveler information system : functional requirements.

DOT National Transportation Integrated Search

2012-08-01

This report describes the System Requirement Specifications (SyRS) for a Freight Advanced Traveler Information System (FRATIS). The SyRS is based on user needs described in the FRATIS Concept of Operations (ConOps), which cover the essential function...

Tank waste remediation system functions and requirements document

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

Carpenter, K.E

1996-10-03

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

Requirements specification for nickel cadmium battery expert system

NASA Technical Reports Server (NTRS)

1986-01-01

The requirements for performance, design, test, and qualification of a computer program identified as NICBES, Nickel Cadmium Battery Expert System, is established. The specific spacecraft power system configuration selected was the Hubble Space Telescope (HST) Electrical Power System (EPS) Testbed. Power for the HST comes from a system of 13 Solar Panel Arrays (SPAs) linked to 6 Nickel Cadmium Batteries which are connected to 3 Busses. An expert system, NICBES, will be developed at Martin Marietta Aerospace to recognize a testbed anomaly, identify the malfunctioning component and recommend a course of action. Besides fault diagnosis, NICBES will be able to evaluate battery status, give advice on battery status and provide decision support for the operator. These requirements are detailed.

A Modular Approach to Video Designation of Manipulation Targets for Manipulators

DTIC Science & Technology

2014-05-12

side view of a ray going through a point cloud of a water bottle sitting on the ground. The bottom left image shows the same point cloud after it has...System (ROS), Point Cloud Library (PCL), and OpenRAVE were used to a great extent to help promote reusability of the code developed during this

NASA TSRV essential flight control system requirements via object oriented analysis

NASA Technical Reports Server (NTRS)

Duffy, Keith S.; Hoza, Bradley J.

1992-01-01

The objective was to analyze the baseline flight control system of the Transport Systems Research Vehicle (TSRV) and to develop a system specification that offers high visibility of the essential system requirements in order to facilitate the future development of alternate, more advanced software architectures. The flight control system is defined to be the baseline software for the TSRV research flight deck, including all navigation, guidance, and control functions, and primary pilot displays. The Object Oriented Analysis (OOA) methodology developed is used to develop a system requirement definition. The scope of the requirements definition contained herein is limited to a portion of the Flight Management/Flight Control computer functionality. The development of a partial system requirements definition is documented, and includes a discussion of the tasks required to increase the scope of the requirements definition and recommendations for follow-on research.

5 CFR 9701.405 - Performance management system requirements.

Code of Federal Regulations, 2013 CFR

2013-01-01

... performance management systems for DHS employees, subject to the requirements set forth in this subpart. (b) Each DHS performance management system must— (1) Specify the employees covered by the system(s); (2... 5 Administrative Personnel 3 2013-01-01 2013-01-01 false Performance management system...

5 CFR 9701.405 - Performance management system requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... performance management systems for DHS employees, subject to the requirements set forth in this subpart. (b) Each DHS performance management system must— (1) Specify the employees covered by the system(s); (2... 5 Administrative Personnel 3 2011-01-01 2011-01-01 false Performance management system...

5 CFR 9701.405 - Performance management system requirements.

Code of Federal Regulations, 2012 CFR

2012-01-01

... performance management systems for DHS employees, subject to the requirements set forth in this subpart. (b) Each DHS performance management system must— (1) Specify the employees covered by the system(s); (2... 5 Administrative Personnel 3 2012-01-01 2012-01-01 false Performance management system...

5 CFR 9701.405 - Performance management system requirements.

Code of Federal Regulations, 2014 CFR

2014-01-01

... performance management systems for DHS employees, subject to the requirements set forth in this subpart. (b) Each DHS performance management system must— (1) Specify the employees covered by the system(s); (2... 5 Administrative Personnel 3 2014-01-01 2014-01-01 false Performance management system...

Functional Requirements for an Electronic Work Package System

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

Oxstrand, Johanna H.

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

Avionic architecture requirements for Space Exploration Initiative systems

NASA Technical Reports Server (NTRS)

Herbella, C. G.; Brown, D. C.

1991-01-01

The authors discuss NASA's Strategic Avionics Technology Working Group (SATWG) and the results of the first study commissioned by the SATWG, the Space Avionics Requirements Study (SARS). The goal of the SARS task was to show that an open avionics architecture, using modular, standardized components, could be applied across the wide range of systems that comprise the Space Exploration Initiative. The study addressed systems ranging from expendable launch vehicles and the space station to surface systems such as Mars or lunar rovers and habitats. Top-level avionics requirements were derived from characterizations of each of the systems considered. Then a set of avionics subsystems were identified, along with estimates of the numbers and types of modules needed to meet the requirements. Applicability of these results across the infrastructure was then illustrated. In addition to these tasks, critical technologies were identified, characterized, and assessed in terms of their criticality and impact on the program. Design, development, test, and evaluation methods were addressed to identify potential areas of improvement.

14 CFR 121.358 - Low-altitude windshear system equipment requirements.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 14 Aeronautics and Space 3 2014-01-01 2014-01-01 false Low-altitude windshear system equipment... OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS Instrument and Equipment Requirements § 121.358 Low-altitude windshear system equipment requirements. (a) Airplanes manufactured after January...

14 CFR 121.358 - Low-altitude windshear system equipment requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 14 Aeronautics and Space 3 2011-01-01 2011-01-01 false Low-altitude windshear system equipment... OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS Instrument and Equipment Requirements § 121.358 Low-altitude windshear system equipment requirements. (a) Airplanes manufactured after January...

14 CFR 121.358 - Low-altitude windshear system equipment requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 14 Aeronautics and Space 3 2010-01-01 2010-01-01 false Low-altitude windshear system equipment... OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS Instrument and Equipment Requirements § 121.358 Low-altitude windshear system equipment requirements. (a) Airplanes manufactured after January...

14 CFR 121.358 - Low-altitude windshear system equipment requirements.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 14 Aeronautics and Space 3 2012-01-01 2012-01-01 false Low-altitude windshear system equipment... OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS Instrument and Equipment Requirements § 121.358 Low-altitude windshear system equipment requirements. (a) Airplanes manufactured after January...

14 CFR 121.358 - Low-altitude windshear system equipment requirements.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 14 Aeronautics and Space 3 2013-01-01 2013-01-01 false Low-altitude windshear system equipment... OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS Instrument and Equipment Requirements § 121.358 Low-altitude windshear system equipment requirements. (a) Airplanes manufactured after January...

Patient Accounting Systems: Are They Fit with the Users' Requirements?

PubMed

Ayatollahi, Haleh; Nazemi, Zahra; Haghani, Hamid

2016-01-01

A patient accounting system is a subsystem of a hospital information system. This system like other information systems should be carefully designed to be able to meet users' requirements. The main aim of this research was to investigate users' requirements and to determine whether current patient accounting systems meet users' needs or not. This was a survey study, and the participants were the users of six patient accounting systems used in 24 teaching hospitals. A stratified sampling method was used to select the participants (n = 216). The research instruments were a questionnaire and a checklist. The mean value of ≥3 showed the importance of each data element and the capability of the system. Generally, the findings showed that the current patient accounting systems had some weaknesses and were able to meet between 70% and 80% of users' requirements. The current patient accounting systems need to be improved to be able to meet users' requirements. This approach can also help to provide hospitals with more usable and reliable financial information.

Patient Accounting Systems: Are They Fit with the Users' Requirements?

PubMed Central

Ayatollahi, Haleh; Nazemi, Zahra

2016-01-01

Objectives A patient accounting system is a subsystem of a hospital information system. This system like other information systems should be carefully designed to be able to meet users' requirements. The main aim of this research was to investigate users' requirements and to determine whether current patient accounting systems meet users' needs or not. Methods This was a survey study, and the participants were the users of six patient accounting systems used in 24 teaching hospitals. A stratified sampling method was used to select the participants (n = 216). The research instruments were a questionnaire and a checklist. The mean value of ≥3 showed the importance of each data element and the capability of the system. Results Generally, the findings showed that the current patient accounting systems had some weaknesses and were able to meet between 70% and 80% of users' requirements. Conclusions The current patient accounting systems need to be improved to be able to meet users' requirements. This approach can also help to provide hospitals with more usable and reliable financial information. PMID:26893945

Expert system verification and validation study. Phase 2: Requirements Identification. Delivery 2: Current requirements applicability

NASA Technical Reports Server (NTRS)

1991-01-01

The second phase of a task is described which has the ultimate purpose of ensuring that adequate Expert Systems (ESs) Verification and Validation (V and V) tools and techniques are available for Space Station Freedom Program Knowledge Based Systems development. The purpose of this phase is to recommend modifications to current software V and V requirements which will extend the applicability of the requirements to NASA ESs.

System Design Techniques for Reducing the Power Requirements of Advanced life Support Systems

NASA Technical Reports Server (NTRS)

Finn, Cory; Levri, Julie; Pawlowski, Chris; Crawford, Sekou; Luna, Bernadette (Technical Monitor)

2000-01-01

The high power requirement associated with overall operation of regenerative life support systems is a critical Z:p technological challenge. Optimization of individual processors alone will not be sufficient to produce an optimized system. System studies must be used in order to improve the overall efficiency of life support systems. Current research efforts at NASA Ames Research Center are aimed at developing approaches for reducing system power and energy usage in advanced life support systems. System energy integration and energy reuse techniques are being applied to advanced life support, in addition to advanced control methods for efficient distribution of power and thermal resources. An overview of current results of this work will be presented. The development of integrated system designs that reuse waste heat from sources such as crop lighting and solid waste processing systems will reduce overall power and cooling requirements. Using an energy integration technique known as Pinch analysis, system heat exchange designs are being developed that match hot and cold streams according to specific design principles. For various designs, the potential savings for power, heating and cooling are being identified and quantified. The use of state-of-the-art control methods for distribution of resources, such as system cooling water or electrical power, will also reduce overall power and cooling requirements. Control algorithms are being developed which dynamically adjust the use of system resources by the various subsystems and components in order to achieve an overall goal, such as smoothing of power usage and/or heat rejection profiles, while maintaining adequate reserves of food, water, oxygen, and other consumables, and preventing excessive build-up of waste materials. Reductions in the peak loading of the power and thermal systems will lead to lower overall requirements. Computer simulation models are being used to test various control system designs.

Information Requirements for a Procurement Management Information System.

DTIC Science & Technology

1975-08-01

Management Information System is...described and some justification for this type of procurement management information system is presented. A literature search was made to determine...information systems. If information requirements are correctly identified and satisfied by a procurement management information system , contract administration and procurement management can be

19 CFR 143.5 - System performance requirements.

Code of Federal Regulations, 2012 CFR

2012-04-01

... 19 Customs Duties 2 2012-04-01 2012-04-01 false System performance requirements. 143.5 Section 143.5 Customs Duties U.S. CUSTOMS AND BORDER PROTECTION, DEPARTMENT OF HOMELAND SECURITY; DEPARTMENT OF... must demonstrate that his system can interface directly with the Customs computer and ensure accurate...

19 CFR 143.5 - System performance requirements.

Code of Federal Regulations, 2011 CFR

2011-04-01

... 19 Customs Duties 2 2011-04-01 2011-04-01 false System performance requirements. 143.5 Section 143.5 Customs Duties U.S. CUSTOMS AND BORDER PROTECTION, DEPARTMENT OF HOMELAND SECURITY; DEPARTMENT OF... must demonstrate that his system can interface directly with the Customs computer and ensure accurate...

19 CFR 143.5 - System performance requirements.

Code of Federal Regulations, 2014 CFR

2014-04-01

... 19 Customs Duties 2 2014-04-01 2014-04-01 false System performance requirements. 143.5 Section 143.5 Customs Duties U.S. CUSTOMS AND BORDER PROTECTION, DEPARTMENT OF HOMELAND SECURITY; DEPARTMENT OF... must demonstrate that his system can interface directly with the Customs computer and ensure accurate...

19 CFR 143.5 - System performance requirements.

Code of Federal Regulations, 2010 CFR

2010-04-01

... 19 Customs Duties 2 2010-04-01 2010-04-01 false System performance requirements. 143.5 Section 143.5 Customs Duties U.S. CUSTOMS AND BORDER PROTECTION, DEPARTMENT OF HOMELAND SECURITY; DEPARTMENT OF... must demonstrate that his system can interface directly with the Customs computer and ensure accurate...

19 CFR 143.5 - System performance requirements.

Code of Federal Regulations, 2013 CFR

2013-04-01

... 19 Customs Duties 2 2013-04-01 2013-04-01 false System performance requirements. 143.5 Section 143.5 Customs Duties U.S. CUSTOMS AND BORDER PROTECTION, DEPARTMENT OF HOMELAND SECURITY; DEPARTMENT OF... must demonstrate that his system can interface directly with the Customs computer and ensure accurate...

Onboard Inert Gas Generation System/Onboard Oxygen Gas Generation System (OBIGGS/OBOGS) Study. Part 1; Aircraft System Requirements

NASA Technical Reports Server (NTRS)

Reynolds, Thomas L.; Bailey, Delbert B.; Lewinski, Daniel F.; Roseburg, Conrad M.; Palaszewski, Bryan (Technical Monitor)

2001-01-01

The purpose of this technology assessment is to define a multiphase research study program investigating Onboard Inert Gas Generation Systems (OBIGGS) and Onboard Oxygen Generation Systems (OBOGS) that would identify current airplane systems design and certification requirements (Subtask 1); explore state-of-the-art technology (Subtask 2); develop systems specifications (Subtask 3); and develop an initial system design (Subtask 4). If feasible, consideration may be given to the development of a prototype laboratory test system that could potentially be used in commercial transport aircraft (Subtask 5). These systems should be capable of providing inert nitrogen gas for improved fire cargo compartment fire suppression and fuel tank inerting and emergency oxygen for crew and passenger use. Subtask I of this research study, presented herein, defines current production aircraft certification requirements and design objectives necessary to meet mandatory FAA certification requirements and Boeing design and performance specifications. These requirements will be utilized for baseline comparisons for subsequent OBIGGS/OBOGS application evaluations and assessments.

Materiel requirements for airborne minefield detection system

NASA Astrophysics Data System (ADS)

Bertsche, Karl A.; Huegle, Helmut

1997-07-01

Within the concept study, Material Requirements for an airborne minefield detection systems (AMiDS) the following topics were investigated: (i) concept concerning airborne minefield detection technique sand equipment, (ii) verification analysis of the AMiDS requirements using simulation models and (iii) application concept of AMiDS with regard o tactics and military operations. In a first approach the problems concerning unmanned airborne minefield detection techniques within a well-defined area were considered. The complexity of unmanned airborne minefield detection is a result of the following parameters: mine types, mine deployment methods, tactical requirements, topography, weather conditions, and the size of the area to be searched. In order to perform the analysis, a simulation model was developed to analyze the usability of the proposed remote controlled air carriers. The basic flight patterns for the proposed air carriers, as well as the preparation efforts of military operations and benefits of such a system during combat support missions were investigated. The results of the conceptual study showed that a proposed remote controlled helicopter drone could meet the stated German MOD scanning requirements of mine barriers. Fixed wing air carriers were at a definite disadvantage because of their inherently large turning loops. By implementing a mine detection system like AMiDS minefields can be reconnoitered before an attack. It is therefore possible either to plan, how the minefields can be circumvented or where precisely breaching lanes through the mine barriers are to be cleared for the advancing force.

17 CFR 242.303 - Record preservation requirements for alternative trading systems.

Code of Federal Regulations, 2014 CFR

2014-04-01

... requirements for alternative trading systems. 242.303 Section 242.303 Commodity and Securities Exchanges... REQUIREMENTS FOR SECURITY FUTURES Regulation Ats-Alternative Trading Systems § 242.303 Record preservation requirements for alternative trading systems. (a) To comply with the condition set forth in paragraph (b)(9) of...

17 CFR 242.303 - Record preservation requirements for alternative trading systems.

Code of Federal Regulations, 2012 CFR

2012-04-01

... requirements for alternative trading systems. 242.303 Section 242.303 Commodity and Securities Exchanges... REQUIREMENTS FOR SECURITY FUTURES Regulation Ats-Alternative Trading Systems § 242.303 Record preservation requirements for alternative trading systems. (a) To comply with the condition set forth in paragraph (b)(9) of...

17 CFR 242.303 - Record preservation requirements for alternative trading systems.

Code of Federal Regulations, 2013 CFR

2013-04-01

... requirements for alternative trading systems. 242.303 Section 242.303 Commodity and Securities Exchanges... REQUIREMENTS FOR SECURITY FUTURES Regulation Ats-Alternative Trading Systems § 242.303 Record preservation requirements for alternative trading systems. (a) To comply with the condition set forth in paragraph (b)(9) of...

17 CFR 242.303 - Record preservation requirements for alternative trading systems.

Code of Federal Regulations, 2010 CFR

2010-04-01

... requirements for alternative trading systems. 242.303 Section 242.303 Commodity and Securities Exchanges... REQUIREMENTS FOR SECURITY FUTURES Regulation Ats-Alternative Trading Systems § 242.303 Record preservation requirements for alternative trading systems. (a) To comply with the condition set forth in paragraph (b)(9) of...

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

NASA Technical Reports Server (NTRS)

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

1981-01-01

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

Places and patterns of drug use in the Scottish dance scene.

PubMed

Forsyth, A J

1996-04-01

Interviews were conducted with 135 participants in the Glasgow dance (rave) scene. Drug use in this group was varied and not merely restricted to drugs associated with dance events, such as MDMA (Ecstasy). The setting in which each drug was used varied greatly. Amphetamine, nitrites and Ecstasy were the drugs most commonly used at dance events. Pharmaceuticals were least likely to be used in such settings. However, some drugs, such as Temazepam, were sometimes used prior to or after attending rave events. It is suggested that dance drug users are polydrug users who use drugs in a setting specific fashion. As such it would be wrong to classify such users solely on the grounds of their very visible behaviour in the public arena (at dance events). Other forms of substance use engaged in by this group may have a greater potential for harm than that seen at raves. The implications of these findings are discussed.

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

NASA Technical Reports Server (NTRS)

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.

Space Transportation System Availability Requirement and Its Influencing Attributes Relationships

NASA Technical Reports Server (NTRS)

Rhodes, Russell E.; Adams, Timothy C.; McCleskey, Carey M.

2008-01-01

It is important that engineering and management accept the need for an availability requirement that is derived with its influencing attributes. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability. Also important to provide bounds of the variables providing engineering the insight required to control the system's engineering solution, e.g., these influencing attributes become design requirements also. These variables will drive the need to provide integration of similar discipline functions or technology selection to allow control of the total parts count. The relationship of selecting a reliability requirement will place a constraint on parts count to achieve a given availability requirement or if allowed to increase the parts count will drive the system reliability requirement higher. They also provide the understanding for the relationship of mean repair time (or mean down time) to maintainability, e.g., accessibility for repair, and both the mean time between failure, e.g., reliability of hardware and availability. The concerns and importance of achieving a strong availability requirement is driven by the need for affordability, the choice of using the two launch solution for the single space application, or the need to control the spare parts count needed to support the long stay in either orbit or on the surface of the moon. Understanding the requirements before starting the architectural design concept will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable

Space Transportation System Availability Requirements and Its Influencing Attributes Relationships

NASA Technical Reports Server (NTRS)

Rhodes, Russell E.; Adams, Timothy C.; McCleskey, Carey M.

2008-01-01

It is important that engineering and management accept the need for an availability requirement that is derived with its influencing attributes. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability. Also important to provide bounds of the variables providing engineering the insight required to control the system's engineering solution, e.g., these influencing attributes become design requirements also. These variables will drive the need to provide integration of similar discipline functions or technology selection to allow control of the total parts count. The relationship of selecting a reliability requirement will place a constraint on parts count to achieve a given availability requirement or if allowed to increase the parts count will drive the system reliability requirement higher. They also provide the understanding for the relationship of mean repair time (or mean down time) to maintainability, e.g., accessibility for repair, and both the mean time between failure, e.g., reliability of hardware and availability. The concerns and importance of achieving a strong availability requirement is driven by the need for affordability, the choice of using the two launch solution for the single space application, or the need to control the spare parts count needed to support the long stay in either orbit or on the surface of the moon. Understanding the requirements before starting the architectural design concept will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable

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

NASA Technical Reports Server (NTRS)

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.

30 CFR 764.21 - Data base and inventory system requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

... 30 Mineral Resources 3 2012-07-01 2012-07-01 false Data base and inventory system requirements... SURFACE COAL MINING OPERATIONS § 764.21 Data base and inventory system requirements. (a) The regulatory authority shall develop a data base and inventory system which will permit evaluation of whether reclamation...

30 CFR 764.21 - Data base and inventory system requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

... 30 Mineral Resources 3 2013-07-01 2013-07-01 false Data base and inventory system requirements... SURFACE COAL MINING OPERATIONS § 764.21 Data base and inventory system requirements. (a) The regulatory authority shall develop a data base and inventory system which will permit evaluation of whether reclamation...

30 CFR 764.21 - Data base and inventory system requirements.

Code of Federal Regulations, 2014 CFR

2014-07-01

... 30 Mineral Resources 3 2014-07-01 2014-07-01 false Data base and inventory system requirements... SURFACE COAL MINING OPERATIONS § 764.21 Data base and inventory system requirements. (a) The regulatory authority shall develop a data base and inventory system which will permit evaluation of whether reclamation...

30 CFR 764.21 - Data base and inventory system requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 30 Mineral Resources 3 2011-07-01 2011-07-01 false Data base and inventory system requirements... SURFACE COAL MINING OPERATIONS § 764.21 Data base and inventory system requirements. (a) The regulatory authority shall develop a data base and inventory system which will permit evaluation of whether reclamation...

Online mass storage system detailed requirements document

NASA Technical Reports Server (NTRS)

1976-01-01

The requirements for an online high density magnetic tape data storage system that can be implemented in a multipurpose, multihost environment is set forth. The objective of the mass storage system is to provide a facility for the compact storage of large quantities of data and to make this data accessible to computer systems with minimum operator handling. The results of a market survey and analysis of candidate vendor who presently market high density tape data storage systems are included.

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

NASA Technical Reports Server (NTRS)

Dory, Jonathan

2010-01-01

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

Requirements for Workflow-Based EHR Systems - Results of a Qualitative Study.

PubMed

Schweitzer, Marco; Lasierra, Nelia; Hoerbst, Alexander

2016-01-01

Today's high quality healthcare delivery strongly relies on efficient electronic health records (EHR). These EHR systems or in general healthcare IT-systems are usually developed in a static manner according to a given workflow. Hence, they are not flexible enough to enable access to EHR data and to execute individual actions within a consultation. This paper reports on requirements pointed by experts in the domain of diabetes mellitus to design a system for supporting dynamic workflows to serve personalization within a medical activity. Requirements were collected by means of expert interviews. These interviews completed a conducted triangulation approach, aimed to gather requirements for workflow-based EHR interactions. The data from the interviews was analyzed through a qualitative approach resulting in a set of requirements enhancing EHR functionality from the user's perspective. Requirements were classified according to four different categorizations: (1) process-related requirements, (2) information needs, (3) required functions, (4) non-functional requirements. Workflow related requirements were identified which should be considered when developing and deploying EHR systems.

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

NASA Technical Reports Server (NTRS)

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.

Future Orbital Power Systems Technology Requirements

NASA Technical Reports Server (NTRS)

1978-01-01

NASA is actively involved in program planning for missions requiring several orders of magnitude, more energy than in the past. Therefore, a two-day symposium was held to review the technology requirements for future orbital power systems. The purpose of the meeting was to give leaders from government and industry a broad view of current government supported technology efforts and future program plans in space power. It provided a forum for discussion, through workshops, to comment on current and planned programs and to identify opportunities for technology investment. Several papers are presented to review the technology status and the planned programs.

Proposed system safety design and test requirements for the microlaser ordnance system

NASA Technical Reports Server (NTRS)

Stoltz, Barb A.; Waldo, Dale F.

1993-01-01

Safety for pyrotechnic ignition systems is becoming a major concern for the military. In the past twenty years, stray electromagnetic fields have steadily increased during peacetime training missions and have dramatically increased during battlefield missions. Almost all of the ordnance systems in use today depend on an electrical bridgewire for ignition. Unfortunately, the bridgewire is the cause of the majority of failure modes. The common failure modes include the following: broken bridgewires; transient RF power, which induces bridgewire heating; and cold temperatures, which contracts the explosive mix away from the bridgewire. Finding solutions for these failure modes is driving the costs of pyrotechnic systems up. For example, analyses are performed to verify that the system in the environment will not see more energy than 20 dB below the 'No-fire' level. Range surveys are performed to determine the operational, storage, and transportation RF environments. Cryogenic tests are performed to verify the bridgewire to mix interface. System requirements call for 'last minute installation,' 'continuity checks after installation,' and rotating safety devices to 'interrupt the explosive train.' As an alternative, MDESC has developed a new approach based upon our enabling laser diode technology. We believe that Microlaser initiated ordnance offers a unique solution to the bridgewire safety concerns. For this presentation, we will address, from a system safety viewpoint, the safety design and the test requirements for a Microlaser ordnance system. We will also review how this system could be compliant to MIL-STD-1576 and DOD-83578A and the additional necessary requirements.

The effect of requirements prioritization on avionics system conceptual design

NASA Astrophysics Data System (ADS)

Lorentz, John

This dissertation will provide a detailed approach and analysis of a new collaborative requirements prioritization methodology that has been used successfully on four Coast Guard avionics acquisition and development programs valued at $400M+. A statistical representation of participant study results will be discussed and analyzed in detail. Many technically compliant projects fail to deliver levels of performance and capability that the customer desires. Some of these systems completely meet "threshold" levels of performance; however, the distribution of resources in the process devoted to the development and management of the requirements does not always represent the voice of the customer. This is especially true for technically complex projects such as modern avionics systems. A simplified facilitated process for prioritization of system requirements will be described. The collaborative prioritization process, and resulting artifacts, aids the systems engineer during early conceptual design. All requirements are not the same in terms of customer priority. While there is a tendency to have many thresholds inside of a system design, there is usually a subset of requirements and system performance that is of the utmost importance to the design. These critical capabilities and critical levels of performance typically represent the reason the system is being built. The systems engineer needs processes to identify these critical capabilities, the associated desired levels of performance, and the risks associated with the specific requirements that define the critical capability. The facilitated prioritization exercise is designed to collaboratively draw out these critical capabilities and levels of performance so they can be emphasized in system design. Developing the purpose, scheduling and process for prioritization events are key elements of systems engineering and modern project management. The benefits of early collaborative prioritization flow throughout the

Space Transportation System Availability Requirements and Its Influencing Attributes Relationships

NASA Technical Reports Server (NTRS)

Rhodes, Russel E.; Adams, TImothy C.

2008-01-01

It is essential that management and engineering understand the need for an availability requirement for the customer's space transportation system as it enables the meeting of his needs, goal, and objectives. There are three types of availability, e.g., operational availability, achieved availability, or inherent availability. The basic definition of availability is equal to the mean uptime divided by the sum of the mean uptime plus the mean downtime. The major difference is the inclusiveness of the functions within the mean downtime and the mean uptime. This paper will address tIe inherent availability which only addresses the mean downtime as that mean time to repair or the time to determine the failed article, remove it, install a replacement article and verify the functionality of the repaired system. The definitions of operational availability include the replacement hardware supply or maintenance delays and other non-design factors in the mean downtime. Also with inherent availability the mean uptime will only consider the mean time between failures (other availability definitions consider this as mean time between maintenance - preventive and corrective maintenance) that requires the repair of the system to be functional. It is also essential that management and engineering understand all influencing attributes relationships to each other and to the resultant inherent availability requirement. This visibility will provide the decision makers with the understanding necessary to place constraints on the design definition for the major drivers that will determine the inherent availability, safety, reliability, maintainability, and the life cycle cost of the fielded system provided the customer. This inherent availability requirement may be driven by the need to use a multiple launch approach to placing humans on the moon or the desire to control the number of spare parts required to support long stays in either orbit or on the surface of the moon or mars. It is

5 CFR 9701.405 - Performance management system requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... requirements. 9701.405 Section 9701.405 Administrative Personnel DEPARTMENT OF HOMELAND SECURITY HUMAN RESOURCES MANAGEMENT SYSTEM (DEPARTMENT OF HOMELAND SECURITY-OFFICE OF PERSONNEL MANAGEMENT) DEPARTMENT OF HOMELAND SECURITY HUMAN RESOURCES MANAGEMENT SYSTEM Performance Management § 9701.405 Performance...

Formal analysis of imprecise system requirements with Event-B.

PubMed

Le, Hong Anh; Nakajima, Shin; Truong, Ninh Thuan

2016-01-01

Formal analysis of functional properties of system requirements needs precise descriptions. However, the stakeholders sometimes describe the system with ambiguous, vague or fuzzy terms, hence formal frameworks for modeling and verifying such requirements are desirable. The Fuzzy If-Then rules have been used for imprecise requirements representation, but verifying their functional properties still needs new methods. In this paper, we propose a refinement-based modeling approach for specification and verification of such requirements. First, we introduce a representation of imprecise requirements in the set theory. Then we make use of Event-B refinement providing a set of translation rules from Fuzzy If-Then rules to Event-B notations. After that, we show how to verify both safety and eventuality properties with RODIN/Event-B. Finally, we illustrate the proposed method on the example of Crane Controller.

27 CFR 25.41 - Measuring system required.

Code of Federal Regulations, 2010 CFR

2010-04-01

..., DEPARTMENT OF THE TREASURY LIQUORS BEER Measurement of Beer § 25.41 Measuring system required. The brewer shall accurately and reliably measure the quantity of beer transferred from the brewery cellars for...

27 CFR 25.41 - Measuring system required.

Code of Federal Regulations, 2014 CFR

2014-04-01

..., DEPARTMENT OF THE TREASURY ALCOHOL BEER Measurement of Beer § 25.41 Measuring system required. The brewer shall accurately and reliably measure the quantity of beer transferred from the brewery cellars for...

27 CFR 25.41 - Measuring system required.

Code of Federal Regulations, 2012 CFR

2012-04-01

..., DEPARTMENT OF THE TREASURY LIQUORS BEER Measurement of Beer § 25.41 Measuring system required. The brewer shall accurately and reliably measure the quantity of beer transferred from the brewery cellars for...

27 CFR 25.41 - Measuring system required.

Code of Federal Regulations, 2013 CFR

2013-04-01

..., DEPARTMENT OF THE TREASURY ALCOHOL BEER Measurement of Beer § 25.41 Measuring system required. The brewer shall accurately and reliably measure the quantity of beer transferred from the brewery cellars for...

27 CFR 25.41 - Measuring system required.

Code of Federal Regulations, 2011 CFR

2011-04-01

..., DEPARTMENT OF THE TREASURY LIQUORS BEER Measurement of Beer § 25.41 Measuring system required. The brewer shall accurately and reliably measure the quantity of beer transferred from the brewery cellars for...

47 CFR 15.517 - Technical requirements for indoor UWB systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 1 2010-10-01 2010-10-01 false Technical requirements for indoor UWB systems. 15.517 Section 15.517 Telecommunication FEDERAL COMMUNICATIONS COMMISSION GENERAL RADIO FREQUENCY DEVICES Ultra-Wideband Operation § 15.517 Technical requirements for indoor UWB systems. (a) Operation...

Requirements Analysis for the Army Safety Management Information System (ASMIS)

DTIC Science & Technology

1989-03-01

8217_>’ Telephone Number « .. PNL-6819 Limited Distribution Requirements Analysis for the Army Safety Management Information System (ASMIS) Final...PNL-6819 REQUIREMENTS ANALYSIS FOR THE ARMY SAFETY MANAGEMENT INFORMATION SYSTEM (ASMIS) FINAL REPORT J. S. Littlefield A. L. Corrigan March...accidents. This accident data is available under the Army Safety Management Information System (ASMIS) which is an umbrella for many databases

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

NASA Technical Reports Server (NTRS)

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

1988-01-01

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

5 CFR 9901.405 - Performance management system requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 5 Administrative Personnel 3 2010-01-01 2010-01-01 false Performance management system requirements. 9901.405 Section 9901.405 Administrative Personnel DEPARTMENT OF DEFENSE HUMAN RESOURCES MANAGEMENT AND LABOR RELATIONS SYSTEMS (DEPARTMENT OF DEFENSE-OFFICE OF PERSONNEL MANAGEMENT) DEPARTMENT OF...

47 CFR 15.513 - Technical requirements for medical imaging systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 1 2010-10-01 2010-10-01 false Technical requirements for medical imaging systems. 15.513 Section 15.513 Telecommunication FEDERAL COMMUNICATIONS COMMISSION GENERAL RADIO FREQUENCY DEVICES Ultra-Wideband Operation § 15.513 Technical requirements for medical imaging systems. (a) The UWB...

47 CFR 15.515 - Technical requirements for vehicular radar systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 47 Telecommunication 1 2011-10-01 2011-10-01 false Technical requirements for vehicular radar... DEVICES Ultra-Wideband Operation § 15.515 Technical requirements for vehicular radar systems. (a..., changing gears, or engaging a turn signal. (b) The UWB bandwidth of a vehicular radar system operating...

47 CFR 15.515 - Technical requirements for vehicular radar systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 1 2010-10-01 2010-10-01 false Technical requirements for vehicular radar... DEVICES Ultra-Wideband Operation § 15.515 Technical requirements for vehicular radar systems. (a..., changing gears, or engaging a turn signal. (b) The UWB bandwidth of a vehicular radar system operating...

47 CFR 15.515 - Technical requirements for vehicular radar systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 47 Telecommunication 1 2014-10-01 2014-10-01 false Technical requirements for vehicular radar... DEVICES Ultra-Wideband Operation § 15.515 Technical requirements for vehicular radar systems. (a..., changing gears, or engaging a turn signal. (b) The UWB bandwidth of a vehicular radar system operating...

47 CFR 15.515 - Technical requirements for vehicular radar systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 47 Telecommunication 1 2013-10-01 2013-10-01 false Technical requirements for vehicular radar... DEVICES Ultra-Wideband Operation § 15.515 Technical requirements for vehicular radar systems. (a..., changing gears, or engaging a turn signal. (b) The UWB bandwidth of a vehicular radar system operating...

47 CFR 15.515 - Technical requirements for vehicular radar systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 47 Telecommunication 1 2012-10-01 2012-10-01 false Technical requirements for vehicular radar... DEVICES Ultra-Wideband Operation § 15.515 Technical requirements for vehicular radar systems. (a..., changing gears, or engaging a turn signal. (b) The UWB bandwidth of a vehicular radar system operating...

National Maglev initiative: California line electric utility power system requirements

NASA Technical Reports Server (NTRS)

Save, Phil

1994-01-01

The electrical utility power system requirements were determined for a Maglev line from San Diego to San Francisco and Sacramento with a maximum capacity of 12,000 passengers an hour in each direction at a speed of 300 miles per hour, or one train every 30 seconds in each direction. Basically the Maglev line requires one 50-MVA substation every 12.5 miles. The need for new power lines to serve these substations and their voltage levels are based not only on equipment loading criteria but also on limitations due to voltage flicker and harmonics created by the Maglev system. The resulting power system requirements and their costs depend mostly on the geographical area, urban or suburban with 'strong' power systems, or mountains and rural areas with 'weak' power systems. A reliability evaluation indicated that emergency power sources, such as a 10-MW battery at each substation, were not justified if sufficient redundancy is provided in the design of the substations and the power lines serving them. With a cost of $5.6 M per mile, the power system requirements, including the 12-kV DC cables and the inverters along the Maglev line, were found to be the second largest cost component of the Maglev system, after the cost of the guideway system ($9.1 M per mile), out of a total cost of $23 M per mile.

40 CFR 141.712 - Unfiltered system Cryptosporidium treatment requirements.

Code of Federal Regulations, 2014 CFR

2014-07-01

..., ozone, or UV as described in § 141.720 to meet the Cryptosporidium inactivation requirements of this... violation of the treatment technique requirement. (2) Systems that use UV light and fail to achieve the...

40 CFR 141.712 - Unfiltered system Cryptosporidium treatment requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

..., ozone, or UV as described in § 141.720 to meet the Cryptosporidium inactivation requirements of this... violation of the treatment technique requirement. (2) Systems that use UV light and fail to achieve the...

40 CFR 141.712 - Unfiltered system Cryptosporidium treatment requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

..., ozone, or UV as described in § 141.720 to meet the Cryptosporidium inactivation requirements of this... violation of the treatment technique requirement. (2) Systems that use UV light and fail to achieve the...

User requirements for a patient scheduling system

NASA Technical Reports Server (NTRS)

Zimmerman, W.

1979-01-01

A rehabilitation institute's needs and wants from a scheduling system were established by (1) studying the existing scheduling system and the variables that affect patient scheduling, (2) conducting a human-factors study to establish the human interfaces that affect patients' meeting prescribed therapy schedules, and (3) developing and administering a questionnaire to the staff which pertains to the various interface problems in order to identify staff requirements to minimize scheduling problems and other factors that may limit the effectiveness of any new scheduling system.

Data System Implications Derived from User Application Requirements for Satellite Data

NASA Technical Reports Server (NTRS)

Neiers, J.

1979-01-01

An investigation of the data system needs as driven by users of space acquired Earth observation data is documented. Two major categories of users, operational and research, are identified. Limiting data acquisition alleviates some of the delays in processing thus improving timeliness of the delivered product. Trade offs occur between timeliness and data distribution costs, and between data storage and reprocessing. The complexity of the data system requirements to apply space data to users' needs is such that no single analysis suffices to design and implement the optimum system. A series of iterations is required with analyses of the salient problems in a general way, followed by a limited implementation of benefit to some users with a continual upgrade in system capacity, functions, and applications served. The resulting most important requirement for the data system is flexibility to accommodate changing requirements as the system is implemented.

Reliability program requirements for aeronautical and space system contractors

NASA Technical Reports Server (NTRS)

1987-01-01

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

Safety policy and requirements for payloads using the space transportation system

NASA Technical Reports Server (NTRS)

1989-01-01

The safety policy and requirements are established applicable to the Space Transportation System (STS) payloads and their ground support equipment (GSE). The requirements are intended to protect flight and ground personnel, the STS, other payloads, GSE, the general public, public-private property, and the environment from payload-related hazards. The technical and system safety requirements applicable to STS payloads (including payload-provided ground and flight supports systems) during ground and flight operations are contained.

Formal Verification of Complex Systems based on SysML Functional Requirements

DTIC Science & Technology

2014-12-23

Formal Verification of Complex Systems based on SysML Functional Requirements Hoda Mehrpouyan1, Irem Y. Tumer2, Chris Hoyle2, Dimitra Giannakopoulou3...requirements for design of complex engineered systems. The proposed ap- proach combines a SysML modeling approach to document and structure safety requirements...methods and tools to support the integration of safety into the design solution. 2.1. SysML for Complex Engineered Systems Traditional methods and tools

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

DOT National Transportation Integrated Search

2008-03-31

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

Automated Derivation of Complex System Constraints from User Requirements

NASA Technical Reports Server (NTRS)

Foshee, Mark; Murey, Kim; Marsh, Angela

2010-01-01

The Payload Operations Integration Center (POIC) located at the Marshall Space Flight Center has the responsibility of integrating US payload science requirements for the International Space Station (ISS). All payload operations must request ISS system resources so that the resource usage will be included in the ISS on-board execution timelines. The scheduling of resources and building of the timeline is performed using the Consolidated Planning System (CPS). The ISS resources are quite complex due to the large number of components that must be accounted for. The planners at the POIC simplify the process for Payload Developers (PD) by providing the PDs with a application that has the basic functionality PDs need as well as list of simplified resources in the User Requirements Collection (URC) application. The planners maintained a mapping of the URC resources to the CPS resources. The process of manually converting PD's science requirements from a simplified representation to a more complex CPS representation is a time-consuming and tedious process. The goal is to provide a software solution to allow the planners to build a mapping of the complex CPS constraints to the basic URC constraints and automatically convert the PD's requirements into systems requirements during export to CPS.

40 CFR 141.712 - Unfiltered system Cryptosporidium treatment requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... inactivation. (c) Inactivation treatment technology requirements. Unfiltered systems must use chlorine dioxide... section. (1) Systems that use chlorine dioxide or ozone and fail to achieve the Cryptosporidium...

40 CFR 141.712 - Unfiltered system Cryptosporidium treatment requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

... inactivation. (c) Inactivation treatment technology requirements. Unfiltered systems must use chlorine dioxide... section. (1) Systems that use chlorine dioxide or ozone and fail to achieve the Cryptosporidium...

Requirement Generation for Space Infrastructure Systems

NASA Astrophysics Data System (ADS)

Hempsell, M.

Despite heavy investment, in the half-century period between 1970 and 2020 there will almost no progress in the capability provided by the space infrastructure. It is argued that this is due to a failure during the requirement generation phase of the infrastructure's elements, a failure that is primarily due to following the accepted good practice of involving stakeholders while establishing a mission based set of technical requirements. This argument is supported by both a consideration of the history of the requirement generation phase of past space infrastructure projects, in particular the Space Shuttle, and an analysis of the interactions of the stakeholders during this phase. Traditional stakeholder involvement only works well in mature infrastructures where investment aims to make minor improvements, whereas space activity is still in the early experimental stages and is open to major new initiatives that aim to radically change the way we work in space. A new approach to requirement generation is proposed, which is more appropriate to these current circumstances. This uses a methodology centred on the basic functions the system is intended to perform rather than its expected missions.

47 CFR 90.633 - Conventional systems loading requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... of need. In a ribbon, regional or statewide system, a mobile station will be counted for channel... 47 Telecommunication 5 2011-10-01 2011-10-01 false Conventional systems loading requirements. 90... RADIO SERVICES PRIVATE LAND MOBILE RADIO SERVICES Regulations Governing Licensing and Use of Frequencies...

Enhancing requirements engineering for patient registry software systems with evidence-based components.

PubMed

Lindoerfer, Doris; Mansmann, Ulrich

2017-07-01

Patient registries are instrumental for medical research. Often their structures are complex and their implementations use composite software systems to meet the wide spectrum of challenges. Commercial and open-source systems are available for registry implementation, but many research groups develop their own systems. Methodological approaches in the selection of software as well as the construction of proprietary systems are needed. We propose an evidence-based checklist, summarizing essential items for patient registry software systems (CIPROS), to accelerate the requirements engineering process. Requirements engineering activities for software systems follow traditional software requirements elicitation methods, general software requirements specification (SRS) templates, and standards. We performed a multistep procedure to develop a specific evidence-based CIPROS checklist: (1) A systematic literature review to build a comprehensive collection of technical concepts, (2) a qualitative content analysis to define a catalogue of relevant criteria, and (3) a checklist to construct a minimal appraisal standard. CIPROS is based on 64 publications and covers twelve sections with a total of 72 items. CIPROS also defines software requirements. Comparing CIPROS with traditional software requirements elicitation methods, SRS templates and standards show a broad consensus but differences in issues regarding registry-specific aspects. Using an evidence-based approach to requirements engineering for registry software adds aspects to the traditional methods and accelerates the software engineering process for registry software. The method we used to construct CIPROS serves as a potential template for creating evidence-based checklists in other fields. The CIPROS list supports developers in assessing requirements for existing systems and formulating requirements for their own systems, while strengthening the reporting of patient registry software system descriptions. It may be

Seaway Information System Management and Control Requirements

DOT National Transportation Integrated Search

1973-10-01

This report examines in detail the control and information system requirements of the St. Lawrence Seaway development program in terms of the needs of the vessel traffic controllers and the management users. Structural control models of Seaway operat...

Facility Systems, Ground Support Systems, and Ground Support Equipment General Design Requirements

NASA Technical Reports Server (NTRS)

Thaxton, Eric A.; Mathews, Roger E.

2014-01-01

This standard establishes requirements and guidance for design and fabrication of ground systems (GS) that includes: ground support equipment (GSE), ground support systems (GSS), and facility ground support systems (F GSS) to provide uniform methods and processes for design and development of robust, safe, reliable, maintainable, supportable, and cost-effective GS in support of space flight and institutional programs and projects.

Power system requirements and definition for lunar and Mars outposts

NASA Technical Reports Server (NTRS)

Petri, D. A.; Cataldo, R. L.; Bozek, J. M.

1990-01-01

Candidate power systems being considered for outpost facilities (stationary power systems) and vehicles (mobile systems) are discussed, including solar, chemical, isotopic, and reactor. The current power strategy was an initial outpost power system composed of photovoltaic arrays for daytime energy needs and regenerative fuel cells for power during the long lunar night. As day and night power demands grow, the outpost transitions to nuclear-based power generation, using thermoelectric conversion initially and evolving to a dynamic conversion system. With this concept as a guideline, a set of requirements has been established, and a reference definition of candidate power systems meeting these requirements has been identified.

Satellite Power Systems (SPS) concept definition study, exhibit C. Volume 7: System/subsystem requirements data book

NASA Technical Reports Server (NTRS)

Hanley, G. M.

1979-01-01

Volume 7 of the Satellite Power Systems (SPS) Concept Definition Study final report summarizes the basic requirements used as a guide to systems analysis and is a basis for the selection of candidate SPS point design(s). Initially, these collected data reflected the level of definition resulting from the evaluation of a broad spectrum of SPS concepts. As the various concepts matured these requirements were updated to reflect the requirements identified for the projected satellite system/subsystem point design(s). The identified subsystem/systems requirements are defined, and where appropriate, recommendations for alternate approaches which may represent improved design features are presented. A more detailed discussion of the selected point design(s) will be found in Volume 2 of this report.

Latency in Visionic Systems: Test Methods and Requirements

NASA Technical Reports Server (NTRS)

Bailey, Randall E.; Arthur, J. J., III; Williams, Steven P.; Kramer, Lynda J.

2005-01-01

A visionics device creates a pictorial representation of the external scene for the pilot. The ultimate objective of these systems may be to electronically generate a form of Visual Meteorological Conditions (VMC) to eliminate weather or time-of-day as an operational constraint and provide enhancement over actual visual conditions where eye-limiting resolution may be a limiting factor. Empirical evidence has shown that the total system delays or latencies including the imaging sensors and display systems, can critically degrade their utility, usability, and acceptability. Definitions and measurement techniques are offered herein as common test and evaluation methods for latency testing in visionics device applications. Based upon available data, very different latency requirements are indicated based upon the piloting task, the role in which the visionics device is used in this task, and the characteristics of the visionics cockpit display device including its resolution, field-of-regard, and field-of-view. The least stringent latency requirements will involve Head-Up Display (HUD) applications, where the visionics imagery provides situational information as a supplement to symbology guidance and command information. Conversely, the visionics system latency requirement for a large field-of-view Head-Worn Display application, providing a Virtual-VMC capability from which the pilot will derive visual guidance, will be the most stringent, having a value as low as 20 msec.

Comparison on Human Resource Requirement between Manual and Automated Dispensing Systems.

PubMed

Noparatayaporn, Prapaporn; Sakulbumrungsil, Rungpetch; Thaweethamcharoen, Tanita; Sangseenil, Wunwisa

2017-05-01

This study was conducted to compare human resource requirement among manual, automated, and modified automated dispensing systems. Data were collected from the pharmacy department at the 2100-bed university hospital (Siriraj Hospital, Bangkok, Thailand). Data regarding the duration of the medication distribution process were collected by using self-reported forms for 1 month. The data on the automated dispensing machine (ADM) system were obtained from 1 piloted inpatient ward, whereas those on the manual system were the average of other wards. Data on dispensing, returned unused medication, and stock management processes under the traditional manual system and the ADM system were from actual activities, whereas the modified ADM system was modeled. The full-time equivalent (FTE) of each model was estimated for comparison. The result showed that the manual system required 46.84 FTEs of pharmacists and 132.66 FTEs of pharmacy technicians. By adding pharmacist roles on screening and verification under the ADM system, the ADM system required 117.61 FTEs of pharmacists. Replacing counting and filling medication functions by ADM has decreased the number of pharmacy technicians to 55.38 FTEs. After the modified ADM system canceled the return unused medication process, FTEs requirement for pharmacists and pharmacy technicians decreased to 69.78 and 51.90 FTEs, respectively. The ADM system decreased the workload of pharmacy technicians, whereas it required more time from pharmacists. However, the increased workload of pharmacists was associated with more comprehensive patient care functions, which resulted from the redesigned work process. Copyright © 2017. Published by Elsevier Inc.

Requirements for migration of NSSD code systems from LTSS to NLTSS

NASA Technical Reports Server (NTRS)

Pratt, M.

1984-01-01

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

Tsunami Detection Systems for International Requirements

NASA Astrophysics Data System (ADS)

Lawson, R. A.

2007-12-01

Results are presented regarding the first commercially available, fully operational, tsunami detection system to have passed stringent U.S. government testing requirements and to have successfully demonstrated its ability to detect an actual tsunami at sea. Spurred by the devastation of the December 26, 2004, Indian Ocean tsunami that killed more than 230,000 people, the private sector actively supported the Intergovernmental Oceanographic Commission's (IOC"s) efforts to develop a tsunami warning system and mitigation plan for the Indian Ocean region. As each country in the region developed its requirements, SAIC recognized that many of these underdeveloped countries would need significant technical assistance to fully execute their plans. With the original focus on data fusion, consequence assessment tools, and warning center architecture, it was quickly realized that the cornerstone of any tsunami warning system would be reliable tsunami detection buoys that could meet very stringent operational standards. Our goal was to leverage extensive experience in underwater surveillance and oceanographic sensing to produce an enhanced and reliable deep water sensor that could meet emerging international requirements. Like the NOAA Deep-ocean Assessment and Recording of Tsunamis (DART TM ) buoy, the SAIC Tsunami Buoy (STB) system consists of three subsystems: a surfaccommunications buoy subsystem, a bottom pressure recorder subsystem, and a buoy mooring subsystem. With the operational success that DART has demonstrated, SAIC decided to build and test to the same high standards. The tsunami detection buoy system measures small changes in the depth of the deep ocean caused by tsunami waves as they propagate past the sensor. This is accomplished by using an extremely sensitive bottom pressure sensor/recorder to measure very small changes in pressure as the waves move past the buoy system. The bottom pressure recorder component includes a processor with algorithms that

Formalization of software requirements for information systems using fuzzy logic

NASA Astrophysics Data System (ADS)

Yegorov, Y. S.; Milov, V. R.; Kvasov, A. S.; Sorokoumova, S. N.; Suvorova, O. V.

2018-05-01

The paper considers an approach to the design of information systems based on flexible software development methodologies. The possibility of improving the management of the life cycle of information systems by assessing the functional relationship between requirements and business objectives is described. An approach is proposed to establish the relationship between the degree of achievement of business objectives and the fulfillment of requirements for the projected information system. It describes solutions that allow one to formalize the process of formation of functional and non-functional requirements with the help of fuzzy logic apparatus. The form of the objective function is formed on the basis of expert knowledge and is specified via learning from very small data set.

48 CFR 7.106 - Additional requirements for major systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

.... (b) In planning for the solicitation of a major system (see part 34) production contract, planners... REGULATION ACQUISITION PLANNING ACQUISITION PLANNING Acquisition Plans 7.106 Additional requirements for major systems. (a) In planning for the solicitation of a major system (see part 34) development contract...

48 CFR 7.106 - Additional requirements for major systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

.... (b) In planning for the solicitation of a major system (see part 34) production contract, planners... REGULATION ACQUISITION PLANNING ACQUISITION PLANNING Acquisition Plans 7.106 Additional requirements for major systems. (a) In planning for the solicitation of a major system (see part 34) development contract...

48 CFR 7.106 - Additional requirements for major systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

.... (b) In planning for the solicitation of a major system (see part 34) production contract, planners... REGULATION ACQUISITION PLANNING ACQUISITION PLANNING Acquisition Plans 7.106 Additional requirements for major systems. (a) In planning for the solicitation of a major system (see part 34) development contract...

48 CFR 7.106 - Additional requirements for major systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

.... (b) In planning for the solicitation of a major system (see part 34) production contract, planners... REGULATION ACQUISITION PLANNING ACQUISITION PLANNING Acquisition Plans 7.106 Additional requirements for major systems. (a) In planning for the solicitation of a major system (see part 34) development contract...

48 CFR 7.106 - Additional requirements for major systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

.... (b) In planning for the solicitation of a major system (see part 34) production contract, planners... REGULATION ACQUISITION PLANNING ACQUISITION PLANNING Acquisition Plans 7.106 Additional requirements for major systems. (a) In planning for the solicitation of a major system (see part 34) development contract...

Information security requirements in patient-centred healthcare support systems.

PubMed

Alsalamah, Shada; Gray, W Alex; Hilton, Jeremy; Alsalamah, Hessah

2013-01-01

Enabling Patient-Centred (PC) care in modern healthcare requires the flow of medical information with the patient between different healthcare providers as they follow the patient's treatment plan. However, PC care threatens the stability of the balance of information security in the support systems since legacy systems fall short of attaining a security balance when sharing their information due to compromises made between its availability, integrity, and confidentiality. Results show that the main reason for this is that information security implementation in discrete legacy systems focused mainly on information confidentiality and integrity leaving availability a challenge in collaboration. Through an empirical study using domain analysis, observations, and interviews, this paper identifies a need for six information security requirements in legacy systems to cope with this situation in order to attain the security balance in systems supporting PC care implementation in modern healthcare.

Exploring Propulsion System Requirements for More and All-Electric Helicopters

NASA Technical Reports Server (NTRS)

Snyder, Christopher A.

2015-01-01

Helicopters offer unique capabilities that are important for certain missions. More and all-electric propulsion systems for helicopters offer the potential for improved efficiency, reliability, vehicle and mission capabilities as well as reduced harmful emissions. To achieve these propulsion system-based benefits, the relevant requirements must be understood and developed for the various component, sub-component and ancillary systems of the overall propulsion system. Three representative helicopters were used to explore propulsion and overall vehicle and mission requirements. These vehicles varied from light utility (one to three occupants) to highly capable (three crew members plus ten passengers and cargo). Assuming 15 and 30 year technology availability, analytical models for electric system components were developed to understand component and ancillary requirements. Overall propulsion system characteristics were developed and used for vehicle sizing and mission analyses to understand the tradeoffs of component performance and weight, with increase in vehicle size and mission capability. Study results indicate that only the light utility vehicle retained significant payload for an arbitrary 100 nautical mile range assuming 15 year technology. Thirty year technology assumptions for battery energy storage are sufficient to enable some range and payload capabilities, but further improvements in energy density are required to maintain or exceed payload and range capabilities versus present systems. Hydrocarbon-fueled range extenders can be prudently used to recover range and payload deficiencies resulting from battery energy density limitations. Thermal loads for electric systems are low heat quality, but seem manageable. To realize the benefits from more and all-electric systems, technology goals must be achieved, as well as vehicles, missions and systems identified that are best suited to take advantage of their unique characteristics.

Exploring Propulsion System Requirements for More and All-Electric Helicopters

NASA Technical Reports Server (NTRS)

Snyder, Christopher A.

2015-01-01

Helicopters offer unique capabilities that are important for certain missions. More and all-electric propulsion systems for helicopters offer the potential for improved efficiency, reliability, vehicle and mission capabilities as well as reduced harmful emissions. To achieve these propulsion system-based benefits, the relevant requirements must be understood and developed for the various component, sub-component and ancillary systems of the overall propulsion system. Three representative helicopters were used to explore propulsion and overall vehicle and mission requirements. These vehicles varied from light utility (one to three occupants) to highly capable (three crew members plus ten passengers and cargo). Assuming 15 and 30 year technology availability, analytical models for electric system components were developed to understand component and ancillary requirements. Overall propulsion system characteristics were developed and used for vehicle sizing and mission analyses to understand the tradeoffs of component performance and weight, with increase in vehicle size and mission capability. Study results indicate that only the light utility vehicle retained significant payload for an arbitrary 100 nautical mile range assuming 15 year technology. Thirty year technology assumptions for battery energy storage are sufficient to enable some range and payload capabilities, but further improvements in energy density are required to maintain or exceed payload and range capabilities versus present systems. Hydrocarbon-fueled range extenders can be prudently used to recover range and payload deficiencies resulting from battery energy density limitations. Thermal loads for electric systems are low heat quality, but seem manageable. To realize the benefits from more and all-electric systems, technology goals must be achieved, as well as identify vehicles, missions and systems that are best suited to take advantage of their unique characteristics.

40 CFR 63.1085 - What are the general requirements for heat exchange systems?

Code of Federal Regulations, 2011 CFR

2011-07-01

... heat exchange systems? 63.1085 Section 63.1085 Protection of Environment ENVIRONMENTAL PROTECTION... Exchange Systems and Waste Operations Heat Exchange System Requirements § 63.1085 What are the general requirements for heat exchange systems? Unless you meet one of the requirements for exemptions in § 63.1084...

40 CFR 63.1085 - What are the general requirements for heat exchange systems?

Code of Federal Regulations, 2013 CFR

2013-07-01

... heat exchange systems? 63.1085 Section 63.1085 Protection of Environment ENVIRONMENTAL PROTECTION... Exchange Systems and Waste Operations Heat Exchange System Requirements § 63.1085 What are the general requirements for heat exchange systems? Unless you meet one of the requirements for exemptions in § 63.1084...

40 CFR 63.1085 - What are the general requirements for heat exchange systems?

Code of Federal Regulations, 2014 CFR

2014-07-01

... heat exchange systems? 63.1085 Section 63.1085 Protection of Environment ENVIRONMENTAL PROTECTION... Exchange Systems and Waste Operations Heat Exchange System Requirements § 63.1085 What are the general requirements for heat exchange systems? Unless you meet one of the requirements for exemptions in § 63.1084...

40 CFR 63.1085 - What are the general requirements for heat exchange systems?

Code of Federal Regulations, 2012 CFR

2012-07-01

... heat exchange systems? 63.1085 Section 63.1085 Protection of Environment ENVIRONMENTAL PROTECTION... Exchange Systems and Waste Operations Heat Exchange System Requirements § 63.1085 What are the general requirements for heat exchange systems? Unless you meet one of the requirements for exemptions in § 63.1084...

Defense Logistics Standard Systems Functional Requirements.

DTIC Science & Technology

1987-03-01

Artificial Intelligence - the development of a machine capability to perform functions normally concerned with human intelligence, such as learning , adapting...Basic Data Base Machine Configurations .... ......... D- 18 xx ~ ?f~~~vX PART I: MODELS - DEFENSE LOGISTICS STANDARD SYSTEMS FUNCTIONAL REQUIREMENTS...On-line, Interactive Access. Integrating user input and machine output in a dynamic, real-time, give-and- take process is considered the optimum mode

Technology requirements for a generic aerocapture system. [for atmospheric entry

NASA Technical Reports Server (NTRS)

Cruz, M. I.

1980-01-01

The technology requirements for the design of a generic aerocapture vehicle system are summarized. These spacecraft have the capability of completely eliminating fuel-costly retropropulsion for planetary orbit capture through a single aerodynamically controlled atmospheric braking pass from a hyperbolic trajectory into a near circular orbit. This generic system has application at both the inner and outer planets. Spacecraft design integration, navigation, communications, and aerothermal protection system design problems were assessed in the technology requirements study and are discussed in this paper.

17 CFR 242.301 - Requirements for alternative trading systems.

Code of Federal Regulations, 2014 CFR

2014-04-01

... 17 Commodity and Securities Exchanges 4 2014-04-01 2014-04-01 false Requirements for alternative trading systems. 242.301 Section 242.301 Commodity and Securities Exchanges SECURITIES AND EXCHANGE COMMISSION (CONTINUED) REGULATIONS M, SHO, ATS, AC, AND NMS AND CUSTOMER MARGIN REQUIREMENTS FOR SECURITY...

17 CFR 242.301 - Requirements for alternative trading systems.

Code of Federal Regulations, 2012 CFR

2012-04-01

... 17 Commodity and Securities Exchanges 3 2012-04-01 2012-04-01 false Requirements for alternative trading systems. 242.301 Section 242.301 Commodity and Securities Exchanges SECURITIES AND EXCHANGE COMMISSION (CONTINUED) REGULATIONS M, SHO, ATS, AC, AND NMS AND CUSTOMER MARGIN REQUIREMENTS FOR SECURITY...

17 CFR 242.301 - Requirements for alternative trading systems.

Code of Federal Regulations, 2013 CFR

2013-04-01

... 17 Commodity and Securities Exchanges 3 2013-04-01 2013-04-01 false Requirements for alternative trading systems. 242.301 Section 242.301 Commodity and Securities Exchanges SECURITIES AND EXCHANGE COMMISSION (CONTINUED) REGULATIONS M, SHO, ATS, AC, AND NMS AND CUSTOMER MARGIN REQUIREMENTS FOR SECURITY...

17 CFR 242.301 - Requirements for alternative trading systems.

Code of Federal Regulations, 2011 CFR

2011-04-01

... 17 Commodity and Securities Exchanges 3 2011-04-01 2011-04-01 false Requirements for alternative trading systems. 242.301 Section 242.301 Commodity and Securities Exchanges SECURITIES AND EXCHANGE COMMISSION (CONTINUED) REGULATIONS M, SHO, ATS, AC, AND NMS AND CUSTOMER MARGIN REQUIREMENTS FOR SECURITY...

Connecting Requirements to Architecture and Analysis via Model-Based Systems Engineering

NASA Technical Reports Server (NTRS)

Cole, Bjorn F.; Jenkins, J. Steven

2015-01-01

In traditional systems engineering practice, architecture, concept development, and requirements development are related but still separate activities. Concepts for operation, key technical approaches, and related proofs of concept are developed. These inform the formulation of an architecture at multiple levels, starting with the overall system composition and functionality and progressing into more detail. As this formulation is done, a parallel activity develops a set of English statements that constrain solutions. These requirements are often called "shall statements" since they are formulated to use "shall." The separation of requirements from design is exacerbated by well-meaning tools like the Dynamic Object-Oriented Requirements System (DOORS) that remained separated from engineering design tools. With the Europa Clipper project, efforts are being taken to change the requirements development approach from a separate activity to one intimately embedded in formulation effort. This paper presents a modeling approach and related tooling to generate English requirement statements from constraints embedded in architecture definition.

Validating a biometric authentication system: sample size requirements.

PubMed

Dass, Sarat C; Zhu, Yongfang; Jain, Anil K

2006-12-01

Authentication systems based on biometric features (e.g., fingerprint impressions, iris scans, human face images, etc.) are increasingly gaining widespread use and popularity. Often, vendors and owners of these commercial biometric systems claim impressive performance that is estimated based on some proprietary data. In such situations, there is a need to independently validate the claimed performance levels. System performance is typically evaluated by collecting biometric templates from n different subjects, and for convenience, acquiring multiple instances of the biometric for each of the n subjects. Very little work has been done in 1) constructing confidence regions based on the ROC curve for validating the claimed performance levels and 2) determining the required number of biometric samples needed to establish confidence regions of prespecified width for the ROC curve. To simplify the analysis that address these two problems, several previous studies have assumed that multiple acquisitions of the biometric entity are statistically independent. This assumption is too restrictive and is generally not valid. We have developed a validation technique based on multivariate copula models for correlated biometric acquisitions. Based on the same model, we also determine the minimum number of samples required to achieve confidence bands of desired width for the ROC curve. We illustrate the estimation of the confidence bands as well as the required number of biometric samples using a fingerprint matching system that is applied on samples collected from a small population.

Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts.

PubMed

Shah, Hemant; Allard, Raymond D; Enberg, Robert; Krishnan, Ganesh; Williams, Patricia; Nadkarni, Prakash M

2012-03-09

A large body of work in the clinical guidelines field has identified requirements for guideline systems, but there are formidable challenges in translating such requirements into production-quality systems that can be used in routine patient care. Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable. Further, additional requirements emerge as a result of such analysis. During such an analysis, study of examples of existing, software-engineering efforts in non-biomedical fields can provide useful signposts to the implementer of a clinical guideline system. In addition to requirements described by guideline-system authors, comparative reviews of such systems, and publications discussing information needs for guideline systems and clinical decision support systems in general, we have incorporated additional requirements related to production-system robustness and functionality from publications in the business workflow domain, in addition to drawing on our own experience in the development of the Proteus guideline system (http://proteme.org). The sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008. We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context. When analyzing requirements from the implementation viewpoint, knowledge of successes and failures in related software-engineering efforts can guide implementers in the choice of effective design and development strategies.

Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts

PubMed Central

2012-01-01

Background A large body of work in the clinical guidelines field has identified requirements for guideline systems, but there are formidable challenges in translating such requirements into production-quality systems that can be used in routine patient care. Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable. Further, additional requirements emerge as a result of such analysis. During such an analysis, study of examples of existing, software-engineering efforts in non-biomedical fields can provide useful signposts to the implementer of a clinical guideline system. Methods In addition to requirements described by guideline-system authors, comparative reviews of such systems, and publications discussing information needs for guideline systems and clinical decision support systems in general, we have incorporated additional requirements related to production-system robustness and functionality from publications in the business workflow domain, in addition to drawing on our own experience in the development of the Proteus guideline system (http://proteme.org). Results The sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008. We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context. Conclusions When analyzing requirements from the implementation viewpoint, knowledge of successes and failures in related software-engineering efforts can guide implementers in the choice of effective design and development strategies. PMID:22405400

L-Band System Engineering - Concepts of Use, Systems Performance Requirements, and Architecture

NASA Technical Reports Server (NTRS)

Henriksen, Stephen; Zelkin, Natalie

2011-01-01

This document is being provided as part of ITT s NASA Glenn Research Center Aerospace Communication Systems Technical Support (ACSTS) contract NNC05CA85C, Task 7: New ATM Requirements-Future Communications, C-band and L-band Communications Standard Development. Task 7 was motivated by the five year technology assessment performed for the Federal Aviation Administration (FAA) under the joint FAA-EUROCONTROL cooperative research Action Plan (AP-17), also known as the Future Communications Study (FCS). It was based on direction provided by the FAA project-level agreement (PLA FY09_G1M.02-02v1) for "New ATM Requirements-Future Communications." Task 7 was separated into two distinct subtasks, each aligned with specific work elements and deliverable items. Subtask 7-1 addressed C-band airport surface data communications standards development, systems engineering, test bed development, and tests/demonstrations to establish operational capability for what is now referred to as the Aeronautical Mobile Airport Communications System (AeroMACS). Subtask 7-2, which is the subject of this report, focused on preliminary systems engineering and support of joint FAA/EUROCONTROL development and evaluation of a future L-band (960 to 1164 MHz) air/ground (A/G) communication system known as the L-band digital aeronautical communications system (L-DACS), which was defined during the FCS. The proposed L-DACS will be capable of providing ATM services in continental airspace in the 2020+ timeframe. Subtask 7-2 was performed in two phases. Phase I featured development of Concepts of Use, high level functional analyses, performance of initial L-band system safety and security risk assessments, and development of high level requirements and architectures. It also included the aforementioned support of joint L-DACS development and evaluation, including inputs to L-DACS design specifications. Phase II provided a refinement of the systems engineering activities performed during Phase I, along

Flight software requirements and design support system

NASA Technical Reports Server (NTRS)

Riddle, W. E.; Edwards, B.

1980-01-01

The desirability and feasibility of computer-augmented support for the pre-implementation activities occurring during the development of flight control software was investigated. The specific topics to be investigated were the capabilities to be included in a pre-implementation support system for flight control software system development, and the specification of a preliminary design for such a system. Further, the pre-implementation support system was to be characterized and specified under the constraints that it: (1) support both description and assessment of flight control software requirements definitions and design specification; (2) account for known software description and assessment techniques; (3) be compatible with existing and planned NASA flight control software development support system; and (4) does not impose, but may encourage, specific development technologies. An overview of the results is given.

Design requirements for SRB production control system. Volume 1: Study background and overview

NASA Technical Reports Server (NTRS)

1981-01-01

The solid rocket boosters assembly environment is described in terms of the contraints it places upon an automated production control system. The business system generated for the SRB assembly and the computer system which meets the business system requirements are described. The selection software process and modifications required to the recommended software are addressed as well as the hardware and configuration requirements necessary to support the system.

The study on knowledge transferring incentive for information system requirement development

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

Li, Yang

2015-03-10

Information system requirement development is a process of users’ knowledge sharing and transferring. However the tacit requirements developing is a main problem during requirement development process, for the reason of difficult to encoding, express, and communicate. Knowledge fusion and corporate effort is needed to finding tacit requirements. Under this background, our paper try to find out the rule of effort dynamic evolutionary of software developer and user by building an evolutionary game model on the condition of incentive system. And in addition this paper provides an in depth discussion at the end of this paper.

Advanced solar dynamic space power systems perspectives, requirements and technology needs

NASA Technical Reports Server (NTRS)

Dustin, M. O.; Savino, J. M.; Lacy, D. E.; Migra, R. P.; Juhasz, A. J.; Coles, C. E.

1986-01-01

Projected NASA, Civil, Commercial, and Military missions will require space power systems of increased versatility and power levels. The Advanced Solar Dynamic (ASD) Power systems offer the potential for efficient, lightweight, survivable, relatively compact, long-lived space power systems applicable to a wide range of power levels (3 to 300 kWe), and a wide variety of orbits. The successful development of these systems could satisfy the power needs for a wide variety of these projected missions. Thus, the NASA Lewis Research Center has embarked upon an aggressive ASD reserach project under the direction of NASA's Office of Aeronautics and Space Technology (DAST). The project is being implemented through a combination of in-house and contracted efforts. Key elements of this project are missions analysis to determine the power systems requirements, systems analysis to identify the most attractive ASD power systems to meet these requirements, and to guide the technology development efforts, and technology development of key components.

Human Systems Integration: Requirements and Functional Decomposition

NASA Technical Reports Server (NTRS)

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.

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

NASA Astrophysics Data System (ADS)

Maksimov, Andrey

2010-08-01

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

40 CFR 141.560 - Is my system subject to individual filter turbidity requirements?

Code of Federal Regulations, 2013 CFR

2013-07-01

... filter turbidity requirements? 141.560 Section 141.560 Protection of Environment ENVIRONMENTAL PROTECTION... Filtration and Disinfection-Systems Serving Fewer Than 10,000 People Individual Filter Turbidity Requirements § 141.560 Is my system subject to individual filter turbidity requirements? If your system is a subpart...

40 CFR 141.560 - Is my system subject to individual filter turbidity requirements?

Code of Federal Regulations, 2010 CFR

2010-07-01

... filter turbidity requirements? 141.560 Section 141.560 Protection of Environment ENVIRONMENTAL PROTECTION... Filtration and Disinfection-Systems Serving Fewer Than 10,000 People Individual Filter Turbidity Requirements § 141.560 Is my system subject to individual filter turbidity requirements? If your system is a subpart...

40 CFR 141.560 - Is my system subject to individual filter turbidity requirements?

Code of Federal Regulations, 2012 CFR

2012-07-01

... filter turbidity requirements? 141.560 Section 141.560 Protection of Environment ENVIRONMENTAL PROTECTION... Filtration and Disinfection-Systems Serving Fewer Than 10,000 People Individual Filter Turbidity Requirements § 141.560 Is my system subject to individual filter turbidity requirements? If your system is a subpart...

40 CFR 141.560 - Is my system subject to individual filter turbidity requirements?

Code of Federal Regulations, 2011 CFR

2011-07-01

... filter turbidity requirements? 141.560 Section 141.560 Protection of Environment ENVIRONMENTAL PROTECTION... Filtration and Disinfection-Systems Serving Fewer Than 10,000 People Individual Filter Turbidity Requirements § 141.560 Is my system subject to individual filter turbidity requirements? If your system is a subpart...

40 CFR 141.560 - Is my system subject to individual filter turbidity requirements?

Code of Federal Regulations, 2014 CFR

2014-07-01

... filter turbidity requirements? 141.560 Section 141.560 Protection of Environment ENVIRONMENTAL PROTECTION... Filtration and Disinfection-Systems Serving Fewer Than 10,000 People Individual Filter Turbidity Requirements § 141.560 Is my system subject to individual filter turbidity requirements? If your system is a subpart...

Dynamic least-cost optimisation of wastewater system remedial works requirements.

PubMed

Vojinovic, Z; Solomatine, D; Price, R K

2006-01-01

In recent years, there has been increasing concern for wastewater system failure and identification of optimal set of remedial works requirements. So far, several methodologies have been developed and applied in asset management activities by various water companies worldwide, but often with limited success. In order to fill the gap, there are several research projects that have been undertaken in exploring various algorithms to optimise remedial works requirements, but mostly for drinking water supply systems, and very limited work has been carried out for the wastewater assets. Some of the major deficiencies of commonly used methods can be found in either one or more of the following aspects: inadequate representation of systems complexity, incorporation of a dynamic model into the decision-making loop, the choice of an appropriate optimisation technique and experience in applying that technique. This paper is oriented towards resolving these issues and discusses a new approach for the optimisation of wastewater systems remedial works requirements. It is proposed that the optimal problem search is performed by a global optimisation tool (with various random search algorithms) and the system performance is simulated by the hydrodynamic pipe network model. The work on assembling all required elements and the development of an appropriate interface protocols between the two tools, aimed to decode the potential remedial solutions into the pipe network model and to calculate the corresponding scenario costs, is currently underway.

Nursing Information Systems Requirements: A Milestone for Patient Outcome and Patient Safety Improvement.

PubMed

Farzandipour, Mehrdad; Meidani, Zahra; Riazi, Hossein; Sadeqi Jabali, Monireh

2016-12-01

Considering the integral role of understanding users' requirements in information system success, this research aimed to determine functional requirements of nursing information systems through a national survey. Delphi technique method was applied to conduct this study through three phases: focus group method modified Delphi technique and classic Delphi technique. A cross-sectional study was conducted to evaluate the proposed requirements within 15 general hospitals in Iran. Forty-three of 76 approved requirements were clinical, and 33 were administrative ones. Nurses' mean agreements for clinical requirements were higher than those of administrative requirements; minimum and maximum means of clinical requirements were 3.3 and 3.88, respectively. Minimum and maximum means of administrative requirements were 3.1 and 3.47, respectively. Research findings indicated that those information system requirements that support nurses in doing tasks including direct care, medicine prescription, patient treatment management, and patient safety have been the target of special attention. As nurses' requirements deal directly with patient outcome and patient safety, nursing information systems requirements should not only address automation but also nurses' tasks and work processes based on work analysis.

The Requirement Generation for the SKYLON Launch System

NASA Astrophysics Data System (ADS)

Hempsell, M.

SKYLON is a reusable single stage to orbit spaceplane intended to lower the cost of reaching space. The project has a 25 year history stretching back to the British Aerospace HOTOL study and over the many configuration iterations the performance has been established using feasibility designs, with market studies being used to establish that the resulting system has utility. In preparation for the final concept study of the D1 configuration the market and other stakeholder's requirements have been prepared as an input rather than an output to the design process. These requirements have been established from both an analysis of the existing market - as a model for the entry into service requirements - and future studies of advanced applications - as a model for the longer term requirements. The final conclusions have been incorporated into a preliminary User Manual which is the basis of a requirements' validation exercise.

Study of data collection platform concepts: Data collection system user requirements

NASA Technical Reports Server (NTRS)

1973-01-01

The overall purpose of the survey was to provide real world data on user requirements. The intent was to assess data collection system user requirements by questioning actual potential users rather than speculating on requirements. The end results of the survey are baseline requirements models for both a data collection platform and a data collection system. These models were derived from the survey results. The real value of these models lies in the fact that they are based on actual user requirements as delineated in the survey questionnaires. Some users desire data collection platforms of small size and light weight. These sizes and weights are beyond the present state of the art. Also, the survey provided a wealth of information on the nature and constituency of the data collection user community as well as information on user applications for data collection systems. Finally, the data sheds light on the generalized platform concept. That is, the diversity of user requirements shown in the data indicates the difficulty that can be anticipated in attempting to implement such a concept.

31 CFR 1.22 - Requirements relating to systems of records.

Code of Federal Regulations, 2010 CFR

2010-07-01

... 31 Money and Finance: Treasury 1 2010-07-01 2010-07-01 false Requirements relating to systems of records. 1.22 Section 1.22 Money and Finance: Treasury Office of the Secretary of the Treasury DISCLOSURE OF RECORDS Privacy Act § 1.22 Requirements relating to systems of records. (a) In general. Subject to 5 U.S.C. 552a (j) and (k) and § 1.23(c),...

Developing IVHM Requirements for Aerospace Systems

NASA Technical Reports Server (NTRS)

Rajamani, Ravi; Saxena, Abhinav; Kramer, Frank; Augustin, Mike; Schroeder, John B.; Goebel, Kai; Shao, Ginger; Roychoudhury, Indranil; Lin, Wei

2013-01-01

The term Integrated Vehicle Health Management (IVHM) describes a set of capabilities that enable sustainable and safe operation of components and subsystems within aerospace platforms. However, very little guidance exists for the systems engineering aspects of design with IVHM in mind. It is probably because of this that designers have to use knowledge picked up exclusively by experience rather than by established process. This motivated a group of leading IVHM practitioners within the aerospace industry under the aegis of SAE's HM-1 technical committee to author a document that hopes to give working engineers and program managers clear guidance on all the elements of IVHM that they need to consider before designing a system. This proposed recommended practice (ARP6883 [1]) will describe all the steps of requirements generation and management as it applies to IVHM systems, and demonstrate these with a "real-world" example related to designing a landing gear system. The team hopes that this paper and presentation will help start a dialog with the larger aerospace community and that the feedback can be used to improve the ARP and subsequently the practice of IVHM from a systems engineering point-of-view.

Ecstasy: It's the Rave

ERIC Educational Resources Information Center

Dennis, Dixie; Ballard, Michael

2002-01-01

National statistics reveal an alarming trend concerning the use of 3,4-methylenedioxymethamphetamine, which is better known as ecstasy. Results from the Monitoring the Future survey of 50,000 secondary youth reveal that use among 8th graders rose to 3.1%, 5.4% among 10th graders, and 8.2% among 12th graders. High school faculty and staff must be…

Propulsion element requirements using electrical power system unscheduled power

NASA Technical Reports Server (NTRS)

Zimmermann, Frank; Hodge, Kathy

1989-01-01

The suitability of using the electrical energy from the Space Station's Electrical Power System (EPS) during the periods of peak solar insolation which is currently not specifically allocated (unscheduled power) to produce propulsion propellants, gaseous hydrogen, and oxygen by electrolyzing water is investigated. Reboost propellant requirements are emphasized, but the results are more generally relevant because the balance of recurring propellant requirements are an order of magnitude smaller and the nonrecurring requirements are not significant on an average basis.

Onboard shuttle on-line software requirements system: Prototype

NASA Technical Reports Server (NTRS)

Kolkhorst, Barbara; Ogletree, Barry

1989-01-01

The prototype discussed here was developed as proof of a concept for a system which could support high volumes of requirements documents with integrated text and graphics; the solution proposed here could be extended to other projects whose goal is to place paper documents in an electronic system for viewing and printing purposes. The technical problems (such as conversion of documentation between word processors, management of a variety of graphics file formats, and difficulties involved in scanning integrated text and graphics) would be very similar for other systems of this type. Indeed, technological advances in areas such as scanning hardware and software and display terminals insure that some of the problems encountered here will be solved in the near-term (less than five years). Examples of these solvable problems include automated input of integrated text and graphics, errors in the recognition process, and the loss of image information which results from the digitization process. The solution developed for the Online Software Requirements System is modular and allows hardware and software components to be upgraded or replaced as industry solutions mature. The extensive commercial software content allows the NASA customer to apply resources to solving the problem and maintaining documents.

Concepts, requirements, and design approaches for building successful planning and scheduling systems

NASA Technical Reports Server (NTRS)

Hornstein, Rhoda Shaller; Willoughby, John K.

1991-01-01

Traditional practice of systems engineering management assumes requirements can be precisely determined and unambiguously defined prior to system design and implementation; practice further assumes requirements are held static during implementation. Human-computer decision support systems for service planning and scheduling applications do not conform well to these assumptions. Adaptation to the traditional practice of systems engineering management are required. Basic technology exists to support these adaptations. Additional innovations must be encouraged and nutured. Continued partnership between the programmatic and technical perspective assures proper balance of the impossible with the possible. Past problems have the following origins: not recognizing the unusual and perverse nature of the requirements for planning and scheduling; not recognizing the best starting point assumptions for the design; not understanding the type of system that being built; and not understanding the design consequences of the operations concept selected.

Microwave Landing System signal requirements for conventional aircraft

DOT National Transportation Integrated Search

1972-07-01

The results of analysis directed towards determining Microwave Landing System (MLS) signal requirements for conventional aircraft are discussed. The phases of flight considered include straight-in final approach, flareout, and rollout. A limited numb...

System Modeling of Lunar Oxygen Production: Mass and Power Requirements

NASA Technical Reports Server (NTRS)

Steffen, Christopher J.; Freeh, Joshua E.; Linne, Diane L.; Faykus, Eric W.; Gallo, Christopher A.; Green, Robert D.

2007-01-01

A systems analysis tool for estimating the mass and power requirements for a lunar oxygen production facility is introduced. The individual modeling components involve the chemical processing and cryogenic storage subsystems needed to process a beneficiated regolith stream into liquid oxygen via ilmenite reduction. The power can be supplied from one of six different fission reactor-converter systems. A baseline system analysis, capable of producing 15 metric tons of oxygen per annum, is presented. The influence of reactor-converter choice was seen to have a small but measurable impact on the system configuration and performance. Finally, the mission concept of operations can have a substantial impact upon individual component size and power requirements.

47 CFR 90.691 - Emission mask requirements for EA-based systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 5 2010-10-01 2010-10-01 false Emission mask requirements for EA-based systems. 90.691 Section 90.691 Telecommunication FEDERAL COMMUNICATIONS COMMISSION (CONTINUED) SAFETY AND... of Ea-Based Smr Systems in the 809-824/851-869 Mhz Band § 90.691 Emission mask requirements for EA...

Unmanned Aircraft System Control and ATC Communications Bandwidth Requirements

NASA Technical Reports Server (NTRS)

Henriksen, Steve

2008-01-01

There are significant activities taking place to establish the procedures and requirements for safe and routine operation of unmanned aircraft systems (UAS) in the National Airspace System (NAS). Among the barriers to overcome in achieving this goal is the lack of sufficient frequency spectrum necessary for the UAS control and air traffic control (ATC) communications links. This shortcoming is compounded by the fact that the UAS control communications links will likely be required to operate in protected frequency spectrum, just as ATC communications links are, because they relate to "safety and regularity of flight." To support future International Telecommunications Union (ITU) World Radio Conference (WRC) agenda items concerning new frequency allocations for UAS communications links, and to augment the Future Communications Study (FCS) Technology Evaluation Group efforts, NASA Glenn Research Center has sponsored a task to estimate the UAS control and ATC communications bandwidth requirements for safe, reliable, and routine operation of UAS in the NAS. This report describes the process and results of that task. The study focused on long-term bandwidth requirements for UAS approximately through 2030.

Ground Systems Development Environment (GSDE) interface requirements and prototyping plan

NASA Technical Reports Server (NTRS)

Church, Victor E.; Philips, John; Bassman, Mitchell; Williams, C.

1990-01-01

This report describes the data collection and requirements analysis effort of the Ground System Development Environment (GSDE) Interface Requirements study. It identifies potential problems in the interfaces among applications and processors in the heterogeneous systems that comprises the GSDE. It describes possible strategies for addressing those problems. It also identifies areas for further research and prototyping to demonstrate the capabilities and feasibility of those strategies and defines a plan for building the necessary software prototypes.

Enabling Requirements-Based Programming for Highly-Dependable Complex Parallel and Distributed Systems

NASA Technical Reports Server (NTRS)

Hinchey, Michael G.; Rash, James L.; Rouff, Christopher A.

2005-01-01

The manual application of formal methods in system specification has produced successes, but in the end, despite any claims and assertions by practitioners, there is no provable relationship between a manually derived system specification or formal model and the customer's original requirements. Complex parallel and distributed system present the worst case implications for today s dearth of viable approaches for achieving system dependability. No avenue other than formal methods constitutes a serious contender for resolving the problem, and so recognition of requirements-based programming has come at a critical juncture. We describe a new, NASA-developed automated requirement-based programming method that can be applied to certain classes of systems, including complex parallel and distributed systems, to achieve a high degree of dependability.

46 CFR 167.45-45 - Carbon dioxide fire extinguishing system requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 7 2012-10-01 2012-10-01 false Carbon dioxide fire extinguishing system requirements. 167.45-45 Section 167.45-45 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) NAUTICAL SCHOOLS PUBLIC NAUTICAL SCHOOL SHIPS Special Firefighting and Fire Prevention Requirements § 167.45-45 Carbon dioxide fire extinguishing system...

46 CFR 167.45-45 - Carbon dioxide fire extinguishing system requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 7 2013-10-01 2013-10-01 false Carbon dioxide fire extinguishing system requirements. 167.45-45 Section 167.45-45 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) NAUTICAL SCHOOLS PUBLIC NAUTICAL SCHOOL SHIPS Special Firefighting and Fire Prevention Requirements § 167.45-45 Carbon dioxide fire extinguishing system...

46 CFR 167.45-45 - Carbon dioxide fire extinguishing system requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 7 2014-10-01 2014-10-01 false Carbon dioxide fire extinguishing system requirements. 167.45-45 Section 167.45-45 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) NAUTICAL SCHOOLS PUBLIC NAUTICAL SCHOOL SHIPS Special Firefighting and Fire Prevention Requirements § 167.45-45 Carbon dioxide fire extinguishing system...

Man-systems requirements for the control of teleoperators in space

NASA Technical Reports Server (NTRS)

Shields, Nicholas L., Jr.

1988-01-01

The microgravity of the space environment has profound effects on humans and, consequently, on the design requirements for subsystems and components with which humans interact. There are changes in the anthropometry, vision, the perception of orientation, posture, and the ways in which we exert energy. The design requirements for proper human engineering must reflect each of the changes that results, and this is especially true in the exercise of control over remote and teleoperated systems where the operator is removed from any direct sense of control. The National Aeronautics and Space Administration has recently completed the first NASA-wide human factors standard for microgravity. The Man-Systems Integration Standard, NASA-STD-3000, contains considerable information on the appropriate design criteria for microgravity, and there is information that is useful in the design for teleoperated systems. There is not, however, a dedicated collection of data which pertains directly to the special cases of remote and robotic operations. The design considerations for human-system interaction in the control of remote systems in space are discussed, with brief details on the information to be found in the NASA-STD-3000, and arguments for a dedicated section within the Standard which deals with robotic, teleoperated and remote systems and the design requirements for effective human control of these systems in the space environment, and from the space environment.

Cleared for Launch - Lessons Learned from the OSIRIS-REx System Requirements Verification Program

NASA Technical Reports Server (NTRS)

Stevens, Craig; Adams, Angela; Williams, Bradley; Goodloe, Colby

2017-01-01

Requirements verification of a large flight system is a challenge. It is especially challenging for engineers taking on their first role in space systems engineering. This paper describes our approach to verification of the Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) system requirements. It also captures lessons learned along the way from developing systems engineers embroiled in this process. We begin with an overview of the mission and science objectives as well as the project requirements verification program strategy. A description of the requirements flow down is presented including our implementation for managing the thousands of program and element level requirements and associated verification data. We discuss both successes and methods to improve the managing of this data across multiple organizational interfaces. Our approach to verifying system requirements at multiple levels of assembly is presented using examples from our work at instrument, spacecraft, and ground segment levels. We include a discussion of system end-to-end testing limitations and their impacts to the verification program. Finally, we describe lessons learned that are applicable to all emerging space systems engineers using our unique perspectives across multiple organizations of a large NASA program.

Step 1: Human System Interface (HSI) Functional Requirements Document (FRD). Version 2

NASA Technical Reports Server (NTRS)

2006-01-01

This Functional Requirements Document (FRD) establishes a minimum set of Human System Interface (HSI) functional requirements to achieve the Access 5 Vision of "operating High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) routinely, safely, and reliably in the National Airspace System (NAS)". Basically, it provides what functions are necessary to fly UAS in the NAS. The framework used to identify the appropriate functions was the "Aviate, Navigate, Communicate, and Avoid Hazards" structure identified in the Access 5 FRD. As a result, fifteen high-level functional requirements were developed. In addition, several of them have been decomposed into low-level functional requirements to provide more detail.

System requirements for a computerised patient record information system at a busy primary health care clinic.

PubMed

Blignaut, P J; McDonald, T; Tolmie, C J

2001-05-01

A prototyping approach was used to determine the essential system requirements of a computerised patient record information system for a typical township primary health care clinic. A pilot clinic was identified and the existing manual system and business processes in this clinic was studied intensively before the first prototype was implemented. Interviews with users, incidental observations and analysis of actual data entered were used as primary techniques to refine the prototype system iteratively until a system with an acceptable data set and adequate functionalities were in place. Several non-functional and user-related requirements were also discovered during the prototyping period.

Generic waste management requirements for a controlled ecological life support system /CELSS/

NASA Technical Reports Server (NTRS)

Hoshizaki, T.; Hansen, B. D., III

1981-01-01

Regenerative life support systems for future space missions will require closure of the waste-food loop. Each mission application will generate specific requirements for the waste management system. However, there are generic input and output requirements that can be identified when a probable scenario is chosen. This paper discusses the generic requirements when higher plants are chosen as the primary food source. Attention is focused on the quality and quantity of nutrients necessary for culturing higher plants. The types of wastes to be processed are also discussed. In addition, requirements generated by growing plants on three different substrates are presented. This work suggests that the mineral composition of waste materials may require minimal adjustment to satisfy the plant requirements.

Fusing Quantitative Requirements Analysis with Model-based Systems Engineering

NASA Technical Reports Server (NTRS)

Cornford, Steven L.; Feather, Martin S.; Heron, Vance A.; Jenkins, J. Steven

2006-01-01

A vision is presented for fusing quantitative requirements analysis with model-based systems engineering. This vision draws upon and combines emergent themes in the engineering milieu. "Requirements engineering" provides means to explicitly represent requirements (both functional and non-functional) as constraints and preferences on acceptable solutions, and emphasizes early-lifecycle review, analysis and verification of design and development plans. "Design by shopping" emphasizes revealing the space of options available from which to choose (without presuming that all selection criteria have previously been elicited), and provides means to make understandable the range of choices and their ramifications. "Model-based engineering" emphasizes the goal of utilizing a formal representation of all aspects of system design, from development through operations, and provides powerful tool suites that support the practical application of these principles. A first step prototype towards this vision is described, embodying the key capabilities. Illustrations, implications, further challenges and opportunities are outlined.

Robot-Assisted Fracture Surgery: Surgical Requirements and System Design.

PubMed

Georgilas, Ioannis; Dagnino, Giulio; Tarassoli, Payam; Atkins, Roger; Dogramadzi, Sanja

2018-03-09

The design of medical devices is a complex and crucial process to ensure patient safety. It has been shown that improperly designed devices lead to errors and associated accidents and costs. A key element for a successful design is incorporating the views of the primary and secondary stakeholders early in the development process. They provide insights into current practice and point out specific issues with the current processes and equipment in use. This work presents how information from a user-study conducted in the early stages of the RAFS (Robot Assisted Fracture Surgery) project informed the subsequent development and testing of the system. The user needs were captured using qualitative methods and converted to operational, functional, and non-functional requirements based on the methods derived from product design and development. This work presents how the requirements inform a new workflow for intra-articular joint fracture reduction using a robotic system. It is also shown how the various elements of the system are developed to explicitly address one or more of the requirements identified, and how intermediate verification tests are conducted to ensure conformity. Finally, a validation test in the form of a cadaveric trial confirms the ability of the designed system to satisfy the aims set by the original research question and the needs of the users.

Statistical Requirements For Pass-Fail Testing Of Contraband Detection Systems

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

Gilliam, David M.

2011-06-01

Contraband detection systems for homeland security applications are typically tested for probability of detection (PD) and probability of false alarm (PFA) using pass-fail testing protocols. Test protocols usually require specified values for PD and PFA to be demonstrated at a specified level of statistical confidence CL. Based on a recent more theoretical treatment of this subject [1], this summary reviews the definition of CL and provides formulas and spreadsheet functions for constructing tables of general test requirements and for determining the minimum number of tests required. The formulas and tables in this article may be generally applied to many othermore » applications of pass-fail testing, in addition to testing of contraband detection systems.« less

Statistical Requirements For Pass-Fail Testing Of Contraband Detection Systems

NASA Astrophysics Data System (ADS)

Gilliam, David M.

2011-06-01

Contraband detection systems for homeland security applications are typically tested for probability of detection (PD) and probability of false alarm (PFA) using pass-fail testing protocols. Test protocols usually require specified values for PD and PFA to be demonstrated at a specified level of statistical confidence CL. Based on a recent more theoretical treatment of this subject [1], this summary reviews the definition of CL and provides formulas and spreadsheet functions for constructing tables of general test requirements and for determining the minimum number of tests required. The formulas and tables in this article may be generally applied to many other applications of pass-fail testing, in addition to testing of contraband detection systems.

NASA's Systems Engineering Approaches for Addressing Public Health Surveillance Requirements

NASA Technical Reports Server (NTRS)

Vann, Timi

2003-01-01

NASA's systems engineering has its heritage in space mission analysis and design, including the end-to-end approach to managing every facet of the extreme engineering required for successful space missions. NASA sensor technology, understanding of remote sensing, and knowledge of Earth system science, can be powerful new tools for improved disease surveillance and environmental public health tracking. NASA's systems engineering framework facilitates the match between facilitates the match between partner needs and decision support requirements in the areas of 1) Science/Data; 2) Technology; 3) Integration. Partnerships between NASA and other Federal agencies are diagrammed in this viewgraph presentation. NASA's role in these partnerships is to provide systemic and sustainable solutions that contribute to the measurable enhancement of a partner agency's disease surveillance efforts.

SEPS mission and system integration/interface requirements for the space transportation system. [Solar Electric Propulsion System

NASA Technical Reports Server (NTRS)

Cork, M. J.; Barnett, P. M.; Shaffer, J., Jr.; Doran, B. J.

1979-01-01

Earth escape mission requirements on Solar Electric Propulsion System (SEPS), and the interface definition and planned integration between SEPS, user spacecraft, and other elements of the STS. Emphasis is placed on the Comet rendezvous mission, scheduled to be the first SEPS user. Interactive SEPS interface characteristics with spacecraft and mission, as well as the multiple organizations and inter-related development schedules required to integrate the SEPS with spacecraft and STS, require early attention to definition of interfaces in order to assure a successful path to the first SEPS launch in July 1985

77 FR 18709 - Quality Assurance Requirements for Continuous Opacity Monitoring Systems at Stationary Sources

Federal Register 2010, 2011, 2012, 2013, 2014

2012-03-28

... Quality Assurance Requirements for Continuous Opacity Monitoring Systems at Stationary Sources AGENCY... direct final rule titled ``Quality Assurance Requirements for Continuous Opacity Monitoring Systems at...--Quality Assurance Requirements for Continuous Opacity Monitoring Systems at Stationary Sources Docket, EPA...

US-75 ICM system requirements : Dallas Integrated Corridor Management (ICM) demonstration project.

DOT National Transportation Integrated Search

2010-12-01

This document is intended as a listing and discussion of the Requirements for the US-75 Integrated Corridor Management System (ICMS) Demonstration Project in Dallas. This document describes what the system is to do (the functional requirements), how ...

Shared-Ride Taxi Computer Control System Requirements Study

DOT National Transportation Integrated Search

1977-08-01

The technical problem of scheduling and routing shared-ride taxi service is so great that only computers can handle it efficiently. This study is concerned with defining the requirements of such a computer system. The major objective of this study is...

Requirements Development Issues for Advanced Life Support Systems: Solid Waste Management

NASA Technical Reports Server (NTRS)

Levri, Julie A.; Fisher, John W.; Alazraki, Michael P.; Hogan, John A.

2002-01-01

Long duration missions pose substantial new challenges for solid waste management in Advanced Life Support (ALS) systems. These possibly include storing large volumes of waste material in a safe manner, rendering wastes stable or sterilized for extended periods of time, and/or processing wastes for recovery of vital resources. This is further complicated because future missions remain ill-defined with respect to waste stream quantity, composition and generation schedule. Without definitive knowledge of this information, development of requirements is hampered. Additionally, even if waste streams were well characterized, other operational and processing needs require clarification (e.g. resource recovery requirements, planetary protection constraints). Therefore, the development of solid waste management (SWM) subsystem requirements for long duration space missions is an inherently uncertain, complex and iterative process. The intent of this paper is to address some of the difficulties in writing requirements for missions that are not completely defined. This paper discusses an approach and motivation for ALS SWM requirements development, the characteristics of effective requirements, and the presence of those characteristics in requirements that are developed for uncertain missions. Associated drivers for life support system technological capability are also presented. A general means of requirements forecasting is discussed, including successive modification of requirements and the need to consider requirements integration among subsystems.

17 CFR 242.302 - Recordkeeping requirements for alternative trading systems.

Code of Federal Regulations, 2011 CFR

2011-04-01

... alternative trading systems. 242.302 Section 242.302 Commodity and Securities Exchanges SECURITIES AND... SECURITY FUTURES Regulation Ats-Alternative Trading Systems § 242.302 Recordkeeping requirements for alternative trading systems. To comply with the condition set forth in paragraph (b)(8) of § 242.301, an...

17 CFR 242.302 - Recordkeeping requirements for alternative trading systems.

Code of Federal Regulations, 2013 CFR

2013-04-01

... alternative trading systems. 242.302 Section 242.302 Commodity and Securities Exchanges SECURITIES AND... SECURITY FUTURES Regulation Ats-Alternative Trading Systems § 242.302 Recordkeeping requirements for alternative trading systems. To comply with the condition set forth in paragraph (b)(8) of § 242.301, an...

17 CFR 242.302 - Recordkeeping requirements for alternative trading systems.

Code of Federal Regulations, 2012 CFR

2012-04-01

... alternative trading systems. 242.302 Section 242.302 Commodity and Securities Exchanges SECURITIES AND... SECURITY FUTURES Regulation Ats-Alternative Trading Systems § 242.302 Recordkeeping requirements for alternative trading systems. To comply with the condition set forth in paragraph (b)(8) of § 242.301, an...

17 CFR 242.302 - Recordkeeping requirements for alternative trading systems.

Code of Federal Regulations, 2014 CFR

2014-04-01

... alternative trading systems. 242.302 Section 242.302 Commodity and Securities Exchanges SECURITIES AND... SECURITY FUTURES Regulation Ats-Alternative Trading Systems § 242.302 Recordkeeping requirements for alternative trading systems. To comply with the condition set forth in paragraph (b)(8) of § 242.301, an...

17 CFR 242.302 - Recordkeeping requirements for alternative trading systems.

Code of Federal Regulations, 2010 CFR

2010-04-01

... alternative trading systems. 242.302 Section 242.302 Commodity and Securities Exchanges SECURITIES AND... SECURITY FUTURES Regulation Ats-Alternative Trading Systems § 242.302 Recordkeeping requirements for alternative trading systems. To comply with the condition set forth in paragraph (b)(8) of § 242.301, an...

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

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

Harris, James M.; Burns, John F.; Satpathi, Meara Allena

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 datamore » but includes requirements for the dissemination of radionuclide data and products.« less

IDC Re-Engineering Phase 2 System Requirements Document Version 1.4

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

Harris, James M.; Burns, John F.; Satpathi, Meara Allena

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,more » but includes requirements for the dissemination of radionuclide data and products.« less

Definition of mission requirements for the follow-on EUMETSAT polar system

NASA Astrophysics Data System (ADS)

Phillips, P. L.; Schlüssel, P.; Accadia, C. J.; Munro, R.; Wilson, J. J. W.; Perez-Albinana, A.; Banfi, S.

2007-10-01

EUMETSAT has initiated preparatory activities for the definition of the follow-on EUMETSAT Polar System (post- EPS) needed for the timeframe 2020 onwards as a replacement for the current EUMETSAT Polar System. Based on the first outputs of the EUMETSAT post-EPS user consultation process initiated in 2005, mission requirements for potential post-EPS missions have been drafted. Expertise from a variety of communities was drawn upon in order to ascertain user needs expressed in terms of geophysical variables, for operational meteorology, climate monitoring, atmospheric chemistry, oceanography, and hydrology. Current trends in the evolution of these applications were considered in order to derive the necessary satellite products that will be required in the post-EPS era. The increasing complexity of models with regard to parameterisation and data assimilation, along with the trend towards coupled atmosphere, ocean and land models, generates new requirements, particularly in the domains of clouds and precipitation, trace gases and ocean/land surface products. Following the requirements definition, concept studies at instrument and system levels will shortly commence with the support of the European Space Agency (ESA), together with industry and representatives of the user and science communities. Such studies, planned for completion by end of 2008, aim at defining and trading off possible mission and system concepts and will establish preliminary functional requirements for full or partial implementation of post-EPS mission requirements. Cost drivers and needs for critical research and development will also be identified. The generation of both the user and mission requirements have been supported substantially by the post-EPS Mission Experts Team and the Application Expert Groups. Their support is gratefully acknowledged.

Flexibility Requirements concerning the Design of Synchronous E-Learning Systems

ERIC Educational Resources Information Center

Jahn, Matthias; Piesche, Claudia; Jablonski, Stefan

2012-01-01

Purpose: Today's requirements concerning successful learning support comprise a variety of application scenarios. Therefore, the development of supporting software preferably aims at modular design. This article discusses requirements regarding flexibility of e-learning systems and presents important principles, which should be met by successful…

Satellite Power Systems (SPS) concept definition study (Exhibit D). Volume 7: System/subsystems requirements databook

NASA Technical Reports Server (NTRS)

Hanley, G. M.

1981-01-01

This volume summarizes the basic requirements used as a guide to systems analysis, and is a basis for the selection of candidate Satellite Power Systems (SPS) point designs. Initially, these collected data reflected the level of definition resulting from the evaluation of a broad spectrum of SPS concepts. As the various concepts matured, these requirements were updated to reflect the requirements identified for the projected satellite system/subsystem point designs. Included is an updated version of earlier Rockwell concepts using klystrons as the specific microwave power amplification approach, as well as a more in-depth definition, analysis and preliminary point design on two concepts based on the use of advanced solid state technology to accomplish the task of high power amplification of the 2.45 GHz transmitted power beam to the Earth receiver. Finally, a preliminary definition of a concept using magnetrons as the microwave power amplifiers is presented.

Making a Big Bang on the small screen

NASA Astrophysics Data System (ADS)

Thomas, Nick

2010-01-01

While the quality of some TV sitcoms can leave viewers feeling cheated out of 30 minutes of their lives, audiences and critics are raving about the science-themed US comedy The Big Bang Theory. First shown on the CBS network in 2007, the series focuses on two brilliant postdoc physicists, Leonard and Sheldon, who are totally absorbed by science. Adhering to the stereotype, they also share a fanatical interest in science fiction, video-gaming and comic books, but unfortunately lack the social skills required to connect with their 20-something nonacademic contemporaries.

Architectural requirements for the Red Storm computing system.

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

Camp, William J.; Tomkins, James Lee

This report is based on the Statement of Work (SOW) describing the various requirements for delivering 3 new supercomputer system to Sandia National Laboratories (Sandia) as part of the Department of Energy's (DOE) Accelerated Strategic Computing Initiative (ASCI) program. This system is named Red Storm and will be a distributed memory, massively parallel processor (MPP) machine built primarily out of commodity parts. The requirements presented here distill extensive architectural and design experience accumulated over a decade and a half of research, development and production operation of similar machines at Sandia. Red Storm will have an unusually high bandwidth, low latencymore » interconnect, specially designed hardware and software reliability features, a light weight kernel compute node operating system and the ability to rapidly switch major sections of the machine between classified and unclassified computing environments. Particular attention has been paid to architectural balance in the design of Red Storm, and it is therefore expected to achieve an atypically high fraction of its peak speed of 41 TeraOPS on real scientific computing applications. In addition, Red Storm is designed to be upgradeable to many times this initial peak capability while still retaining appropriate balance in key design dimensions. Installation of the Red Storm computer system at Sandia's New Mexico site is planned for 2004, and it is expected that the system will be operated for a minimum of five years following installation.« less

Manned orbital systems concepts study. Book 2: Requirements for extended-duration missions

NASA Technical Reports Server (NTRS)

1975-01-01

In order to provide essential data needed in long-range program planning, the Manned Orbital Systems Concepts (MOSC) study attempted to define, evaluate, and compare concepts for manned orbital systems that provide extended experiment mission capabilities in space, flexibility of operation, and growth potential. Specific areas discussed include roles and requirements for man in future space missions, requirements for extended capability, mission/payload concepts, and preliminary design and operational requirements.

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

NASA Technical Reports Server (NTRS)

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.

Transforming Functional Requirements from UML into BPEL to Efficiently Develop SOA-Based Systems

NASA Astrophysics Data System (ADS)

Vemulapalli, Anisha; Subramanian, Nary

The intended behavior of any system such as services, tasks or functions can be captured by functional requirements of the system. As our dependence on online services has grown steadily, the web applications are being developed employing the SOA. BPEL4WS provides a means for expressing functional requirements of an SOA-based system by providing constructs to capture business goals and objectives for the system. In this paper we propose an approach for transforming user-centered requirements captured using UML into a corresponding BPEL specification, where the business processes are captured by means of use-cases from which UML sequence diagrams and activity diagrams are extracted. Subsequently these UML models are mapped to BPEL specifications that capture the essence of the initial business requirements to develop the SOA-based system by employing CASE tools. A student housing system is used as a case study to illustrate this approach and the system is validated using NetBeans.

Aerothermodynamic testing requirements for future space transportation systems

NASA Technical Reports Server (NTRS)

Paulson, John W., Jr.; Miller, Charles G., III

1995-01-01

Aerothermodynamics, encompassing aerodynamics, aeroheating, and fluid dynamic and physical processes, is the genesis for the design and development of advanced space transportation vehicles. It provides crucial information to other disciplines involved in the development process such as structures, materials, propulsion, and avionics. Sources of aerothermodynamic information include ground-based facilities, computational fluid dynamic (CFD) and engineering computer codes, and flight experiments. Utilization of this triad is required to provide the optimum requirements while reducing undue design conservatism, risk, and cost. This paper discusses the role of ground-based facilities in the design of future space transportation system concepts. Testing methodology is addressed, including the iterative approach often required for the assessment and optimization of configurations from an aerothermodynamic perspective. The influence of vehicle shape and the transition from parametric studies for optimization to benchmark studies for final design and establishment of the flight data book is discussed. Future aerothermodynamic testing requirements including the need for new facilities are also presented.

30 CFR 250.442 - What are the requirements for a subsea BOP system?

Code of Federal Regulations, 2014 CFR

2014-07-01

..., DEPARTMENT OF THE INTERIOR OFFSHORE OIL AND GAS AND SULPHUR OPERATIONS IN THE OUTER CONTINENTAL SHELF Oil and Gas Drilling Operations Blowout Preventer (bop) System Requirements § 250.442 What are the requirements for a subsea BOP system? When you drill with a subsea BOP system, you must install the BOP system...

30 CFR 250.442 - What are the requirements for a subsea BOP system?

Code of Federal Regulations, 2012 CFR

2012-07-01

..., DEPARTMENT OF THE INTERIOR OFFSHORE OIL AND GAS AND SULPHUR OPERATIONS IN THE OUTER CONTINENTAL SHELF Oil and Gas Drilling Operations Blowout Preventer (bop) System Requirements § 250.442 What are the requirements for a subsea BOP system? When you drill with a subsea BOP system, you must install the BOP system...

30 CFR 250.442 - What are the requirements for a subsea BOP system?

Code of Federal Regulations, 2013 CFR

2013-07-01

..., DEPARTMENT OF THE INTERIOR OFFSHORE OIL AND GAS AND SULPHUR OPERATIONS IN THE OUTER CONTINENTAL SHELF Oil and Gas Drilling Operations Blowout Preventer (bop) System Requirements § 250.442 What are the requirements for a subsea BOP system? When you drill with a subsea BOP system, you must install the BOP system...

30 CFR 250.442 - What are the requirements for a subsea BOP system?

Code of Federal Regulations, 2011 CFR

2011-07-01

... ENFORCEMENT, DEPARTMENT OF THE INTERIOR OFFSHORE OIL AND GAS AND SULPHUR OPERATIONS IN THE OUTER CONTINENTAL SHELF Oil and Gas Drilling Operations Blowout Preventer (bop) System Requirements § 250.442 What are the requirements for a subsea BOP system? When you drill with a subsea BOP system, you must install the BOP system...

Requirements analysis notebook for the flight data systems definition in the Real-Time Systems Engineering Laboratory (RSEL)

NASA Technical Reports Server (NTRS)

Wray, Richard B.

1991-01-01

A hybrid requirements analysis methodology was developed, based on the practices actually used in developing a Space Generic Open Avionics Architecture. During the development of this avionics architecture, a method of analysis able to effectively define the requirements for this space avionics architecture was developed. In this methodology, external interfaces and relationships are defined, a static analysis resulting in a static avionics model was developed, operating concepts for simulating the requirements were put together, and a dynamic analysis of the execution needs for the dynamic model operation was planned. The systems engineering approach was used to perform a top down modified structured analysis of a generic space avionics system and to convert actual program results into generic requirements. CASE tools were used to model the analyzed system and automatically generate specifications describing the model's requirements. Lessons learned in the use of CASE tools, the architecture, and the design of the Space Generic Avionics model were established, and a methodology notebook was prepared for NASA. The weaknesses of standard real-time methodologies for practicing systems engineering, such as Structured Analysis and Object Oriented Analysis, were identified.

Requirements analysis notebook for the flight data systems definition in the Real-Time Systems Engineering Laboratory (RSEL)

NASA Astrophysics Data System (ADS)

Wray, Richard B.

1991-12-01

A hybrid requirements analysis methodology was developed, based on the practices actually used in developing a Space Generic Open Avionics Architecture. During the development of this avionics architecture, a method of analysis able to effectively define the requirements for this space avionics architecture was developed. In this methodology, external interfaces and relationships are defined, a static analysis resulting in a static avionics model was developed, operating concepts for simulating the requirements were put together, and a dynamic analysis of the execution needs for the dynamic model operation was planned. The systems engineering approach was used to perform a top down modified structured analysis of a generic space avionics system and to convert actual program results into generic requirements. CASE tools were used to model the analyzed system and automatically generate specifications describing the model's requirements. Lessons learned in the use of CASE tools, the architecture, and the design of the Space Generic Avionics model were established, and a methodology notebook was prepared for NASA. The weaknesses of standard real-time methodologies for practicing systems engineering, such as Structured Analysis and Object Oriented Analysis, were identified.

Reliability analysis and initial requirements for FC systems and stacks

NASA Astrophysics Data System (ADS)

Åström, K.; Fontell, E.; Virtanen, S.

In the year 2000 Wärtsilä Corporation started an R&D program to develop SOFC systems for CHP applications. The program aims to bring to the market highly efficient, clean and cost competitive fuel cell systems with rated power output in the range of 50-250 kW for distributed generation and marine applications. In the program Wärtsilä focuses on system integration and development. System reliability and availability are key issues determining the competitiveness of the SOFC technology. In Wärtsilä, methods have been implemented for analysing the system in respect to reliability and safety as well as for defining reliability requirements for system components. A fault tree representation is used as the basis for reliability prediction analysis. A dynamic simulation technique has been developed to allow for non-static properties in the fault tree logic modelling. Special emphasis has been placed on reliability analysis of the fuel cell stacks in the system. A method for assessing reliability and critical failure predictability requirements for fuel cell stacks in a system consisting of several stacks has been developed. The method is based on a qualitative model of the stack configuration where each stack can be in a functional, partially failed or critically failed state, each of the states having different failure rates and effects on the system behaviour. The main purpose of the method is to understand the effect of stack reliability, critical failure predictability and operating strategy on the system reliability and availability. An example configuration, consisting of 5 × 5 stacks (series of 5 sets of 5 parallel stacks) is analysed in respect to stack reliability requirements as a function of predictability of critical failures and Weibull shape factor of failure rate distributions.

Calibration Issues and Operating System Requirements for Electron-Probe Microanalysis

NASA Technical Reports Server (NTRS)

Carpenter, P.

2006-01-01

Instrument purchase requirements and dialogue with manufacturers have established hardware parameters for alignment, stability, and reproducibility, which have helped improve the precision and accuracy of electron microprobe analysis (EPMA). The development of correction algorithms and the accurate solution to quantitative analysis problems requires the minimization of systematic errors and relies on internally consistent data sets. Improved hardware and computer systems have resulted in better automation of vacuum systems, stage and wavelength-dispersive spectrometer (WDS) mechanisms, and x-ray detector systems which have improved instrument stability and precision. Improved software now allows extended automated runs involving diverse setups and better integrates digital imaging and quantitative analysis. However, instrumental performance is not regularly maintained, as WDS are aligned and calibrated during installation but few laboratories appear to check and maintain this calibration. In particular, detector deadtime (DT) data is typically assumed rather than measured, due primarily to the difficulty and inconvenience of the measurement process. This is a source of fundamental systematic error in many microprobe laboratories and is unknown to the analyst, as the magnitude of DT correction is not listed in output by microprobe operating systems. The analyst must remain vigilant to deviations in instrumental alignment and calibration, and microprobe system software must conveniently verify the necessary parameters. Microanalysis of mission critical materials requires an ongoing demonstration of instrumental calibration. Possible approaches to improvements in instrument calibration, quality control, and accuracy will be discussed. Development of a set of core requirements based on discussions with users, researchers, and manufacturers can yield documents that improve and unify the methods by which instruments can be calibrated. These results can be used to

Requirements for the conceptual design of advanced underground coal extraction systems

NASA Technical Reports Server (NTRS)

Gangal, M. D.; Lavin, M. L.

1981-01-01

Conceptual design requirements are presented for underground coal mining systems having substantially improved performance in the areas of production cost and miner safety. Mandatory performance levels are also set for miner health, environmental impact, and coal recovery. In addition to mandatory design goals and constraints, a number of desirable system characteristics are identified which must be assessed in terms of their impact on production cost and their compatibility with other system elements. Although developed for the flat lying, moderately thick seams of Central Appalachia, these requirements are designed to be easily adaptable to other coals.

Minimum Control Requirements for Advanced Life Support Systems

NASA Technical Reports Server (NTRS)

Boulange, Richard; Jones, Harry; Jones, Harry

2002-01-01

Advanced control technologies are not necessary for the safe, reliable and continuous operation of Advanced Life Support (ALS) systems. ALS systems can and are adequately controlled by simple, reliable, low-level methodologies and algorithms. The automation provided by advanced control technologies is claimed to decrease system mass and necessary crew time by reducing buffer size and minimizing crew involvement. In truth, these approaches increase control system complexity without clearly demonstrating an increase in reliability across the ALS system. Unless these systems are as reliable as the hardware they control, there is no savings to be had. A baseline ALS system is presented with the minimal control system required for its continuous safe reliable operation. This baseline control system uses simple algorithms and scheduling methodologies and relies on human intervention only in the event of failure of the redundant backup equipment. This ALS system architecture is designed for reliable operation, with minimal components and minimal control system complexity. The fundamental design precept followed is "If it isn't there, it can't fail".

30 CFR 250.803 - Additional production system requirements.

Code of Federal Regulations, 2014 CFR

2014-07-01

... pressure vessels at any time when there is a change in operating pressures that requires new settings for... significant change in operating pressures. The most recent pressure-recorder charts used to determine... subfreezing climates, the lessee shall furnish evidence to the District Manager that the firefighting system...

30 CFR 250.803 - Additional production system requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

... pressure vessels at any time when there is a change in operating pressures that requires new settings for... significant change in operating pressures. The most recent pressure-recorder charts used to determine... subfreezing climates, the lessee shall furnish evidence to the District Manager that the firefighting system...

30 CFR 250.803 - Additional production system requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

... pressure vessels at any time when there is a change in operating pressures that requires new settings for... significant change in operating pressures. The most recent pressure-recorder charts used to determine... subfreezing climates, the lessee shall furnish evidence to the District Manager that the firefighting system...

5 CFR 9901.405 - Performance management system requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... management system for NSPS employees, subject to the requirements set forth in this subpart. (b) The NSPS performance management system— (1) Provides for the appraisal of the performance of each employee annually; (2... employees based on performance and contribution; (3) Foster and reward excellent performance; (4) Address...

Digital Avionics Information System (DAIS): Training Requirements Analysis Model (TRAMOD).

ERIC Educational Resources Information Center

Czuchry, Andrew J.; And Others

The training requirements analysis model (TRAMOD) described in this report represents an important portion of the larger effort called the Digital Avionics Information System (DAIS) Life Cycle Cost (LCC) Study. TRAMOD is the second of three models that comprise an LCC impact modeling system for use in the early stages of system development. As…

Microgravity fluid management requirements of advanced solar dynamic power systems

NASA Technical Reports Server (NTRS)

Migra, Robert P.

1987-01-01

The advanced solar dynamic system (ASDS) program is aimed at developing the technology for highly efficient, lightweight space power systems. The approach is to evaluate Stirling, Brayton and liquid metal Rankine power conversion systems (PCS) over the temperature range of 1025 to 1400K, identify the critical technologies and develop these technologies. Microgravity fluid management technology is required in several areas of this program, namely, thermal energy storage (TES), heat pipe applications and liquid metal, two phase flow Rankine systems. Utilization of the heat of fusion of phase change materials offers potential for smaller, lighter TES systems. The candidate TES materials exhibit large volume change with the phase change. The heat pipe is an energy dense heat transfer device. A high temperature application may transfer heat from the solar receiver to the PCS working fluid and/or TES. A low temperature application may transfer waste heat from the PCS to the radiator. The liquid metal Rankine PCS requires management of the boiling/condensing process typical of two phase flow systems.

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

PubMed Central

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

40 CFR 63.2490 - What requirements must I meet for heat exchange systems?

Code of Federal Regulations, 2012 CFR

2012-07-01

... requirements must I meet for heat exchange systems? (a) You must comply with each requirement in Table 10 to this subpart that applies to your heat exchange systems, except as specified in paragraphs (b) and (c... 40 Protection of Environment 13 2012-07-01 2012-07-01 false What requirements must I meet for heat...

40 CFR 63.2490 - What requirements must I meet for heat exchange systems?

Code of Federal Regulations, 2013 CFR

2013-07-01

... requirements must I meet for heat exchange systems? (a) You must comply with each requirement in Table 10 to this subpart that applies to your heat exchange systems, except as specified in paragraphs (b) and (c... 40 Protection of Environment 13 2013-07-01 2012-07-01 true What requirements must I meet for heat...

40 CFR 63.2490 - What requirements must I meet for heat exchange systems?

Code of Federal Regulations, 2014 CFR

2014-07-01

... requirements must I meet for heat exchange systems? (a) You must comply with each requirement in Table 10 to this subpart that applies to your heat exchange systems, except as specified in paragraphs (b) and (c... 40 Protection of Environment 13 2014-07-01 2014-07-01 false What requirements must I meet for heat...

Systems planning for automated commercial vehicle licensing and permitting systems : national ITS/CVO program requirements

DOT National Transportation Integrated Search

1997-07-01

This report describes the work of the study, Systems Planning for Automated Commercial Vehicle Licensing and Permitting Systems. The objective of this study is to define the market, organization, and resource requirements for a national program...

46 CFR 58.30-50 - Requirements for miscellaneous fluid power and control systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

...) MARINE ENGINEERING MAIN AND AUXILIARY MACHINERY AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-50 Requirements for miscellaneous fluid power and control systems. (a) All fluid power and control... 46 Shipping 2 2010-10-01 2010-10-01 false Requirements for miscellaneous fluid power and control...

46 CFR 58.30-50 - Requirements for miscellaneous fluid power and control systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

...) MARINE ENGINEERING MAIN AND AUXILIARY MACHINERY AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-50 Requirements for miscellaneous fluid power and control systems. (a) All fluid power and control... 46 Shipping 2 2014-10-01 2014-10-01 false Requirements for miscellaneous fluid power and control...

46 CFR 58.30-50 - Requirements for miscellaneous fluid power and control systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

...) MARINE ENGINEERING MAIN AND AUXILIARY MACHINERY AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-50 Requirements for miscellaneous fluid power and control systems. (a) All fluid power and control... 46 Shipping 2 2013-10-01 2013-10-01 false Requirements for miscellaneous fluid power and control...

46 CFR 58.30-50 - Requirements for miscellaneous fluid power and control systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

...) MARINE ENGINEERING MAIN AND AUXILIARY MACHINERY AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-50 Requirements for miscellaneous fluid power and control systems. (a) All fluid power and control... 46 Shipping 2 2011-10-01 2011-10-01 false Requirements for miscellaneous fluid power and control...

46 CFR 58.30-50 - Requirements for miscellaneous fluid power and control systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

...) MARINE ENGINEERING MAIN AND AUXILIARY MACHINERY AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-50 Requirements for miscellaneous fluid power and control systems. (a) All fluid power and control... 46 Shipping 2 2012-10-01 2012-10-01 false Requirements for miscellaneous fluid power and control...

Nuclear Thermal Propulsion Mars Mission Systems Analysis and Requirements Definition

NASA Technical Reports Server (NTRS)

Mulqueen, Jack; Chiroux, Robert C.; Thomas, Dan; Crane, Tracie

2007-01-01

This paper describes the Mars transportation vehicle design concepts developed by the Marshall Space Flight Center (MSFC) Advanced Concepts Office. These vehicle design concepts provide an indication of the most demanding and least demanding potential requirements for nuclear thermal propulsion systems for human Mars exploration missions from years 2025 to 2035. Vehicle concept options vary from large "all-up" vehicle configurations that would transport all of the elements for a Mars mission on one vehicle. to "split" mission vehicle configurations that would consist of separate smaller vehicles that would transport cargo elements and human crew elements to Mars separately. Parametric trades and sensitivity studies show NTP stage and engine design options that provide the best balanced set of metrics based on safety, reliability, performance, cost and mission objectives. Trade studies include the sensitivity of vehicle performance to nuclear engine characteristics such as thrust, specific impulse and nuclear reactor type. Tbe associated system requirements are aligned with the NASA Exploration Systems Mission Directorate (ESMD) Reference Mars mission as described in the Explorations Systems Architecture Study (ESAS) report. The focused trade studies include a detailed analysis of nuclear engine radiation shield requirements for human missions and analysis of nuclear thermal engine design options for the ESAS reference mission.

30 CFR 75.1103-10 - Fire suppression systems; additional requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... requirements. 75.1103-10 Section 75.1103-10 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT... Protection § 75.1103-10 Fire suppression systems; additional requirements. For each conveyor belt flight... per minute, an additional cache of the materials specified in § 75.1103-9(a)(1), (2), and (3) shall be...

49 CFR 236.1005 - Requirements for Positive Train Control systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

... be determined and reported as follows: (i) The traffic density threshold of 5 million gross tons... in rail traffic such as reductions in total traffic volume or cessation of passenger or PIH service... requirement to install PTC on a low density track segment where a PTC system is otherwise required by this...

49 CFR 236.1005 - Requirements for Positive Train Control systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

... be determined and reported as follows: (i) The traffic density threshold of 5 million gross tons... in rail traffic such as reductions in total traffic volume to a level below 5 million gross tons... requirement to install PTC on a low density track segment where a PTC system is otherwise required by this...

49 CFR 236.1005 - Requirements for Positive Train Control systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

... be determined and reported as follows: (i) The traffic density threshold of 5 million gross tons... in rail traffic such as reductions in total traffic volume to a level below 5 million gross tons... requirement to install PTC on a low density track segment where a PTC system is otherwise required by this...

49 CFR 236.1005 - Requirements for Positive Train Control systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

... be determined and reported as follows: (i) The traffic density threshold of 5 million gross tons... in rail traffic such as reductions in total traffic volume to a level below 5 million gross tons... requirement to install PTC on a low density track segment where a PTC system is otherwise required by this...

Space-based multifunctional end effector systems functional requirements and proposed designs

NASA Technical Reports Server (NTRS)

Mishkin, A. H.; Jau, B. M.

1988-01-01

The end effector is an essential element of teleoperator and telerobot systems to be employed in space in the next decade. The report defines functional requirements for end effector systems to perform operations that are currently only feasible through Extra-Vehicular Activity (EVA). Specific tasks and functions that the end effectors must be capable of performing are delineated. Required capabilities for forces and torques, clearances, compliance, and sensing are described, using current EVA requirements as guidelines where feasible. The implications of these functional requirements on the elements of potential end effector systems are discussed. The systems issues that must be considered in the design of space-based manipulator systems are identified; including impacts on subsystems tightly coupled to the end effector, i.e., control station, information processing, manipulator arm, tool and equipment stowage. Possible end effector designs are divided into three categories: single degree-of-freedom end effectors, multiple degree of freedom end effectors, and anthropomorphic hands. Specific design alternatives are suggested and analyzed within the individual categories. Two evaluations are performed: the first considers how well the individual end effectors could substitute for EVA; the second compares how manipulator systems composed of the top performers from the first evaluation would improve the space shuttle Remote Manipulator System (RMS) capabilities. The analysis concludes that the anthropomorphic hand is best-suited for EVA tasks. A left- and right-handed anthropomorphic manipulator arm configuration is suggested as appropriate to be affixed to the RMS, but could also be used as part of the Smart Front End for the Orbital Maneuvering Vehicle (OMV). The technical feasibility of the anthropomorphic hand and its control are demonstrated. An evolutionary development approach is proposed and approximate scheduling provided for implementing the suggested

40 CFR Table 6 to Subpart Vvvvvv... - Emission Limits and Compliance Requirements for Wastewater Systems

Code of Federal Regulations, 2010 CFR

2010-07-01

... Requirements for Wastewater Systems 6 Table 6 to Subpart VVVVVV of Part 63 Protection of Environment... of Part 63—Emission Limits and Compliance Requirements for Wastewater Systems As required in § 63.11498, you must comply with the requirements for wastewater systems as shown in the following table. For...

40 CFR Table 6 to Subpart Vvvvvv... - Emission Limits and Compliance Requirements for Wastewater Systems

Code of Federal Regulations, 2012 CFR

2012-07-01

... Requirements for Wastewater Systems 6 Table 6 to Subpart VVVVVV of Part 63 Protection of Environment... of Part 63—Emission Limits and Compliance Requirements for Wastewater Systems As required in § 63.11498, you must comply with the requirements for wastewater systems as shown in the following table. For...

40 CFR Table 6 to Subpart Vvvvvv... - Emission Limits and Compliance Requirements for Wastewater Systems

Code of Federal Regulations, 2014 CFR

2014-07-01

... Requirements for Wastewater Systems 6 Table 6 to Subpart VVVVVV of Part 63 Protection of Environment... of Part 63—Emission Limits and Compliance Requirements for Wastewater Systems [As required in § 63.11498, you must comply with the requirements for wastewater systems as shown in the following table] For...

40 CFR Table 6 to Subpart Vvvvvv... - Emission Limits and Compliance Requirements for Wastewater Systems

Code of Federal Regulations, 2013 CFR

2013-07-01

... Requirements for Wastewater Systems 6 Table 6 to Subpart VVVVVV of Part 63 Protection of Environment... of Part 63—Emission Limits and Compliance Requirements for Wastewater Systems [As required in § 63.11498, you must comply with the requirements for wastewater systems as shown in the following table] For...

An Analysis of Minimum System Requirements to Support Computerized Adaptive Testing.

DTIC Science & Technology

1986-09-01

adaptive test ( CAT ); adaptive test ing A;4SRAC:’ (Continue on reverie of necessary and ident4f by block number) % This pape-r discusses the minimum system...requirements needed to develop a computerized adaptive test ( CAT ). It lists some of the benefits of adaptive testing, establishes a set of...discusses the minimum system requirements needed to develop a computerized adaptive test ( CAT ). It lists some of the benefits of adaptive testing

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

NASA Technical Reports Server (NTRS)

West, R. S.

1975-01-01

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

Rotational-translational fourier imaging system requiring only one grid pair

NASA Technical Reports Server (NTRS)

Campbell, Jonathan W. (Inventor)

2006-01-01

The sky contains many active sources that emit X-rays, gamma rays, and neutrons. Unfortunately hard X-rays, gamma rays, and neutrons cannot be imaged by conventional optics. This obstacle led to the development of Fourier imaging systems. In early approaches, multiple grid pairs were necessary in order to create rudimentary Fourier imaging systems. At least one set of grid pairs was required to provide multiple real components of a Fourier derived image, and another set was required to provide multiple imaginary components of the image. It has long been recognized that the expense associated with the physical production of the numerous grid pairs required for Fourier imaging was a drawback. Herein one grid pair (two grids), with accompanying rotation and translation, can be used if one grid has one more slit than the other grid, and if the detector is modified.

Medical examiner/death investigator training requirements in state medical examiner systems.

PubMed

Prahlow, J A; Lantz, P E

1995-01-01

Comprehensive and properly performed investigation of suspicious, unusual, unnatural, and various natural deaths is necessary to maintain the health, safety, and well-being of society as a whole. Adequate investigation requires the combined efforts and cooperation of law-enforcement and other public-service agencies, medical professionals, and those within the forensic community. As such, the "death investigator" plays a crucial role in the investigation process. These front-line investigators, whether they be coroners, medical examiners, physicians, other medical professionals, or lay-people, are required to make important decisions which have far-reaching consequences on how death investigation cases proceed. Death investigation practices vary greatly among medico-legal jurisdictions. A recent publication has categorized state death investigation systems by type of system. In an attempt to better delineate death investigation practices with specific regard to investigators' training and continuing education requirements, we surveyed the 20 systems categorized as state medical examiner systems and the five states with combined state medical examiner and county coroner/medical examiner systems. We present our findings and make recommendations which address the attributes and deficiencies of current death investigation practices.

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

NASA Technical Reports Server (NTRS)

Lewis, James L.

2011-01-01

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

Models of Human Information Requirements: "When Reasonable Aiding Systems Disagree"

NASA Technical Reports Server (NTRS)

Corker, Kevin; Pisanich, Gregory; Shafto, Michael (Technical Monitor)

1994-01-01

Aircraft flight management and Air Traffic Control (ATC) automation are under development to maximize the economy of flight and to increase the capacity of the terminal area airspace while maintaining levels of flight safety equal to or better than current system performance. These goals are being realized by the introduction of flight management automation aiding and operations support systems on the flight deck and by new developments of ATC aiding systems that seek to optimize scheduling of aircraft while potentially reducing required separation and accounting for weather and wake vortex turbulence. Aiding systems on both the flight deck and the ground operate through algorithmic functions on models of the aircraft and of the airspace. These models may differ from each other as a result of variations in their models of the immediate environment. The resultant flight operations or ATC commands may differ in their response requirements (e.g. different preferred descent speeds or descent initiation points). The human operators in the system must then interact with the automation to reconcile differences and resolve conflicts. We have developed a model of human performance including cognitive functions (decision-making, rule-based reasoning, procedural interruption recovery and forgetting) that supports analysis of the information requirements for resolution of flight aiding and ATC conflicts. The model represents multiple individuals in the flight crew and in ATC. The model is supported in simulation on a Silicon Graphics' workstation using Allegro Lisp. Design guidelines for aviation automation aiding systems have been developed using the model's specification of information and team procedural requirements. Empirical data on flight deck operations from full-mission flight simulation are provided to support the model's predictions. The paper describes the model, its development and implementation, the simulation test of the model predictions, and the empirical

A Scenario-Based Process for Requirements Development: Application to Mission Operations Systems

NASA Technical Reports Server (NTRS)

Bindschadler, Duane L.; Boyles, Carole A.

2008-01-01

The notion of using operational scenarios as part of requirements development during mission formulation (Phases A & B) is widely accepted as good system engineering practice. In the context of developing a Mission Operations System (MOS), there are numerous practical challenges to translating that notion into the cost-effective development of a useful set of requirements. These challenges can include such issues as a lack of Project-level focus on operations issues, insufficient or improper flowdown of requirements, flowdown of immature or poor-quality requirements from Project level, and MOS resource constraints (personnel expertise and/or dollars). System engineering theory must be translated into a practice that provides enough structure and standards to serve as guidance, but that retains sufficient flexibility to be tailored to the needs and constraints of a particular MOS or Project. We describe a detailed, scenario-based process for requirements development. Identifying a set of attributes for high quality requirements, we show how the portions of the process address many of those attributes. We also find that the basic process steps are robust, and can be effective even in challenging Project environments.

24 CFR 3280.904 - Specific requirements for designing the transportation system.

Code of Federal Regulations, 2010 CFR

2010-04-01

... the transportation system. 3280.904 Section 3280.904 Housing and Urban Development Regulations... SAFETY STANDARDS Transportation § 3280.904 Specific requirements for designing the transportation system. (a) General. The entire system (frame, drawbar and coupling mechanism, running gear assembly, and...

42 CFR 431.832 - Reporting requirements for claims processing assessment systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... assessment systems. 431.832 Section 431.832 Public Health CENTERS FOR MEDICARE & MEDICAID SERVICES... GENERAL ADMINISTRATION Quality Control Medicaid Quality Control (mqc) Claims Processing Assessment System § 431.832 Reporting requirements for claims processing assessment systems. (a) The agency must submit...

Technical Requirements Analysis and Control Systems (TRACS) Initial Operating Capability (IOC) documentation

NASA Technical Reports Server (NTRS)

Hammond, Dana P.

1991-01-01

The Technical Requirements Analysis and Control Systems (TRACS) software package is described. TRACS offers supplemental tools for the analysis, control, and interchange of project requirements. This package provides the fundamental capability to analyze and control requirements, serves a focal point for project requirements, and integrates a system that supports efficient and consistent operations. TRACS uses relational data base technology (ORACLE) in a stand alone or in a distributed environment that can be used to coordinate the activities required to support a project through its entire life cycle. TRACS uses a set of keyword and mouse driven screens (HyperCard) which imposes adherence through a controlled user interface. The user interface provides an interactive capability to interrogate the data base and to display or print project requirement information. TRACS has a limited report capability, but can be extended with PostScript conventions.

Transforming user needs into functional requirements for an antibiotic clinical decision support system: explicating content analysis for system design.

PubMed

Bright, T J

2013-01-01

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. 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). 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. 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. 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 antibiotic CDS system, resolving unmet antibiotic prescribing

Earth Sciences Requirements for the Information Sciences Experiment System

NASA Technical Reports Server (NTRS)

Bowker, David E. (Editor); Katzberg, Steve J. (Editor); Wilson, R. Gale (Editor)

1990-01-01

The purpose of the workshop was to further explore and define the earth sciences requirements for the Information Sciences Experiment System (ISES), a proposed onboard data processor with real-time communications capability intended to support the Earth Observing System (Eos). A review of representative Eos instrument types is given and a preliminary set of real-time data needs has been established. An executive summary is included.

75 FR 22844 - Construction Fall Protection Systems Criteria and Practices and Training Requirements; Extension...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-04-30

...] Construction Fall Protection Systems Criteria and Practices and Training Requirements; Extension of the Office of Management and Budget's (OMB) Approval of Information Collection (Paperwork) Requirements AGENCY... requirements contained in the construction standards on Fall Protection Systems Criteria and Practices (29 CFR...

Requirements for a mobile communications satellite system. Volume 1: Executive summary

NASA Technical Reports Server (NTRS)

1983-01-01

Three types of satellite-aided mobile communications are considered for users in areas not served by (terrestrial) cellular radio systems. In System 1, mobile units are provided a direct satellite link to a gateway station, which serves as the interface to the terrestrial toll network. In System 2, a terrestrial radio link similar to those in cellular systems connects the mobile unit to a translator station; each translator relays the traffic from mobile units in its vicinity, via satellite, to the regional gateway. It is not feasible for System 2 to provide ubiquitous coverage. Therefore, System 3 is introduced, in which the small percentage of users not within range of a translator are provided a direct satellite link as in System 1. While System 2 can operate with leased satellite capacity, Systems 1 and 3 require a dedicated satellite. A major portion of this study is concerned with the design of a satellite for System 1. A weight limit of 10,000 lbs, corresponding to the projected 1990 STS capability, is imposed on the design. Frequency re-use of the allocated spectrum, through multiple satellite beams, is employed to generate the specified system capacity. Both offset-fed and center-fed reflectors are considered. For an assumed 10-MHz allocation and a population of 350,000 subscribers, a two-satellite system is required. The reflector diameters corresponding to offset-fed and center-fed geometries are 46 m and 62 m, respectively. Thus, large-space-structure technology is inherent to the implementation of System 1. In addition to establishing the technical requirements for the three types of satellite systems, the monthly service charge needed to provide a specified return on invested capital is computed. A net present value analysis is used for this purpose.

40 CFR Table 6 to Subpart Hhhhh of... - Requirements for Heat Exchange Systems

Code of Federal Regulations, 2010 CFR

2010-07-01

... 40 Protection of Environment 13 2010-07-01 2010-07-01 false Requirements for Heat Exchange Systems... Manufacturing Pt. 63, Subpt. HHHHH, Table 6 Table 6 to Subpart HHHHH of Part 63—Requirements for Heat Exchange... your heat exchange systems. For each . . . You must . . . Heat exchange system, as defined in § 63.101...

40 CFR Table 6 to Subpart Hhhhh of... - Requirements for Heat Exchange Systems

Code of Federal Regulations, 2014 CFR

2014-07-01

... 40 Protection of Environment 14 2014-07-01 2014-07-01 false Requirements for Heat Exchange Systems... Manufacturing Pt. 63, Subpt. HHHHH, Table 6 Table 6 to Subpart HHHHH of Part 63—Requirements for Heat Exchange... your heat exchange systems. For each . . . You must . . . Heat exchange system, as defined in § 63.101...

40 CFR Table 6 to Subpart Hhhhh of... - Requirements for Heat Exchange Systems

Code of Federal Regulations, 2012 CFR

2012-07-01

... 40 Protection of Environment 14 2012-07-01 2011-07-01 true Requirements for Heat Exchange Systems... Manufacturing Pt. 63, Subpt. HHHHH, Table 6 Table 6 to Subpart HHHHH of Part 63—Requirements for Heat Exchange... your heat exchange systems. For each . . . You must . . . Heat exchange system, as defined in § 63.101...

40 CFR Table 6 to Subpart Hhhhh of... - Requirements for Heat Exchange Systems

Code of Federal Regulations, 2013 CFR

2013-07-01

... 40 Protection of Environment 14 2013-07-01 2013-07-01 false Requirements for Heat Exchange Systems... Manufacturing Pt. 63, Subpt. HHHHH, Table 6 Table 6 to Subpart HHHHH of Part 63—Requirements for Heat Exchange... your heat exchange systems. For each . . . You must . . . Heat exchange system, as defined in § 63.101...

40 CFR Table 6 to Subpart Hhhhh of... - Requirements for Heat Exchange Systems

Code of Federal Regulations, 2011 CFR

2011-07-01

... 40 Protection of Environment 13 2011-07-01 2011-07-01 false Requirements for Heat Exchange Systems... Manufacturing Pt. 63, Subpt. HHHHH, Table 6 Table 6 to Subpart HHHHH of Part 63—Requirements for Heat Exchange... your heat exchange systems. For each . . . You must . . . Heat exchange system, as defined in § 63.101...

Impact of science objectives and requirements on probe mission and system design

NASA Technical Reports Server (NTRS)

Ledbetter, K. W.

1974-01-01

Problem areas in probe science technology are discussed that require a solution before probe systems can actually be designed. Considered are the effects of the model atmospheres on probe design; secondly, the effects of implementing the requirements to locate and measure the clouds and, trade-offs between descent sampling and measurement criteria as they affect probe system design.

A new approach in dry technology for non-degrading optical and EUV mask cleaning

NASA Astrophysics Data System (ADS)

Varghese, Ivin; Smith, Ben; Balooch, Mehdi; Bowers, Chuck

2012-11-01

The Eco-Snow Systems group of RAVE N.P., Inc. has developed a new cleaning technique to target several of the advanced and next generation mask clean challenges. This new technique, especially when combined with Eco-Snow Systems cryogenic CO2 cleaning technology, provides several advantages over existing methods because it: 1) is solely based on dry technique without requiring additional complementary aggressive wet chemistries that degrade the mask, 2) operates at atmospheric pressure and therefore avoids expensive and complicated equipment associated with vacuum systems, 3) generates ultra-clean reactants eliminating possible byproduct adders, 4) can be applied locally for site specific cleaning without exposing the rest of the mask or can be used to clean the entire mask, 5) removes organic as well as inorganic particulates and film contaminations, and 6) complements current techniques utilized for cleaning of advanced masks such as reduced chemistry wet cleans. In this paper, we shall present examples demonstrating the capability of this new technique for removal of pellicle glue residues and for critical removal of carbon contamination on EUV masks.

Requirements for the Military Message System (MMS) Family: Data Types and User Commands.

DTIC Science & Technology

1986-04-11

AD-A167 126 REQUIREMENTS FOR THE MILITARY MESSASE SYSTEM (NHS) i FRILY: DATA TYPES AND USER CONNNDS(U) NAVAL RESEARCH LAB WASHINGTON DC C L HEITHEVER... System (MMS) Family: Data Types and User Commands CONSTANCE L. HEITMEYER Computer Science and Systems Branch I Information Technology Division April 11...Security Classification) Requirements for the Military Message System (MMS) Family: Data Types and User Commands 12. PERSONAL AUTHOR(S) Heitmeer, Constance

Support requirements for remote sensor systems on unmanned planetary missions, phase 3

NASA Technical Reports Server (NTRS)

1971-01-01

The results of a study to determine the support requirements for remote sensor systems on unmanned planetary flyby and orbiter missions are presented. Sensors and experiment groupings for selected missions are also established. Computer programs were developed to relate measurement requirements to support requirements. Support requirements were determined for sensors capable of performing required measurements at various points along the trajectories of specific selected missions.

Parameter Requirements for Description of Alternative LINC Systems. Final Report.

ERIC Educational Resources Information Center

Center for Applied Linguistics, Washington, DC. Language Information Network and Clearinghouse System.

This study was undertaken for the Center for Applied Linguistics to survey and analyze its information system program for the language sciences. The study identifies and defines the generalized sets of parameters required for subsequent quantitative analysis of proposed alternative Language Information Network and Clearinghouse Systems by means of…

Some requirements and suggestions for a methodology to develop knowledge based systems.

PubMed

Green, D W; Colbert, M; Long, J

1989-11-01

This paper describes an approach to the creation of a methodology for the development of knowledge based systems. It specifies some requirements and suggests how these requirements might be met. General requirements can be satisfied using a systems approach. More specific ones can be met by viewing an organization as a network of consultations for coordinating expertise. The nature of consultations is described and the form of a possible cognitive model using a blackboard architecture is outlined. The value of the approach is illustrated in terms of certain knowledge elicitation methods.

Information systems requirements for the Microgravity Science and Applications Program

NASA Technical Reports Server (NTRS)

Kicza, M. E.; Kreer, J. R.

1991-01-01

NASA's Microgravity Science and Applications (MSAD) Program is presented. Additionally, the types of information produced wiithin the program and the anticipated growth in information system requirements as the program transitions to Space Station Freedom utilization are discussed. Plans for payload operations support in the Freedom era are addressed, as well as current activities to define research community requirements for data and sample archives.

Information systems requirements for the microgravity science and applications program

NASA Technical Reports Server (NTRS)

Kicza, M. E.; Kreer, J. R.

1990-01-01

NASA's Microgravity Science and Applications (MSAD) Program is presented. Additionally, the types of information produced within the program and the anticipated growth in information system requirements as the program transitions to Space Station Freedom utilization are discussed. Plans for payload operations support in the Freedom era are addressed, as well as current activities to define research community requirements for data and sample archives.

Does a new steam meal catering system meet patient requirements in hospital?

PubMed

Hickson, M; Fearnley, L; Thomas, J; Evans, S

2007-10-01

It has been consistently observed that a significant proportion of hospital inpatients are malnourished and many actually develop malnutrition in hospital. The NHS provides over 300 million meals each year at a cost of pound 500 million, yet there is relatively little research evaluating how well different catering systems provide for the needs of hospital inpatients. The aim of the study was to: (i) evaluate whether a new steam meal catering system (Steamplicity) enables patients in theory to meet their energy requirements in hospital and (ii) compare energy and protein intake using Steamplicity with a traditional bulk cook-chill system. Patients not at nutritional risk had their food intake at one lunchtime assessed. Energy intake was compared with the patients' energy requirements and energy and protein intake were compared with previous data from a bulk system. Fifty-seven patients had a median daily energy requirement of 7648 kJ (1821 kcal) [inter-quartile range (IQR): 6854-9164 kJ]. Assuming 30% [2293 kJ (546 kcal)] should be supplied by the lunch meal the average intake of 1369 kJ (326 kcal) fell short by 40%. Patients served meals from Steamplicity ate less energy [1369 kJ versus 1562 kJ (326 kcal versus 372 kcal) P = 0.04] but similar protein (18 g versus 19 g P = 0.34) to the bulk system. The largest difference was the energy provided by the dessert since the bulk system served more hot high-calorie desserts. Patient intakes did not meet their estimated requirements. The patients in this study were eating well and not at nutritional risk, thus patients with a poor appetite will be even less likely to meet their nutritional requirements. Steamplicity meals result in a lower energy intake than meals from a bulk cook-chill system, but similar protein intakes.

An iterative requirements specification procedure for decision support systems.

PubMed

Brookes, C H

1987-08-01

Requirements specification is a key element in a DSS development project because it not only determines what is to be done, it also drives the evolution process. A procedure for requirements elicitation is described that is based on the decomposition of the DSS design task into a number of functions, subfunctions, and operators. It is postulated that the procedure facilitates the building of a DSS that is complete and integrates MIS, modelling and expert system components. Some examples given are drawn from the health administration field.

Integrated propulsion/energy transfer control systems for lift-fan V/STOL aircraft. [reduction of total propulsion system and control system installation requirements

NASA Technical Reports Server (NTRS)

Deckert, W. H.; Rolls, L. S.

1974-01-01

An integrated propulsion/control system for lift-fan transport aircraft is described. System behavior from full-scale experimental and piloted simulator investigations are reported. The lift-fan transport is a promising concept for short-to-medium haul civil transportation and for other missions. The lift-fan transport concept features high cruise airspeed, favorable ride qualities, small perceived noise footprints, high utilization, transportation system flexibility, and adaptability to VTOL, V/STOL, or STOL configurations. The lift-fan transport has high direct operating costs in comparison to conventional aircraft, primarily because of propulsion system and aircraft low-speed control system installation requirements. An integrated lift-fan propulsion system/aircraft low-speed control system that reduces total propulsion system and control system installation requirements is discussed.

76 FR 52581 - Automated Data Processing and Information Retrieval System Requirements

Federal Register 2010, 2011, 2012, 2013, 2014

2011-08-23

..., however, conduct pre and/or post implementation reviews. These reviews would be intended to: Evaluate... payment accuracy. This proposed rule would also specify the requirements for submission of a test plan... eligibility systems are adequately reviewed and tested. The law requires accountability for ensuring test...

40 CFR 63.11498 - What are the standards and compliance requirements for wastewater systems?

Code of Federal Regulations, 2011 CFR

2011-07-01

... requirements for wastewater systems? 63.11498 Section 63.11498 Protection of Environment ENVIRONMENTAL... and compliance requirements for wastewater systems? (a) You must comply with the requirements in paragraph (a)(1) and (2) of this section and in Table 6, Item 1 to this subpart for all wastewater streams...

40 CFR 63.11498 - What are the standards and compliance requirements for wastewater systems?

Code of Federal Regulations, 2013 CFR

2013-07-01

... requirements for wastewater systems? 63.11498 Section 63.11498 Protection of Environment ENVIRONMENTAL... and compliance requirements for wastewater systems? (a) You must comply with the requirements in paragraph (a)(1) and (2) of this section and in Table 6, Item 1 to this subpart for all wastewater streams...

40 CFR 63.11498 - What are the standards and compliance requirements for wastewater systems?

Code of Federal Regulations, 2014 CFR

2014-07-01

... requirements for wastewater systems? 63.11498 Section 63.11498 Protection of Environment ENVIRONMENTAL... and compliance requirements for wastewater systems? (a) You must comply with the requirements in paragraph (a)(1) and (2) of this section and in Table 6, Item 1 to this subpart for all wastewater streams...

47 CFR 80.231 - Technical Requirements for Class B Automatic Identification System (AIS) equipment.

Code of Federal Regulations, 2012 CFR

2012-10-01

... Identification System (AIS) equipment. 80.231 Section 80.231 Telecommunication FEDERAL COMMUNICATIONS COMMISSION... § 80.231 Technical Requirements for Class B Automatic Identification System (AIS) equipment. (a) Class B Automatic Identification System (AIS) equipment must meet the technical requirements of IEC 62287...

47 CFR 80.231 - Technical Requirements for Class B Automatic Identification System (AIS) equipment.

Code of Federal Regulations, 2013 CFR

2013-10-01

... Identification System (AIS) equipment. 80.231 Section 80.231 Telecommunication FEDERAL COMMUNICATIONS COMMISSION... § 80.231 Technical Requirements for Class B Automatic Identification System (AIS) equipment. (a) Class B Automatic Identification System (AIS) equipment must meet the technical requirements of IEC 62287...

47 CFR 80.231 - Technical Requirements for Class B Automatic Identification System (AIS) equipment.

Code of Federal Regulations, 2014 CFR

2014-10-01

... Identification System (AIS) equipment. 80.231 Section 80.231 Telecommunication FEDERAL COMMUNICATIONS COMMISSION... § 80.231 Technical Requirements for Class B Automatic Identification System (AIS) equipment. (a) Class B Automatic Identification System (AIS) equipment must meet the technical requirements of IEC 62287...

Operational characterisation of requirements and early validation environment for high demanding space systems

NASA Technical Reports Server (NTRS)

Barro, E.; Delbufalo, A.; Rossi, F.

1993-01-01

The definition of some modern high demanding space systems requires a different approach to system definition and design from that adopted for traditional missions. System functionality is strongly coupled to the operational analysis, aimed at characterizing the dynamic interactions of the flight element with its surrounding environment and its ground control segment. Unambiguous functional, operational and performance requirements are to be defined for the system, thus improving also the successive development stages. This paper proposes a Petri Nets based methodology and two related prototype applications (to ARISTOTELES orbit control and to Hermes telemetry generation) for the operational analysis of space systems through the dynamic modeling of their functions and a related computer aided environment (ISIDE) able to make the dynamic model work, thus enabling an early validation of the system functional representation, and to provide a structured system requirements data base, which is the shared knowledge base interconnecting static and dynamic applications, fully traceable with the models and interfaceable with the external world.

75 FR 43487 - Proposed Information Collection; Comment Request; Vessel Monitoring System Requirements in...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-07-26

... Monitoring System Requirements in the Western Pacific Pelagic Longline Fishery), OMB Control No. 0648-0519... requirement from OMB Control No. 0648-0584 (Permitting, Vessel Identification and Vessel Monitoring System... one collection (OMB Control No. 0648-0441). II. Method of Collection Automatic. III. Data OMB Control...

30 CFR 75.1101-7 - Installation of water sprinkler systems; requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

... Protection § 75.1101-7 Installation of water sprinkler systems; requirements. (a) The fire-control components of each water sprinkler system shall be installed, as far as practicable in accordance with the... 30 Mineral Resources 1 2011-07-01 2011-07-01 false Installation of water sprinkler systems...

30 CFR 75.1101-7 - Installation of water sprinkler systems; requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

... Protection § 75.1101-7 Installation of water sprinkler systems; requirements. (a) The fire-control components of each water sprinkler system shall be installed, as far as practicable in accordance with the... 30 Mineral Resources 1 2013-07-01 2013-07-01 false Installation of water sprinkler systems...

30 CFR 75.1101-7 - Installation of water sprinkler systems; requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

... Protection § 75.1101-7 Installation of water sprinkler systems; requirements. (a) The fire-control components of each water sprinkler system shall be installed, as far as practicable in accordance with the... 30 Mineral Resources 1 2012-07-01 2012-07-01 false Installation of water sprinkler systems...

30 CFR 75.1101-7 - Installation of water sprinkler systems; requirements.

Code of Federal Regulations, 2014 CFR

2014-07-01

... Protection § 75.1101-7 Installation of water sprinkler systems; requirements. (a) The fire-control components of each water sprinkler system shall be installed, as far as practicable in accordance with the... 30 Mineral Resources 1 2014-07-01 2014-07-01 false Installation of water sprinkler systems...

30 CFR 75.1101-7 - Installation of water sprinkler systems; requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... 30 Mineral Resources 1 2010-07-01 2010-07-01 false Installation of water sprinkler systems... Protection § 75.1101-7 Installation of water sprinkler systems; requirements. (a) The fire-control components of each water sprinkler system shall be installed, as far as practicable in accordance with the...

40 CFR 141.624 - Additional requirements for consecutive systems.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 40 Protection of Environment 23 2011-07-01 2011-07-01 false Additional requirements for consecutive systems. 141.624 Section 141.624 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) WATER PROGRAMS (CONTINUED) NATIONAL PRIMARY DRINKING WATER REGULATIONS Stage 2 Disinfection...

40 CFR 141.624 - Additional requirements for consecutive systems.

Code of Federal Regulations, 2013 CFR

2013-07-01

... 40 Protection of Environment 24 2013-07-01 2013-07-01 false Additional requirements for consecutive systems. 141.624 Section 141.624 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) WATER PROGRAMS (CONTINUED) NATIONAL PRIMARY DRINKING WATER REGULATIONS Stage 2 Disinfection...

40 CFR 141.624 - Additional requirements for consecutive systems.

Code of Federal Regulations, 2012 CFR

2012-07-01

... 40 Protection of Environment 24 2012-07-01 2012-07-01 false Additional requirements for consecutive systems. 141.624 Section 141.624 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) WATER PROGRAMS (CONTINUED) NATIONAL PRIMARY DRINKING WATER REGULATIONS Stage 2 Disinfection...

40 CFR 141.624 - Additional requirements for consecutive systems.

Code of Federal Regulations, 2014 CFR

2014-07-01

... 40 Protection of Environment 23 2014-07-01 2014-07-01 false Additional requirements for consecutive systems. 141.624 Section 141.624 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) WATER PROGRAMS (CONTINUED) NATIONAL PRIMARY DRINKING WATER REGULATIONS Stage 2 Disinfection...

Space Operations Center System Analysis: Requirements for a Space Operations Center, revision A

NASA Technical Reports Server (NTRS)

Woodcock, G. R.

1982-01-01

The system and program requirements for a space operations center as defined by systems analysis studies are presented as a guide for future study and systems definition. Topics covered include general requirements for safety, maintainability, and reliability, service and habitat modules, the health maintenance facility; logistics modules; the docking tunnel; and subsystem requirements (structures, electrical power, environmental control/life support; extravehicular activity; data management; communications and tracking; docking/berthing; flight control/propulsion; and crew support). Facilities for flight support, construction, satellite and mission servicing, and fluid storage are included as well as general purpose support equipment.

49 CFR 236.1005 - Requirements for Positive Train Control systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... be equipped with a PTC system shall be determined and reported as follows: (i) The traffic density... installed, based upon changes in rail traffic such as reductions in total traffic volume or cessation of... review of the requirement to install PTC on a low density track segment where a PTC system is otherwise...

49 CFR 37.189 - Service requirement for OTRB demand-responsive systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 49 Transportation 1 2010-10-01 2010-10-01 false Service requirement for OTRB demand-responsive systems. 37.189 Section 37.189 Transportation Office of the Secretary of Transportation TRANSPORTATION SERVICES FOR INDIVIDUALS WITH DISABILITIES (ADA) Over-the-Road Buses (OTRBs) § 37.189 Service requirement...

Applying Required Navigation Performance Concept for Traffic Management of Small Unmanned Aircraft Systems

NASA Technical Reports Server (NTRS)

Jung, Jaewoo; D'Souza, Sarah N.; Johnson, Marcus A.; Ishihara, Abraham K.; Modi, Hemil C.; Nikaido, Ben; Hasseeb, Hashmatullah

2016-01-01

In anticipation of a rapid increase in the number of civil Unmanned Aircraft System(UAS) operations, NASA is researching prototype technologies for a UAS Traffic Management (UTM) system that will investigate airspace integration requirements for enabling safe, efficient low-altitude operations. One aspect a UTM system must consider is the correlation between UAS operations (such as vehicles, operation areas and durations), UAS performance requirements, and the risk to people and property in the operational area. This paper investigates the potential application of the International Civil Aviation Organizations (ICAO) Required Navigation Performance (RNP) concept to relate operational risk with trajectory conformance requirements. The approach is to first define a method to quantify operational risk and then define the RNP level requirement as a function of the operational risk. Greater operational risk corresponds to more accurate RNP level, or smaller tolerable Total System Error (TSE). Data from 19 small UAS flights are used to develop and validate a formula that defines this relationship. An approach to assessing UAS-RNP conformance capability using vehicle modeling and wind field simulation is developed to investigate how this formula may be applied in a future UTM system. The results indicate the modeled vehicles flight path is robust to the simulated wind variation, and it can meet RNP level requirements calculated by the formula. The results also indicate how vehicle-modeling fidelity may be improved to adequately verify assessed RNP level.

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

DOT National Transportation Integrated Search

2008-03-31

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

User requirements for NASA data base management systems. Part 1: Oceanographic discipline

NASA Technical Reports Server (NTRS)

Fujimoto, B.

1981-01-01

Generic oceanographic user requirements were collected and analyzed for use in developing a general multipurpose data base management system for future missions of the Office of Space and Terrestrial Applications (OSTA) of NASA. The collection of user requirements involved; studying the state-of-the-art technology in data base management systems; analyzing the results of related studies; formulating a viable and diverse list of scientists to be interviewed; developing a presentation format and materials; and interviewing oceanographic data users. More effective data management systems are needed to handle the increasing influx of data.

Functional and performance requirements of the next NOAA-Kasas City computer system

NASA Technical Reports Server (NTRS)

Mosher, F. R.

1985-01-01

The development of the Advanced Weather Interactive Processing System for the 1990's (AWIPS-90) will result in more timely and accurate forecasts with improved cost effectiveness. As part of the AWIPS-90 initiative, the National Meteorological Center (NMC), the National Severe Storms Forecast Center (NSSFC), and the National Hurricane Center (NHC) are to receive upgrades of interactive processing systems. This National Center Upgrade program will support the specialized inter-center communications, data acquisition, and processing needs of these centers. The missions, current capabilities and general functional requirements for the upgrade to the NSSFC are addressed. System capabilities are discussed along with the requirements for the upgraded system.

Requirements and Solutions for Personalized Health Systems.

PubMed

Blobel, Bernd; Ruotsalainen, Pekka; Lopez, Diego M; Oemig, Frank

2017-01-01

Organizational, methodological and technological paradigm changes enable a precise, personalized, predictive, preventive and participative approach to health and social services supported by multiple actors from different domains at diverse level of knowledge and skills. Interoperability has to advance beyond Information and Communication Technologies (ICT) concerns, including the real world business domains and their processes, but also the individual context of all actors involved. The paper introduces and compares personalized health definitions, summarizes requirements and principles for pHealth systems, and considers intelligent interoperability. It addresses knowledge representation and harmonization, decision intelligence, and usability as crucial issues in pHealth. On this basis, a system-theoretical, ontology-based, policy-driven reference architecture model for open and intelligent pHealth ecosystems and its transformation into an appropriate ICT design and implementation is proposed.

50 CFR 660.14 - Vessel Monitoring System (VMS) requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 50 Wildlife and Fisheries 13 2014-10-01 2014-10-01 false Vessel Monitoring System (VMS) requirements. 660.14 Section 660.14 Wildlife and Fisheries FISHERY CONSERVATION AND MANAGEMENT, NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION, DEPARTMENT OF COMMERCE (CONTINUED) FISHERIES OFF WEST COAST STATES...

Comparison of A-SMGCS Requirements with Observed Performance of an Integrated Airport CNS System

NASA Technical Reports Server (NTRS)

Young, Steven D.

1997-01-01

The International Civil Aviation Organization (ICAO) has recently drafted a reference document describing the operational requirements for Advanced Surface Movement Guidance and Control Systems (A-SMGCS). During the summer of 1997, NASA, the FAA, industry, and academia partners demonstrated a holistic system approach that has the potential to meet many of the proposed A-SMGCS requirements. An assessment of the field tested system and data resulting from the field testing is presented to determine its compliance with A-SMGCS requirements. In those areas where compliance was not demonstrated, a recommendation is presented suggesting further research or a modification of the system architecture.

Course Ontology-Based User's Knowledge Requirement Acquisition from Behaviors within E-Learning Systems

ERIC Educational Resources Information Center

Zeng, Qingtian; Zhao, Zhongying; Liang, Yongquan

2009-01-01

User's knowledge requirement acquisition and analysis are very important for a personalized or user-adaptive learning system. Two approaches to capture user's knowledge requirement about course content within an e-learning system are proposed and implemented in this paper. The first approach is based on the historical data accumulated by an…

Analysis of data systems requirements for global crop production forecasting in the 1985 time frame

NASA Technical Reports Server (NTRS)

Downs, S. W.; Larsen, P. A.; Gerstner, D. A.

1978-01-01

Data systems concepts that would be needed to implement the objective of the global crop production forecasting in an orderly transition from experimental to operational status in the 1985 time frame were examined. Information needs of users were converted into data system requirements, and the influence of these requirements on the formulation of a conceptual data system was analyzed. Any potential problem areas in meeting these data system requirements were identified in an iterative process.