Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...

Articles Figures Tables About

Requirements and Specifications

Lubricant requirements and specifications. The development of North American classification systems for the SAE began in 1911 on the basis of viscosity alone. In 1947, the API (American Petroleum Institute) developed a performance classification system for engine oils in terms of regular, premium and heavy duty lubricants. By 1952, the API and ASTM (American Society for Testing and Materials) further advanced the system to generally classify engine oils. In 1970, the TRIPARTITE of API, ASTM, and SAE was established to manage a completely new API classification system, see Fig. 2.12 (Haycock, 1993). [Pg.57]

Since the development of performance specifications from the 1930s and beyond, the API, Militaiy, OEM (Original Equipment Manufacturer) and European ACEA requirements have reflected the introduction of the new engine technologies as well as the performance of lubricants in the field. The implementation of the new performance requirements will be driven by field experience for realistic correlation with laboratory test tools. [Pg.58]

The increase in the number of performance classifications for passenger car and commercial diesel grades has accelerated dramatically from the 1930s (when 3 classifications were in place) through the 1980s (with over 25 active classifications in US and Europe). This increased complexity reflects the diverse market of vehicles and the specific performance requirements demanded by OEMs. [Pg.58]

There are seventeen engine service classifications as follows (Booser, 1997 Pirro and Wessol, 2001 Wills, 1980)  [Pg.58]

The API classification system is open ended, so that additional classifications can be added when needed. There is a relationship between API engine service classifications and MIL, OEM and ACEA classifications of the oil quality standards previously outlined. These relationships are shown in Table 2, [Pg.58]

The basic requirements for the CBMS II are to reliably detect and identify with sufficient sensitivity and selectivity both CWA and BWA in point detection and reconnaissance missions, in order to be deployable in wheeled reconnaissance vehicles and be operable by nontechnical personnel wearing, at the extreme, MOPP IV protective gear. Contrary to the usual practice for a military detector system, the CBMS II does not have its own requirements document. Instead, the requirements and specifications for the CBMS II are based on the detector requirements of the host platforms in which it will be deployed. These requirements are described in terms of performance, as opposed to the usual practice of being enumerated in volumes of detailed specifications. As is usual for a complex multiyear program, the requirements changed over the course of the CBMS II program as the requirements for the host platforms evolved. [Pg.73]

The CBMS II is to be deployed aboard wheeled reconnaissance vehicles. The platforms include a light armored vehicle, the US Army XM1135 Stryker Nuclear, Biological, Chemical Reconnaissance Vehicle (NBCRV),23 and two vehicles for the US Marine Corps Joint Services Lightweight Nuclear, Biological, Chemical Reconnaissance System (JSLNBCRS) 24 the HMMWV and a wheeled, light armored vehicle very much like the XM1135 Stryker. Consequently the volume, mass, and power available to the instrument are limited. Table 4.1 lists the current physical specification and objective requirement for each parameter. [Pg.73]

To be a deployed military detection system, the CBMS II must survive storage under severe conditions and reliably start up and operate under a wide range [Pg.74]

Resistance to physical shocks and vibration required careful attention to selection of rugged components and to securing electrical and vacuum systems, wiring, connectors, components, and boards. Chemical ionization (Cl) was used for the first time in a fieldable military detector because of the advent of rugged turbomolecular pumps capable of handling the gas load from the Cl reagent. [Pg.75]

The CBMS II must be highly automated in all aspects of operation because the soldiers using the unit are not academically trained in mass spectrometry. [Pg.75]


Review the motor requirements and specifications to make sure that all the unnecessary, nonstandard, special features have been eliminated. Each special requirement such as nonstandard mounting dimensions and nonstandard bearings should be eliminated unless it can be demonstrated the feature is cost effective. In actual practice, many special features are specified because of an isolated case of trouble that occurred years ago. Likewise, some special features may become obsolete through changes in refinery or chemical plant practice or through improved manufacturing techniques. [Pg.257]

Accurate GDMS analysis has required the development of analytical procedures appropriate to the accuracy and detection limits required and specific to the mate-... [Pg.612]

The ability of a system to meet its requirements and specifications must be demonstrated and documented before it can be accepted and fielded as a military system. Performance tests of a military detector system typically are performed by the contractor (Contractor Tests) and by the government (Government Tests). The former often are witnessed by government personnel who independently report on the methodology and results. Contractor testing is conducted at contractor facilities and at government facilities (but... [Pg.79]

For a bit of perspective, a recent study by the Standish Group found that the 83% of projects that either failed or seriously missed the target in time, cost, and function blamed a large portion of their problems on lack of user input and involvement, unclear requirements and specifications, changing requirements, and lack of executive support. [Pg.529]

Pattern 14.30, Specify components (p.615) motivates the extra effort involved in separating specification of expected behavior from its implementation. Pattern 14.31, Bridge requirements and specifications (p.617) outlines a pragmatic view of requirements, as stated and understood by a user, and the more precise specifications that a developer might use to understand what must be built. Pattern 14.32, Use-case led system specification (p.619) explains why a use-case driven approach to requirements capture is prudent, but should always be interleaved with tools of more precise specifications. [Pg.602]

Figure 15.1 Typical user/analyst cycle with requirements and specification... Figure 15.1 Typical user/analyst cycle with requirements and specification...
Requirements and specification cycle. Requirements statements often look quite solid when you first look at them but as soon as you start a specification, gaps and dislocations become painfully apparent. [Pg.607]

JacksonM95] Jackson, M. 1995. Designations. In Software Requirements and Specification A Lexicon of Practice, Principles, and Prejudices. Reading, Mass. Addison Wesley Longman. [Pg.734]

