Method and system for automatically controlling the distribution of data objects.

0001This invention relates generally to the integration of information flow in a business enterprise and, in particular, to a method and system for controlling the distribution of collections of data objects to users or application processes in a computer integrated manufacturing (CIM) system.

0002A key to integration of information flow in a business enterprise is the ability to assemble a diverse collection of data and refer to it in a common way. One example is in the purchasing function where graphics, text history, purchase order formats, management approvals, and accounting calculations are all part of a "file folder" for the purchase of an item. Another example arises in the engineering release function, where geometric information, machinery instructions, bill of material sections, and cost information are routed as a "file folder" for management and technical approvals on the way to the manufacturing facility.

0003Each electronic file folder can be regarded as a logical organization of information or data objects. A folder of data objects can be thought of as a collection of documents similar to a folder in a filing cabinet. In a computer database environment, a document can be in multiple folders at the same time. Techniques exist in the prior art for entering and removing documents from electronic file folders, searching for documents in a file folder, viewing a list of documents in a file folder, and displaying a list of audit information associated with a document. The prior art also provides the capability for developing parallel distribution lists, i.e., distribution lists in which the file folder is sent out simultaneously to all users (destinations) on the distribution list. However, there is no method in the prior art for enabling automated serial distribution of a file folder for appropriate action, such as approval, review or information. Nor is there a method in the prior art for enabling a complete alternating sequence of destinations including a combination of serial and parallel distributions of an electronic file folder. Beyond the capability of serial or alternating serial and parallel distribution of a file folder, there is no prior art technique for automatic delinquency tracking and reporting in which recipients of file folders are reminded of missed dates or alternatively, file folders are sent to other reviewers. Additionally, there is no prior art technique which will enable a sequence of reviewers to make responses or comments electronically and have the comments merged together automatically in a single master history list.

0004It is therefore an object of this invention to enable complex distributions patterns including combinations of serial and parallel distribution for the dissemination of file folders to a plurality of destinations in a computer integrated manufacturing system.

0005It is also an object of this invention to provide a method for automatically tracking due dates and reporting the responses from the destinations and the failure of any destination (reviewer) to respond on time.

0006It is a further object of this invention to provide a method for electronically recording the responses from individual destinations (reviewers) and merging these responses into a master history list.

0007It is a still further object of this invention to automatically forward the electronic file folder to the next higher level of destinations on the distribution list upon successful completion of the review process at the current level.

0008These and other objects and advantages are accomplished by this invention in which collections of heterogeneous data objects are assembled in an electronic file folder in a computer integrated manufacturing system and distributed by a file folder manager to an originator-defined scheduled sequence of reviewers for electronic response and appropriate action. The file folder manager allows the users to establish and maintain a library of file folder descriptions. It also provides reports as defined by the originator.

0009Figure 1 illustrates a computer network implementation of the file folder manager system of this invention.

0010Figure 2A illustrates a table of contents contained in an electronic file folder.

0011Figure 2B illustrates a distribution list of reviewers contained in an electronic file folder.

0012Figure 3 illustrates a graphical representation of the file folder distribution list.

0013Figure 4 illustrates a graphical representation of a modified file folder distribution list.

0014An implementation of the file folder manager system 10 in a computer network is illustrated in Figure 1. One skilled in the art of computer-based manufacturing information systems will be able to apply the concepts discussed herein to both network-based and single data processing system configurations. Although the computer network in Figure 1 is depicted as having a hierarchical relationship between the host processor 20 and remote processors 60, 70, 80 over communications link 50, the network could just as well be depicted as having a distributed peer-to-peer architecture. Likewise, a plurality of individual workstations IWS1 through IWS12 are shown as being directly connected to either host processor 20 or remote processors 60, 70, 80. These workstations could also be linked to their corresponding processor over a local area network (not shown).

0015Running on host processor 20 is the file folder manager application 25. Users at individual workstations 22, 24 and 26 interact with file folder manager 25 through user interface 27. Also shown operating on the host processor 20 is a Computer Integrated Manufacturing (CIM) application 21, which can also interact with file folder manager 25 through application interface 23. The host processor 20 accesses the direct access storage device (DASD) 30 which contains a CIM data repository including file folder library 40 containing a plurality of file folders FF1, FF2, ... FFM, identified collectively by reference numeral 35.

0016Additional file folder manager applications 65, 75 and 85 are shown operating on remote processors 60, 70 and 80, respectively. Individual workstations 62, 64 and 66 interact with file folder manager application 65 through user interface 67. Likewise, file folder manager application 75 interacts with workstations 72, 74 and 76 through user interface 77, and file folder manager application 85 interacts with workstations 82, 84 and 86 through user interface 87.

0017When a destination is on a remote system, the file folder manager 25 uses communication services 45 to route the folder to the remote system. Once the file folder is received at the remote processor 70, the file folder manager 75 manages distribution and tracking at that system to workstations 72, 74, and 76 and communicates the results to the master file folder manager 25 as appropriate.

0018The user at an individual work station interacts with the file folder manager system 10 to define the contents of the file folder and establish routing instructions for the file folder. Although the preferred embodiment is discussed in the context of a Computer Integrated Manufacturing (CIM) environment, the methods are equally applicable to other collections of business enterprise activities, such as insurance, banking and retail. In addition to system users, any CIM process 21 can use the facilities of the file folder manager system 10 to assemble a packet of information for reference by a common name and to issue routing instructions for the packet. File folder interface 27 allows the user at a workstation such as 22 or a CIM application 21 to create a file folder. The file folder manager 25 confirms that the requested data is available and that the user at workstation 22 is authorized access. The file folder definition is added to the library of CIM information resources 40 so that other users or applications may use it. The routing request is checked for availability of resources and monitoring and tracking points are established. File folder manager 25 actually controls movement of the file folder. The file folder manager 25 monitors delays and sends out automatic reminder notices to each destination that has not responded by the scheduled date. The file folder manager 25 forwards the file folder to higher authority or to an alternate destination for approval when a destination is not available or responsive. The reports function of file folder manager 25 enables users to specify report contents, format, media and schedule. In addition, standard reports are available that include status summary, library contents, and delinquency notices.

0019Users at individual workstations describe file folder contents by selection from a menu of CIM information resources satisfying a user-defined query. For example, the user might ask for a display of all of the information on a part number and then select the data items that are to be included in a file folder. Users can describe file folder routing to destinations in text or by constructing a graphic network of destinations from icons at a workstation. The types of routings may include "for approval", "for your information", and "review required" along with schedule requirements (due dates) and alternatives for busy destinations.

0020The file folder manager 25 allows users of CIM applications to define, modify, distribute, and track collections of file folders through the system. The file folder manager 25 monitors activity and provides alerts when file folders are not processed according to the required schedule. It allows users to establish and maintain a library of file folder descriptions 40 and provides reports as defined by the users.

0021The functional capabilities of the file folder manager 25 include creating or changing a file folder description, routing a file folder, monitoring the distribution and responses received for a file folder, managing a file folder library, sending out file folder related reports, and sending and receiving file folders. The user interface 27 is activated by a user's request for the services of the file folder manager. The user interface 27 selects the desired service and issues a request to the appropriate subfunction of the file folder manager. Help services are also available to users at individual workstations to provide overall application description, assistance for terminal input, and recovery from errors. Similarly, the application interface 23 is activated by a request for the services of the file folder manager from a CIM application 21. Application interface 23 determines the nature of the desired service from CIM application 21 and creates requests that are compatible with those from the user interface 27, i.e., create/change requests, routing requests, report requests and library requests.

0022The first of the file folder manager functions to be considered is the create/change function. This function enables the definition or modification of a file folder. A file folder definition includes a header, contents listing the data objects contained in the file folder, routing instructions, a comment log, and follow-up reporting specifications. The routing instructions include a list of destinations and the type (i.e., approval, review, or information), as well as due dates for response. The list of destinations may include serial destinations, parallel destinations, and alternate destinations with predicates for selection. The routing has a default (preferred) path from which the file folder plan is constructed. The plan is updated when alternate paths are selected. However, if a destination type is "information", it must be the last destination on a branch, as no response is required. A list of data objects associated with a user-specified topic is displayed for selection and inclusion in a file folder's contents (e.g., everything associated with a particular part). A file folder can be described initially by an originating user at a workstation and then can be modified by other users as it is routed through the enterprise. The modifications can be the addition, deletion or replacement of data objects and the addition of comments which are appended to the file folder.

0023The file folder definition can be constructed by the user in an interactive terminal session from an individual workstation such as 22, or can be accepted from a CIM application 21. The first component of a file folder definition is the header which specifies a short, unique name and, optionally, a descriptive text as an abstract of the file folder. The header also includes the author, date of original definition, date of last update, and an indication of the completeness of the definition. For a file folder 35 to be considered complete, there must be at least one data object in the contents and at least one legitimate destination for the folder. The owner can modify everything in the definition of a file folder 35 except the name. This includes routing definitions for file folders that have not been executed.

0024In establishing the contents of a file folder 35, the user may enter a list of CIM data objects or can request that a list of all CIM data objects related to a particular topic be displayed for selection. The specification includes a key that allows either the current value of the data object or the value of the data object at the time of user access to file folder 35 to be included. In the first case, the data object is fixed when it is defined as being an element of the folder. In the second case, the file folder 35 points to the most recent value of the data object when someone looks at the folder. The contents of the file folder 35 also contains a log of comments. The contents of the file folder 35 are summarized in a table of contents that can be displayed by anyone having access to the file folder. The table of contents as illustrated in Figure 2A, includes the data object name, the date it was added to the folder, the date of its last update, and the identification of the user who added it to the folder. Any data object can be added to a file folder, but larger objects such as CAD drawings could create files too large for efficient movement in a network. In these instances, pointers or references to these larger objects should be used to keep the file size below a threshold value which is predefined for a given CIM installation.

0025Routing instructions are provided by the calling CIM application 21 or by the user at a workstation such as 22 preferably using a graphics editor. The user can enter destinations or select destinations from a menu of CIM users. For each destination, the user specifies the type of destination (action code), the time of an expected response, and the route structure. The destination types include "for approval", "for review", and "for information". Other useful destination types can be included as well. The time of expected response does not apply if the destination type is "for information". The route structures allowed are parallel, serial, and alternate. The default route structure is parallel. Each alternate structure is specified as a list of alternates with the predicate logic that determines the conditions for selection of the alternative. The total routing is a combination of the three types.

0026The routing function of the file folder manager 25 allows users of CIM applications to change a routing definition for a file folder 35 and to distribute the file folder according to the defined routing. It also creates a list of expected responses (due dates) which, in turn, becomes the basis for a file folder plan that is used to monitor progress and to identify delinquent processes. A completion notice is sent to the appropriate file folder interface (user interface 27 or CIM application interface 23) when the routing request has been satisfied.

0027In modifying a route definition for a file folder 35, new destinations can be added as in the original definition. However, a destination can be deleted only if the file folder has not been transmitted to the destination.

0028The distribution list in the file folder 35 is a network of users. Each node in the network contains the user's electronic address, the required action code and a schedule date for completion of the action. An illustration of a distribution list is provided in Figure 2B. A graphic representation of this distribution list is shown in Figure 3. File folder manager 25 initially distributes the file folder created by the user at workstation 22 to each of the users at the first level of the network. In Figure 3, the users at the first level include those at workstations 24 and 26 which are to review the file folder contents and those at workstations 62, 64, 66 which receive informational copies. In the preferred embodiment, "review" means the user is expected to review the folder and make comments as appropriate; "approve" means the user must review the folder and respond to the originator before the distribution can continue to the next level.

0029After all of the required responders have made appropriate responses, the file folder manager 25 routes the folder to the second level of the network (workstation 72) and the process continues. File folder manager 25 uses the schedule information to send automatic reminder notices to any destination of the review or approve type that has not responded by the schedule date. For example, if the user at workstation 72 fails to respond by the due date, a reminder notice is sent electronically by the file folder manager 25 along with a revised due date. If the user at workstation 72 still does not respond, the file folder manager 25 will send the file folder to alternate destination 76. This is shown in Figure 3 by the dashed arrow indicating the alternate path of the file folder to workstation 76. Similarly, workstation 84 is indicated as an alternate destination for workstation 86 at the fourth level of distribution.

0030If a required responder such as destination 74 at the third level of distribution does not agree with the file folder, he may log disapproval status, include comments and/or additional data objects. Human interaction is required to reach an accommodation before the folder is ready for the next level of distribution. This is indicated in Figure 4, by the feedback arrow drawn from workstation 74 to workstation 22. Once a compromise is reached, file folder 25 can be modified and resent to the same level of the distribution list for a review of the changes that were made to resolve the issues. If further changes are necessary at a subsequent level of review, then the additional modifications are made to the previously revised file folder so that only one version of the file folder is circulating through the network of destinations.

0031The monitoring function of file folder manager 25 updates the file folder plan as activities are completed, and issues delinquency reports on late activities. A log is maintained in the file folder plan noting the receipt of file folders at the destinations and the actions taken at the destinations, i.e., approve or modify. Delinquency notices are triggered by expected response reminders. The notice is also sent to the originator of the file folder. If an alternate destination has been specified for a non-responsive review or approval type destination, a file folder routing request is automatically sent to the routing function of file folder manager 25.

0032The reporting function of file folder manager 25 allows users to specify and update report contents, format, media, distribution lists, and schedules. This function also generates and distributes reports as scheduled. Some of the standard reports are a schedule of planned activities and the current status of activities against the schedule. The schedule of planned activities report is a report of the times of expected responses as defined in the routing, but arranged in chronological order. Reports can be scheduled periodically, on request, or when an event occurs.

0033The library manager function of file folder manager 25 provides the capability to archive, delete, copy and rename file folders. It also allows the inclusion of a file folder 35 into another file folder. The library includes file folder definitions and file folder plans.

0034The last function of the file folder manager is the receiver/sender function which allows a user at a workstation or a CIM application 21 to receive a file folder, make permitted modifications, add comments and indicate approval or concurrence. The destinations do not need to physically receive the folder contents. Instead, the destinations may be presented with a menu list of the folder contents so that they can retrieve the actual data objects from the repository as necessary. "Approve" or "review" destinations require access to this function to receive or process the file folder through a file folder processor. The file folder processor prepares receipt notices from review and approval destinations. The recipient is presented with a menu of file folder contents and the values of the data objects can be displayed or printed. If the destination is "for review", the data object may be checked out of the repository and modified. File folder comments are automatically updated to note the change transaction. "For review" and "for approval" destinations may both add comments to the file folder. A file folder action notice is prepared if the user approves the file folder.