USRE44450E1 - Multi-tiered structure for storing and displaying product and process variants - Google Patents

Multi-tiered structure for storing and displaying product and process variants Download PDF

Info

Publication number
USRE44450E1
USRE44450E1 US12/790,226 US79022610A USRE44450E US RE44450 E1 USRE44450 E1 US RE44450E1 US 79022610 A US79022610 A US 79022610A US RE44450 E USRE44450 E US RE44450E
Authority
US
United States
Prior art keywords
product
component
node
variant
linked
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
US12/790,226
Inventor
Peter Muehleck
Adam Polly
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
SAP SE
Original Assignee
SAP SE
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by SAP SE filed Critical SAP SE
Priority to US12/790,226 priority Critical patent/USRE44450E1/en
Application granted granted Critical
Publication of USRE44450E1 publication Critical patent/USRE44450E1/en
Assigned to SAP SE reassignment SAP SE CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: SAP AG
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00—Computer-aided design [CAD]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • G06Q10/0875—Itemisation or classification of parts, supplies or services, e.g. bill of materials
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Definitions

  • This invention relates to a computer based system and method for displaying component and process structures for configurable product classes stored in a data structure.
  • a database may contain component lists for hundreds of different products, the result being that the same component would be listed separately for each product with which it is associated. While such a system may be useful for manufacturing products, it is impractical from a design perspective. A designer cannot readily view, for example, the extent of specific products or product classes affected by a change to a particular component. Nor could he easily obtain a clear picture of which components are common to certain product classes, and which are specific only to a particular product within a class. Nor could he see the routing a particular product and its components through its production processes.
  • the system includes a data structure with a tree-like representation of the various components and subcomponents for a single model of a car. Each component is represented by a node and is associated with specific variants, such as “leather” and “vinyl” for the component “seat”.
  • the structure is limited to a single product class, however. Since there is no product hierarchy, components are mapped to at most one product class. Therefore, the system does not enable alternative viewing of components associated with broad product classes and components associated with particular products, as would be desirable both from design and production perspectives, respectively.
  • STEP Protocol ISO 10303-214 Another example of a system for depicting a similar structure is the STEP Protocol ISO 10303-214. Although this system can depict the processes as well as components for a particular product class, it does not distinguish between the actual production steps required for a general process, and those steps required for specific processes. Accordingly, the system cannot accurately maintain or display the actual production steps required for production of a particular product variant. Furthermore, STEP does not enable viewing of components and processes associated with different product classes, nor does it allow for more than one possible decomposition of a particular component.
  • a computer based system containing a hierarchy of product classes, whereby individual product components are mapped to all product classes with which the component is related, and all components of a particular product class can be displayed in a graphical format.
  • Specific component variants representing the concrete item used for a particular product variant, would also be associated with each component.
  • the processes required to assemble components would be mapped to those components, and specific variants of those processes, or the actual production steps associated with particular component variants, associated with each process.
  • the computer based system would enable viewing of all of the components and processes associated with any product class within the product class hierarchy on a display.
  • a computer based system is provided with a memory containing a product variant data structure with products grouped hierarchically by classes.
  • Components are mapped to all individual product classes with which they are associated.
  • Processes are mapped to all individual components with which they are associated.
  • Component variants and process variants which are the actual concrete items and production steps used to make a particular product, are associated with each component and process, respectively.
  • Product classes and sub-classes can be displayed graphically on a visual display in a tree-like format with their associated components, component variants, processes and/or process variants.
  • Components which are abstractions of concrete items used in the product, are represented by component nodes. Each component node is associated with a certain product class and with one or more component variants, representing the range of concrete items used in the product for that component.
  • the component “wheel” includes components “tire” and “rim”.
  • Specific component variants for “rim” may include aluminum rim, steel rim type A, and steel rim type B.
  • Component variants have a selection condition which selects the appropriate component variants for a specific product, or “product variant”, within the related product class. The set of all selected component variants forms the bill of materials for that particular product variant.
  • Processes which are abstractions of actual steps used in the production process, are represented by process nodes.
  • Each process node is generally associated with at least one component and with one or more process variants, which are the actual production steps that are employed for particular variants of the affected component or components.
  • the generalized process “mount door” may include a first process variant representing the actual production steps necessary to mount a regular door, and a second process variant representing the different production steps necessary to mount a door equipped, for example, with an automatic lift mechanism.
  • FIG. 1 shows the four-layer approach of the product variant data structure of the computer based system.
  • FIG. 2 shows an example of the application view “Engineering”-on the product family “transportation vehicle” in the data structure.
  • FIG. 3 shows an example for the application view “Materials Requirement Planning” on the product class “mountain bike” in the data structure.
  • FIG. 4 shows an example for the application view “Production and Process Planning (Routing)” associated with the process “mount door” in the data structure.
  • FIG. 5 is a flowchart of the method of displaying a graphical representation of an application view node.
  • FIG. 6 is a flowchart of the method of displaying the bill of materials for a particular product variant.
  • FIG. 7 shows the decomposition of a product class into narrower product classes in the data structure.
  • FIG. 8 shows component variants of a component node related to a product class in the data structure.
  • FIG. 9 shows an example of the alternative decomposition of a component in the data structure.
  • FIG. 10 shows a summary of the elements of the Product Variant Data Structure in a data model according to EXPRESS-G (ISO 10303-11).
  • the product variant data structure 1 of the computer based system is divided into four layers, as shown in FIG. 1 : the Product Layer 2 , the Application View Layer 3 , the Node Structure Layer 4 , and the Variant Layer 5 .
  • the top layer is the Product Layer 2 , which consists of a description of products and product families, each with particular characteristics. This layer may be hierarchically structured to show the relationship between product families. For example, the product class “Compact Car” may consist of sub-classes “Model A” and “Model B”, as shown.
  • the next layer enables the viewing of a particular product class in various ways, depending on departmental requirements.
  • Engineering for example, may need to see all top-level component nodes associated with a generic product class.
  • FIG. 2 shows the application view “Engineering” 13 , which is a collection of all top-level component nodes 101 that are associated with “Transportation Vehicle” or any of its subclasses “bicycle” “mountain bike” or “racing bike”.
  • materials requirement planning may require a view of all component nodes used in the production of a more specific product class.
  • FIG. 3 shows the application view “Production” 14 , which depicts all component nodes 101 used in the production of the more specific product class “mountain bike”.
  • FIG. 4 shows the application view “Production and Process-Planning (Routing)” 15 , which depicts the integration of product decomposition and process operations. Specifically, the process node “mount door” 104 is connected to component node “door” 105 and the nodes 106 representing its sub-components.
  • the Application View Layer 2 preferably stores different views for departments across the company.
  • the central processor of the computer based system converts the application view into a graphical representation for visual display on the display of the computer based system.
  • FIG. 5 is a flowchart showing the sequence of receiving the application view node from the user interface 20 , converting the application view node to a graphical representation 21 and displaying the graphical representation on a visual display 22 .
  • the user interface, central processor and display of SAP's R/3 system, among others, are suitable for receiving the input of the desired application view node, converting it into a graphical representation for visual display, and displaying the graphical representation.
  • the Node Structure Layer 4 represents the functional decomposition of the product into components and processes.
  • the primary elements of the Node Structure Layer 4 are nodes 101 , which include component nodes and process nodes.
  • Component nodes are abstractions of the concrete items that are used in the product. For example, a car may have a separate component node for “engine”, but not for a particular type of engine. Instead, the actual items that are used to produce the product are specified by component variants associated with the component nodes. Component variants are discussed in greater detail below in the context of the Variant Layer 5 .
  • Process nodes are linked to component nodes and are abstractions of the actual steps used to manipulate the component in the production process.
  • the component “door” may have a separate process node for “mount door”, but not for mounting a particular type of door, which may require different production steps. Instead, the actual production steps that are used to manipulate the component in the production process are specified by process variants associated with process nodes. Process variants are discussed in greater detail below in the context of the Variant Layer.
  • the Node Structure Layer 4 consists of all component nodes and process nodes for a particular product class. It has a multi-layer structure to portray components, their subordinate components, and related processes.
  • the lowest-level layer of the Product Variant Structure 1 is the Variant Layer 5 , which consists of variants 102 that are related to nodes 101 , including component variants that are related to component nodes, and process variants that are related to process nodes.
  • Component variants are concrete items that are used as part of the final product.
  • the component node is replaced by one of its related component variants. Since more than one component variant may be related to a component node, there is a selection condition associated with each component node that specifies the product characteristic for which each component variant is used. Accordingly, given a particular product with specific characteristics, or a product variant, the variant layer can supply its bill of materials.
  • the bill of materials for a particular product variant can be obtained by specifying the desired product variant through the user interface of the computer-based system, whereupon the central processor will apply the selection conditions to determine the bill of materials for the specified product variant, and display the specific component variants that are used in the product variant.
  • FIG. 6 shows the steps of receiving the selection of a product variant from the user interface 30 , employing the selection conditions associated with the component nodes 31 , and displaying the bill of materials on a visual display 32 .
  • the central processor can also display the specific process variants, or all of the actual production steps that are used in making the specified product variant, on a visual display.
  • SAP's R/3 system provides a suitable user interface, central processor, and visual display.
  • Process variants represent concrete operations used in the production process for concrete component variants.
  • Process variants are related to process nodes and are selected by a selection condition based upon the desired product variant (and hence the particular component variant). Accordingly, given a particular product with specific component variants, the variant layer can supply its concrete routing through actual production steps.
  • product classes 6 may be represented hierarchically, and consist of “producible” and “non-producible” categories.
  • product classes 6 may be represented hierarchically, and consist of “producible” and “non-producible” categories.
  • “transportation vehicle” 40 and “bicycle” 41 are nonproducible product classes used for structuring only
  • “mountain bike” 42 and “racing bike” 43 are producible product classes. Both the producible and non-producible classes and their associated nodes and variants can be viewed in the application view layer 3 .
  • Component nodes and process nodes are the primary elements of the product variant structure 1 of the computer based system.
  • the component node 101 “Engine” in a car may have the concrete item “2.4 1 6 cyl.” as one of its associated component variants.
  • a node 101 is depicted as a triangle with a letter designating its type 9 (“C” for component node and “P” for process node, for example).
  • a symbol 10 represents the name of the component or process, a number describes its related product class 6 , and bullet points for the variants 102 associated with that node 101 .
  • a variant differentiation function distinguishes attributes of component variants, such as quantity of a specific component variant or the selection condition, according to the product class 6 .
  • Nodes 101 are related to each other in three ways.
  • the component node “wheel” is connected to component nodes “rim” and “tire”. This is called a “decomposition type” node relationship.
  • a process node may also be decomposed into several process nodes, so the decomposition type node relationship may be of the type “CC” or “P-P”.
  • the “connection relationship” establishes the production process flow between component nodes and process nodes. Since processes may also connect to each other without an intervening component, the connection relationship can be of the type “C-P”, “P-C” and “P-P”.
  • nodes 101 are also connected to an application view, which establishes the connection between the Product Layer and the Node Structure Layer 4 of the Product Variant Structure 1 .
  • This is known as a view-type node relationship.
  • FIG. 9 shows how a component node 101 in the node structure layer may have more than one decomposition into subordinate components. The choice among decompositions may depend upon various criteria, including the plant where the product is manufactured. Different node segments 12 are provided for each alternative decomposition of a component into subordinate components.
  • FIG. 10 shows a summary of the Product Variant Structure 1 in a data model 14 with entities according to EXPRESS-G (ISO 10303-11).

