Data management system for problems, releases and parts

• US 5,864,875 A
• Filed: 12/06/1996
• Issued: 01/26/1999
• Est. Priority Date: 12/06/1996
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: McDonald, Darryl James, Van Huben, Gary Alan, Mueller, Joseph Lawrence
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): WALLACE, MICHAEL J
• Application Number:
  US08/761,474
• Time in Patent Office: 781 Days
• Field of Search: 707/8, 707/10, 707/200, 707/201, 707/203, 707/103
• US Class Current: 1/1
• CPC Class Codes: G06F 2111/02 CAD in a network environment, e.g. collaborative CAD or distributed simulation
• CPC Class Codes: G06F 30/00 Computer-aided design [CAD]
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A design control system suitable for use in connection with the design of integrated circuits and other elements of manufacture having many parts which need to be developed in a concurrent engineering environment with inputs provides by users and or systems which may be located anywhere in the world provides a set of control information for coordinating movement of the design information through development and to release while providing dynamic tracking of the status of elements of the bills of materials in an integrated and coordinated activity control system utilizing a repository which can be implemented in the form of a database (relational, object oriented, etc.) or using a flat file system. Once a model is created and/or identified by control information design libraries hold the actual pieces of the design under control of the system without limit to the number of libraries, and providing for tracking and hierarchical designs which are allowed to traverse through multiple libraries. Data Managers become part of the design team, and libraries are programmable to meet the needs of the design group they service.

Claims

1. A data management system for file and database management useful in concurrent engineering processes, comprising:

a design control system for fulfilling requests of a user initiated from a computer system client system coupled to a network, including

a data management control system for managing a plurality of projects, each project having a data repository for data records and a control repository comprising a common access interface and one or more databases,

said control repository communicating with users of said design control system for fulfilling requests of a user and the data repositories of said data management control system through a plurality of managers, each manager performing a unique function wherein said managers act as building blocks which can be combined in a plurality of manners to support an environment for suitable for multiple users of a user community, and wherein

one of said managers is a library manager enabling automated library processing of any application program or tool to be launched using input data from said data management control system and after processing enabling results to be recorded as output data in any data control repository of said data management control system as a record in said data control repository; and

one of said managers is a fix manager for tracking specific iterations of a data object and for associating them with unique problem identifier for a problem, request or enhancement; and

one of said managers is a part number manager for tracking data requiring control of items or parts so as to eliminate the accidental assignment of the same number to two different items or parts; and

one of said managers is a release manager for tracking a coherent collection of data objects in said control repository for release as a collection to an external organization to permit the external organization to prepare for a release; and

said data management control system has a client/server domain and permits data to span multiple computer heterogeneous computer systems; and

each of said records in said data control repository includes data indicating the record filename, library, filetype, version and level, and said fix manager provides means for associating each record with problem identifiers; and

wherein

said fix manager provides operations for multiple modes of tracking problems, including;

disabling all problem fix tracking in all data objects;

collecting any selected data types to be tracked under a single, default problem identifier; and

enabling each data object to have a unique set of problem identifiers whereby multiple pieces of data can be associated with a single problem or a single piece of data for resolving multiple problems

and wherein a library function enables multiple versions of a component data element to be developed in tandem while using the same object name and residing in the same library and at the same level simultaneously.

2. A data management system for file and database management according to claim 1 wherein said fix manager enables a library process to be run on automated library machines (ALMs), including single ALMs, remote execution machines, and in an actor/object environment.

3. A data management system for file and database management useful in concurrent engineering processes, comprising:

a design control system for fulfilling requests of a user initiated from a computer system client system coupled to a network, including

a data management control system for managing a plurality of projects, each project having a data repository for data records and a control repository comprising a common access interface and one or more databases,

said control repository communicating with users of said design control system for fulfilling requests of a user and the data repositories of said data management control system through a plurality of managers, each manager performing a unique function, wherein said managers act as building blocks which can be combined in a plurality of manners to support an environment for suitable for multiple users of a user community, and wherein

one of said managers is a library manager enabling automated library processing of any application program or tool to be launched using input data from said data management control system and after processing enabling results to be recorded as output data in any data control repository of said data management control system as a record in said data control repository; and

one of said managers is a fix manager for tracking specific iterations of a data object and for associating them with unique problem identifier for a problem, request or enhancement; and

one of said managers is a part number manager for tracking data requiring control of items or parts so as to eliminate the accidental assignment of the same number to two different items or parts; and

one of said managers is a release manager for tracking a coherent collection of data objects in said control repository for release as a collection to an external organization to permit the external organization to prepare for a release; and

said data management control system has a client/server domain and permits data to span multiple computer heterogeneous computer systems; and

each of said records in said data control repository includes data indicating the record filename, library, filetype, version and level, and said fix manager provides means for associating each record with problem identifiers; and

wherein said data management system includes flags in records which are subject to tracking, and wherein restricting the library filetypes by setting and resetting said flags controls the library file types being tracked.

4. A data management system for file and database management according to claim 3 wherein said library manager enables two methods for initiating a library process, a first method being library initiated processing, and a second method being designer initiated library processing.

17. A data management system for file and database management according to claim 3 wherein said library manager enables two methods for initiating a library process, a first method being library initiated processing, and a second method being designer initiated library processing for problem fix management, release management and part number control.

5. A data management system for file and database management useful in concurrent engineering processes, comprising:

a design control system for fulfilling requests of a user initiated from a computer system client system coupled to a network, including

