Task-specific descriptions

Job steps and task-specific descriptions Nonroutine (NR) task Risk assessment (RA)... 

Job steps and task-specific description NR RA Existing and potential hazards and/or consequences of exposure At-risk events and preventive measures RR... 

An important point to remember is that if a job has fewer than 3 steps then aJHA may not be needed. If it has more than 10-15 steps then more than one JHA may be required. The objective is to keep the job flow clear and concise and not to make the JHA overly compHcated or it will not be used (Conducting a Job Hazard Analysis (JHA),n.d.) (Refer to Figure 11.1 for details on how to apply Job Steps and Task-Specific Description ). 

The job steps and tasks-specific description will remove the need to review the entire JHA when only a few of the tasks are being performed. The leadership team, employee, or anyone about to perform the job can quickly scan the JHA for the nonroutine tasks noted as an X and review the specific hazards associated with the task before starting work. 

Describe the job steps and task-specific description section of the JHA. 

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... 

Ideally, a specification is only a description of what a program does, and an explanation of how to use that program. A specification should faithfully capture the informal intentions. Such specifications are totally declarative in that they don t express how the program actually works, and they thus don t bias the programmer in her/his task. Specifications have been alternately required to be not (necessarily) executable [Hayes and Jones 89], (preferably) executable [Fuchs 92ab], and so on... 

The reason for an Exposition is so that there is a description of the system showing how it works and how it controls the achievement of quality. This is different from the policies and procedures. The policies are a guide to action and decision and as such are prescriptive. The procedures are the methods to be used to carry out certain tasks and as such are task related. They need to be relatively simple and concise. A car maintenance manual, for example, tells you how to maintain the car but not how the car works. Some requirements, such as those on traceability and identification, cannot be implemented by specific procedures although you can have specific policies covering such topics. There is no sequence of tasks you can perform to achieve traceability and identification. These requirements tend to be implemented as elements of many procedures which when taken as a whole achieve the traceability and identification requirements. In order that you can demonstrate achievement of such requirements and educate your staff, a description of the system rather than a separate procedure would be an advantage. The Exposition can be structured around the requirements of ISO/TS 16949 and other governing standards. It is a guide or reference document and not auditable. 

Documentation is structured around specifications and implementation and their refinement and import relationships. A user manual—a description of how a user accomplishes tasks by using the system(s)—is a particular form of documentation associated with a refinement how the abstract business model and actions are realized by more-detailed actions performed by the users and systems. Test specifications are also associated with refinement relationships. The rules for system architecture are documented in a package that specifies the patterns and frameworks that will be used in other packages that import it. 

As a starting point in the description of the solid intermetallic phases it is useful to recall that their identification and classification requires information about their chemical composition and structure. To be consistent with other fields of descriptive chemistry, this information should be included in specific chemical and structural formulae built up according to well-defined rules. This task, however, in the specific domain of the intermetallic phases, or more generally in the area of solid-state chemistry, is much more complicated than for other chemical compounds. This complexity is related both to the chemical characteristics (formation of variable composition phases) and to the structural properties, since the intermetallic compounds are generally non-molecular in nature, while the conventional chemical symbolism has been mainly developed for the representation of molecular units. As a consequence there is no complete, or generally accepted, method of representing the formulae of intermetallic compounds. 

---