Abstract

A computer based system is provided that is capable of displaying component and process structures for configurable product classes stored in a data structure. Product classes in the data structure are represented by product nodes. Components, which are abstractions of concrete items used in the product, are represented by component nodes. Component nodes are mapped to each product class with which the component is associated, and are associated with one or more component variants, which are concrete items used in the manufacture of a particular product variant. Process nodes, which are abstractions of actual steps required to produce a product variant, known as process variants, are represented by process nodes. The computer based system can display several alternative views of the data structure. For example, upon receiving a selection for a particular product class, the computer based system converts and can graphically display all component and process nodes associated with that product class. Alternatively, the system can receive input of a product variant and display all component variants used in its production, which is its bill of materials.

Description

This application is a continuation reissue application of an earlier reissue application (filed on Apr. 23, 2003, at Ser. No. 10/421,080 for the reissue of U.S. Pat. No. 6,223,094), now reissued U.S. Pat. No. Re. 41,476.
FIELD OF THE INVENTION
This invention relates to a computer based system and method for displaying component and process structures for configurable product classes stored in a data structure.
BACKGROUND
Many industries offer highly variant products to their customers, a prime example being the automotive industry. Automobile manufacturers typically offer several models to their customers, who can often choose among numerous options for a selected model. As a result, it becomes necessary for a manufacturer to keep track of hundreds of products and their corresponding component structures and related production processes. Manufacturing companies offering a high variance of products and wishing to maintain reasonable costs depend on an efficient information system for products and their associated components and processes.
Existing database systems for product structures tend to be redundant. For example, a database may contain component lists for hundreds of different products, the result being that the same component would be listed separately for each product with which it is associated. While such a system may be useful for manufacturing products, it is impractical from a design perspective. A designer cannot readily view, for example, the extent of specific products or product classes affected by a change to a particular component. Nor could he easily obtain a clear picture of which components are common to certain product classes, and which are specific only to a particular product within a class. Nor could he see the routing a particular product and its components through its production processes. These are important features from a cost perspective, since they enable a designer to make decisions as to whether or not to include, or to change, particular components based on the number of products or product classes that are affected. An accurate view of the components and processes associated with product classes is vital for efficient design and manufacturing.
A system for depicting products and their associated components was described at a presentation given by Volkswagen at the CIMData European Conference in 1997. The system includes a data structure with a tree-like representation of the various components and subcomponents for a single model of a car. Each component is represented by a node and is associated with specific variants, such as “leather” and “vinyl” for the component “seat”. The structure is limited to a single product class, however. Since there is no product hierarchy, components are mapped to at most one product class. Therefore, the system does not enable alternative viewing of components associated with broad product classes and components associated with particular products, as would be desirable both from design and production perspectives, respectively.
Another example of a system for depicting a similar structure is the STEP Protocol ISO 10303-214. Although this system can depict the processes as well as components for a particular product class, it does not distinguish between the actual production steps required for a general process, and those steps required for specific processes. Accordingly, the system cannot accurately maintain or display the actual production steps required for production of a particular product variant. Furthermore, STEP does not enable viewing of components and processes associated with different product classes, nor does it allow for more than one possible decomposition of a particular component.
It would be desirable to have a computer based system containing a hierarchy of product classes, whereby individual product components are mapped to all product classes with which the component is related, and all components of a particular product class can be displayed in a graphical format. Specific component variants, representing the concrete item used for a particular product variant, would also be associated with each component. Similarly, the processes required to assemble components would be mapped to those components, and specific variants of those processes, or the actual production steps associated with particular component variants, associated with each process. The computer based system would enable viewing of all of the components and processes associated with any product class within the product class hierarchy on a display.
SUMMARY OF THE INVENTION
It is accordingly an object of the invention to provide a computer based system having a data structure stored in memory, whereby products in the data structure are grouped hierarchically by classes and subclasses.
It is a further object of the invention to provide within the data structure component nodes and process nodes representing individual components and processes used within each of those product classes and subclasses in the data structure.
It is a further object of the invention to map those component and process nodes to each of their associated product classes and subclasses within the data structure.
It is a further object of the invention to provide within the data structure component variants for individual component nodes, representing the range of concrete items used for that component and their quantities.
It is a further object of the invention to provide within the data structure process variants for each process node, representing the range of production steps used for that process.
It is a further object of the invention to provide within the data structure a selection condition that specifies the particular component variant and process variant to be used for a particular product variant according to the specific product characteristics of the product variant.
It is a further object of the invention to support more than one possible decomposition for a particular component within the data structure.
It is a further object of the invention to enable graphical viewing on a visual display of all components associated with a product class specified through a user interface.
It is a further object of the invention to enable graphical viewing on a visual display all processes associated with components within a product class specified through a user interface.
It is a further object of the invention to enable graphical viewing on a visual display all components for a specific product variant, which is the bill of materials for that product variant.
In accordance with these and other objects, a computer based system is provided with a memory containing a product variant data structure with products grouped hierarchically by classes. Components are mapped to all individual product classes with which they are associated. Processes are mapped to all individual components with which they are associated. Component variants and process variants, which are the actual concrete items and production steps used to make a particular product, are associated with each component and process, respectively. Product classes and sub-classes can be displayed graphically on a visual display in a tree-like format with their associated components, component variants, processes and/or process variants.
Components, which are abstractions of concrete items used in the product, are represented by component nodes. Each component node is associated with a certain product class and with one or more component variants, representing the range of concrete items used in the product for that component. For example, the component “wheel” includes components “tire” and “rim”. Specific component variants for “rim” may include aluminum rim, steel rim type A, and steel rim type B. Component variants have a selection condition which selects the appropriate component variants for a specific product, or “product variant”, within the related product class. The set of all selected component variants forms the bill of materials for that particular product variant.
Processes, which are abstractions of actual steps used in the production process, are represented by process nodes. Each process node is generally associated with at least one component and with one or more process variants, which are the actual production steps that are employed for particular variants of the affected component or components. For example, the generalized process “mount door” may include a first process variant representing the actual production steps necessary to mount a regular door, and a second process variant representing the different production steps necessary to mount a door equipped, for example, with an automatic lift mechanism.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 shows the four-layer approach of the product variant data structure of the computer based system.
FIG. 2 shows an example of the application view “Engineering”-on the product family “transportation vehicle” in the data structure.
FIG. 3 shows an example for the application view “Materials Requirement Planning” on the product class “mountain bike” in the data structure.
FIG. 4 shows an example for the application view “Production and Process Planning (Routing)” associated with the process “mount door” in the data structure.
FIG. 5 is a flowchart of the method of displaying a graphical representation of an application view node.
FIG. 6 is a flowchart of the method of displaying the bill of materials for a particular product variant.
FIG. 7 shows the decomposition of a product class into narrower product classes in the data structure.
FIG. 8 shows component variants of a component node related to a product class in the data structure.
FIG. 9 shows an example of the alternative decomposition of a component in the data structure.
FIG. 10 shows a summary of the elements of the Product Variant Data Structure in a data model according to EXPRESS-G (ISO 10303-11).
 DETAILED DESCRIPTION
