PRODUCT NETWORK MANAGEMENT SYSTEM AND METHOD

• US 20090024647A1
• Filed: 07/17/2007
• Published: 01/22/2009
• 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
• Granted Patent: US 8,412,741 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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. An integrated product network manager (PNM) system configured for linking at least one requirements trees to database elements, comprising:

at least one server having memory and a processor;

at least one database capable of exchanging data with the servers,

at least one network communicating with the at least one server and capable of allowing the at least one server to exchange data with other servers and with remote computers connected to the networks;

product lifecycle management software stored in memory and capable of running on the at least one server;

requirements management software stored in memory in the at least one servers and capable of producing requirements trees when executed by a processor; and

product network management software stored in memory and executable by a processor to enable the linking of the requirements trees produced by the requirements management software to at least some of the database elements.

2. The PNM system of claim 1, wherein the product network management software links the requirements trees to the database elements by exposing all of the requirements trees without redacting any portions of the requirements trees.

3. The PNM system of claim 1, wherein the product network management software links the requirements trees to the database elements according to a requirements tree context manager;

the requirements tree context manager being capable of following predetermined rules for determining which portions of the requirements trees are redacted or exposed to users who are using the remote computers.

4. The PNM system of claim 1, wherein the database elements are files selected from the group consisting of product lifecycle management database entry files, process specification files, and product specification files;

and wherein the database elements files are produced from a multiplicity of different native authoring programs, and wherein the different native authoring programs produce a multiplicity of different file types;

wherein the system additionally contains native authoring program file decoder programs running on at least some of the servers;

the file decoder programs being capable of decoding the different file types into a common metafile type that can be transmitted over the networks to the remote computers;

wherein the metafiles can be viewed by users operating the remote computers without the need to run the native authoring programs on the remote computers.

5. The PNM system of claim 1, wherein the database elements are files selected from the group consisting of product lifecycle management database entry files, process specification files, and product specification files;

and wherein the database element files are produced from a multiplicity of different native authoring programs, and wherein the different native authoring programs produce a multiplicity of different file types;

wherein the system additionally contains native authoring program file decoder programs running on at least some of the servers;

the file decoder programs being capable of decoding the different file types into a common metafile type that can be transmitted over the networks to the remote computers;

wherein the common metafiles can be viewed by users operating the remote computers without the need to run the native authoring programs on the remote computers;

wherein the product network management software links the requirements trees to the database elements files that are decoded by the file decoder programs into the common metafile type by linking sections of the metafile to the requirements trees without redacting any portions of the requirements trees.

6. The PNM system of claim 1, wherein the database elements are files selected from the group consisting of product lifecycle management database entry files, process specification files, and product specification files;

and wherein the database element files are produced from a multiplicity of different native authoring programs, and wherein the different native authoring programs produce a multiplicity of different file types;

wherein the system additionally contains native authoring program file decoder programs running on at least some of the servers;

the file decoder programs being capable of decoding the different file types into a common metafile type that can be transmitted over the networks to the remote computers;

wherein the metafiles can be viewed by users operating the remote computers without the need to run the native authoring programs on the remote computers;

wherein the product network management software links the requirements trees to the database elements files that are decoded by the file decoder programs into the common metafile type by linking sections of the metafile to the requirements trees according to a requirements tree context manager;

the requirements tree context manager being capable of following predetermined rules for determining which portions of the requirements trees are redacted or exposed to users who are using the remote computers.

7. The PNM system of claims 4, wherein the file decoder programs are capable of decoding files comprised of files selected from the group consisting of 2 and 3D computer assisted design (CAD) formats, AutoCAD, CATIA, CADKEY, HPGL, Inventor, ME10, MicroStation, Pro/E, Solid Edge, SolidWorks, STEP, Unigraphics, VISIO, VRML formats into a common metafile format;

and

wherein the file decoder programs are also capable of decoding files comprised of files selected from electronic design automation (EDA) formats, Cadence, GDS II, GERBER, Mentor, PADS, PCAD, and Zuken formats into a common metafile format; and

wherein the file decoder programs are capable of decoding files selected from the group consisting of mechanical engineering programs, electrical engineering programs, IC/Device engineering programs, and software engineering programs into a common metafile format.

8. The PNM system of claims 3, wherein the predetermined rules determine how much of the requirements tree to redact or expose based upon predetermined linkages between the database elements and the requirements trees, and redact the portions of the requirements trees that do not set requirements for that database element.

9. The PNM system of claims 3, wherein the predetermined rules determine how much of the requirements trees to redact or expose based upon criteria comprising criteria selected from the group consisting of management security lockouts, user organization, user department, and user access level.

10. The PNM system of claim 8, wherein the predetermined rules also allow the user to further determine how much of the requirement tree previously redacted or exposed by the predetermined rules to further redact or expose in a second-level redaction, the second-level redaction rules comprising criteria selected from the group consisting of mouse over commands, mouse button click commands, mouse wheel commands, mouse gesture commands, light pen button commands, verbal commands, pointing commands, hepatic device commands, keyboard buttons, and pull-down menus.

11. The PNM system of claim 9, wherein the predetermined rules also allow the user to further determine how much of the requirement tree previously redacted or exposed by the predetermined rules to further redact or expose in a second-level redaction, the second-level redaction rules comprising criteria selected from the 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. An integrated product network manager (PNM) system that links one or more requirements trees to database elements, where the database elements are selected from the group consisting of product lifecycle management database entries, process specification files, and product specification files;

wherein the database elements files are produced from a multiplicity of different native authoring programs, and wherein different native authoring programs produce a multiplicity of different file types;

the PNM system comprising;

one or more servers, the servers comprising a memory and a processor,

one or more databases capable of exchanging data with the servers,

one or more networks connected to the servers, the networks capable of allowing the servers to exchange data with each other and with remote computers connected to the networks;

native authoring program file decoder programs running on at least some of the servers;

the file decoder programs being capable of decoding the different file types into a common metafile type that can be transmitted over the networks to the remote computers;

wherein the metafiles can be viewed by users operating the remote computers without the need to run the native authoring programs on the remote computers.

product lifecycle management software running on at least some of the servers;

requirements management software running on at lest some of the servers; and

code configured to enable linking of the requirements trees produced by the requirements management software to at least some of the database elements.

13. The PNM system of claim 12, wherein the file decoder programs are capable of decoding files comprised of files selected from the group consisting of 2 and 3D computer assisted design (CAD) formats, AutoCAD, CATIA, CADKEY, HPGL, Inventor, ME10, MicroStation, Pro/E, Solid Edge, SolidWorks, STEP, Unigraphics, VISIO, VRML formats into a common metafile format;

and

wherein the file decoder programs are also capable of decoding files comprised of files selected from electronic design automation (EDA) formats, Cadence, GDS II, GERBER, Mentor, PADS, PCAD, and Zuken formats into a common metafile format;

and wherein the file decoder programs are capable of decoding files selected from the group consisting of mechanical engineering programs, electrical engineering programs, IC/Device engineering programs, and software engineering programs into a common metafile format.

14. The PNM system of claim 12, wherein the code for linking the requirements trees to at least of some of the database elements link the requirements trees to the database elements by exposing all of the requirements trees without redacting any portions of the requirements trees.

15. The PNM system of claim 12, wherein the code for linking the requirements trees to at least some of the database elements link the requirements trees to the database elements according to a requirements tree context management module;

the requirements tree context management module being capable of following predetermined rules for determining which portions of the requirements trees are redacted or exposed to users who are using the remote computers.

16. The PNM system of claim 12, wherein the code for linking the requirements trees to at least of some of the database elements link the requirements trees to the database elements files that are decoded by the file decoder programs into the common metafile type by linking sections of the metafile to the requirements trees without redacting any portions of the requirements trees.

17. The PNM system of claim 12, wherein the code for linking the requirements trees to at least some of the database elements link the requirements trees to the database elements files that are decoded by the file decoder programs into the common metafile type by linking sections of the metafile to the requirements trees according to a requirements tree context management module;

the requirements tree context management module being capable of following predetermined rules for determining which portions of the requirements trees are redacted or exposed to users who are using the remote computers.

18. The PNM system of claim 12, wherein the database elements comprise data selected from the 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.

19. The PNM system of claim 15, wherein the predetermined rules determine how much of the requirements trees to redact or expose based upon predetermined linkages between the database elements and the requirements trees, and redact the portions of the requirements trees that do not set requirements for those database elements.

20. The PNM system of claim 15, wherein the predetermined rules determine how much of the requirements trees to redact or expose based upon criteria comprising criteria selected from the group consisting of management security lockouts, user organization, user department, and user access level.

21. The PNM system of claim 18, wherein the predetermined rules also allow the user to further determine how much of the requirements tree previously redacted or exposed by the predetermined rules to further redact or expose in a second-level redaction, the second-level redaction rules comprising criteria selected from the group consisting of mouse over commands, mouse button click commands, mouse wheel commands, mouse gesture commands, light pen button commands, verbal commands, pointing commands, hapatic device commands, keyboard buttons, and pull-down menus.

