Tasks identifying

This task identifies characteristics of each source and calculation methods for load calculation. See Fig. 3.7. 

For these tasks identify likely internal and external error modes using flow charts and methods described in Chapter 6. 

A number of tasks can be identified which community teams hold in common whether their clients are the mentally handicapped, drug or alcohol misusers. Not every team would necessarily see every task identified as part of their role, and the emphasis laid on particular tasks will vary from team to team and sometimes within a team itself. It has already been noted that as teams develop the nature of their roles may also change. 

Figure 1.22 Elementary perceptual tasks identified by Cleveland and McGill (1984a). Reprinted with permission from The Journal of the American Statistical Association. Copyright 1984 by the American Statistical Association. All rights reserved.

In moving toward a system design, once tasks have been aneilyzed rmd associated mental models characterized, designers ceui use this knowledge to address the relationship between the human and the interactive system. Task tillocation is a process of assigning the various tasks identified via the... 

Generic intermediate level One of three major hierarchical levels for systems and tasks identified in the elemental resource model. The generic intermediate level represents new systems (e.g., postural maintenance system, object gripper, object lifter, etc.) formed by the combination of functional units at the basic element level (e.g., flexors, extensors, processors, etc.). The term generic is used to imply the high frequency of use of systems at this level in tasks of daily life (i.e., items at the high level in the ERM). 

It is fundamental for assessing human error in systems analyses to identify and describe the human acts with importance for the event sequence under analysis (qualitative assessment). This corresponds to the task analyses, which are characteristic of ergonomic studies. Firstly, the important actions, the moment in time at which they are required and the time period available for their execution have to be determined. Furthermore, the requirements for the action, the information necessary, respectively available, the possibilities of correction in case of omission or faulty execution must be estabhshed. Additionally, other factors of important influence on human reliabihty such as the state of knowledge on the process in question, ergonomically favourable or disadvantageous layout of the workplace, the tools or the environment are identihed. On the basis of this task analysis reliability data (normally failure probabilities on demand) are assigned to the tasks identified. They stem from existing data collections (cf. Table 9.21). 

Establishing correct safety procedures is when a manager analyzes certain tasks and writes safe work procedures for performing the work. Based on risk assessments, the tasks can be risk-ranked and the critical tasks identified. This will help prioritize the writing of procedures. Specific inspection procedures, equipment maintenance procedures, internal audit procedures, and other procedures are vital components of the system. 

The standard includes procedures for dealing with software that contributes to risks in a system. There are tables for assessing software criticality. The standard also lists tasks used selectively in specific system safety projects. Each task identifies its purpose, description, and details. 

The tool developed for functional test, properly configured with suitable workflows, can stimulate the system under test in order to provide evidence of stability. Workflows for Stress testing have been defined from the high-level tasks identified for the functional tests by parallelizing multiple high-level tasks invoked from a variety of users and abbreviating to the minimum the delay between sequential invocations. 

Link training needs to competencies required for performing the team tasks identified in previous step. 

Identify interdependencies among tasks Step 3 requires an understanding of how projects unfold, that is, how tasks are related. It is also a reality check on Step 1. For example, if a task identified in Step 1 does not feed into another task, then the earlier task is not needed. Or if we find that a task could not be started because we would be missing some important information, then we must have omitted a necessary upstream task. The first three steps encourage us to carefully think through our project. 

Table 2. Most prevalent accident mechanism (within the five tasks identified in Table 1). ...

Each contractor shall review the project constructor s project hazard identification report. Potentially hazardous tasks identified by a contractor that are not addressed in the report shall be reported by that contractor to the project constructor. 

Each contractor shall develop a project specific safety and health plan. The plan shall include provisions for addressing complex tasks and other project specific safety and health issues such as potentially hazardous tasks identified during the contractor s project hazard identification process. 

As your first task, identify the kinds of activities and accomplishments you wish to recognize. You may want to brainstorm an initial list of tentative criteria, then ask several design team members to use this list to develop a more complete list of safety contributions that you might want to recognize and sort them into different levels. Figure 11.4 provides an example of possible criteria that might be appropriate for five levels. 

The Regulations establish a clear hierarchy of measures to obviate the risk of injury when performing manual handling tasks. To summarise, manual handling operations which present a risk must be avoided so far as is reasonably practicable if these tasks cannot be avoided, then each task must be assessed and as a result of that assessment, the risk of injury must be reduced for each particular task identified so far as is reasonably practicable. 

Level of protection. The equipment must provide both the kind and degree of protection needed for the potential hazard as well as the particular task identified above. The wrong equipment will create an additional hazard by instilling a false sense of security in the user. 

The PVOL dynamic architecture (and specifically LN3) thus rests on six tasks identified below according to decreasing priorities ... 

For each protective task identified whose operation may be controlled by manual means from the outset or after initiation, the following should be documented ... 

Determine operator behaviour - For each of the tasks identified in Step 2, determine the required operator s behaviours. Three types of behaviours are considered namely, skill-based, rule-based or knowledge-based behaviour. These behaviours are discussed in Sections 9.3. 

The probability of human error is considered for each of the task carried out by determining the type of human behaviour required to carry out the task successbilly. Using the generic human error data by Rasmussen (Table 9.2), each task is assigned the operator behaviour and the generic error probability. This data is then used to compare each task against the others to determine the Level Three matrix. The various tasks identified in this example and the associated generic data are provided in Table 9.8. 

Analyze job data on steps and tasks, identified hazards, and associated risk assessments, and recommended controls. 

---