The product variant data structure 1 of the computer based system is divided into four layers, as shown in FIG. 1: the Product Layer 2, the Application View Layer 3, the Node Structure Layer 4, and the Variant Layer 5. The top layer is the Product Layer 2, which consists of a description of products and product families, each with particular characteristics. This layer may be hierarchically structured to show the relationship between product families. For example, the product class “Compact Car” may consist of sub-classes “Model A” and “Model B”, as shown.
The next layer, the Application View Layer 3, enables the viewing of a particular product class in various ways, depending on departmental requirements. Engineering, for example, may need to see all top-level component nodes associated with a generic product class. FIG. 2 shows the application view “Engineering” 13, which is a collection of all top-level component nodes 101 that are associated with “Transportation Vehicle” or any of its subclasses “bicycle” “mountain bike” or “racing bike”. Similarly, materials requirement planning may require a view of all component nodes used in the production of a more specific product class. FIG. 3 shows the application view “Production” 14, which depicts all component nodes 101 used in the production of the more specific product class “mountain bike”. Production planning, by contrast, may need to view the routing of a particular product through its production steps, and so would need to see all process nodes associated with a particular product class, and all component nodes associated with those process nodes. FIG. 4 shows the application view “Production and Process-Planning (Routing)” 15, which depicts the integration of product decomposition and process operations. Specifically, the process node “mount door” 104 is connected to component node “door” 105 and the nodes 106 representing its sub-components.
The Application View Layer 2 preferably stores different views for departments across the company. Upon specification through the user interface of the desired application view node, the central processor of the computer based system converts the application view into a graphical representation for visual display on the display of the computer based system. FIG. 5 is a flowchart showing the sequence of receiving the application view node from the user interface 20, converting the application view node to a graphical representation 21 and displaying the graphical representation on a visual display 22. The user interface, central processor and display of SAP's R/3 system, among others, are suitable for receiving the input of the desired application view node, converting it into a graphical representation for visual display, and displaying the graphical representation.
The Node Structure Layer 4 represents the functional decomposition of the product into components and processes. The primary elements of the Node Structure Layer 4 are nodes 101, which include component nodes and process nodes. Component nodes are abstractions of the concrete items that are used in the product. For example, a car may have a separate component node for “engine”, but not for a particular type of engine. Instead, the actual items that are used to produce the product are specified by component variants associated with the component nodes. Component variants are discussed in greater detail below in the context of the Variant Layer 5. Process nodes are linked to component nodes and are abstractions of the actual steps used to manipulate the component in the production process. For example, the component “door” may have a separate process node for “mount door”, but not for mounting a particular type of door, which may require different production steps. Instead, the actual production steps that are used to manipulate the component in the production process are specified by process variants associated with process nodes. Process variants are discussed in greater detail below in the context of the Variant Layer. The Node Structure Layer 4 consists of all component nodes and process nodes for a particular product class. It has a multi-layer structure to portray components, their subordinate components, and related processes.
The lowest-level layer of the Product Variant Structure 1 is the Variant Layer 5, which consists of variants 102 that are related to nodes 101, including component variants that are related to component nodes, and process variants that are related to process nodes. Component variants are concrete items that are used as part of the final product. When a particular product is built, the component node is replaced by one of its related component variants. Since more than one component variant may be related to a component node, there is a selection condition associated with each component node that specifies the product characteristic for which each component variant is used. Accordingly, given a particular product with specific characteristics, or a product variant, the variant layer can supply its bill of materials. The bill of materials for a particular product variant can be obtained by specifying the desired product variant through the user interface of the computer-based system, whereupon the central processor will apply the selection conditions to determine the bill of materials for the specified product variant, and display the specific component variants that are used in the product variant. FIG. 6 shows the steps of receiving the selection of a product variant from the user interface 30, employing the selection conditions associated with the component nodes 31, and displaying the bill of materials on a visual display 32. The central processor can also display the specific process variants, or all of the actual production steps that are used in making the specified product variant, on a visual display. SAP's R/3 system, among others, provides a suitable user interface, central processor, and visual display.
Process variants represent concrete operations used in the production process for concrete component variants. Process variants are related to process nodes and are selected by a selection condition based upon the desired product variant (and hence the particular component variant). Accordingly, given a particular product with specific component variants, the variant layer can supply its concrete routing through actual production steps.
Component variants are selected and final products are produced by specifying characteristics of a particular product class. As shown in FIG. 7, product classes 6 may be represented hierarchically, and consist of “producible” and “non-producible” categories. For example, “transportation vehicle” 40 and “bicycle” 41 are nonproducible product classes used for structuring only, while “mountain bike” 42 and “racing bike” 43 are producible product classes. Both the producible and non-producible classes and their associated nodes and variants can be viewed in the application view layer 3.
Component nodes and process nodes are the primary elements of the product variant structure 1 of the computer based system. The component node 101 “Engine” in a car, may have the concrete item “2.4 1 6 cyl.” as one of its associated component variants. As shown in FIG. 8, a node 101 is depicted as a triangle with a letter designating its type 9 (“C” for component node and “P” for process node, for example). A symbol 10 represents the name of the component or process, a number describes its related product class 6, and bullet points for the variants 102 associated with that node 101. Since component nodes may be related to more than one product class 6, a variant differentiation function distinguishes attributes of component variants, such as quantity of a specific component variant or the selection condition, according to the product class 6.
Nodes 101 are related to each other in three ways. In a car, for example, the component node “wheel” is connected to component nodes “rim” and “tire”. This is called a “decomposition type” node relationship. A process node may also be decomposed into several process nodes, so the decomposition type node relationship may be of the type “CC” or “P-P”. The “connection relationship” establishes the production process flow between component nodes and process nodes. Since processes may also connect to each other without an intervening component, the connection relationship can be of the type “C-P”, “P-C” and “P-P”.
As shown in FIGS. 2 and 3, nodes 101 are also connected to an application view, which establishes the connection between the Product Layer and the Node Structure Layer 4 of the Product Variant Structure 1. This is known as a view-type node relationship. FIG. 9 shows how a component node 101 in the node structure layer may have more than one decomposition into subordinate components. The choice among decompositions may depend upon various criteria, including the plant where the product is manufactured. Different node segments 12 are provided for each alternative decomposition of a component into subordinate components.
FIG. 10 shows a summary of the Product Variant Structure 1 in a data model 14 with entities according to EXPRESS-G (ISO 10303-11).
While there have been shown and described and pointed out fundamental novel features of the invention as applied to embodiments thereof, it will be understood that various omissions and substitutions and changes in the form and details of the invention, as herein disclosed, may be made by those skilled in the art without departing from the spirit of the invention. It is expressly intended that all combinations of those elements and/or method steps which perform substantially the same function in substantially the same way to achieve the same results are within the scope of the invention. It is the intention, therefore, to be limited only as indicated by the scope of the claims appended hereto.

