Product network management system and method

• US 8,412,741 B2
• Filed: 07/17/2007
• Issued: 04/02/2013
• Est. Priority Date: 07/17/2007
• Status: Active Grant

• Current Assignee: Agile Software Corporation (Oracle Corporation)
• Original Assignee: Agile Software Corporation (Oracle Corporation)
• Inventors: Hein, Raymond
• Primary Examiner(s): Lee, Wilson
• Assistant Examiner(s): Le, Jessica N
• Application Number:
  US11/779,039
• Publication Number:
  US 20090024647A1
• Time in Patent Office: 2,086 Days
• Field of Search: 705/7, 705/7.11
• US Class Current: 707/797
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06Q 10/04 Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem" market predictions or forecasting for commercial activities G06Q30/0202

Abstract

The invention is directed to an integrated computerized product lifecycle manager and requirements manager system for associating high-level requirements data with everyday product lifecycle management activities. The system includes a networked database comprised of one or more central computerized data servers, and a plurality of user computers (terminals, workstations) connected to the central server or servers by a computer data network. The server or servers will usually run multiple software modules such as database modules, various product lifecycle management modules, data viewer and decoder modules, and requirements management modules all operating in an integrated manner so that selected portions of the requirements tree, from the top high-level requirements to more detailed low level requirements, can be presented to users in a context relevant manner. The invention additionally includes context management module by which selected portions of the requirements data may be exposed or redacted according to organizational needs.

Claims

1. A method for managing product networks, the method comprising:

receiving, at one or more computer systems, a request to access one or more product files stored as database elements in a central database, wherein the database elements are produced from a multiplicity of different native authoring programs providing a multiplicity of different file types;

retrieving, by one or more processors associated with the one or more computer systems, the database elements from the central database;

receiving, at the one or more computer systems, information linking one or more requirement trees produced by requirement management software to the database elements; and

generating, by the one or more processors associated with the one or more computer systems, a metafile according to a common metafile type configured to be viewed by users without the native authoring programs based on the database elements and the information linking the one or more requirement trees produced by the requirement management software to the database elements;

wherein one or more sections of the metafile are configured to retrieve one or more portions of the one or more requirement trees produced by the requirement management software according to a requirements tree context manager evaluating a set of predetermined rules to determine which portions of the one or more requirements trees are exposed to the users; and

wherein the generating, by the one or more processors associated with the one or more computer systems, of the metafile according to the common metafile type configured to be viewed by users without the native authoring programs based on the database elements and the information linking the one or more requirement trees produced by the requirement management software to the database elements comprises exposing one or more subtrees of the one or more requirements trees.

2. The method of claim 1, wherein generating, by the one or more processors associated with the one or more computer systems, the metafile according to the common metafile type configured to be viewed by users without the native authoring programs based on the database elements and the information linking the one or more requirement trees produced by the requirement management software to the database elements comprises exposing all of the one or more requirements trees without redacting any portions of the one or more requirements trees.

3. The method of claim 1, wherein the requirements tree context manager evaluates the set of predetermined rules to determine how much of the requirements tree to expose based upon predetermined linkages between the database elements and the one or more requirements trees and to redact portions of the one or more requirements trees that do not set requirements for one or more of the database elements.

4. The method of claim 1, wherein the requirements tree context manager evaluates the set of predetermined rules to determine how much of the requirements trees to redact or expose based upon criteria selected from a group consisting of management security lockouts, user organization, user department, and user access level.

5. The method of claim 1, wherein the requirements tree context manager evaluates the set of predetermined rules to further determine how much of the requirement trees previously redacted or exposed by the set of predetermined rules to further redact or expose in a second-level redaction, the second-level redaction being based on criteria selected from a group consisting of mouse over commands, mouse button click commands, mouse wheel commands, mouse gesture commands, light pen button commands, verbal commands, pointing commands, haptic device commands, keyboard buttons, and pull-down menus.

6. The method of claim 1, wherein the database elements comprise data selected from a group consisting of product data, supply chain data, component part data, subcontracting company data, partnership data, design data, development data, access privilege data, trade secret data, confidential information data, business relationship data, business documents data, business agreements data, OEM products and components data, CEM products and components data, bill of material data, change order data, component part object data, component part linking data, component part identification data, component part number data, part attribute data, part affiliation data, part product context data, specifications drawing data, color data, size data, type data, price data, quantity data, find number data, cross-reference data, related information data, earlier version data, history of change data, text document data, graphics drawing data, other attribute data, redacted data, discovery privilege data, cost data, component parts specifications data, product specifications data, quantity received data, quantity needed data, availability data, supplier type data, geographical information, and purchase order data.

7. A non-transitory computer-readable medium storing computer-executable code for managing product networks, the non-transitory computer-readable medium comprising:

code for receiving a request to access one or more product files stored as database elements in a central database, wherein the database elements are produced from a multiplicity of different native authoring programs providing a multiplicity of different file types;

code for retrieving the database elements from the central database;

code for receiving information linking one or more requirement trees produced by requirement management software to the database elements; and

code for generating a metafile according to a common metafile type configured to be viewed by users without the native authoring programs based on the database elements and the information linking the one or more requirement trees produced by the requirement management software to the database elements;

wherein one or more sections of the metafile are configured to retrieve one or more portions of the one or more requirement trees produced by the requirement management software according to a requirements tree context manager evaluating a set of predetermined rules to determine which portions of the one or more requirements trees are exposed to the users; and

