Searching and Retrieving Errors

Searching errors in the system is done according to specified fields in a form specifying error data. Figure 6-17 illustrates a screenshot from the system in searching errors. The option to select an error limit is not visible (temporarily removed) due the small amount of data.

IT for Learning and Acquiring of Work Knowledge among Production Workers

82

Searching errors is done according to the following instructions and options for entering data:

• Select a tool from the combo box. The field is mandatory.

• Once can restrict the searching process by selecting (a) only search errors in tool in relation to equipment, (b) a time interval by specifying date from and date to, and (c) if the search is to be or not to be restricted to the current user domain (i.e. based on the current user).

Pressing the search result button commence the searching process based on the options selected by the user. Figure 6-18, Figure 6-19, and Figure 6-20 depicts screenshots from the system concerning the search results7. The results can be viewed as table, form, or as diagram. The view as table and form option views the same error data in different format. The errors shown are sorted according their relevance (the error with the highest relevance comes first and the error with the next highest relevance comes second and so on). The point in having different views is to view the results in different ways dependent on the amount of errors shown. In case of many errors, it may be more readable to select view as table and in case of few errors, it may be more readable to select view as form. The view as diagram option is a way to illustrate the errors’ relevance in relation to each other graphically. Figure 6-21 is a screenshot from the system concerning the error report. Selecting report prints out an errors report on a printer consisting of a diagram and an error list.

Figure 6-18 Retrieving errors –view as table

7 _{The search results have to some extent been manipulated by letting all errors be related to the same tool (i.e. by}

manipulating the tool number). This is not the case when looking at the original errors. The reason for such manipulation is that there at this stage is a wide range of errors concerning different tools and there is a quite large amount of tools. The purpose of the search results screenshots is to illustrate how the system works. In that way, it might be more understandable by also having data showing how errors are retrieved when workers search errors.

6 Information Technology for Learning and Acquiring Work Knowledge

Figure 6-19 Retrieving errors –view as form

IT for Learning and Acquiring of Work Knowledge among Production Workers 84 ODR-diagram Error: Delayed set up tool. Priority:3. Regarding Ställare

Error: Insuff icient instructions for mounting tool on press. Priority:1. Regarding Ställare Error: Short sticks. Do not run

pillow to th e bottom.. Priority:2. Regarding

Ställare

Error: The upper part. How is the

upper part located?. Priority:2. Regarding

Ställare

Error: What is the front and back on

the tool. Priority:2. Regarding

Ställare

Error: Looking for suspensions.

Priority:4. Regarding

Ställare

Disturbances tool: 17649 Date: 2000-01-01 - 2003-10-14 KOD-system version 2.0

. Error: Delayed set up tool Frequency

2 Priority 3 User domain Ställare Cause

Countermeasure Press Eq Sign Date Time

# 1

Short of hoop and suspenders Create new hoop and

suspenders 2511 nian 2001-06-19 10:46:0

1

Short of hoop on top of tool Create new hoop.

Threaded holes exists 2512 frno 2001-06-19 10:50:0

2

Figure 6-21 Error report

6.6 Chapter Summary

In summary, the development process and the information system artifact have the following characteristics:

• The object for explicit learning support is errors in tools in relation to setters’ and operators’ work activities in mounting and operating presses due to such errors impact on the company’s business.

6 Information Technology for Learning and Acquiring Work Knowledge

• The system is based upon principles for detecting, collecting and valuing errors related to tools used by production workers when they do work tasks.

• The system has been developed by developing prototypes that continually have been reviewed and evaluated by workers and management during three so called development tracks.

• The first track was about to grasp the error concept and how errors can be handled. It was also about to assess the value of handling errors impact on the company’s business.

• The second track was about to further outline the error concept in more detail on the basis of how production workers conceived errors. It was also about pinpointing usage situation to seek to integrate use of the system in running work.

• The third track was also about to further refine the error concept. It was also abut to further assess the value of handling errors relative to the time workers may come to put in using the system relative to other work tasks (i.e. producing articles) and the company’s business. This brought the development process to a halt and has postponed the process and the system has not yet been implemented and tried out at larger scale as planned. Connections between the system and other systems in the company were also investigated.