Claims (37)

We claim:
1. A computer based system for displaying components and processes associated with configurable product classes, comprising a display, a memory, a central processor and a user interface, wherein said memory has a data structure, said data structure comprises:
a) a product layer comprising at least one product, wherein each product is represented by a product class;
b) a node structure layer comprising
at least one component node, wherein each of said at least one component node represents a component, and wherein said each of said at least one component node is linked to the product class representing the respective one of said at least one product in which said component is used, and
at least one process node, wherein each of said at. least one process node represents a process, and wherein said each of said at least one process node is linked to the product class representing the respective one of said at least one product in whose manufacture said process is used, and wherein said each of said at least one process node is also linked to the respective one of said at least one component node representing a component used in said process represented by said each of said at least one process node;
c) a variant layer comprising
at least one component variant, wherein each of said at least one component variant is associated with one of said at least one component node, and wherein said each of said at least one component variant represents a concrete item that is used in a specific product variant of the respective one of said at least one product represented by the product class to which said one of said at least one component node associated with said each of said at least one component variant is linked;
at least one process variant, wherein each of said at least one process variant is associated with one of said at least one process node, and wherein said each of said at least one process variant represents actual production steps used in the manufacture of a specific product variant of the respective one of said at least one product represented by the product class to which said one of said at least one process node associated with said each of said at least one process variant is linked;
d) an application view layer comprising
at least one application view node, wherein each of said at least one application view node is linked to a product class, and wherein said each of said at least one application view node comprises at least one of
a collection of all component nodes that are linked to the product class to which the respective one of said each of said at least one application view node is linked, and
a collection of all process nodes that are linked to said product class to which the respective one of said each of said at least one application view node is linked; and
wherein said user interface is used to receive a selection of one of said at least one application view node, and wherein said central processor converts said selected application view node into a graphical representation for visual display on said display.
2. The computer based system of claim 1, wherein each of said at least one component variant is associated with a selection condition that indicates which of said at least one component variant is used in said specific product variant according to specific product characteristics of said specific product variant.
3. The computer based system of claim 2, wherein said user interface is used to receive a selection of said specific product variant, and wherein said central processor employs said selection condition for each of said at least one component node linked to the product class of said specific product variant to determine all component variants associated with said selected product variant in said data structure, which is the bill of materials for said specific product variant, and wherein said central processor displays said bill of materials for said specific product variant on said display.
4. The computer based system of claim 1, wherein said at least one product is a plurality of products, and wherein said plurality of products are arranged based on the hierarchical relationship between product classes.
5. The computer based system of claim 1, wherein said at least one component node is a plurality of component nodes, and wherein said plurality of component nodes are arranged based on the hierarchical relationship between components.
6. The computer based system of claim 5, wherein said hierarchical relationship between components depicts the decomposition of components into sub-components.
7. The computer based system of claim 6, wherein there are a plurality of decompositions of a particular component into sub-components.
8. The computer based system of claim 7, wherein selection of one of said plurality of decompositions for a particular component into sub-components is based on the plant where the product associated with said particular component is manufactured.
9. A method of graphically displaying components and processes associated with configurable products stored in a data structure, the data structure comprising:
a) a product layer comprising at least one product, wherein each product is represented by a product class;
b) a node structure layer comprising
at least one component node, wherein each of said at least one component node represents a component, and wherein said each of said at least one component node is linked to the product class representing the respective one of said at least one product in which said component is used, and
at least one process node, wherein each of said at least one process node represents a process, and wherein said each of said at least one process node is linked to the product class representing the respective one of said at least one product in whose manufacture said process is used, and wherein said each of said at least one process node is also linked to the respective one of said at least one component node representing a component used in said process represented by said each of said at least one process node;
c) a variant layer comprising
at least one component variant, wherein each of said at least one component variant is associated with one of said at least one component node, and wherein said each of said at least one component variant represents a concrete item that is used in a specific product variant of the respective one of said at least one product represented by the product class to which said one of said at least one component node associated with said each of said at least one component variant is linked;
at least one process variant, wherein each of said at least one process variant is associated with one of said at least one process node, and wherein said each of said at least one process variant represents actual production steps used in the manufacture of a specific product variant of the respective one of said at least one product represented by the product class to which said one of said at least one process node associated with said each of said at least one process variant is linked;
d) an application view layer comprising
at least one application view node, wherein each of said at least one application view node is linked to a product class, and wherein said each of said at least one application view node comprises at least one of
a collection of all component nodes that are linked to the product class to which the respective one of said each of said at least one application view node is linked, and
a collection of all process nodes that are linked to said product class to which the respective one of said each of said at least one application view node is linked;
the method comprising the steps of
i) receiving a selection of one of said at least one application view node from a user interface;
ii) converting said one of said at least one application view node into a graphical representation for visual display; and
iii) displaying said graphical representation on a display.
10. The method of claim 9, wherein each of said at least one component variant is associated with a selection condition that indicates which of said at least one component variant is used in said specific product variant according to specific product characteristics of said specific product variant.
11. The method of claim 10, wherein said user interface is used to receive a selection of said specific product variant, and wherein said central processor employs said selection condition for each of said at least one component node linked to the product class of said specific product variant to determine all component variants associated with said selected product variant in said data structure, which is the bill of materials for said specific product variant, and wherein said central processor displays said bill of materials for said specific product variant on said display.
12. The method of claim 9, wherein said at least one product is a plurality of products, and wherein said plurality of products are arranged based on the hierarchical relationship between product classes.
13. The method of claim 9, wherein said at least one component node is a plurality of component nodes, and wherein said plurality of component nodes are arranged based on the hierarchical relationship between components.
14. The method of claim 13, wherein said hierarchical relationship between components depicts the decomposition of components into sub-components.
15. The method of claim 14, wherein there are a plurality of decompositions of a particular component into sub-components.
16. The method of claim 15, wherein selection of one of said plurality of decompositions for a particular component into sub-components is based on the plant where the product associated with said particular component is manufactured.
17. A computer based system for displaying components and processes associated with hierarchical product classes, comprising a display, a memory, a central processor and a user interface, wherein said memory has a data structure, said data structure comprises:
a) a product layer comprising at least one product, wherein each product is represented by a product class;
b) a node structure layer comprising
at least one component node, wherein each of said at least one component node represents a component, and wherein said each of said at least one component node is linked to the product class representing the respective one of said at least one product in which said component is used, and
at least one process node, wherein each of said at least one process node represents a process, and wherein said each of said at least one process node is linked to the product class representing the respective one of said at least one product in whose manufacture said process is used, and wherein said each of said at least one process node is also linked to the respective one of said at least one component node representing a component used in said process represented by said each of said at least one process node;
c) a variant layer comprising
at least one component variant, wherein each of said at least one component variant is associated with one of said at least one component node, and wherein said each of said at least one component variant represents a concrete item that is used in a specific product variant of the respective one of said at least one product represented by the product class to which said one of said at least one component node associated with said each of said at least one component variant is linked;
at least one process variant, wherein each of said at least one process variant is associated with one of said at least one process node, and wherein said each of said at least one process variant represents actual production steps used in the manufacture of a specific product variant of the respective one of said at least one product represented by the product class to which said one of said at least one process node associated with said each of said at least one process variant is linked;
d) an application view layer comprising
at least one application view node, wherein each of said at least one application view node is linked to a product class, and wherein said each of said at least one application view node comprises at least one of
a collection of all component nodes that are linked to the product class to which the respective one of said each of said at least one application view node is linked, and
a collection of all process nodes that are linked to said product class to which the respective one of said each of said at least one application view node is linked;
the computer based system further comprising
i) means for receiving a selection of one of said at least one application view node from a user interface;
ii) means for converting said selected application view node into a graphical representation for visual display; and
iii) means for displaying said graphical representation on a display.
18. The computer based system of claim 17, wherein each of said at least one component variant is associated with a selection condition that indicates which of said at least one component variant is used in said specific product variant according to specific product characteristics of said specific product variant.
19. The computer based system of claim 18, wherein said user interface is used to receive a selection of said specific product variant, and wherein said central processor employs said selection condition for each of said at least one component node linked to the product class of said specific product variant to determine all component variants associated with said selected product variant in said data structure, which is the bill of materials for said specific product variant, and wherein said central processor displays said bill of materials for said specific product variant on said display.
20. The computer based system of claim 17, wherein said at least one product is a plurality of products, and wherein said plurality of products are arranged based on the hierarchical relationship between product classes.
21. The computer based system of claim 17, wherein said at least one component node is a plurality of component nodes, and wherein said plurality of component nodes are arranged based on the hierarchical relationship between components.
22. The computer based system of claim 21, wherein said hierarchical relationship between components depicts the decomposition of components into sub-components.
23. The computer based system of claim 22, wherein there are a plurality of decompositions of a particular component into sub-components.
24. The computer based system of claim 23, wherein selection of one of said plurality of decompositions for a particular component into sub-components is based on the plant where the product associated with said particular component is manufactured.
25. A computer based system for displaying components and processes associated with configurable product classes, comprising a display, a memory, a central processor and a user interface, wherein said memory has a data structure, said data structure comprises:
a) a product layer comprising a product represented by a product class;
b) a node structure layer comprising
a component node, wherein said component node represents a component, and wherein said component node is linked to said product class, and
a process node, wherein said process node represents a process, and wherein said process node is linked to said product class, and wherein said process node is also linked to said component node;
c) a variant layer comprising
a component variant, wherein said component variant is associated with said component node, and wherein said component variant represents a concrete item that is used in a specific product variant of said product represented by said product class;
a process variant, wherein said process variant is associated with said process node, and wherein said process variant represents actual production steps that are used in the manufacture of a specific product variant of said product represented by said product class;
d) an application view layer comprising
an application view node, wherein said application view node is linked to said product class, and wherein said application view node comprises at least one of said component node and said process node;
wherein said user interface is used to receive a selection of said application view node, and wherein said central processor converts said selected application view node into a graphical representation for visual display on said display.
26. A computer-based system comprising a memory having a data structure, said data structure comprising
a representation of a product having product variants,
a component node linked to said product representation and associated with component variants used in the product variants, and
a process node linked to the component node and associated with actual production steps that are used in the manufacture of product variants.
27. A medium bearing a data structure, said data structure comprising:
a representation of a product having product variants,
a component node linked to said product representation and associated with component variants used in the product variants, and
a process node linked to the component node and associated with specific production steps that are used in the manufacture of product variants.
28. A computer-based method comprising:
representing products by a product class;
linking to the product class a component node that represents a component and a process node that represents a process, the process node being linked to the component node,
associating component variants with the component node, the component variants representing items that are used in the product variants, and
associating process variants with a process node that represent actual production steps that are used in the manufacture of the product variants of the product.
29. The method of claim 28 also including
converting an application view node linked to the product class into a graphical representation for visual display.
30. The method of claim 29 also including
receiving from a user interface a selection of an application view node.
31. A method comprising
displaying a user interface,
receiving a selection by a user of an application view node that is linked to a product class and is associated with at least one of a component node associated with the product class or a process node associated with the product class,
the component node being associated with component variants and the process node being associated with process variants, the component variants representing items and the process variants representing actual production steps that are used in the manufacture of the product variants, and
converting the selected application view node into a graphical representation for visual display.
32. A computer implemented method for handling a product in a production process, wherein the product has a plurality of product variants, comprising:
providing a plurality of component nodes, wherein each component node is an abstraction of a concrete item that is used in the product;
assigning at least one component variant to each component node, wherein each component variant specifies a concrete item that can be used for the manufacture of a particular product variant of the product, so that for a component node of the product only a component variant that is assigned to the component node can be selected;
connecting a plurality of component nodes through a plurality of process nodes, wherein a process node is an abstraction of the actual steps used to manipulate the components that it is linked to; and
assigning at least one process variant to each process node, wherein a process variant represents concrete operations used in the production process for the components linked to a corresponding process node.
33. The method of claim 32 further comprising:
associating at least one selection condition with each component node, wherein each selection condition specifies a product characteristic for which a specific component variant is used;
obtaining a bill of materials for a specified product variant by employing the selection conditions to determine the component variants that are used in the specified product variant.
34. A computer system for handling a product in a production process, wherein the product has a plurality of product variants, comprising the following means:
a means for providing a plurality of component nodes, wherein each component node is an abstraction of a concrete item that is used in the product;
a means for assigning at least one component variant to each component node,
wherein each component variant specifies a concrete item that can be used for the manufacture of a particular product variant of the product, so that for a component node of the product only a component variant that is assigned to the component node can be selected;
a means for connecting a plurality of component nodes through a plurality of process nodes, wherein a process node is an abstraction of the actual steps used to manipulate the components that it is linked to; and
a means for assigning at least one process variant to each process node, wherein a process variant represents concrete operations used in the production process for the components linked to a corresponding process node.
35. The computer system of claim 34 comprising the further means:
a means for associating at least one selection condition with each component node, wherein each selection condition specifies a product characteristic for which a specific component variant is used;
a means for obtaining a bill of materials for a specified product variant by employing the selection conditions to determine the component variants that are used in the specified product variant.
36. A computer system for handling a product in a production process, wherein the product has a plurality of product variants, comprising:
a memory storing a data structure, wherein the data structure provides the following data:
a) a plurality of component nodes, wherein each component node is an abstraction of a concrete item that is used in the product;
b) a plurality of component variants, wherein each component variant specifies a concrete item that can be used for the manufacture of a particular product variant of the product, so that for a component node of the product only a component variant that is assigned to the component node can be selected;
c) a plurality of process nodes, wherein each process node is an abstraction of the actual steps used to manipulate the components that it is linked to;
d) a plurality of process variants, wherein each process variant represents concrete operations used in the production process for the components linked to a corresponding process node; and
a processor executing the following steps:
a) assigning at least one component variant to each component node;
b) connecting a plurality of component nodes through a plurality of process nodes; and
c) assigning at least one process variant to each process node.
37. The computer system of claim 36, wherein
the data structure further provides a plurality of selection conditions, each selection condition specifying a component variant to be used for a specified product variant according to a product characteristic of the specific product variant; and
the processor obtaining a bill of materials for the specified product variant, the bills of materials comprising component variants that are determined by employing the selection conditions and that are used in the specified product variant.
US12/790,226 1998-08-21 2010-05-28 Multi-tiered structure for storing and displaying product and process variants Expired - Lifetime USRE44450E1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/790,226 USRE44450E1 (en) 1998-08-21 2010-05-28 Multi-tiered structure for storing and displaying product and process variants

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US09/138,147 US6223094B1 (en) 1998-08-21 1998-08-21 Multi-tiered structure for storing and displaying product and process variants
US10/421,080 USRE41476E1 (en) 1998-08-21 2003-04-23 Multi-tiered structure for storing and displaying product and process variants
US12/790,226 USRE44450E1 (en) 1998-08-21 2010-05-28 Multi-tiered structure for storing and displaying product and process variants

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/138,147 Reissue US6223094B1 (en) 1998-08-21 1998-08-21 Multi-tiered structure for storing and displaying product and process variants

