Integration of groupware with the integrated quality control methodology via facilitated work sessions

Abstract

A network application for automatically formatting and printing documents to be used as planning manuals to be used by company personnel for improving quality control. The outputted documents can also be educational manuals for dispersing among organizational personnel common information for integrated strategic planning for quality control improvement. Facilitated collaborative work sessions among work groups inputting and sharing comments and ideas provide starting data to the network application.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. .sctn. 120 as a continuation-in-part application of U.S. patent application Ser. No. 08/229,967, filed Apr. 19, 1994, entitled "The Application of GroupWare to ISO 9000 Registration via Facilitated Work Sessions" and now abandoned.

U.S. patent applications Ser. No. 08/248,617, entitled "The Integration of GroupWare with Activity Based Management via Facilitated Work Sessions", and Ser. No. 08/248,616, entitled "The Integration of GroupWare with the Quality Function Deployment Methodology via Facilitated Work Sessions", filed concurrently herewith and now abandoned, are assigned to the same assignee hereof and contains subject matter related, in certain respect, to the subject matter of the present application. The above-identified patent applications are incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to a computer network application for sharing, combining, formatting, and printing into a predetermined document format information gathered from a number of users or work groups formed within an organization to improve quality control. The application is implemented in a networked, multi-user environment. In particular, this invention effectuates the documentation of an organization's quality baseline model via facilitated, computer-based, cooperative work sessions, thereby streamlining the improvement process for its quality control plans.

2. Description of the Prior Art

The Integrated Quality Control (IQC) methodology is a difficult and time-consuming process for any organization. The typical approach is to assign groups of people to the IQC deliverables. However, a lack of tools means excessive resource and time is spent before the organization has its quality baseline completed. Facilitated work sessions using GroupWare tools were developed in response to this need.

SUMMARY OF THE INVENTION

This invention comprises a network application for manipulating information gathered in a multi-user collaborative environment in order to conduct Integrated Quality Control sessions. The information gathered in the multi-user environment includes input such as comments and ideas from the process improvement team members. These are input into computer storage to be accessed by special programs for formatting and printing in predefined formats. GroupWare tools allow the team members to quickly organize their ideas, reach consensus, and make decisions. Process flows, opportunity tables, quality control plans, reaction plans, and indices are programmed for automatic output. User intervention is unnecessary after the information gathering session and before the printing of the documents, which takes place immediately and automatically.

The initial facilitated work sessions document the organization's manufacturing process flows. After that, the other facilitated work sessions develop the reaction plans and quality control plans. Opportunities are documented at any time during any of the facilitated work sessions. The indices provide a scorecard to measure the organization's quality level and serve as a benchmark for continuous improvement.

The participants in the information gathering sessions are prompted to identify the steps in a manufacturing process or opportunities for improvement. Networked PC's and workstations facilitate the information gathering among the work groups, group editing of the data gathered, and group approval of the final edited group responses. Commercially available group decision support tools fit very well with these information gathering sessions. Commercially available database tools work well for storage of and access to the data that is collected in these information gathering sessions. Commercially available word processors and flowcharting tools can further manipulate the data collected into other useful formats. Specialized bridge programs automate the manipulation and movement of data between these various tools.

Other features and advantages of this invention will become apparent from the following detailed description of the presently preferred embodiment of the invention, taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a representation of the overall system configuration and the various applications available on the file server.

FIG. 2 is a sample process document.

FIG. 3 is a sample opportunity table.

FIGS. 4a-f are sample quality control plans.

FIGS. 5a-f are sample indices.

FIG. 6 is a sample reaction plan.

FIG. 7 is a functional flowchart of the session for documenting the scope.

FIG. 8 is a functional flowchart of the session for documenting processes and opportunities.

FIG. 9 is a functional flowchart of the session for developing quality control plans and indices.

FIG. 10 is a functional flowchart of the session for developing reaction plans.

FIG. 11 is a pseudocode implementation of the TeamFocus Export bridge program.