22. The PNM system of claim 19, wherein the predetermined rules also allow the user to further determine how much of the requirement tree previously redacted or exposed by the predetermined rules to further redact or expose in a second level redaction, the second level redaction rules comprising criteria selected from the 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.

23. An integrated product network manager (PNM) system that links one or more requirements trees to database elements, where the database elements are selected from the group consisting of product lifecycle management database entries, process specification files, and product specification files;

wherein the database elements files are produced from a multiplicity of different native authoring programs, and wherein different native authoring programs produce a multiplicity of different file types;

the PNM system comprising;

one or more servers, the servers comprising memory and a processor,

one or more databases capable of exchanging data with the servers,

one or more networks connected to the servers, the networks capable of allowing the servers to exchange data with each other and with remote computers connected to the networks;

native authoring program file decoder programs running on at least some of the servers;

the file decoder programs being capable of decoding the different file types into a common metafile type that can be transmitted over the networks to the remote computers;

wherein the metafiles can be viewed by users operating the remote computers without the need to run the native authoring programs on the remote computers.

product lifecycle management software running on at least some of the servers,

requirements management software running on at lest some of the servers, and

code for linking the requirements trees produced by the requirements management software to at least some of the database elements;

wherein the code for linking the requirements trees to at least some of the database elements link the requirements trees to the database elements according to a requirements tree context management module;

the requirements tree context management module being capable of following predetermined rules for determining which portions of the requirements trees are redacted or exposed to users who are using the remote computers.

24. The PNM system of claim 23, wherein the file decoder programs are capable of decoding files comprised of files selected from the group consisting of 2 and 3D computer assisted design (CAD) formats, AutoCAD, CATIA, CADKEY, HPGL, Inventor, ME10, MicroStation, Pro/E, Solid Edge, SolidWorks, STEP, Unigraphics, VISIO, VRML formats into a common metafile format;

and

wherein the file decoder programs are also capable of decoding files comprised of files selected from electronic design automation (EDA) formats, Cadence, GDS II, GERBER, Mentor, PADS, PCAD, and Zuken formats into a common metafile format;

and wherein the file decoder programs are capable of decoding files selected from the group consisting of mechanical engineering programs, electrical engineering programs, IC/Device engineering programs, and software engineering programs into a common metafile format.

25. The PNM system of claim 23, wherein the code for linking requirements trees to at least some of the database elements transfer this link to the common metafile type by linking sections of the metafile to the requirements trees according to the requirements tree context management module following the predetermined rules.

26. The PNM system of claim 23, wherein the predetermined rules determine how much of the requirements trees to redact or expose based upon predetermined linkages between the database elements and the requirements tree, and redact the portions of the requirements tree that do not set requirements for those database elements.

27. The PNM system of claim 23, wherein the predetermined rules determine how much of the requirements trees to redact or expose based upon criteria comprising criteria selected from the group consisting of management security lockouts, user organization, user department, and user access level.

28. The PMN system of claim 23, wherein the file decoder programs, the requirements management software and optionally the product lifecycle management software cooperate to produce an indexed metafile of the file types;

the indexed metafile comprising the file type metafile and additionally containing index pointers that link database elements in the file type metafile to the portions of the requirements trees;

the portions of the requirements tree redacted or exposed according to the requirements tree context management module and the predetermined rules,

wherein the servers transmit the indexed metafile over the networks to the remote computers, and which the indexed metafile resides in a memory cache in the remote computers.

29. The PNM system of claim 23, wherein the database elements comprise data selected from the 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.

30. The PMN system of claim 28, wherein the servers additionally transmit a portion of the requirements trees to the remote computers,

the portion of the requirements tree being in a file that is separate from the indexed metafile,

the portion of the requirements tree being exposed or redacted by the server prior to transmission according to the database elements contained in the indexed metafile and the requirements tree context management module and the predetermined rules.

31. The PMN system of claim 28, wherein portions of the requirements trees that are exposed by the context tree management module and the predetermined rules are incorporated into the indexed metafile creating an annotated metafile;

the annotated metafile comprising the file type metafile, annotation pointers that link database elements in the file type metafile to the portions of the requirements tree, and the redacted or exposed portions of the requirements tree created by the predetermined rules;

and wherein the annotated metafile is transmitted over the network to the remote computers.

32. The PNM system of claim 30, wherein the predetermined rules also allow the user to further determine how much of the requirement trees previously redacted or exposed by the predetermined rules to further redact or expose in a second-level redaction, the second-level redaction rules comprising criteria selected from the 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.

33. The PMN system of claim 32, wherein the user can export the annotated metafile as a stand alone document file intended to be read by a stand alone document viewer.

34. The PMN system of claim 33, wherein the stand alone document viewer is also capable of reading pdf document files.