Descriptive documents

The requirements of clause 4.5 therefore apply to policies and practices, derived documents, and external documents that are prescriptive but not descriptive. The descriptive documents are covered by clause 4.16 on quality records. 

The refinement relation between the two levels of description documents this mapping. The state chart shows how the parameters and state changes in the detailed action sequence translate to the abstract action and its parameters. In this example we use a counter attribute to define this mapping it is an attribute of a specification type representing a restocking in progress at the more detailed level (Pattern 14.13, Action Reification). 

All laboratory members should accept and recognize the individual s responsibility and authority. This responsibility and authority of each individual is defined in job description documents, which are agreed with the interested parties and communicated to all relevant laboratory sectors. 

It is a fact of experience that pressurized apparatus should be fitted with a control and monitoring unit to ensure an appropriate purging procedure and maintain the protective gas flow and pressure differential which guarantee the safe operation of the apparatus. Purely hand-operated purging procedures are susceptible to errors and slips, and a permanently man-operated flow or pressure control for the protective gas is too remote from all basic principles of economic efficiency. Besides, the standards for pressurization contain requirements for safety devices for zone 1 apparatus (EN 50016) and for type px, py and pz-apparatus (IEC 60079-2, see Table 6.7). So, a safety device, or better a control and monitoring unit, is an essential part of a p-apparatus especially for Group I application and for zone 1. It is by no means an imperative that the control unit forms an integral part of the apparatus or has been made by its manufacturer pressurized apparatus without a control unit shall be marked X and the description documents shall contain all necessary information required by the user to ensure conformity with the requirements of the p-standards. 

Since the space available for marking is rather limited on small apparatus, the descriptive documentation and/or the certificate should be referred to for a detailed Ex-protection specification. 

There are a number of very good books which deal with job analysis methods (e.g., Brannick et al. 2007 Prien et al. 2009 Wilson 2012), and also very good guidelines on how to avoid error in job analysis data (e.g., Morgeson and Campion 1997). In general, the aim of job analysis is to produce two documents, a job description and a person specification. The job description document contains aU of the information relating to a job s roles and tasks, a description of the context within which these are performed, and performance expectations, and benefits. Where appropriate, the job description should also include a specific section on the job safety risks and hazards (see Fig. 3.1 in Chap. 3). The other main document that... 

Each approach to profiling a job s safety risk will provide a unique perspective. Furthermore, collectively the data from these assessments will reflect a job s safety risk profile. Chapter 3 discusses how information on a job s safety risks should be included in a job description document (see Fig. 3.1). For any specific job, the safety risk profile assessment can show a range from a normal and expected safety risk level, through to an extreme and unexpected safety risk. That is, while an organization may think that its management systems are controlling a job s safety risks to a normal and expected level, reality maybe very different. Of course, it would be particularly risky to bring a new employee into a job that has safety risks beyond the normal and expected level. 

Narrative In an analytical report, a descriptive documentation of any problems encountered in processing the samples, along with corrective action taken and problem resolution. 

Input data for preparation of the PHL include project description documents (narrative descriptions, sketches, preliminary drawings, artists concepts, drawings or photographs of existing similar products, and analytical trees), historical data (safety, reliability, and loss data and accident reports from similar end products and/or components), and any other relevant studies or research. 

All available project description documents and relevant historical data are used in preparing the PHL. 

Detailed project description documents and drawings are required to perform an SSHA. Additionally, relevant codes, standards, and regulations, the PHL, and the PHA for the projects should be available. Access to lessons learned and reliability data is also needed. 

Analytical trees can be used in a variety of ways in the system safety effort. The most common application of analytical trees in current system safety programs is probably the use of fault trees for fault tree analysis (FTA). However, analytical trees can also be used as planning tools, project description documents, status charts, and feeder documents for several hazard analysis techniques (including fault tree analysis). Analytical trees can be multipurpose, life cycle documents and represent one of the most useful tools available to managers, engineers, and safety professionals. 

Positive or objective trees are extremely useful planning tools. In the early stages of a project, they can be used to outline project requirements and list alternatives. As decisions are made, they evolve into graphic checklists and also make excellent status charts and project description documents. 

Analytical trees make excellent project description documents because they are relatively easy to construct and easy to understand. Many end users and some safety professionals, engineers, and managers are not skilled in reading blueprints, electrical schematics, or other technical documents. The analytical too is an excellent means for communicating project information within a system safety working group. 

If an analytical tree is not used, in addition to defining the system and clarifying the scope in terms of breadth (limits of resolution) and depth (indenture levels), a block diagram or other project description document may be required. 

Additionally, traditional project description documents (such as analytical... 

The first step in performing a fault tree analysis is to collect the appropriate project description documents, existing hazard analyses, and guidance documents and carefully review them to determine the limits, scope, and ground rules for the FTA.This review includes defining the system to be analyzed, the depth or indenture levels to be included in the effort, and, of course, the nature of the undesired event or failure to be studied. 

Product description In a project, the product description documents the characteristics of the physical product, service, or result sought in pursuing the project. It is established prior to project initiation and should be embellished as the project progresses. The product description should have sufficient detail to support project planning throughout the project. (Adapted from PMBOK Guide— 2000 edition )... 

Be fair and consistent — Give all prospective candidates an equal opportunity for selection. Prepare a job description documenting the essential functions and minimum qualifications for the position. 

A procedure in which hazardous wastes are identified as they are produced and are followed through further treatment, transportation, and disposal by a series of permanent, linkable, descriptive documents. 

System testing is defined as when the development team is in charge of testing the entire system from the point of view of the functions the software is supposed to fulfill. The validation process is completed when aU tests required in the system test plan are satisfied. The development team will then produce a system description document. 

---