FIG. 12 is a pseudocode implementation of the IQC bridge program.

FIGS. 13a-g are sample screens from the IQC bridge program user interface.

DESCRIPTION OF THE PREFERRED EMBODIMENT

Overview

Integrated Quality Control is a difficult and time-consuming process for any organization trying to document process flows and establish baseline metrics. The typical approach is to assign groups of people to the IQC deliverables. However, a lack of tools means excessive resource and time is spent before the organization has its quality baseline completed. The "process improvement teams" go about the task of documenting process flows, reaction plans, and quality control plans in the traditional manner, which requires many iterations and reviews before the final version is complete. Without GroupWare tools, taking notes during the session often slows the entire process down as the scribe must make sure everything written down is accurate.

Teambuilding and consensus are required for the "process improvement teams" to really be successful. This is difficult to achieve without GroupWare tools and a strong facilitator. Quite often, one or two people dominate the discussion during a session. As a result, valuable information is suppressed and fewer team members "buy in" to the IQC methodology.

Outside of the sessions, other problems arise. The facilitator has to take time to prepare all of the documentation from notes taken during the session. In addition, the process flows and reaction plans must be made available to the appropriate people within the organization. Furthermore, these documents can easily get out of date if they are not updated as procedures change. Document control is essential to ensure everyone is operating from the correct version.

This invention provides a more efficient means to collect and organize the data captured during Integrated Quality Control sessions and a process to transform the data into a format usable by existing commercially available database, flowcharting, and word processing software tools.

The approach to Integrated Quality Control described here is being used successfully in IBM. IBM's GroupWare product, TeamFocus, is used in facilitated work sessions for Integrated Quality Control. TeamFocus is a GroupWare product that provides group decision support functions such as:

Electronic Brainstorming Idea Organization Voting Topic Commenting Alternative Evaluation Group outlining Group Matrix

Following the facilitated sessions the resulting data is stored in a database tool such as Microsoft Access, thus making the data available for documentation. The documents are produced automatically by specialized bridge programs that use a word processor, such as IBM BookMaster. The documents are stored in another GroupWare tool for document management, such as LotusNotes.

The Integrated Quality Control methodology is used by a manufacturing organization to baseline its processes and systems. This baseline provides an objective assessment of the organization's quality with respect to:

process variables product variables gages or instrumentation equipment information and data

IQC begins with documentation on existing process flows. Process variables, product variables, and gages are identified from the process flows. Specifications are documented for each variable and reaction plans are developed to document the steps taken when specifications are not met. Quality control plans are developed to indicate a variety of things such as ownership, recording and tracking mechanisms, procedures, and capability. The information in the quality control plans is used to build indices that result in a score for the organization. The score then becomes a baseline for quality improvements. All opportunities to improve quality are documented and tracked.

Groups of people from manufacturing, engineering, maintenance, and development work on the IQC deliverables as a team. These groups are known as "process improvement teams" and include a facilitator to help the meetings run smoothly. The facilitator is also responsible for documenting the team's results in the various IQC tables and forms and making this information available to the team members. GroupWare refers to computer applications that allow groups of people to work together through the sharing of information. Most GroupWare products provide one or more of the following functions:

Calendar Electronic Mail Word Processing Data or Document Management Group Decision Support Work Flow Support

GroupWare products all run on a network, so that information is easily shared and accessible to all users who need it. LotusNotes is a GroupWare product that provides word processing and documentation management functions. TeamFocus is a GroupWare product that provides group decision support functions in an electronic meeting setting.

Scope Exercise

Referring to FIG. 1, the workgroup gathers in a joint meeting to provide input in response to questions provided by a facilitator, shown as a PC (2) in FIG. 1. The PC server (5), operating system (6) and applications (6) are also shown. The session can also include a projector (4) and screen (3) for viewing and a printer (7) for hardcopy output. Each workgroup member participates in the meeting via a PC (1) and the questions and answers may be selectively displayed on the screen or on each PC.

Referring to FIG. 7, the Scope Exercise begins with a definition of the process in the words of the team. The bounds of the process are set by identifying the beginning step and the ending step of the process. It is important that the team agree on these bounds, otherwise the team will spend time discussing things that are outside of the scope of the project. Next, the team identifies their customers and suppliers in a brainstorming exercise. A GroupWare tool such as TeamFocus is used for the brainstorming. This initial facilitated session takes the process improvement team through a series of exercises that are designed to give them a common understanding of the scope of the Integrated Quality Control project. It takes them through some basic definitions and brainstorming exercises that must be made to get started. The definitions and ideas come directly from the group, in their own words, and are stored. Their responses are organization-specific. FIG. 2 shows a sample output of the present invention relating to the scope exercise.

In TeamFocus Idea Organization or Group Outliner, each participant suggests customers and suppliers that they are aware of. The responses from the group are collected, reviewed, and consolidated into a list that everyone concurs with. Next, the team collects additional information about each customer and supplier, such as a definition of who or what they are, the process inputs that they provide (supplier), and the process outputs that they receive (customer). The TeamFocus session data is copied to diskette and loaded into a database tool such as Microsoft Access for storage and later retrieval. Hardcopy documentation may be generated from TeamFocus or from the database. The documentation can also be stored in a GroupWare tool such as LotusNotes, a document management tool, for sharing the IQC Scope information across the organization.

Process Flow and Opportunities Exercise

The Process Flow and Opportunities Exercise identifies all the steps in the process and the sequence in which they are performed. Referring to FIG. 8, the Process Flow and Opportunities Exercise begins with a review of the definition of the process and its bounds. It is important that the team agree on these bounds, otherwise the team will spend time discussing things that are outside of the scope of the project. Next, the team identifies the process steps in a brainstorming exercise. A GroupWare tool such as TeamFocus is used for the brainstorming. In TeamFocus Idea Organization or Group Outliner, each participant suggests process steps that they are aware of. The responses from the group are collected, reviewed, consolidated into a list, and sequenced with concurrence from everyone in the group. Discussion then follows to determine the type of step, that is procedure, operation, transfer, delay, or data recording. The type is noted in TeamFocus in the comment section for each process step. Also noted in the comment section is other relevant information such as a description of the procedure followed, tools needed, parameters or specifications that apply, and average distance traveled or time required. The TeamFocus session data is copied to diskette and loaded into a database tool such as Microsoft Access for storage and later retrieval. The process documentation will identify the variables and specifications needed to develop the quality control plans and indices later on in the Integrated Quality Control process. Hardcopy documentation may be generated from TeamFocus or from the database. The documentation can also be stored in a GroupWare tool such as LotusNotes, which is a document management tool, for sharing the process flow information across the organization. FIG. 3 shows a sample output of the present invention relating to the process flow and opportunities exercise.

During the brainstorming exercise, it is quite natural for problems and opportunities to be brought to light. As they are identified, they need to be recorded for later discussion and analysis. A GroupWare tool such as TeamFocus is used for capturing these opportunities. In TeamFocus Idea Organization or Group Outliner, participants or the facilitator can identify opportunities. Any additional information about the opportunity is recorded in the comment section, such as date, owner, status, dependencies, resolution, and potential benefits. Alternatively, the opportunities is input directly into a database tool such as Microsoft Access by creating an input screen that prompts for the appropriate information. Hardcopy documentation of the opportunities may be generated from TeamFocus or from the database in a report format. The documentation can also be stored in a GroupWare tool such as LotusNotes, which is a document management tool, for sharing the opportunity information across the organization.

Quality Control Plan and Index Development Session