wherein the code for the generating of the metafile according to the common metafile type configured to be viewed by users without the native authoring programs based on the database elements and the information linking the one or more requirement trees produced by the requirement management software to the database elements comprises code for exposing one or more subtrees of the one or more requirements trees.

8. The non-transitory computer-readable medium of claim 7, wherein code for generating the metafile according to the common metafile type configured to be viewed by users without the native authoring programs based on the database elements and the information linking the one or more requirement trees produced by the requirement management software to the database elements comprises code for exposing all of the one or more requirements trees without redacting any portions of the one or more requirements trees.

9. The non-transitory computer-readable medium of claim 7, wherein the requirements tree context manager evaluates the set of predetermined rules to determine how much of the requirements tree to expose based upon predetermined linkages between the database elements and the one or more requirements trees and to redact portions of the one or more requirements trees that do not set requirements for one or more of the database elements.

10. The non-transitory computer-readable medium of claim 7, wherein the requirements tree context manager evaluates the set of predetermined rules to determine how much of the requirements trees to redact or expose based upon criteria selected from a group consisting of management security lockouts, user organization, user department, and user access level.

11. The non-transitory computer-readable medium of claim 7, wherein the requirements tree context manager evaluates the set of predetermined rules to further determine how much of the requirement trees previously redacted or exposed by the set of predetermined rules to further redact or expose in a second-level redaction, the second-level redaction being based on criteria selected from a group consisting of mouse over commands, mouse button click commands, mouse wheel commands, mouse gesture commands, light pen button commands, verbal commands, pointing commands, haptic device commands, keyboard buttons, and pull-down menus.

12. The non-transitory computer-readable medium of claim 7, wherein the database elements comprise data selected from a group consisting of product data, supply chain data, component part data, subcontracting company data, partnership data, design data, development data, access privilege data, trade secret data, confidential information data, business relationship data, business documents data, business agreements data, OEM products and components data, CEM products and components data, bill of material data, change order data, component part object data, component part linking data, component part identification data, component part number data, part attribute data, part affiliation data, part product context data, specifications drawing data, color data, size data, type data, price data, quantity data, find number data, cross-reference data, related information data, earlier version data, history of change data, text document data, graphics drawing data, other attribute data, redacted data, discovery privilege data, cost data, component parts specifications data, product specifications data, quantity received data, quantity needed data, availability data, supplier type data, geographical information, and purchase order data.

13. A system for managing product networks, the system comprising:

a processor; and

a memory, in communication with the processor, and configured to store a set of instructions which when executed by the processor configure the processor to;

receive a request to access one or more product files stored as database elements in a central database, wherein the database elements are produced from a multiplicity of different native authoring programs providing a multiplicity of different file types;

retrieve the database elements from the central database;

receive information linking one or more requirement trees produced by requirement management software to the database elements; and

generate a metafile according to a common metafile type configured to be viewed by users without the native authoring programs based on the database elements and the information linking the one or more requirement trees produced by the requirement management software to the database elements;

wherein one or more sections of the metafile are configured to retrieve one or more portions of the one or more requirement trees produced by the requirement management software according to a requirements tree context manager evaluating a set of predetermined rules to determine which portions of the one or more requirements trees are exposed to the users; and

wherein the generating of the metafile according to the common metafile type configured to be viewed by users without the native authoring programs based on the database elements and the information linking the one or more requirement trees produced by the requirement management software to the database elements comprises exposing one or more subtrees of the one or more requirements trees.

14. The system of claim 13, wherein the processor is configured to generate the metafile according to the common metafile type configured to be viewed by users without the native authoring programs based on the database elements and the information linking the one or more requirement trees produced by the requirement management software to the database elements by exposing all of the one or more requirements trees without redacting any portions of the one or more requirements trees.

15. The system of claim 13, wherein the requirements tree context manager evaluates the set of predetermined rules to determine how much of the requirements tree to expose based upon predetermined linkages between the database elements and the one or more requirements trees and to redact portions of the one or more requirements trees that do not set requirements for one or more of the database elements.

16. The system of claim 13, wherein the requirements tree context manager evaluates the set of predetermined rules to determine how much of the requirements trees to redact or expose based upon criteria selected from a group consisting of management security lockouts, user organization, user department, and user access level.

17. The system of claim 13, wherein the requirements tree context manager evaluates the set of predetermined rules to further determine how much of the requirement trees previously redacted or exposed by the set of predetermined rules to further redact or expose in a second-level redaction, the second-level redaction being based on criteria selected from a group consisting of mouse over commands, mouse button click commands, mouse wheel commands, mouse gesture commands, light pen button commands, verbal commands, pointing commands, haptic device commands, keyboard buttons, and pull-down menus.

18. The system of claim 13, wherein the database elements comprise data selected from a group consisting of product data, supply chain data, component part data, subcontracting company data, partnership data, design data, development data, access privilege data, trade secret data, confidential information data, business relationship data, business documents data, business agreements data, OEM products and components data, CEM products and components data, bill of material data, change order data, component part object data, component part linking data, component part identification data, component part number data, part attribute data, part affiliation data, part product context data, specifications drawing data, color data, size data, type data, price data, quantity data, find number data, cross-reference data, related information data, earlier version data, history of change data, text document data, graphics drawing data, other attribute data, redacted data, discovery privilege data, cost data, component parts specifications data, product specifications data, quantity received data, quantity needed data, availability data, supplier type data, geographical information, and purchase order data.