Publications (1)

Publication Number Publication Date
USRE44450E1 true USRE44450E1 (en) 2013-08-20

Family

ID=22480650

Family Applications (3)

Application Number Title Priority Date Filing Date
US09/138,147 Ceased US6223094B1 (en) 1998-08-21 1998-08-21 Multi-tiered structure for storing and displaying product and process variants
US10/421,080 Expired - Lifetime USRE41476E1 (en) 1998-08-21 2003-04-23 Multi-tiered structure for storing and displaying product and process variants
US12/790,226 Expired - Lifetime USRE44450E1 (en) 1998-08-21 2010-05-28 Multi-tiered structure for storing and displaying product and process variants

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US09/138,147 Ceased US6223094B1 (en) 1998-08-21 1998-08-21 Multi-tiered structure for storing and displaying product and process variants
US10/421,080 Expired - Lifetime USRE41476E1 (en) 1998-08-21 2003-04-23 Multi-tiered structure for storing and displaying product and process variants

Country Status (7)

Country Link
US (3) US6223094B1 (en)
EP (2) EP1105822A1 (en)
JP (1) JP3581655B2 (en)
AU (2) AU765185B2 (en)
CA (1) CA2338630C (en)
IL (1) IL140749A0 (en)
WO (1) WO2000011579A1 (en)