a data management control system for managing a plurality of projects, each project having a data repository for data records and a control repository comprising a common access interface and one or more databases,

said control repository communicating with users of said design control system for fulfilling requests of a user and the data repositories of said data management control system through a plurality of managers, each manager performing a unique function, wherein said managers act as building blocks which can be combined in a plurality of manners to support an environment for suitable for multiple users of a user community, and wherein

one of said managers is a library manager enabling automated library processing of any application program or tool to be launched using input data from said data management control system and after processing enabling results to be recorded as output data in any data control repository of said data management control system as a record in said data control repository; and

one of said managers is a fix manager for tracking specific iterations of a data object and for associating them with unique problem identifier for a problem, request or enhancement; and

one of said managers is a part number manager for tracking data requiring control of items or parts so as to eliminate the accidental assignment of the same number to two different items or parts; and

one of said managers is a release manager for tracking a coherent collection of data objects in said control repository for release as a collection to an external organization to permit the external organization to prepare for a release; and

said data management control system has a client/server domain and permits data to span multiple computer heterogeneous computer systems; and

each of said records in said data control repository includes data indicating the record filename, library, filetype, version and level, and said fix manager provides means for associating each record with problem identifiers; and

wherein a data object may exist at multiple library levels, and a superseded flag is provided for denoting whether a particular data object reference is superseded by a later iteration at a lower level, the lowest level file being the active or non-superseded data object.

6. A data management system for file and database management according to claim 5 wherein each data object may sit at multiple levels and, within the common repository:

(a) the data objects at each level may have the same set of problem identifiers associated to them;

or

(b) the data objects may have some problem identifiers in common and some unique problem identifiers associated to the;

or

(c) the data object may have no problem identifiers in common.

7. A data management system for file and database management useful in concurrent engineering processes, comprising:

a design control system for fulfilling requests of a user initiated from a computer system client system coupled to a network, including

a data management control system for managing a plurality of projects, each project having a data repository for data records and a control repository comprising a common access interface and one or more databases,

said control repository communicating with users of said design control system for fulfilling requests of a user and the data repositories of said data management control system through a plurality of managers, each manager performing a unique function, wherein said managers act as building blocks which can be combined in a plurality of manners to support an environment for suitable for multiple users of a user community, and wherein

one of said managers is a library manager enabling automated library processing of any application program or tool to be launched using input data from said data management control system and after processing enabling results to be recorded as output data in any data control repository of said data management control system as a record in said data control repository; and

one of said managers is a fix manager for tracking specific iterations of a data object and for associating them with unique problem identifier for a problem, request or enhancement; and

one of said managers is a part number manager for tracking data requiring control of items or parts so as to eliminate the accidental assignment of the same number to two different items or parts; and

one of said managers is a release manager for tracking a coherent collection of data objects in said control repository for release as a collection to an external organization to permit the external organization to prepare for a release; and

said data management control system has a client/server domain and permits data to span multiple computer heterogeneous computer systems; and

each of said records in said data control repository includes data indicating the record filename, library, filetype, version and level, and said fix manager provides means for associating each record with problem identifiers; and

wherein said release control manager maintains a pool of release or engineering change (EC) numbers which are associated to problem fix numbers and part numbers via interaction between said fix manager, part number manager, release control manager and library manager enabling both association during file movement through the data management system and manual associations so as to enable a user regarding a release to view all the problems, data and Part Number information included in the entire release.

8. A data management system for file and database management according to claim 7 wherein said release control manager has an engineering change collision avoidance mechanism for constantly monitoring all of the problem identifier, part number and engineering change information in the control repository to detect a known set of violations or or illegal conditions.

9. A data management system for file and database management according to claim 8 wherein said release control manager has means for detecting if a data object, part number or problem identifier is associated with multiple releases, and for ensuring that any released problem identifiers, part number or file reference numbers are never reused in a different release while permitting a data manager to assign an engineering change number to a release level.

10. A data management system for file and database management according to claim 8 wherein said release control manager has means for engineering change collision avoidance mechanism polices the library records to ensure only data associated with a desired engineering change actually resides in that level.

11. A data management system for file and database management according to claim 9 wherein said release control manager has means for notification of user recipients to assist in coordinating the delivery of a release with a release date defined for any part numbers in the data management system sent as the release date approaches at a predetermined interval prior to the release date which contains a list of all the part numbers, along with any other pertinent information, included in that release and to assist the recipient in planning their resources accordingly and react to any design changes in advance.

12. A data management system for file and database management according to claim 7 wherein said release control manager has means for grouping lower level data objects within a higher level data object library, and supports multiple release streams.

13. A data management system for file and database management according to claim 7 wherein said release control manager has means for providing system engineering change numbers to hierarchically group a collection of lower level engineering change numbers.

14. A data management system for file and database management according to claim 7 wherein said release control manager has means for creating collections of engineering changes into system engineering changes and for creating listings of all data objects in an engineering change, which listings can be combined to show all data objects in a system engineering change.

15. A data management system for file and database management according to claim 7 wherein said part number manager for tracking data requiring control of items or parts provides means for tracking extents with extent part numbers, and said data management system assigns extent part numbers, tracks and releases extends in the same manner as component part numbers.

16. A data management system for file and database management according to claim 13 wherein said release manager processes extent and component releases the same regardless of the underlying technology or process employed.

18. A data management system for file and database management according to claim 7 wherein there is a data manager for setting starting level for a set of data objects being tracked.