The Quality Control Plan and Index Development Exercise consolidates all the relevant data about the various manufacturing variables and provides a score or measurement of the organization's quality level. Referring to FIG. 9 the Quality Control Plan and Index Development Exercise begins with the identification of manufacturing variables--process variables, product variables--as well as quality measurements. If manufacturing equipment is part of the scope of the IQC project, components are identified for each type of equipment. This is usually performed in a brainstorming exercise, although some of the variables may already be identified in the process documentation. Each quality control plan (QCP) is developed as a separate exercise, so that the brainstorming is focused on one topic at a time. A GroupWare tool such as TeamFocus is used for the brainstorming. In TeamFocus Idea Organization or Group Outliner, each participant suggests variables that they are aware of, or quality measurements or equipment components, depending on which QCP is being developed. The responses from the group are collected, reviewed, and consolidated into a list with concurrence from everyone in the group. Discussion then follows to identify the additional information required for each variable. Alternatively, the team is subdivided into groups that each take a few of the variables. The additional data is captured in TeamFocus in the comment section for each variable. The additional information varies depending on the type of QCP. Refer to the sample quality control plans in FIGS. 4a-f for details on the additional data required. The TeamFocus session data is copied to diskette and loaded into a database tool such as Microsoft Access for storage and later retrieval. Hardcopy documentation may be generated from TeamFocus or from the database. A specialized bridge program is used to automatically create this documentation in a word processing tool. The documentation can also be stored in a GroupWare tool such as LotusNotes, which is a document management tool, for sharing the quality control plans across the organization. FIGS. 4a-f show a sample output of the present invention relating to the quality control plan exercise. FIGS. 5a-g show a sample output of the present invention relating to the index development exercise.

Once all of the quality control plans have been developed, the indices are developed. In a database or spreadsheet tool, each variable is evaluated against the various parameters in the index. For example, process variables are evaluated on their specification, their sampling, their means of control, their capability, and their reaction plans. Each parameter has several possible states. Process variable specifications, for example, may not exist or may be expressed as a point, range, or nominal value with tolerances. Similar states exist for the other parameters. Each state has an available point value assigned to it. The organizations score is calculated by dividing the number of variables in that state by the total number of variables and then multiplying by the available points. Points are calculated for each state of each parameter, and then totaled for an overall score on that index. The index document is developed in a word processor or as a report from the spreadsheet or database tool.

Reaction Plan Development Exercise

The Reaction Plan Development Exercise develops specific instructions for the line operators to follow when specifications are not met. Referring to FIG. 10, the Reaction Plan Development Exercise begins with the identification of manufacturing variables--process variables, product variables--as well as quality measurements. If manufacturing equipment is part of the scope of the IQC project, components are identified for each type of equipment. This is usually performed in a brainstorming exercise, although some of the variables may already be identified in the quality control plans. Each reaction plan (RP) is developed as a separate exercise, so that the brainstorming is focused on one topic at a time. A GroupWare tool such as TeamFocus is used for the brainstorming. In TeamFocus Idea Organization or Group Outliner, each participant suggests variables that they are aware of, or quality measurements or equipment components, depending on which RP is being developed. The responses from the group are collected, reviewed, and consolidated into a list with concurrence from everyone in the group. Discussion then follows to identify the additional information required for each variable. Alternatively, the team is subdivided into groups that each take a few of the variables. For reaction plans, this includes the specification, the means of detection, and the specific instructions. The instructions should address both exceeding the upper limit and lower limit of the specification for the variable, when the required action is different. The additional data is captured in TeamFocus in the comment section for each variable. The TeamFocus session data is copied to diskette and loaded into a database tool such as Microsoft Access for storage and later retrieval. Hardcopy documentation may be generated from TeamFocus or from the database. A specialized bridge program is used to automatically create this documentation in a word processing tool. FIG. 6 shows a sample output of the present invention relating to the reaction plan development exercise. The documentation can also be stored in a GroupWare tool such as LotusNotes, which is a document management tool, for sharing the reaction plans across the organization.

Bridge Programs

The TeamFocus sessions produce data files comprised of all the groups' responses to the facilitator's prompts for information. Upon execution of the bridge programs these files are formatted into import files for various tools. Also, the files can be formatted into printed documents, such as process documents, opportunity tables, QCPs, and RPs automatically.