The three tenders submitted were all of a very high standard and achieved Orica s requirements and specifications. The tender selected was therefore based on lowest net operating cost and was awarded to Kvaerner Chemetics in conjunction with Chlorine Engineers Corporation for electrolyser supply. Kvaerner Chemetics also separately contracted Kvaerner Process Australia to provide local construction management and some local design expertise. [Pg.149]

Satisfactory performance of the fireproofing material over its expected lifetime depends on the user s and the applier s knowledge of materials and application techniques and on continuing inspection by qualified personnel. Specifically, once a fireproofing system has been chosen, it is imperative that personnel involved in each phase of the project be familiar with the relevant aspects of the manufacturer s requirements and specifications. [Pg.154]

The first edition of Automatic Chemical Analysis was published in 1974 and was written in coUahoration with the late Jim Foreman. It was well received and became a set course book in many universities. Its aim was to provide a basic grounding in the subject and to cover the wider issues of economic assessments, educational requirements and specification of systems. TTiere are now other books on laboratory automation in print [1,2], but none of these will help potential users of automation to evaluate the economic viability of a project indeed, they may even put them off. The other hooks are scholarly rather than practical. [Pg.8]

A computer system is composed of software and hardware, equipment, a processor, and a user, and it is used to execute a specific procedure. Regardless of whether the computer system is developed in-house or by a contractor or purchased off the shelf, establishing documented end-user requirements is extremely important for computer systems validation. Without first establishing end-user needs and intended use, it is virtually impossible to confirm that the system can consistently meet them. Once established, it should obtain evidence that the computer system implements those needs correctly and that they are traceable to system design requirements and specifications. It is important that the end-user requirements specifications take into account predicate rules [12]. [Pg.830]

To be successful, an organization must offer services and products that meet a well-defined purpose or need. A company must satisfy its users, including delivery time scales. It should be ensured that applicable standards, statuary requirements, and specifications are in compliance. The offered product or services should be within budget and provide value. Companies should ensure that their total operations are carefully reviewed before implementation to reduce the occurrence of error and quickly correct any error inadvertently made. Control should be demonstrated on changes through proactive communication and feedback loops between the company and external interfaces. Training needs must be identified to promote efficiency and cost-effectiveness. [Pg.8]

Environmental requirements and specifications must be documented and assurance provided that the environmental parameters are within the range specified by the manufacturer. [Pg.66]

Be vigilant and stay fully apprised of new developments by actively following regulatory actions imposed upon other firms. This allows a firm to anticipate potential new requirements and specific areas of interest during inspections. [Pg.119]

Reagents and standards—inventory all reagents, standards, and supplies to determine acceptability with method requirements and specifications. [Pg.172]

New lubricant requirements and specifications of passenger car motor oils. [Pg.60]

With the array of molecular configurations, possible formulation procedures, physiological requirements, and specific responses found among the organic herbicides, the most useful scheme of classification to the chemist is one that will place herbicides in groups having similar chemical properties. One such classification is shown in Table VII. [Pg.24]

Components used and approved for human food may also be considered as potential ingredients for certain applications. Hazardous components cannot be used at all or have to be removed during the process. Special conditions (see Registration Requirements and specific guidelines on this topic) apply to the use of starting material of human or animal origin to avoid the presence of adventitious agents in the final product. [Pg.55]

Requirements traceability should also ease inspections by facilitating the rapid location of any specification-to-test information requested. For many organizations, this forward tracking of requirements can be quite cumbersome if they rely solely on reverse tracking offered by test documentation referencing requirements and specifications. [Pg.117]

Lighting system drawings showing arrangement of lighting panels, lighting requirements, and specific details as required. [Pg.170]

All software and computer systems used in accredited and GLP- and GMP-regulated analytical laboratories for the generation and analysis of critical data should be retrospectively evaluated and formally validated. As a first step, the user should list all systems in the laboratory, assess the need for validation for each system and develop an implementation plan. For validation of individual systems, the validation plan should describe user requirements and specific validation steps. It should also list the person or persons responsible for each step as well as the criteria that must be met to achieve validated status. [Pg.54]


See other pages where Requirements and Specifications is mentioned: [Pg.287]    [Pg.296]    [Pg.67]    [Pg.170]    [Pg.185]    [Pg.73]    [Pg.75]    [Pg.77]    [Pg.120]    [Pg.606]    [Pg.405]    [Pg.33]    [Pg.287]    [Pg.56]    [Pg.156]    [Pg.11]    [Pg.388]    [Pg.561]    [Pg.141]    [Pg.136]    [Pg.54]    [Pg.196]    [Pg.120]   


SEARCH



Ammonium Nitrate US Specification Requirements and Tests

Ammonium Nitrate, US Military Specification Requirements and Tests

Requirement specification

Requirements and Design Specification

Specific Health and Environmental Requirements

© 2024 chempedia.info