Families Citing this family (83)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19949954B4 (en) * 1999-10-16 2007-12-06 Basf Coatings Ag Method for analyzing and optimizing a multi-stage manufacturing process
US7113919B1 (en) * 2000-02-29 2006-09-26 Chemdomain, Inc. System and method for configuring products over a communications network
WO2001067193A2 (en) * 2000-03-06 2001-09-13 Siemens Aktiengesellschaft Device and method for inputting machine parameters and for simulating and observing
JP2003529159A (en) * 2000-03-31 2003-09-30 エスアーペー アクチエンゲゼルシャフト Matrix method and system for supply chain management
WO2001075553A2 (en) * 2000-04-04 2001-10-11 Digital Site Systems, Inc. Vertically integrated construction business
US20040073617A1 (en) 2000-06-19 2004-04-15 Milliken Walter Clark Hash-based systems and methods for detecting and preventing transmission of unwanted e-mail
US8600783B2 (en) 2000-08-18 2013-12-03 The Crawford Group, Inc. Business to business computer system for communicating and processing rental car reservations using web services
US7899690B1 (en) 2000-08-18 2011-03-01 The Crawford Group, Inc. Extended web enabled business to business computer system for rental vehicle services
US7275038B1 (en) * 2000-08-18 2007-09-25 The Crawford Group, Inc. Web enabled business to business operating system for rental car services
US20030125992A1 (en) * 2001-12-26 2003-07-03 The Crawford Group, Inc. Web browser based computer network for processing vehicle rental transactions on a large scale
US20070226640A1 (en) * 2000-11-15 2007-09-27 Holbrook David M Apparatus and methods for organizing and/or presenting data
AU2002220172A1 (en) * 2000-11-15 2002-05-27 David M. Holbrook Apparatus and method for organizing and/or presenting data
US7123978B2 (en) * 2000-12-27 2006-10-17 Insyst Ltd. Method for dynamically targeting a batch process
US7349868B2 (en) 2001-05-15 2008-03-25 I2 Technologies Us, Inc. Pre-qualifying sellers during the matching phase of an electronic commerce transaction
SG108855A1 (en) * 2001-06-12 2005-02-28 United Technologies Corp Method and apparatus for managing maintenance operations
US7603317B2 (en) * 2001-06-19 2009-10-13 International Business Machines Corporation Using a privacy agreement framework to improve handling of personally identifiable information
US7069427B2 (en) * 2001-06-19 2006-06-27 International Business Machines Corporation Using a rules model to improve handling of personally identifiable information
US7962962B2 (en) 2001-06-19 2011-06-14 International Business Machines Corporation Using an object model to improve handling of personally identifiable information
US20030115108A1 (en) * 2001-12-17 2003-06-19 William Scott Method and system for designing and ordering products for manufacture on-line
US7130300B2 (en) * 2001-12-21 2006-10-31 Visteon Global Technologies, Inc. Use of phone—UART multiplexer to create low software overhead external access to internal data modem with wireless communications and phone
JP2003281198A (en) 2002-03-25 2003-10-03 Honda Motor Co Ltd Electronic part list system and creation method for electronic part list
JP3824152B2 (en) * 2002-03-26 2006-09-20 本田技研工業株式会社 Comprehensive inspection system and comprehensive inspection method
JP3824153B2 (en) 2002-03-26 2006-09-20 本田技研工業株式会社 Electronic parts list system
JP3824154B2 (en) * 2002-03-29 2006-09-20 本田技研工業株式会社 Equipment application calculation system and equipment application calculation method
JP3824155B2 (en) * 2002-03-29 2006-09-20 本田技研工業株式会社 Electronic parts list system and method for creating electronic parts list
US7085776B2 (en) * 2002-04-24 2006-08-01 The Boeing Company Logical hierarchical data model for sharing product information across product families
US20020188494A1 (en) * 2002-05-24 2002-12-12 United Technologies Corporation Method and apparatus for managing an operation
US20040039612A1 (en) * 2002-06-14 2004-02-26 Neil Fitzgerald Method and apparatus for customer direct on-line reservation of rental vehicles
US8108231B2 (en) 2002-06-14 2012-01-31 The Crawford Group, Inc. Method and apparatus for improved customer direct on-line reservation of rental vehicles
DE10247748A1 (en) * 2002-10-12 2004-04-22 Metzger, Uwe Value calculation using hierarchical networks
EP1413964A3 (en) * 2002-10-23 2006-08-02 Siemens Aktiengesellschaft Method and apparatus for automatic mapping of data elements while modeling a technical system
US7469217B2 (en) * 2002-12-10 2008-12-23 Savvis Communications Corporation Product toolkit system and method
US6732157B1 (en) 2002-12-13 2004-05-04 Networks Associates Technology, Inc. Comprehensive anti-spam system, method, and computer program product for filtering unwanted e-mail messages
US20040122750A1 (en) * 2002-12-18 2004-06-24 Gateway, Inc. Delivery refusal retest and pack process for direct mail order computers
US8078489B1 (en) * 2003-01-24 2011-12-13 Emcien, Inc. Product configuration modeling and optimization
US6925375B2 (en) * 2003-03-20 2005-08-02 Detroit Diesel Corporation System and method for determining a parameter set for an engine controller module
US6983187B2 (en) * 2003-08-14 2006-01-03 Sap Aktiengesellschaft Method and system for automatically generating selection conditions in a product configuration system
US20050044107A1 (en) * 2003-08-22 2005-02-24 Widner Steven W. Auto generation of build of material data
US7225038B2 (en) * 2003-09-26 2007-05-29 Sap Ag Method and system for checking consistency and completeness of selection conditions in a product configuration system
US20050137950A1 (en) * 2003-12-17 2005-06-23 International Business Machines Corporation Method and apparatus for a value framework and return on investment model
US20050144033A1 (en) * 2003-12-30 2005-06-30 Rational Systems, Llc Structured products based enterprise management system
US20050182666A1 (en) * 2004-02-13 2005-08-18 Perry Timothy P.J. Method and system for electronically routing and processing information
US7698159B2 (en) * 2004-02-13 2010-04-13 Genworth Financial Inc. Systems and methods for performing data collection
US7320003B2 (en) * 2004-02-13 2008-01-15 Genworth Financial, Inc. Method and system for storing and retrieving document data using a markup language string and a serialized string
JP4153883B2 (en) * 2004-03-02 2008-09-24 株式会社東芝 Hierarchical database device and product selection method and program in hierarchical database device
US7739080B1 (en) * 2004-04-19 2010-06-15 Versata Development Group, Inc. Consolidation of product data models
US20050251520A1 (en) * 2004-05-07 2005-11-10 Nrx Global Corp. Systems and methods for the matching of materials data to parts data
US7110842B2 (en) * 2004-05-18 2006-09-19 Paccar Inc. Modular design method
EP1628248A1 (en) * 2004-08-20 2006-02-22 Sap Ag Modelling a bill of materials for a configurable product in a managed supply chain.
US20060167778A1 (en) * 2004-09-21 2006-07-27 Whitebirch Software, Inc. Object-oriented financial modeling
DE102004053230B4 (en) * 2004-11-04 2006-07-20 Daimlerchrysler Ag Apparatus and method for configuring a product
JP4660264B2 (en) * 2005-04-22 2011-03-30 株式会社東芝 Information processing apparatus and program
US7734514B2 (en) * 2005-05-05 2010-06-08 Grocery Shopping Network, Inc. Product variety information
US8271309B2 (en) 2006-03-16 2012-09-18 The Crawford Group, Inc. Method and system for providing and administering online rental vehicle reservation booking services
US8117537B1 (en) * 2007-02-02 2012-02-14 The United States Of America As Represented By The United States Department Of Energy Platform-independent method for computer aided schematic drawings
US8234619B2 (en) * 2007-04-20 2012-07-31 Sap Ag System, method, and software for facilitating business object development testing
US20090158218A1 (en) * 2007-05-04 2009-06-18 Lockheed Martin Corporation Structured model navigator
US8060237B2 (en) * 2007-09-11 2011-11-15 The Boeing Company Method and apparatus for work instruction generation
US9087164B2 (en) * 2008-01-26 2015-07-21 National Semiconductor Corporation Visualization of tradeoffs between circuit designs
US7966588B1 (en) 2008-01-26 2011-06-21 National Semiconductor Corporation Optimization of electrical circuits
US8014886B2 (en) * 2008-05-12 2011-09-06 Ford Motor Company Method and system for generating an assembly configuration
US8078443B2 (en) * 2008-05-12 2011-12-13 Ford Motor Company Method and system for generating configuration constraints for computer models
US20100106280A1 (en) * 2008-10-29 2010-04-29 Siemens Aktiengesellschaft Method and an apparatus for identifying variable and common module variants in a product family and managing resulting variants
US20100318974A1 (en) * 2009-06-16 2010-12-16 Sap Ag Business object mockup architecture
JP5635247B2 (en) * 2009-08-20 2014-12-03 富士通株式会社 Multi-chip module
US10169308B1 (en) 2010-03-19 2019-01-01 Google Llc Method and system for creating an online store
US8713525B2 (en) * 2010-03-25 2014-04-29 International Business Machines Corporation Software management system for network data processing systems
US8712741B2 (en) 2010-06-28 2014-04-29 National Semiconductor Corporation Power supply architecture system designer
US8797342B2 (en) * 2010-09-10 2014-08-05 Siemens Aktiengesellschaft Method for visual project modeling
US9734503B1 (en) 2011-06-21 2017-08-15 Google Inc. Hosted product recommendations
US8700494B2 (en) 2011-09-06 2014-04-15 Google Inc. Identifying product variants
US8725763B2 (en) * 2011-11-23 2014-05-13 Siemens Product Lifecycle Management Software Inc. Massive model visualization with spatial indexing
US9836801B2 (en) 2012-01-23 2017-12-05 Quipip, Llc Systems, methods and apparatus for providing comparative statistical information in a graphical format for a plurality of markets using a closed-loop production management system
US9254583B2 (en) 2012-01-23 2016-02-09 Quipip, Llc Systems, methods and apparatus for providing comparative statistical information for a plurality of production facilities in a closed-loop production management system
US20150026077A1 (en) * 2013-07-18 2015-01-22 Netapp, Inc. Centralized Method for Customer Assistance and System Verification
US20150026076A1 (en) * 2013-07-18 2015-01-22 Netapp, Inc. System and Method for Providing Customer Guidance in Deploying a Computing System
US10184928B2 (en) 2014-01-29 2019-01-22 Quipip, Llc Measuring device, systems, and methods for obtaining data relating to condition and performance of concrete mixtures
US9194855B2 (en) 2014-02-28 2015-11-24 Quipip, Llc Systems, methods and apparatus for providing to a driver of a vehicle carrying a mixture real-time information relating to a characteristic of the mixture
US9442968B2 (en) 2014-03-31 2016-09-13 Sap Se Evaluation of variant configuration using in-memory technology
US9727596B2 (en) 2014-04-24 2017-08-08 International Business Machines Corporation Scalable visualization of a product and its variants
WO2016123228A1 (en) 2015-01-30 2016-08-04 Quipip, Llc Systems, apparatus and methods for testing and predicting the performance of concrete mixtures
US10614632B2 (en) 2015-04-23 2020-04-07 Siemens Industry Software Inc. Massive model visualization with a product lifecycle management system
US10318703B2 (en) 2016-01-19 2019-06-11 Ford Motor Company Maximally standard automatic completion using a multi-valued decision diagram

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4835709A (en) 1987-11-25 1989-05-30 Bell Communications Research, Inc. Assembly modeling process
US4862376A (en) * 1987-10-28 1989-08-29 International Business Machines Corp. Bill of material interface to CAD/CAM environment
US5109337A (en) * 1987-10-28 1992-04-28 Ibm Corporation Conceptual design tool
US5216613A (en) * 1971-04-16 1993-06-01 Texas Instruments Incorporated Segmented asynchronous operation of an automated assembly line
US5523942A (en) * 1994-03-31 1996-06-04 New England Mutual Life Insurance Company Design grid for inputting insurance and investment product information in a computer system
US5675784A (en) * 1995-05-31 1997-10-07 International Business Machnes Corporation Data structure for a relational database system for collecting component and specification level data related to products
US5708798A (en) 1993-03-29 1998-01-13 Trilogy Development Group Method and apparatus for configuring systems
US5740425A (en) * 1995-09-26 1998-04-14 Povilus; David S. Data structure and method for publishing electronic and printed product catalogs
EP0838773A1 (en) 1996-10-28 1998-04-29 Volkswagen Aktiengesellschaft Method and apparatus for handling the serial numbers of multiple components of a product
US5815395A (en) * 1995-06-29 1998-09-29 Interface Definition Systems, Inc. Diagnostic method and apparatus for configuration errors
US5980096A (en) * 1995-01-17 1999-11-09 Intertech Ventures, Ltd. Computer-based system, methods and graphical interface for information storage, modeling and stimulation of complex systems
US6112181A (en) * 1997-11-06 2000-08-29 Intertrust Technologies Corporation Systems and methods for matching, selecting, narrowcasting, and/or classifying based on rights management and/or other information

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2621172B2 (en) 1987-04-22 1997-06-18 トヨタ自動車株式会社 production management system
US4847761A (en) * 1987-09-24 1989-07-11 International Business Machines Corp. Automated bill of material
DE3911465C2 (en) 1989-04-06 1996-03-28 Licentia Gmbh Process for the automatic configuration of technical systems from components
US5119307A (en) 1989-12-22 1992-06-02 General Electric Company Method and system for automated bill-of-material generation
US5197001A (en) 1990-05-14 1993-03-23 International Business Machines Corp. Bill of material and project network processing
US5201046A (en) * 1990-06-22 1993-04-06 Xidak, Inc. Relational database management system and method for storing, retrieving and modifying directed graph data structures
US5210686A (en) 1990-10-19 1993-05-11 International Business Machines Corporation Multilevel bill of material processing
JP3447286B2 (en) 1990-11-28 2003-09-16 株式会社日立製作所 Production plan creation system and production plan creation method
US5307261A (en) 1991-06-28 1994-04-26 International Business Machines Corporation Method and system for product configuration management in a computer based manufacturing system
US5311424A (en) 1991-06-28 1994-05-10 International Business Machines Corporation Method and system for product configuration definition and tracking
JPH05233644A (en) 1991-12-05 1993-09-10 Internatl Business Mach Corp <Ibm> Method and system for optimizing transferring of material within computer base manufacturing system
JPH06215014A (en) 1993-01-18 1994-08-05 Mitsubishi Electric Corp Method and device for instructing number of products to be inserted and manufacturing system for the same
US6115547A (en) 1993-03-29 2000-09-05 Trilogy Development Group, Inc. Flash configuration cache
US5434791A (en) 1993-06-29 1995-07-18 Electronic Data Systems Corporation Product structure management
US5630070A (en) 1993-08-16 1997-05-13 International Business Machines Corporation Optimization of manufacturing resource planning
US5515269A (en) 1993-11-08 1996-05-07 Willis; Donald S. Method of producing a bill of material for a configured product
GB2289963B (en) 1994-05-25 1999-05-12 Matsushita Electric Ind Co Ltd Production line controller operated in accordance with generated production plans
JP3563132B2 (en) 1994-12-13 2004-09-08 富士通株式会社 Parts arrangement processing method
US5764519A (en) 1995-03-08 1998-06-09 Hitachi, Inc. Method and device for computing material requirements
US5764824A (en) 1995-08-25 1998-06-09 International Business Machines Corporation Clustering mechanism for identifying and grouping of classes in manufacturing process behavior
DE19614789C1 (en) 1996-04-06 1997-09-25 Daimler Benz Ag Process for the automatic configuration of a technical system taking into account different qualities of component external effects
EP0802495A3 (en) 1996-04-16 2002-03-06 Volkswagen Aktiengesellschaft Method and device for parameter oriented selection of groups of objects
US5974395A (en) 1996-08-21 1999-10-26 I2 Technologies, Inc. System and method for extended enterprise planning across a supply chain
US5825651A (en) 1996-09-03 1998-10-20 Trilogy Development Group, Inc. Method and apparatus for maintaining and configuring systems
US6040834A (en) * 1996-12-31 2000-03-21 Cisco Technology, Inc. Customizable user interface for network navigation and management
US6865524B1 (en) 1997-01-08 2005-03-08 Trilogy Development Group, Inc. Method and apparatus for attribute selection
GB2325066B (en) 1997-03-24 1999-06-02 Honda Motor Co Ltd Method of manufacturing dies
JPH10301604A (en) 1997-04-23 1998-11-13 Hitachi Ltd Material required amount calculating device and material required amount calculating method
US6141598A (en) 1998-04-06 2000-10-31 Hyundai Motor Company Vehicle assembly line control system and method

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5216613A (en) * 1971-04-16 1993-06-01 Texas Instruments Incorporated Segmented asynchronous operation of an automated assembly line
US4862376A (en) * 1987-10-28 1989-08-29 International Business Machines Corp. Bill of material interface to CAD/CAM environment
US5109337A (en) * 1987-10-28 1992-04-28 Ibm Corporation Conceptual design tool
US4835709A (en) 1987-11-25 1989-05-30 Bell Communications Research, Inc. Assembly modeling process
US5708798A (en) 1993-03-29 1998-01-13 Trilogy Development Group Method and apparatus for configuring systems
US5523942A (en) * 1994-03-31 1996-06-04 New England Mutual Life Insurance Company Design grid for inputting insurance and investment product information in a computer system
US5980096A (en) * 1995-01-17 1999-11-09 Intertech Ventures, Ltd. Computer-based system, methods and graphical interface for information storage, modeling and stimulation of complex systems
US5675784A (en) * 1995-05-31 1997-10-07 International Business Machnes Corporation Data structure for a relational database system for collecting component and specification level data related to products
US5815395A (en) * 1995-06-29 1998-09-29 Interface Definition Systems, Inc. Diagnostic method and apparatus for configuration errors
US5740425A (en) * 1995-09-26 1998-04-14 Povilus; David S. Data structure and method for publishing electronic and printed product catalogs
EP0838773A1 (en) 1996-10-28 1998-04-29 Volkswagen Aktiengesellschaft Method and apparatus for handling the serial numbers of multiple components of a product
US6112181A (en) * 1997-11-06 2000-08-29 Intertrust Technologies Corporation Systems and methods for matching, selecting, narrowcasting, and/or classifying based on rights management and/or other information

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
Erens, F. et al: "Product Modelling Using Multiple Levels of Abstraction Instances as Types" Computers in Industry, NL, Elsevier Science Publishers, Amsterdam. Bd. 24, Nr. 1, 1994, Seite 17-28.
Gu, P. et al: "Product modeling using step". Computer Aided Design, GB, Elsevier Publishers, BV., Barking Bd. 27, Nr. 3, 1995, Seite 163-179.
IBM Technical Disclosure Bulletin, vol. 33 issue 6B, p. 147-150, title: TFR Expert system Shell, Nov. 1990. *
Peters, H.D., "TI-Syncro-The New BoM Approach of Volkswagen," presentation at CIMData PDM Europe Conference, Nov. 28-30, 1997, in Noordwijk, Netherlands.
Peters, H.D., "TI-Syncro—The New BoM Approach of Volkswagen," presentation at CIMData PDM Europe Conference, Nov. 28-30, 1997, in Noordwijk, Netherlands.
STEP Application Protocol ISO 10303-214 Updated CDII Document (Sep. 30, 1997)-Core Data for Automotive Mechanical Design Processes, 1997, Technical University Darmstadt, Germany (Relevant sections enclosed).
STEP Application Protocol ISO 10303-214 Updated CDII Document (Sep. 30, 1997)—Core Data for Automotive Mechanical Design Processes, 1997, Technical University Darmstadt, Germany (Relevant sections enclosed).

