Method for the storage of multi-versioned data with retrieval based on searched query

• US 5,317,729 A
• Filed: 10/24/1990
• Issued: 05/31/1994
• Est. Priority Date: 10/24/1990
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Ryan, James L., Mukherjee, Sujan K., Wason, James R.
• Primary Examiner(s): Lee, Thomas C.
• Assistant Examiner(s): ORZECH, JENNIFER
• Application Number:
  US07/602,600
• Time in Patent Office: 1,315 Days
• Field of Search: 395/600, 395/575, 395/425, 395/, 395/275, 364/401, 364/148
• US Class Current: 1/1
• CPC Class Codes: G05B 19/41845 characterised by system universality, reconfigurability, modularity
• CPC Class Codes: G05B 2219/32398 Operator controls setting, changing of setting, of different machines
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: Y02P 90/02 Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A method for storage and retrieval of both time-oriented versions and view-oriented versions of engineering change information in which the engineering change information progresses through a set of status conditions and access to the data by different user groups is conditioned upon the status of the information. Version control software logic enables users to create versioned objects by logical key grouping of data elements. The version control logic acts upon the logical keys and special versioned attributes of these objects for the proper specification and selection of object instances during creation, update or retrieval processing. Insert and extract sequence numbers are automatically generated for both historical preservation of previous engineering change information and efficient retrieval of the currently effective designs. Instance level security facilitates the merger of different versions of the engineering change data having different engineering change status levels so that similar types of data can be contained within a single data base table.

Claims

1. A method for implementing the control of versioned data objects affected by engineering changes to a product design in a computer-based information processing system in which a master item file comprised of items resides on a non-volatile storage device with each of said items representing a part to be used to assemble a product, said method comprising:

creating a first engineering change notice that identifies a first plurality of items in a master item file, said first plurality of items comprised of at least a first item, said first item affected by a first engineering change;

creating a first affected item record for said first item and storing said first affected item record in an affected item file on said non-volatile storage device;

identifying said first affected item record by a first sequence number;

determining a first plurality of versioned data objects that are affected by said first engineering change,

modifying each of said first plurality of versioned data objects, said modification including modifying a plurality of version control attributes, said attributes comprising at least a sequence number field and said modification comprising at least modifying said sequence number field to contain said first sequence number, the result of such modification being a first modified plurality of versioned data objects and

storing said first modified plurality of versioned data objects in a plurality of versioned data object data files on said non-volatile storage device;

creating a second engineering change notice that identifies a second plurality of items in said master item file, said second plurality of items comprised of at least a second item, said second item affected by a second engineering change;

creating a second affected item record for said at least one item and storing said second affected item record in said affected item file;

identifying said second affected item record by a second sequence number;

determining a second plurality of versioned data objects that are affected by said second engineering change,

modifying each of said second plurality of versioned data objects, said modification comprised of modifying said plurality of version control attributes, said attributes comprising at least said sequence number field and said modification comprising at least modifying said sequence number field to contain said second sequence number, the result of such modification being a second modified plurality of versioned data objects and storing said second modified plurality of versioned data objects in said plurality of versioned data object data files; and

if said first engineering change satisfies a search query, retrieving said first affected item record and said first modified plurality of versioned data objects by means of said first sequence number; and

if said second engineering change satisfies a search query, retrieving said second affected item record and said second modified plurality of versioned data objects by means of said second sequence number.

2. The method of claim 1 wherein said first affected item record is comprised of an item identifier field, an affected item status field, a security level field, a component identifier field, and at least one affectivity attribute field.

3. The method of claim 2 in which a first subset of said modified first plurality of versioned data objects is stored in a first of said plurality of versioned data object data files, and each of said first subset of said modified first plurality of versioned data objects comprises an item identifier field with said item identifier field being used as a logical key.

4. The method of claim 2 in which a second subset of said modified first plurality of versioned data objects is stored in a second of said plurality of versioned data object data files, and each of said second subset of said modified first plurality of versioned data objects comprises an item identifier field and a component identifier field with a combination of said item identifier field and said component identifier field being used as a logical key.

5. The method of claim 2 in which said affected item status field of said first affected item record is set initially to a code indicating pre-release, and said code subsequently is set to indicate released, accepted, effective and closed as said first item progresses through design, manufacturing and production.

6. The method of claim 2 wherein said security level field contains a code which controls access to each of said first modified plurality of versioned data objects and said code of said security level field has a direct correspondence to said affected item status field of said first affected item record.

7. The method of claim 2 wherein said view identifier field in said first affected item record is used to identify and retrieve said first modified plurality of data objects.

8. The method of claim 2 including the step of automatically generating said sequence number when said first engineering change notice is created wherein said generated sequence number represents a unique attribute of said first item and has a direct correlation to said engineering change identifier field and said affected item status field of said first affected item record.

9. The method of claim 2 further including the step of identifying a superseded versioned data object that is superseded by a superseding versioned data object by including said sequence number of said superseding versioned data object in an extract sequence number field of said superseded versioned data object.

10. The method of claim 2 wherein said retrieving step includes:

presenting an interface screen to said authorized user containing user-selectable search query options;

selecting a search query option and identifying a set of input parameters for said search query to collectively define a search strategy;

searching said plurality of versioned data object data files and identified a target plurality of versioned data objects, each versioned data object of said target plurality satisfying said search strategy;

presenting said target plurality of versioned data objects to said authorized user as the result of said search query.

11. The method of claim 10 wherein said set of input parameters for said search query includes a first parameter to be searched for in said item identifier field and a pair of parameters to be searched for in said engineering change identifier field, said pair of parameters being entered to identify and to provide said authorized user with a composite view of the versioned data objects that are effective between the engineering changes represented by said pair of parameters.

12. The method of claim 10 wherein said affectivity attribute fields comprise an effective data field and the set of input parameters for said search query includes a first parameter to be searched for in said item identifier field and a pair of specified dates to be searched for in said effective data field, said pair of specified dates being entered to identify and to provide said authorized user with a composite view of the versioned data objects that are effective between said pair of specified dates.

13. The method of claim 7 wherein said affected item record further includes a based on view attribute and a based on sequence number attribute.

14. The method of claim 13 wherein multiple view versions of said versioned data objects are created in which a first view version is based on a second view version which, in turn, can be based on a third view version, said based on view and based on sequence number attributes being used to associate said multiple view versions.