Referring to FIG. 11 showing a pseudocode implementation of the bridge program EXPORT, this specialized program used by IBM bridges data from a TeamFocus Idea Organization (IO) session to a DBASE III database file. The program begins with a prompt to the user to enter the path to the SESSION.DBF file created by TeamFocus. The program then verifies that the path entered is correct, and if so, reads the file to determine the names of all available sessions. These are entered into a list box control on the main form. The default source and destination paths are set as the current directory. They are changed by the user if need be. The user can select as many sessions as desired to be exported. When OK is clicked, the EXPORT program validates all data fields entered by the user. If all is valid, the Session Id for the first selected session is used to determine input file names. The file containing all the IO list items and their associated comment file names is named "LIST.sub.-- x.IO" where x is the Session Id. The first LIST.sub.-- x.IO record is read and assigned to the Idea field. The next line is then read and assigned to the Comment File Name variable. This represents the name of the file that contains any comments associated with that Idea. If the Comment File exists, then each line of the file is read and appended to the Comment field. Session Id, Idea, and Comment are then written to the DBase III database file. This process of reading and processing 2 LIST.sub.-- x.IO lines at a time is then repeated until the file is empty.

IQC Bridge

Referring to FIG. 12 showing a pseudocode implementation of the bridge program IQC, this specialized program used by IBM bridges data from a TeamFocus Idea Organization (IO) session to an IBM Bookmaster file that produces the documentation from IQC sessions. The program begins by reading in the values set by the user in the Options pull-down menu, as shown in the sample screens in FIGS. 13a-g. These include:

TeamFocus Version Document Format Header Parameters Directory Paths Print Control Printer Name

The TeamFocus version is needed in order to properly access the TeamFocus data as the file structures vary from release to release. The document format indicates which type of IQC document is to be produced. Header parameters allow for customized titles for the IQC documents. The directory paths establish the source directory where the TeamFocus data is found and the destination directory where the Bookmaster file is written. Print Control determines whether or not to route the document to a printer. The printer name is needed if Print Control is turned on. Next the program verifies that all of the input files exist. Then it sets up the page header information by writing out the document title and date. At this point, the program begins to construct the body of the document, which is a Bookmaster table. It reads the LIST.sub.-- x.IO file to determine the Level 1 entries and their corresponding comment file. It opens the table, starts the first row, and reads the C.sub.-- x-n.IO comment file for the first Level 1 entry. Each field of information in the comment file becomes a column in the table. The various fields of information in the comment files are distinguished either by tags or by skipping a line. Each type of IQC document has a different set of information required, so the tables vary by the type of IQC document. (Reference the sample IQC documents in FIGS. 2-6). When all of the fields are written for that particular Level 1 entry, the program begins a new row and reads the comment file for the next Level 1 entry. This continues for each Level 1 entry. When all Level 1 entries have been processed, the table is closed and the output file is closed. The program executes the word processor program that formats the output file with its Bookmaster commands in a document. If print control is turned on, the appropriate print command is executed to send the document to the designated printer. The output file is copied to the destination directory and the program ends.

Advantages over the Prior Art

The combination of facilitated work sessions and GroupWare products, when applied to the Integrated Quality Control methodology, allows an organization to assess its manufacturing operations in less time than it would otherwise have required. The facilitated work sessions allow the "process improvement teams" to focus their efforts and make effective use of their time. They also promote teamwork and ownership of procedures and opportunities. The GroupWare tools allow the work team to quickly collect, organize, and document their ideas. At the end of the facilitated session, the team has immediate documentation of their work. The GroupWare tools also allow for the proper management of the documentation, making immediate access throughout the organization possible. Although Integrated Quality Control was developed specifically to study and improve manufacturing operations, these methods need not be limited to physical production of goods. A medical office or hospital emergency room, for example, consists of inputs, processes performed by people or machines, and outputs. Medical services can be analyzed and improved using the Integrated Quality Control methodology. The only difference would be that the session teams will use different terms to describe similar problems such as "How long does it take?", "How many can we handle in a day?", and "How long will they have to wait?"