Also Published As

Publication number Publication date
WO2000011579A1 (en) 2000-03-02
JP3581655B2 (en) 2004-10-27
JP2002523829A (en) 2002-07-30
CA2338630A1 (en) 2000-03-02
IL140749A0 (en) 2002-02-10
US6223094B1 (en) 2001-04-24
AU6079299A (en) 2000-03-14
CA2338630C (en) 2005-03-29
EP1231552A1 (en) 2002-08-14
AU765185B2 (en) 2003-09-11
AU2003268829B2 (en) 2005-11-24
USRE41476E1 (en) 2010-08-03
EP1105822A1 (en) 2001-06-13
AU2003268829A1 (en) 2004-01-22

Similar Documents

Publication Publication Date Title
USRE44450E1 (en) Multi-tiered structure for storing and displaying product and process variants
US5367627A (en) Computer-assisted parts sales method
US6785689B1 (en) Consolidation of multiple source content schemas into a single target content schema
US8700677B2 (en) Metadata driven customization of a software-implemented business process
US20050278296A1 (en) Method and system for creating, sustaining and using a transactional bill of materials (T-BOM ™)
US20080027970A1 (en) Business intelligent architecture system and method
KR20010093775A (en) Multi-dimensional data management system
CA2244388A1 (en) Computer-based method of structuring product configuration information and configuring a product
US20090063172A1 (en) Virtual vehicle system
CN111126906A (en) Automobile BOM data generation method and system
US7209869B1 (en) Method and system for resource requirement planning and generating a production schedule using a uniform data model
US8117157B2 (en) External evaluation processes
US20050197972A1 (en) Method of and system for assignment of price groups
US20050065804A1 (en) Method and system for furnishing of customized information to venues targeted to selected audiences
US7127307B2 (en) Generation/management apparatus of production processing structure in factory production management system
US20030120564A1 (en) Method and system for retail product management
JP2002523840A (en) Method and system of production schedule generation by resource requirement planning and uniform data model
JP2002318870A (en) Repair part order control system
US20040193623A1 (en) IC foundry manufacturing technology master data management structure
Brooks Design—the starting point for CIM
CN115934211A (en) Universal data mode applied to big data CDP field and application thereof
CN110910212B (en) Cross-information system order configuration logic conversion method and system
JP2000132630A (en) Vehicle information managing method
Karthik et al. Rapid Application Development of Process Capability: Supplier Models
CN114625932A (en) Method and device for determining vehicle body bill of materials

Legal Events

Date Code Title Description
AS Assignment

Owner name: SAP SE, GERMANY

Free format text: CHANGE OF NAME;ASSIGNOR:SAP AG;REEL/FRAME:033625/0334

Effective date: 20140707

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY