HS.2.7 Usability Engineering Integration

Purpose : To facilitate information exchange and communication about system operability

Successful outcomes:

1. HF data are provided in suitable format(s) for use by project stakeholders
2. potential risks arising from operability issues related to the product system and its context are identified
3. the methods and techniques used in operability processes are matched to the needs of project stakeholders

For each of the activities below please select one of the following options:

No No - this doesn't happen

Partially This happens occasionally but there is no consistency

Largely Yes this usually happens

Fully This is recognised as the way we do business

Activity

N

P

L

F

1. All project stakeholders develop a common language for HS issues. For example, speaking the same language as system designers, safety engineering and specialist engineering disciplines

2. The context of use is presented in a comprehensible form with a description of the real operational environment and its implications.

3. A systems approach to engineering is promoted.

4. Documents and working groups are used to control dependencies between activities that address operability issues and other project activities.

5. Common data formats and exchange procedures are used between operability and other project activities. e.g. common checklists, review formats, risk and issue management

6. Human aspects of the design are presented in a form suitable for trade-off studies

7. Personnel costs or performance are presented in a form that can be traded off against equipment costs or performance.

8. User evaluations produce easily understood feedback.

9. Methods and techniques are matched to the way the organisation works.

10. Tools and methods already in use within the organisation are used where possible.

11. Engineering changes, requirements changes and configuration changes are reviewed for operability impact.

12. There is early identification of situations requiring trade-offs between operability and other specialist engineering (e.g. safety, ILS).

13. There is early identification of situations requiring trade-offs between operability and other mainstream engineering (e.g. time and cost).

14. All affected parties are notified when a particular design feature is found to affect training, support, documentation or procedures

15. Operability people work as a team with safety specialists e.g. participate in HAZOPs.