GroupWare tools can help overcome some of the risks of the manual methods for Integrated Quality Control mentioned above. Team members can submit ideas anonymously, so that people uncomfortable speaking out in a group can share their ideas. Also, since ideas are submitted electronically via computer keyboard, nothing is forgotten or incorrectly recorded. Some time is saved, since all team members can type their ideas simultaneously. Finally, and probably most importantly, GroupWare helps the process improvement teams reach a consensus more rapidly than manual methods, because everyone has a voice and everyone has a vote.

Alternative Embodiments

It will be appreciated that, although specific embodiments of the invention have been described herein for purposes of illustration, various modifications may be made without departing from the spirit and scope of the invention. In particular, other bridge programs can similarly be written for various analysis tools chosen by the IQC team. Other tools might include spreadsheet or flowcharting tools. The advantages offered by the bridge programs are in time saving and accuracy, as the data need not by manually keyed into each tool. Accordingly, the scope of protection of this invention is limited only by the following claims and their equivalents.

Claims

1. A method for establishing and documenting a quality control plan for production or service processes, comprising the steps of:

providing a group decision support environment for a plurality of participants, the environment including a network of a multitude of computer interface stations, each station including input means and a display means;

simultaneously soliciting from a plurality of the participants information concerning presently existing or desired processes;

simultaneously inputting into a plurality of the computer stations data representing the information concerning presently existing or desired processes, by a plurality of the participants;

storing the data concerning presently existing or desired processes in the network;

simultaneously soliciting from a plurality of the participants information concerning variables affecting quality of the presently existing or desired processes;

simultaneously inputting into a plurality of the workstations data representing the information concerning variables affecting quality of the presently existing or desired processes, by a plurality of the participants;

storing the data concerning variables affecting quality of the presently existing or desired process in the network;

formatting stored data representing the information concerning processes and the variables affecting quality in a format suitable for use by a selected database tool:

executing a selected bridge program for retrieving the formatted data from the database tool: and

automatically retrieving from network storage information contained in the computer network, outlining the quality control plan for manuals containing the information that was input by a plurality of the participants concerning presently existing or desired processes and variables affecting quality of the presently existing or desired processes.

2. The method according to claim 1 wherein the participants include personnel responsible for an implementation of the actual and desired manufacturing processes.

3. The method according to claim 1, further including the steps of:

simultaneously soliciting from a plurality of the participants, information concerning variables affecting quality of presently existing or desired process outputs;

simultaneously inputting into a plurality of the workstation information concerning variables affecting quality of the presently existing or desired process outputs by a plurality of the participants; and

storing the variables affecting quality of the presently existing or desired process outputs.

4. The method according to claim 1, further including the steps of:

simultaneously inputting into a plurality of the workstations values representing baseline indices derived from the information concerning variables affecting quality of the presently existing or desired processes by a plurality of the participants;

simultaneously inputting into a plurality of the workstations values representing target indices derived from the information concerning variables affecting quality of the existing or desired processes by a plurality of the participants; and

storing the values representing target indices, in the network.

5. The method according to claim 4, further including the steps of:

simultaneously soliciting from a plurality of the participants information concerning possible states and associated values of the variables affecting quality of presently existing or desired processes; and

simultaneously inputting into a plurality of the workstations the possible states and associated values of the variables affecting quality of presently existing or desired processes by a plurality of the participants.

6. The method according to claim 5, further including the steps of:

executing export programs for formatting the data stored in the computer system, the format compatible for use by the selected bridge program;

the bridge program automatically reformatting the retrieved data into predefined formats suitable for efficient interfunctional organization use, the predefined formats including predefined chapter and page headings; and

the bridge program automatically printing the data in a form of manuals suitable for use by the personnel responsible for an implementation of the actual and desired manufacturing processes.

7. The method according to claim 6, wherein the selected database tool includes an export program for use by the bridge program to retrieve the formatted data.

8. The method according to claim 6, wherein the bridge program includes an import tool to retrieve the formatted data from the database tool.