Data management system having data management configuration

Claim 2

A data management system according to claim 1 wherein said tasks of the user's data manager include defining and altering the structure of the library which includes the library levels and versions, types of files to be tracked, and specifying the file type which will be tracked at which levels, and the physical repositories for said levels, versions and types of files.

Claim 3

A data management system according to claim 1 wherein said tasks of the user's data manager include defining an Release, Engineering, and Sideways Release Levels for a library and acquiring information about their state, defining the types of files to be stored at each Release and Sideways Release Level, defining an optional EC number for each Release Level, and establishing the migration paths between Engineering Levels and the Release Level within a given version of said library.

Claim 4

A data management system according to claim 1 wherein said tasks of the user's data manager include defining the Package Control Data for a library which includes the identities of the Data Managers, a Fix Management Control Mode, Default Problem Fix and Engineering Change numbers for said library, and Part Number and Engineering Change Control Levels for said library.

Claim 5

A data management system according to claim 1 wherein said tasks of the user's data manager include defining which types of files will participate in Part Number and Problem Fix Tracking.

Claim 6

A data management system according to claim 1 wherein said tasks of the user's data manager include defining various types of authorities using either simple data entry screens or authority profiles for actions such as file promotion, file check out, creating BOMs, setting locks, and setting process results.

Claim 7

A data management system according to claim 1 wherein said tasks of the user's data manager include creating or copying Automated Library Process Definitions which include all the information required for the Library Process Manager to initiate, manage and complete a Library Process.

Claim 8

A data management system according to claim 1 wherein said tasks of the user's data manager include defining the relationships and dependencies between multiple Library Processes which exist at the same Version, Level and File Type within a given Library.

Claim 9

A data management system according to claim 7 wherein said tasks of the user's data manager include using Process Groups to install one or more previously defined Library Processes defined by said creating or copying Automated Library Process Definitions without the need to manually enter all the required information, and wherein these process groups also permit the Data Manager to install the same Library Processes across multiple libraries in an identical fashion.

Claim 10

A data management system according to claim 1 wherein said tasks of the user's data manager include defining one or more Automated Library Machines to perform work for said Library, including the type of Automated Library Machine and various workload balancing and monitoring facilities to aid in distribution and assignment of jobs across the library enterprise.

Claim 11

A data management system according to claim 1 wherein said tasks of the user's data manager include creating one or more reports to query and display the multitude of characteristics and properties defined within a Library, including Versions, Levels, file types, Authorities, Library Processes, Automated File Groups, Library Process Definitions, and Package Control Data.

Claim 12

A data management system according to claim 1 wherein said tasks of the user's data manager include deleting any or all of the properties defined within a Library, including Versions, Levels, file types, Authorities, Library Processes, Automated File Groups, Library Process Definitions, and Package Control Data at a time after they've been defined within a given Library.

Claim 13

A data management system according to claim 1 wherein a process includes gathering the information entered by the Data Manager for purposes of defining the plurality of attributes and characteristics necessary to manage a Library, and performing comparisons with the existing configuration information within the Control Repository such that only changed information needs to be committed to the Control Repository, thus resulting in more efficient use of the Control Repository tables and a minimized number of queries.

Claim 14

A date management system according to claim 1 wherein a process incorporates an Authority Manager to oversee which users may perform tasks such as file check out and check in, file promotion, setting locks, installing files into the DMS, creating and promoting BOMs, setting process results and performing data management functions.

Claim 15

A data management system for file and database management useful in concurrent engineering processes, comprising: 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 utility for a user of said data management system, proclaimed as the Data Manager, to perform tasks, which managers can be combined to support an environment for suitable for multiple users of a user community; and wherein said data management control system has a data management model structure capable of tracking a plurality of data objects governed under similar or disparate processes, and wherein all objects are classified as part of a library; and said library is a grouping of objects which all have common characteristics causing them to belong to the same library grouping, and wherein within a library, having one or more types, each type having one or more versions, and each version having one or more levels; and, wherein versions allow parallel evolution of the same component data elements coexist in the same library enabling 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, wherein a process permits the use of Authority Profiles along with a method for installing the information contained within the profiles into the Control Repository, and said method allows the user to create external files containing the detailed authority information for a particular type of user, and said method then permits the Data Manager to associate each profile with one or more users in an automated fashion without the need to manually enter the detailed authority information, and said method incorporates a utility to update the Control Repository with the authority information contained within the profiles, and wherein the said utility permits two modes of operation: delta mode in which any new authorities are added, but any existing authorities are retained in the control repository, and a full mode which completely synchronizes the authority information in the profiles with the authority tables in the control repository including deleting existing authorities which are no longer defined in the profiles, as well as adding new authorities.

Claim 16

A data management system according to claim 1 wherein owners of the data residing in the data management system may define Surrogates to act on their behalf with the power to take ownership of the user's data, and upon taking ownership notification is sent to the user indicating that the surrogate has taken ownership, and Managers may designate surrogates for any users with whom they associate.

Claim 17

A data management system for file and database management useful in concurrent engineering processes, comprising: 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 utility for a user of said data management system, proclaimed as the Data Manager, to perform tasks, which managers can be combined to support an environment for suitable for multiple users of a user community; and wherein said data management control system has a data management model structure capable of tracking a plurality of data objects governed under similar or disparate processes, and wherein all objects are classified as part of a library; and said library is a grouping of objects which all have common characteristics causing them to belong to the same library grouping, and wherein within a library, having one or more types, each type having one or more versions, and each version having one or more levels; and, wherein versions allow parallel evolution of the same component data element to coexist in the same library enabling 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, and wherein said system includes a Lock Manager to permit the following four types of locks to exist against any object residing in the DMS: Out-for-Update: to indicate ownership of an object whereby multiple users may possess Out-for-Update locks for the same object at different levels and versions; Move: to prevent data from being overlaid or promoted out of a given level; Overlay: to prevent data from being overlaid, but permits it to be promoted to higher levels; and, Processing: to lock data while undergoing Library Processing.

Claim 18

A data management system according to claim 1 including Lock Management Utilities which permit users to set, view and reset Out-for-Update, Move and Overlay Locks.