CA2338630C - Method and system for displaying and configuring component and process structures - Google Patents
Method and system for displaying and configuring component and process structures Download PDFInfo
- Publication number
- CA2338630C CA2338630C CA002338630A CA2338630A CA2338630C CA 2338630 C CA2338630 C CA 2338630C CA 002338630 A CA002338630 A CA 002338630A CA 2338630 A CA2338630 A CA 2338630A CA 2338630 C CA2338630 C CA 2338630C
- Authority
- CA
- Canada
- Prior art keywords
- component
- product
- 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 - Fee Related
Links
Classifications
-
- 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
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
Abstract
The invention relates to a computer-aided system which is capable of displaying component and process structures for configurable product classes, said product classes being stored in a data structure.
Product classes in the data structure are represented by product nodes. Components, which are abstractions of actual items used in the product, are represented by component nodes. Component nodes are mapped onto each product class to which the component is allocated, and are allocated to one or more component variants, these being actual items used in the production 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. On receiving the selection of a particular product class, the computer-aided system transfers all of the component nodes and process nodes that are allocated to this product class and is able to represent them graphically, for example.
Alternatively, the system receives the input of a product variant and displays all of the component variants used in the production of this product variant, in the form of lists of materials.
Product classes in the data structure are represented by product nodes. Components, which are abstractions of actual items used in the product, are represented by component nodes. Component nodes are mapped onto each product class to which the component is allocated, and are allocated to one or more component variants, these being actual items used in the production 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. On receiving the selection of a particular product class, the computer-aided system transfers all of the component nodes and process nodes that are allocated to this product class and is able to represent them graphically, for example.
Alternatively, the system receives the input of a product variant and displays all of the component variants used in the production of this product variant, in the form of lists of materials.
Description
Method and system for displaying and configuring component and process structures This invenvion relates to a computer based system and method for displaying component and process structures for configurable product classes stored in a data structure.
Many indust.r.ies offer highly variant products to their customers, a prime example being the automotive industry. Automobile manufacturers typically offer several models ~o 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 as:~ociated. While such a system may be useful for manufact=uring products, it is impractical from a design pei:~spec:tive. A designer cannot readily view, for' example; t;he 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 a.re specific only to a particular product within a class. Nor could he see the routing of a particular proauct 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
Many indust.r.ies offer highly variant products to their customers, a prime example being the automotive industry. Automobile manufacturers typically offer several models ~o 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 as:~ociated. While such a system may be useful for manufact=uring products, it is impractical from a design pei:~spec:tive. A designer cannot readily view, for' example; t;he 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 a.re specific only to a particular product within a class. Nor could he see the routing of a particular proauct 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
2 -change, particular components based on the number of products or prod.uc~ classes that are affected. An accurate view of the components and processes associated with p=roduct classes is vital for efficient design and manufacturing.
A system fox- depicting products and their associated components was described at the CIMData European Conference in 1997. The system includes a data structure with a tree-like representation of the various components a:rxd 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, and components are mapped to at most one product class.
Therefore, the c;y;~tem does not enable alternative viewing of component=s associated with broad product classes and componE=nts associated with particular products, as would be desirable both from design and production perspectives, respectively.
Another example of a known 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, whereby individual product components are mapped to all product. classes with which the component is related, and a7_.l components of a particular product
A system fox- depicting products and their associated components was described at the CIMData European Conference in 1997. The system includes a data structure with a tree-like representation of the various components a:rxd 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, and components are mapped to at most one product class.
Therefore, the c;y;~tem does not enable alternative viewing of component=s associated with broad product classes and componE=nts associated with particular products, as would be desirable both from design and production perspectives, respectively.
Another example of a known 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, whereby individual product components are mapped to all product. classes with which the component is related, and a7_.l components of a particular product
- 3 -class can be displayed in a graphical format. Specific component. variant~~, representing the concrete item used for a particular product variant, would also be associated with E=_ach component. Similarly, the processes required to assemble components would be mapped to those ~..~_omponents, 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.
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.
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 in the data structure.
It is a further object of the invention to provide within th.e data structure component variants for individual component nodes, representing the range and possible user 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 rnore than one possible decomposition for a particular component w=ithin 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.
l.t is a further object of the invention to enable graphical viewing on a visual display of all processes. associated with components within a product class.
I:t is a further object of the invention to enable g:raphi_cal viewing on a visual display of all components for a specific product variant.
To achieve these objects, a computer based system is provided with a memory containing a product variant data structure with products grouped hierarchically by c:Lasses. Components are mapped to all individual product classes with which they are associated. Proces~~es 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., ara associated with each component and process, respectively. Product classes and sub classes can be displayed graphically on a visual display in a tree-7_ike format with their associated components, component variants, 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 _rar~ge of concrete items used in the product for that component. For example, the component "wheel" includes components "tire" and "rim". Specific component variants :=or "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 vari<~n.ts , 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 ~;rariant representing the different production steps necessary to mount a door equipped, for example, with an automatic 1__.ft mechanism.
Features de,vel.oping the invention are specified in the patent claims. The invention is explained in more detail below with the aid of illustrative embodiments shown in the figures, in which:
Figure 1 shows the four-layer approach of the product variant data structure of the computer based system, Figure 2 shows an example of the application view "Engineering" on the product family "transportation vehi.c:le" in the data structure, Figure 3 shows an example for the application view "Mat:erials Requirement Planning" on the product class "mountain bike" in the data structure, Figure 4 ;~h.ows an example for the application view "Production a:nd Process Planning (Routing)"
associated with t:ze process "mount door" in the data structure, Figure 5 is a flowchart of the method of displaying a graphical representation of an application view node, Figure 6 is a flowchart of the method of displaying the ball of materials for a particular product variant, Figure 7 shows the decomposition of a product class into narrower product classes in the data structure, ~~igure 8 shows component variants of a component. node related to a product class in the data structure, Figure 9 shows an example of the alternative decomposition of a component in the data structure, and Figure 10 ;s:hows 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 Figure 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 w_i_th 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 "Mode7_ B", as shown.
The next layer, the Application View Layer 3, enables t:he viewing of a particular product class in various ways, depending on departmental requirements.
Engineering, for example, may need to see all top-layer component nodes a:~sociated with a generic product class.
Figure 2 shows the application view "Engineering" 13, which is a collection of all top-layer component nodes 101 that are associated with "Transportation Vehicle" or any of its subclasses "bicycle", "mounta.in 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.
Figure _i shows the application view "Production" 14, vth:ich depicts all component nodes 101 used in the production of the more specific product class "mountain bilce". Production planning, by contrast, may need. to view the routing of a particular product through its production steps, and so would need 7 _ to see all proce:>s nodes associated with a particular product class, and all component nodes associated with those process nodes.
Figure 4 shows the application view "Production and Process-Planning (Routing)" 15, which depicts the integration of product decomposition and process operations. Specif:ical.ly, the process node "mount door"
104 is connected to component node "door" 105 and the nodes 106 repre:~enting its sub-components. The Application View Layer 2 preferably stores different views for depaz-t:ments 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 r.=presentation for visual display on the display of the <:omputer based system.
Figure 5 is a flowchart showing the sequence of receiving the app7_ication 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 the R/3 system, among ot=hers, are suitable for receiving the input of the desired application view node, converting it into a graphical representation for visual display, arid displaying the graphical representation.
The Node Structure Layer 4 represents the functional decomposition of the product into components and processes. 'I'h~~ primary elements of the I~Tode 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 examp~~e, a car may have a separate component node foz- "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 _ g _ context of the Variant Layer 5. Process nodes are linked to component. nodes and are abstractions of the actual steps used t:o 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 discu~~sed in greater detail below in the context of the Variant Layer. The Node Structure Layer
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.
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 in the data structure.
It is a further object of the invention to provide within th.e data structure component variants for individual component nodes, representing the range and possible user 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 rnore than one possible decomposition for a particular component w=ithin 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.
l.t is a further object of the invention to enable graphical viewing on a visual display of all processes. associated with components within a product class.
I:t is a further object of the invention to enable g:raphi_cal viewing on a visual display of all components for a specific product variant.
To achieve these objects, a computer based system is provided with a memory containing a product variant data structure with products grouped hierarchically by c:Lasses. Components are mapped to all individual product classes with which they are associated. Proces~~es 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., ara associated with each component and process, respectively. Product classes and sub classes can be displayed graphically on a visual display in a tree-7_ike format with their associated components, component variants, 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 _rar~ge of concrete items used in the product for that component. For example, the component "wheel" includes components "tire" and "rim". Specific component variants :=or "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 vari<~n.ts , 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 ~;rariant representing the different production steps necessary to mount a door equipped, for example, with an automatic 1__.ft mechanism.
Features de,vel.oping the invention are specified in the patent claims. The invention is explained in more detail below with the aid of illustrative embodiments shown in the figures, in which:
Figure 1 shows the four-layer approach of the product variant data structure of the computer based system, Figure 2 shows an example of the application view "Engineering" on the product family "transportation vehi.c:le" in the data structure, Figure 3 shows an example for the application view "Mat:erials Requirement Planning" on the product class "mountain bike" in the data structure, Figure 4 ;~h.ows an example for the application view "Production a:nd Process Planning (Routing)"
associated with t:ze process "mount door" in the data structure, Figure 5 is a flowchart of the method of displaying a graphical representation of an application view node, Figure 6 is a flowchart of the method of displaying the ball of materials for a particular product variant, Figure 7 shows the decomposition of a product class into narrower product classes in the data structure, ~~igure 8 shows component variants of a component. node related to a product class in the data structure, Figure 9 shows an example of the alternative decomposition of a component in the data structure, and Figure 10 ;s:hows 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 Figure 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 w_i_th 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 "Mode7_ B", as shown.
The next layer, the Application View Layer 3, enables t:he viewing of a particular product class in various ways, depending on departmental requirements.
Engineering, for example, may need to see all top-layer component nodes a:~sociated with a generic product class.
Figure 2 shows the application view "Engineering" 13, which is a collection of all top-layer component nodes 101 that are associated with "Transportation Vehicle" or any of its subclasses "bicycle", "mounta.in 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.
Figure _i shows the application view "Production" 14, vth:ich depicts all component nodes 101 used in the production of the more specific product class "mountain bilce". Production planning, by contrast, may need. to view the routing of a particular product through its production steps, and so would need 7 _ to see all proce:>s nodes associated with a particular product class, and all component nodes associated with those process nodes.
Figure 4 shows the application view "Production and Process-Planning (Routing)" 15, which depicts the integration of product decomposition and process operations. Specif:ical.ly, the process node "mount door"
104 is connected to component node "door" 105 and the nodes 106 repre:~enting its sub-components. The Application View Layer 2 preferably stores different views for depaz-t:ments 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 r.=presentation for visual display on the display of the <:omputer based system.
Figure 5 is a flowchart showing the sequence of receiving the app7_ication 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 the R/3 system, among ot=hers, are suitable for receiving the input of the desired application view node, converting it into a graphical representation for visual display, arid displaying the graphical representation.
The Node Structure Layer 4 represents the functional decomposition of the product into components and processes. 'I'h~~ primary elements of the I~Tode 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 examp~~e, a car may have a separate component node foz- "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 _ g _ context of the Variant Layer 5. Process nodes are linked to component. nodes and are abstractions of the actual steps used t:o 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 discu~~sed 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 mufti-layer structure to poz:tray components, their subordinate components, and related processes.
'fhe lowes~-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 ~~:hat 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 components variants. Since more than one component variant m.ay 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 charade=ristics, 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 condition~> to determine the bill of materials for the specified product variant, and display the specific component variants that are used in the product ~Tariant .
Figure 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 bil:L of materials on a vi:~ual display 32. The central processor can also display the specific process variants, or' all of the actual produr.tion steps that are used in making the specified product variant, on a 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.
A.s shown in Figure 7, product classes 6 are represented hierarchically, and consist of "producible"
and "non-produc:ible" categories. For example, "transportation veh.ic.l.e" 40 and "bicycle" 41 are non-producible 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 more detail in the application view layer 3.
Component nodes and process nodes are the primary elements of t:he product variant structure 1 of the computer bast=d ;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 Figure 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 stand 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 attx-i:but:es of component variants, such as quantity of a specific component variant or the selection condition, according to the product class 6.
Ddodes 101 a:re related to each other in t:hree 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 "C-C" 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".
A.s shown in :Figures 2 and 3, nodes 101 are also connected to an app:Lication view, which establishes the connection between the Product Layer and the Node Structure Layer 4 c>i= the Product Variant Structure 1.
This is known as a view-type node -relationship.
Figure 9 ~~hows how a component node 101 in the node structure layer may have more than one decomposition into subordinate components. The choice among decomposition.; depends 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.
Figure 10 shows a summary of the Product Variant Structure 1 i:n a data model 14 with entities according to EXPRESS-(~ (ISO 10303-11).
While there have been shown and described and pointed out fundamental novel features of the invention as applied to embodiments thereof, the invention also includes embodiments not shown in which vaz-ious omissions and sub:~tit~utions 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 whv-ch perfo:rrrc substantially the same function in substantially the sa.rne 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 th.e claims appended hereto.
'fhe lowes~-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 ~~:hat 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 components variants. Since more than one component variant m.ay 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 charade=ristics, 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 condition~> to determine the bill of materials for the specified product variant, and display the specific component variants that are used in the product ~Tariant .
Figure 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 bil:L of materials on a vi:~ual display 32. The central processor can also display the specific process variants, or' all of the actual produr.tion steps that are used in making the specified product variant, on a 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.
A.s shown in Figure 7, product classes 6 are represented hierarchically, and consist of "producible"
and "non-produc:ible" categories. For example, "transportation veh.ic.l.e" 40 and "bicycle" 41 are non-producible 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 more detail in the application view layer 3.
Component nodes and process nodes are the primary elements of t:he product variant structure 1 of the computer bast=d ;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 Figure 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 stand 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 attx-i:but:es of component variants, such as quantity of a specific component variant or the selection condition, according to the product class 6.
Ddodes 101 a:re related to each other in t:hree 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 "C-C" 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".
A.s shown in :Figures 2 and 3, nodes 101 are also connected to an app:Lication view, which establishes the connection between the Product Layer and the Node Structure Layer 4 c>i= the Product Variant Structure 1.
This is known as a view-type node -relationship.
Figure 9 ~~hows how a component node 101 in the node structure layer may have more than one decomposition into subordinate components. The choice among decomposition.; depends 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.
Figure 10 shows a summary of the Product Variant Structure 1 i:n a data model 14 with entities according to EXPRESS-(~ (ISO 10303-11).
While there have been shown and described and pointed out fundamental novel features of the invention as applied to embodiments thereof, the invention also includes embodiments not shown in which vaz-ious omissions and sub:~tit~utions 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 whv-ch perfo:rrrc substantially the same function in substantially the sa.rne 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 th.e claims appended hereto.
Claims (25)
1. Computer bared 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, and 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 ins 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 true 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 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 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.
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 ins 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 true 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 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 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. Computer based system according to 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. Computer based system according to 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. Computer based system according to 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. Computer based system according to Claim 1, wherein said at least one component node is a plurality of component node, and wherein said plurality of component nodes are arranged based on the hierarchical relationship between components.
6. Computer based system according to Claim 5, wherein said hierarchical relationship between components depicts the decomposition of components into sub-components.
7. Computer based system according to Claim 6, wherein there are a plurality of decompositions of a particular component into sub-components.
8. Computer based system according to 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. 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 ones 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 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 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 representa-tion on a display.
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 ones 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 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 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 representa-tion on a display.
10. Method according to 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. Method according to 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. Method according to 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. Method according to 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. Method according to Claim 13, wherein said hierarchical relationship between components depicts the decomposition of components into sub-components.
15. Method according to Claim 14, wherein there are a plurality of decompositions of a particular component into sub-components.
16. Method according to 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. 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, and 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 leash 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 ones 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 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 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.
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 leash 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 ones 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 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 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. Computer based system according to 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. Computer based system according to 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. Computer based system according to 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. Computer based system according to 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. Computer based system according to Claim 21, wherein said hierarchical relationship between components depicts the decomposition of components into sub-components.
23. Computer based system according to Claim 22, wherein there are a plurality of decompositions of a particular component into sub-components.
24. Computer based system according to 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. 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, and 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 products 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.
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 products 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.
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 |
| US09/138,147 | 1998-08-21 | ||
| PCT/EP1999/006087 WO2000011579A1 (en) | 1998-08-21 | 1999-08-19 | Method and system for displaying and configuring component- and process structures |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2338630A1 CA2338630A1 (en) | 2000-03-02 |
| CA2338630C true CA2338630C (en) | 2005-03-29 |
Family
ID=22480650
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002338630A Expired - Fee Related CA2338630C (en) | 1998-08-21 | 1999-08-19 | Method and system for displaying and configuring component and process structures |
Country Status (7)
| Country | Link |
|---|---|
| US (3) | US6223094B1 (en) |
| EP (2) | EP1231552A1 (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)
| 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 |
| EP1299832A2 (en) * | 2000-03-31 | 2003-04-09 | Sap Ag | Matrix methods and systems 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 |
| US7275038B1 (en) * | 2000-08-18 | 2007-09-25 | The Crawford Group, Inc. | Web enabled business to business operating system for rental car services |
| 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 |
| 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 |
| US7899690B1 (en) | 2000-08-18 | 2011-03-01 | The Crawford Group, Inc. | Extended web enabled business to business computer system for rental vehicle services |
| AU2002220172A1 (en) * | 2000-11-15 | 2002-05-27 | David M. Holbrook | Apparatus and method for organizing and/or presenting data |
| US20070226640A1 (en) * | 2000-11-15 | 2007-09-27 | Holbrook David M | Apparatus and methods 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 |
| 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 |
| US20050182666A1 (en) * | 2004-02-13 | 2005-08-18 | Perry Timothy P.J. | Method and system for electronically routing and processing information |
| 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 |
| US9766221B2 (en) | 2015-01-30 | 2017-09-19 | 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 |
| US10318702B2 (en) | 2016-01-19 | 2019-06-11 | Ford Motor Company | Multi-valued decision diagram reversible restriction |
Family Cites Families (41)
| 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 |
| 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 |
| 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 |
| 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 |
| US5515524A (en) | 1993-03-29 | 1996-05-07 | Trilogy Development Group | Method and apparatus for configuring systems |
| 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 |
| 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 |
| 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 |
| 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 |
| US5764519A (en) | 1995-03-08 | 1998-06-09 | Hitachi, Inc. | Method and device for computing material requirements |
| 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 |
| US5764824A (en) | 1995-08-25 | 1998-06-09 | International Business Machines Corporation | Clustering mechanism for identifying and grouping of classes in manufacturing process behavior |
| US5740425A (en) * | 1995-09-26 | 1998-04-14 | Povilus; David S. | Data structure and method for publishing electronic and printed product catalogs |
| 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 |
| DE19644680A1 (en) | 1996-10-28 | 1998-05-07 | Volkswagen Ag | Method and device for handling identification data of a plurality of components of a product |
| 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 |
| 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 |
| US6141598A (en) | 1998-04-06 | 2000-10-31 | Hyundai Motor Company | Vehicle assembly line control system and method |
-
1998
- 1998-08-21 US US09/138,147 patent/US6223094B1/en not_active Ceased
-
1999
- 1999-08-19 EP EP02008116A patent/EP1231552A1/en not_active Ceased
- 1999-08-19 AU AU60792/99A patent/AU765185B2/en not_active Ceased
- 1999-08-19 EP EP99947267A patent/EP1105822A1/en not_active Ceased
- 1999-08-19 IL IL14074999A patent/IL140749A0/en unknown
- 1999-08-19 CA CA002338630A patent/CA2338630C/en not_active Expired - Fee Related
- 1999-08-19 WO PCT/EP1999/006087 patent/WO2000011579A1/en not_active Application Discontinuation
- 1999-08-19 JP JP2000566767A patent/JP3581655B2/en not_active Expired - Lifetime
-
2003
- 2003-04-23 US US10/421,080 patent/USRE41476E1/en not_active Expired - Lifetime
- 2003-12-11 AU AU2003268829A patent/AU2003268829B2/en not_active Ceased
-
2010
- 2010-05-28 US US12/790,226 patent/USRE44450E1/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| US6223094B1 (en) | 2001-04-24 |
| AU765185B2 (en) | 2003-09-11 |
| WO2000011579A1 (en) | 2000-03-02 |
| JP2002523829A (en) | 2002-07-30 |
| AU6079299A (en) | 2000-03-14 |
| AU2003268829B2 (en) | 2005-11-24 |
| CA2338630A1 (en) | 2000-03-02 |
| EP1231552A1 (en) | 2002-08-14 |
| JP3581655B2 (en) | 2004-10-27 |
| EP1105822A1 (en) | 2001-06-13 |
| AU2003268829A1 (en) | 2004-01-22 |
| USRE44450E1 (en) | 2013-08-20 |
| IL140749A0 (en) | 2002-02-10 |
| USRE41476E1 (en) | 2010-08-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2338630C (en) | Method and system for displaying and configuring component and process structures | |
| Fredrikson et al. | Temporal, geographical and categorical aggregations viewed through coordinated displays: a case study with highway incident data | |
| US20050187925A1 (en) | Schechinger/Fennell System and method for filtering data search results by utilizing user selected checkboxes" | |
| US20110087466A1 (en) | Method and apparatus for transparently displaying information relating to development of a motor vehicle | |
| CN1867909A (en) | System and method for cross attribute analysis and manipulation in online analytical processing (OLAP) and multi-dimensional planning applications by dimension splitting | |
| JP2002526833A (en) | Multidimensional data management system | |
| US7590566B2 (en) | Method and system for manufacturing and retailing products provided by remote vendors to remote customers | |
| DE102016210453A1 (en) | Vehicle, system in communication with a communication module of the vehicle, and system in communication with a group of vehicles | |
| EP3985594A1 (en) | Method for recommending vehicles | |
| US7103519B2 (en) | Virtual manufacturing system | |
| Prasad | Enabling principles of concurrency and simultaneity in concurrent engineering | |
| US20030014329A1 (en) | System and method for cataloguing | |
| US20150339626A1 (en) | Product intelligence engine | |
| DE102007040289A1 (en) | Operating manual preparing method for motor vehicle, involves defining and accessing explanation module, such that module is not selected based on component characteristics, and only variants are accessed by characteristics dataset | |
| WO2023280074A1 (en) | Vehicle system illustration generation method and display method, and method for assisting in fault diagnosis | |
| Bellotti et al. | Designing configurable automotive dashboards on liquid crystal displays | |
| Brooks | Design—the starting point for CIM | |
| KR100224858B1 (en) | Design data construction method | |
| Oh et al. | A Framework for Development Architecture for Modular Products: Cross-Domain Variety Management Perspective | |
| Thrall et al. | Desktop GIS software | |
| Cebi et al. | Design evaluation model for display designs of automobiles | |
| Aybet | Interoperability of GIS in an open system environment | |
| Pirotte et al. | Integrating two descriptions of taxonomies with materialization | |
| Hassan et al. | Flexibility of platforms and its impact on platforms lifecycle: a review and a focused case | |
| JP2000132630A (en) | Vehicle information managing method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |
Effective date: 20150819 |