Navigating and authoring configured product lifecycle data

• US 10,409,922 B2
• Filed: 11/07/2014
• Issued: 09/10/2019
• Est. Priority Date: 06/10/2014
• Status: Active Grant

• Current Assignee: Siemens Industry Software Limited (Siemens AG)
• Original Assignee: Siemens Product Lifecycle Management Software Incorporated (Siemens AG)
• Inventors: Srinivasan, Krishnan, Ray, Charubrata, Kandi, Girish, Goyal, Nitin
• Primary Examiner(s): Dorais, Craig C
• Application Number:
  US14/535,844
• Publication Number:
  US 20150356211A1
• Time in Patent Office: 1,768 Days
• Field of Search: None
• CPC Class Codes: G06F 30/00 Computer-aided design [CAD]
• CPC Class Codes: G06F 30/13 Architectural design, e.g. computer-aided architectural design [CAAD] related to design of buildings, bridges, landscapes, production plants or roads
• CPC Class Codes: G06F 30/15 Vehicle, aircraft or watercraft design

Abstract

Methods for product data management and corresponding systems and computer-readable mediums. The systems and methods include receiving a request for expanded details about an architecture element of a model from an application client, parsing the request to identify the expanded details of the architecture element, identifying a structure and configuration details of the model, configuring the model according to the structure and configuration details, traversing the model to collect the expanded details for the architecture element, packaging the expanded details into an application format for the client, and returning the expanded details.

Claims

1. An application server comprising:

a network adapter configured to communicate with an application client;

an accessible memory configured to store server data; and

a processor operably coupled to the network adapter and the accessible memory, the processor configured to;

receive a request for expanded details about an architecture element of a model from the application client;

parse the request to identify the expanded details for a plurality of subsystems in the architecture element;

identify a structure and configuration details of the model stored in the server data;

configure the model according to the structure and configuration details, wherein the model includes a requirement development stage, a functional analysis stage, and a logical modeling stage;

data traverse the model to collect the expanded details for the plurality of subsystems in the architecture element, wherein the expanded details comprise ports on the architecture element, and connections between architecture elements;

package the expanded details by converting the server data into an application format for the application client; and

return the packaged expanded details to the application client,

wherein the application client incorporates the expanded details for the plurality of subsystems in the architecture element into a single diagram including the requirement development stage, the functional analysis stage, and the logical modeling stage.

2. The application server of claim 1, wherein the architecture element of a model comprises one of a requirement element, a feature element, a logical element, or a physical element.

3. The application server of claim 1, wherein the structure of the model comprises one of a bill of materials or an indexed representation.

4. The application server of claim 1, wherein the configuration details comprise model year and model package.

5. The application server of claim 1, wherein to parse the request comprises converting application data of the request to server data.

6. An application server comprising:

a network adapter configured to communicate with an application client;

an accessible memory configured to store server data; and

a processor operably coupled to the network adapter and the accessible memory, the processor configured to;

receive a request for expanded details about an architecture element of a model from the application client;

parse the request to identify the expanded details for a plurality of subsystems in the architecture element;

identify a structure and configuration details of the model stored in the server data;

configure the model according to the structure and configuration details, wherein the model includes a requirement development stage, a functional analysis stage, and a logical modeling stage;

data traverse the model to collect the expanded details for the plurality of subsystems in the architecture element;

package the expanded details by converting the server data into an application format for the application client, wherein the application format an XML data format; and

return the packaged expanded details to the application client,

wherein the application client incorporates the expanded details for the plurality of subsystems in the architecture element into a single diagram including the requirement development stage, the functional analysis stage, and the logical modeling stage.

7. A method for navigating and authoring configured product lifecycle data of a product data management (PDM) system, the method performed by an application server and comprising:

receiving a request for expanded details about an architecture element of a model from an application client;

parsing the request to identify the expanded details for a plurality of subsystems in the architecture element;

identifying a structure and configuration details of the model stored in server data;

configuring the model according to the structure and configuration details, wherein the model includes a requirement development stage, a functional analysis stage, and a logical modeling stage;

data traversing the model to collect the expanded details for the plurality of subsystems in the architecture element, wherein the expanded details comprise ports on the architecture element, and connections between architecture elements;

packaging the expanded details by converting the server data into an application format for the application client; and

return the packaged expanded details to the application client,

wherein the application client incorporates the expanded details for the plurality of subsystems in architecture element into a single diagram including the requirement development stage, the functional analysis stage, and the logical modeling stage.

8. The method of claim 7, wherein the architecture element of a model comprises one of a requirement element, a feature element, a logical element, or a physical element.

9. The method of claim 7, wherein the structure of the model comprises one of a bill of materials or an indexed representation.

10. The method of claim 7, wherein the configuration details comprise model year and model package.

11. The method of claim 7, wherein to parse the request comprises converting application data of the request to server data.

12. A method for navigating and authoring configured product lifecycle data of a product data management (PDM) system, the method performed by an application server and comprising:

receiving a request for expanded details about an architecture element of a model from an application client;

parsing the request to identify the expanded details for a plurality of subsystems in the architecture element;

identifying a structure and configuration details of the model stored in server data;

configuring the model according to the structure and configuration details, wherein the model includes a requirement development stage, a functional analysis stage, and a logical modeling stage;

data traversing the model to collect the expanded details for the plurality of subsystems in the architecture element;

packaging the expanded details by converting the server data into an application format for the application client, wherein the application format is an XML data format; and

return the packaged expanded details to the application client,

wherein the application client incorporates the expanded details for the plurality of subsystems in architecture element into a single diagram including the requirement development stage, the functional analysis stage, and the logical modeling stage.

13. A non-transitory computer-readable medium encoded with executable instructions that, when executed, cause one or more data processing systems to perform the steps of:

receiving a request for expanded details about an architecture element of a model from an application client;

parsing the request to identify the expanded details for a plurality of subsystems in the architecture element;

identifying a structure and configuration details of the model stored in server data;

configuring the model according to the structure and configuration details, wherein the model includes a requirement development stage, a functional analysis stage, and a logical modeling stage;

data traversing the model to collect the expanded details for the plurality of subsystems in the architecture element, wherein the expanded details comprise ports on the architecture element, and connections between architecture elements;

packaging the expanded details by converting the server data into an application format for the application client; and

returning the packaged expanded details to the application client,

wherein the application client incorporates the expanded details for the plurality of subsystems in the architecture element into a single diagram including the requirement development stage, the functional analysis stage, and the logical modeling stage.

14. The computer-readable medium of claim 13, wherein the architecture element of a model comprises one of a requirement element, a feature element, a logical element, or a physical element.

15. The computer-readable medium of claim 13, wherein the structure of the model comprises one of a bill of materials or an indexed representation.

16. The computer-readable medium of claim 13, wherein the configuration details comprise model year and model package.

17. A non-transitory computer-readable medium encoded with executable instructions that, when executed, cause one or more data processing systems to perform the steps of:

receiving a request for expanded details about an architecture element of a model from an application client;

parsing the request to identify the expanded details for a plurality of subsystems in the architecture element;

identifying a structure and configuration details of the model stored in server data;

configuring the model according to the structure and configuration details, wherein the model includes a requirement development stage, a functional analysis stage, and a logical modeling stage;

data traversing the model to collect the expanded details for the plurality of subsystems in the architecture element;

packaging the expanded details by converting the server data into an application format for the application client, wherein the application format is an XML data format; and

returning the packaged expanded details to the application client,

wherein the application client incorporates the expanded details for the plurality of subsystems in the architecture element into a single diagram including the requirement development stage, the functional analysis stage, and the logical modeling stage.