Vehicle component selection system and method

Abstract

Systems and methods to select a vehicle component are provided. In at least one embodiment, a system receives first configuration data defining a first vehicle assembly configuration, category data defining a component category, and component data defining a vehicle component. The system stores the configuration data and the category data in memory. The system automatically determines whether the component data satisfies a selected vehicle assembly configuration definition and whether the component data satisfies a selected component category definition. The system outputs a representation of the vehicle component if the component data satisfies the selected vehicle assembly configuration definition and the selected component category definition thereby automatically selecting the component.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to vehicle component selection systems and methods.

2. Background

Assembling a vehicle within a manufacturing facility may involve a number of components, e.g., wheels and doors, and processes, e.g., attach wheel to vehicle and attach door to vehicle.

Planning for the assembly of a vehicle within a manufacturing facility may involve identifying and assigning the vehicle's components to the appropriate processes. Software may assist with this task. Current software, such as those from Dassault Systems Inc. and UGS, allows a user to manually assign a vehicle component to a process. For example, the user may assign “part number 53X261, 15″×6″ steel wheel” to the process “attach wheel to vehicle.” The user identifies the component to be assigned by inspecting a list containing at least a portion of all the components to be used during the vehicle's assembly. Manually assigning components to processes, however, may be time consuming and inefficient because of the number of components used in the vehicle.

A vehicle may also have several configurations, e.g., two-door, four-door, 4×2, 4×4. Different configurations may require different components, e.g., a two-door configuration may require two doors whereas a four-door configuration may require four doors. When using current software, a user must decide upon a particular configuration and manually assign the components to the appropriate processes. If the user wishes to pick a different configuration, the user must again manually assign each of the components of that configuration to the appropriate processes.

SUMMARY

In at least one embodiment, the invention takes the form of a computer-implemented component selection system. The system receives first configuration data defining a first vehicle assembly configuration, category data defining a component category, and component data defining a vehicle component. The system is also stores the configuration data and the category data in memory. The system automatically determines whether the component data satisfies a selected vehicle assembly configuration definition and whether the component data satisfies a selected component category definition. The system outputs a representation of the vehicle component if the component data satisfies the selected vehicle assembly configuration definition and the selected component category definition thereby automatically selecting the component.

In at least one embodiment, the invention takes the form of a component selection method. The method includes receiving first configuration data defining a first vehicle assembly configuration, category data defining a component category, and component data defining a vehicle component. The method also includes storing the configuration data and the category data in memory. The method further includes automatically determining whether the component data satisfies a selected vehicle assembly configuration definition and automatically determining whether the component data satisfies a selected component category definition. The method still further includes outputting a representation of the vehicle component if the component data satisfies the selected vehicle assembly configuration definition and the selected component category definition thereby automatically selecting the component.

While exemplary embodiments in accordance with the invention are illustrated and disclosed, such disclosure should not be construed to limit the claims. It is anticipated that various modifications and alternative designs may be made without departing from the scope of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system in accordance with an embodiment of the invention.

FIG. 2 shows data in accordance with an embodiment of the invention.

FIG. 3 shows data in accordance with an embodiment of the invention.

FIG. 4 shows data in accordance with an embodiment of the invention.

FIG. 5 shows data in accordance with an embodiment of the invention.

FIGS. 6 a-6h show screens in accordance with an embodiment of the invention.

FIG. 7 shows an algorithm in accordance with an embodiment of the invention.

FIG. 8 shows an algorithm in accordance with an embodiment of the invention.

FIG. 9 shows a screen in accordance with an embodiment of the invention.

FIG. 10 shows an algorithm in accordance with an embodiment of the invention.

FIG. 11 shows a screen in accordance with an embodiment of the invention.

FIG. 12 shows a screen in accordance with an embodiment of the invention.

FIGS. 13 a-13b show screens in accordance with an embodiment of the invention.

FIG. 14 shows a method in accordance with an embodiment of the invention.

FIG. 15 shows a method in accordance with an embodiment of the invention.

DETAILED DESCRIPTION

FIG. 1 shows computer-implemented component selection system 10 for manufacturing facility 11. System 10 includes computer 12 configured to receive several types of data 13. Data 13 may be input in any desired fashion including via keyboard or loaded from storage media. Data 13 may include configuration data 14, category data 16, and component data 18. Data 13 may also include tool data 20, process data 22, and requirement data 24. Configuration data 14, category data 16, and component data 18 need not be input simultaneously. Similarly, tool data 20, process data 22, and requirement data 24 need not be input simultaneously.

Configuration data 14 defines vehicle assembly configurations to be assembled within manufacturing facility 11. Vehicle assembly configurations may include an entire vehicle. Vehicle assembly configurations may also include only portions of a vehicle, e.g., engine and seat. Configuration data 14 is associated with component data 18 as will be explained in detail below. Configuration data 14 may be used by system 10 to determine whether vehicle components 28, i.e., 28a-28n, satisfy selected vehicle configuration definition 15 as will be explained in detail below. Configuration data 14 may define a trim level, e.g., low-line or high-line, a preferred package of options, e.g., stick shift and spoiler, or a model, e.g., sedan or coupe. Configuration data 14 may define any desired vehicle configuration.

Configuration data 14 may include trim level indicator 26 that may be used by system 10 to determine whether, for example, vehicle component 28a, e.g., a 15″×6″ wheel, is used in a low-line trim package of a vehicle. For example, if a user of system 10 selects the low-line as vehicle configuration definition 15, as will be explained in detail below, system 10 may automatically select the 15″×6″ wheel.

Configuration data 14 may include model indicator 30 that may be used by system 10 to determine whether, for example, vehicle component 28a, e.g., a 15″×6″ wheel, is used in a sedan model of a vehicle. For example, if a user of system 10 selects sedan as vehicle configuration definition 15, as will be explained in detail below, system 10 may automatically select the 15″×6″ wheel.

Category data 16 defines component categories. Category data 16 is associated with component data 18 as will be explained in detail below. Category data 16 may be used by system 10 to determine whether vehicle component 28 satisfies selected component category definition 17 as will be explained in detail below. Examples of component category descriptions 29 include wheels, tires, doors, and fenders.

Category data 16 may include vehicle position indicator 32 that may be used by system 10 to determine whether, for example, vehicle component 28a, e.g., a 15″×6″ wheel, is used on the front of a vehicle. For example, if a user of system 10 selects wheels and rear as component category definition 17, as will be explained in detail below, system 10 may automatically select the 15″×6″ wheel.

Component data 18 defines vehicle components 28. Component data 18 may include information found on an engineering bill of materials, e.g., part number 34, part description 36. Component data 18 may also include component geometry 38, or mathematical data, used to generate a computer model of vehicle component 28.

Tool data 20 defines tools 21, i.e., 21a-21n. Tool data 20 may include attributes 42, i.e., 42a-42n. Attributes 42 may be used by system 10 to determine whether tool 21 satisfies selected process definition 43 or selected requirement definition 45 as will be explained in detail below.

Process data 22 defines a process for assembling at least a portion of a vehicle in manufacturing facility 11. Process data 22 may include requirement data 24, i.e., one or more requirements 24a-24n, defining a requirement of the process to be performed within manufacturing facility 11.

System 10 stores configuration data 14, category data 16, and component data 18 in memory 40 in a database. System 10 stores tool data 20, process data 22, and requirement data 24 in memory 40 in a database. Data 13, however, may be stored in any manner.

FIG. 2 shows an association between configuration data 14, category data 16, and component data 18 within memory 40. Data 13 that appear in a particular row are associated together.

FIG. 3 shows an example set of tool data 20. Attribute 42a indicates that tool 21, i.e., 21a-21n, is located within manufacturing facility 11. Attribute 42b indicates the location of tool 21 within manufacturing facility 11. Attribute 42c indicates, in this example, the maximum torque tool 21 can apply to a nut. Attribute 42d describes tool 21 and identifies its manufacturer. Attributes 42 may indicate any desired characteristic or capability of tool 21.

FIG. 4 shows an example set of process data 22. Process data 22 includes description 44 of particular process 46, e.g., assemble wheel to vehicle. First Requirement 24a specifies the amount of torque required. Second Requirement 24b specifies the desired runner length of tool 21. Third Requirement 24c specifies the desired manufacturer of tool 21. As explained above, there may be any number of requirements 24.

FIG. 5 shows that certain of category data 16 may be associated with process data 22. System 10 is thus informed as to which component categories are used during a process. For example, the process “assemble wheel to vehicle” uses component categories “wheel, nut, and hub.”

FIGS. 2 and 5 illustrate an association between different types of data 13. The tabular format used in FIGS. 2 and 5, however, is for illustration purposes and does not necessarily suggest that data 13 of FIGS. 2 and 5 are associated or stored in such a tabular format. Data 13 of FIGS. 2 and 5 may be associated together using any desired technique. For example, Data 13 may be manually associated together, data 13 may be associated together using an algorithm, or data 13 may be associated together before it is received by system 10.

FIGS. 6 a, 6b, 6c, and 6d show a series of screen shots of system 10 permitting a user to select vehicle configuration definition 15 and process definition 43. Once vehicle configuration definition 15, e.g., sedan and low-line, and process definition 43, e.g., assemble wheel to vehicle, are selected, computer 12 automatically determines whether component data 18 satisfies selected vehicle configuration definition 15 and automatically determines whether component data 18 satisfies selected component category definition 17.

In the example of FIGS. 6a, 6b, 6c, and 6d, component category definition 17 was implicitly selected by selecting process definition 43 because of the association between process data 22 and category data 16 as illustrated in FIG. 5 as will be explained in detail below.

FIGS. 6 e, 6f, 6g, and 6h show a series of screen shots of system 10 in an alternative embodiment permitting a user to explicitly select component category definition 17.

In the embodiment of FIGS. 6e, 6f, 6g, and 6h, computer 12 may automatically determine whether component data 18 satisfies selected component category definition 17 based on, for example, vehicle position indicator 32 as will be explained below.

FIG. 7 shows an example algorithm used to select component category definition 17 based on selected process definition 43. At step 54, computer 12 compares selected process definition 43 with process data 22. At step 56, computer 12 determines the logical correctness of the statement: selected process definition 43 matches particular process 46. If true, at step 58, computer 12 returns category data 16 associated with particular process 46. If false, at step 60, computer 12 may prompt the user to add category data 16.

FIG. 8 shows an example algorithm used to automatically determine whether component data 18 satisfies selected vehicle configuration definition 15 and selected component category definition 17. At step 62, computer 12 compares selected vehicle configuration definition 15, e.g., sedan and low-line, with model indicator 30 and trim level indicator 26 associated with component 28x of component data 18. At step 64, computer 12 determines the logical correctness of the statement: selected vehicle configuration definition 15 matches model indicator 30 and trim level indicator 26. If true, at step 66, computer 12 returns component data 18 associated with model indicator 30 and trim level indicator 26. At step 67, computer 12 determines whether there are more components, e.g., component 28x+1. If true, computer 12 returns to step 62. If false, at step 69, the algorithm is complete. Returning to step 64, if false, computer 12 determines whether there are more components, e.g., component 28x+1. If true, computer 12 returns to step 62. If false, at step 69, the algorithm is complete. Computer 12 performs this algorithm for each component 28, i.e., 28a-28n.

The computer 12 may automatically determine whether component data 18 satisfies selected component category definition 17 based on vehicle position indicator 32 using algorithms similar to those of FIGS. 7 and 8.

FIG. 9 shows output 68 representing vehicle components 28, e.g., 28a, 28b, and 28e, selected as a result of computer 12 performing the algorithms of FIGS. 7 and 8. Output 68 includes alpha-numeric characters. Output 68, however, may take any desired form. Output 68 may be in electronic or hard copy format. In the embodiment of FIG. 9, output 68 appears on a display screen.

FIG. 10 shows an example algorithm used to automatically determine whether tool data 20 satisfies selected process definition 43. At step 70, computer 12 compares selected process definition 43 with process data 22. At step 72, computer 12 determines the logical correctness of the statement: selected process definition 43 matches particular process 46. If true, at step 74 computer 12 compares requirements 24 associated with particular process 46 with attributes 42 of tool data 20. As such, requirement definition 45 is implicitly selected. Requirement definition 45 may be explicitly selected in a manner similar to that explained with reference to FIGS. 6e, 6f, 6g, and 6h. If false, at step 76, computer 12 may prompt the user to add requirements 24. At step 80, computer 12 determines the logical correctness of the statement: requirement definition 45 matches attributes 42 of tool data 20. If true, at step 82, computer 12 returns tool 21, e.g., 28x of 28a-28n, associated with attributes 42. If false, at step 84, computer 12 may prompt the user to add a tool.

FIGS. 11 and 12 show output 86 representing tools 21, e.g., 21b, 21c, and 21d, as a result of computer 12 performing the algorithm of FIG. 10. Output 86 includes alpha-numeric characters. Output 86, however, may take any form. Output 86 may be in electronic or hard copy format. In the embodiment of FIG. 11, output 86 appears on a display screen.

Output 86 may indicate tool location 42b. Output 86 also permits the user to select one or more tools 21, e.g., 21b and 21c, by selecting fields 87. FIG. 12 shows two of fields 87 selected. Tools 21, however, may be selected in any desired fashion. Selected tools 21 may be stored in memory 40 using any desired technique. Output 68 of FIG. 9 may also be shown simultaneously with output 86 of FIG. 11.

FIG. 13 a shows an alternative embodiment of output 86. FIG. 13a shows a spreadsheet including grid 88 listing the processes to be performed in manufacturing facility 11 on y-axis 83, e.g., assemble wheel to vehicle, and the locations of all the work cells within manufacturing facility 11 along x-axis 85, e.g., cell 1, cell 2, etc. In the embodiment of FIG. 13a, x-axis 85 is generally perpendicular to y-axis 83. Empty circles 89 in each of location cells 23, 35, and 45 indicate the locations within manufacturing facility 11 where tool 21 satisfies selected process definition 43.

FIG. 13 b shows that a user is able select empty circle 89 to indicate where the process is currently being performed, e.g., cell 23. The user may, for example select one of circles 89 with a mouse click. The user is also able to indicate desired location 85 to perform the process within manufacturing facility 11, e.g., the “X” in cell 1. The user may, for example, type an “X” directly in the field of interest.

FIG. 14 shows a component selection method. At step 90, first configuration data including a model indicator and a trim level indicator defining a first vehicle assembly configuration is received. At step 92, category data defining a component category is received. At step 94, component data defining a vehicle component is received. At step 96, the configuration data and the category data are stored in memory. At step 98, a determination is automatically made as to whether the component data satisfies a selected vehicle assembly configuration definition based on the model indicator and the trim level indicator. At step 100, a determination is automatically made as to whether the component data satisfies a selected component category definition. At step 102, a representation of the vehicle component is output if the component data satisfies the selected vehicle assembly configuration definition and the selected component category definition.

FIG. 15 shows a component selection method. At step 90, first configuration data defining a first vehicle assembly configuration is received. At step 92, second configuration data defining a second vehicle configuration is received. At step 94, category data including a vehicle position indicator defining a component category is received. At step 96, component data defining a vehicle component is received. At step 98, the configuration data and the category data are stored in memory. At step 100, a vehicle assembly configuration definition is selected. At step 102, a determination is automatically made as to whether the component data satisfies the selected vehicle assembly configuration definition. At step 104, a determination is automatically made as to whether the component data satisfies a selected component category definition based on the vehicle position indicator. At step 106, a representation of the vehicle component is output if the component data satisfies the selected vehicle assembly configuration definition and the selected component category definition.

While embodiments of the invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention.

Claims

1. A computer-implemented component selection system comprising: a computer configured to receive first configuration data including a trim level indicator, the first configuration data defining a first vehicle assembly configuration,receive category data defining a component category,receive component data defining a vehicle component,store the configuration data and the category data in memory,automatically determine whether the component data satisfies a selected vehicle assembly configuration definition based on the trim level indicator,automatically determine whether the component data satisfies a selected component category definition, andoutput a representation of the vehicle component if the component data satisfies the selected vehicle assembly configuration definition and the selected component category definition thereby automatically selecting the component.

2. The system of claim 1 wherein the category data includes a vehicle position indicator and wherein the computer automatically determines whether the component data satisfies the selected component category definition based on the vehicle position indicator.

3. The system of claim 1 wherein the component data includes a part number.

4. The system of claim 1 wherein the representation is in an electronic format.

5. The system of claim 1 wherein the representation is in a hard copy format.

6. The system of claim 1 wherein the configuration data further includes a model indicator and wherein the computer automatically determines whether the component data satisfies the selected vehicle assembly configuration definition further based on the model indicator.

7. The system of claim 1 wherein the component data includes component geometry.

8. The system of claim 1 wherein the computer is further configured to receive second configuration data defining a second vehicle assembly configuration and to receive the selected vehicle assembly configuration definition.

9. A computer-implemented component selection system comprising: a computer configured to receive first configuration data defining a first vehicle assembly configuration;receive category data including a vehicle position indicator, the category data defining a component category;receive component data defining a vehicle component;store the configuration data and the category data in memory;automatically determine whether the component data satisfies a selected vehicle assembly configuration definition;automatically determine whether the component data satisfies a selected component category definition based on the vehicle position indicator; andoutput a representation of the vehicle component if the component data satisfies the selected vehicle assembly configuration definition and the selected component category definition thereby automatically selecting the component.

10. The system of claim 9 wherein the first configuration data includes a trim level indicator and wherein the computer automatically determines whether the component data satisfies the selected vehicle assembly configuration definition based on the trim level indicator.

11. The system of claim 9 wherein the component data includes a part number.

12. The system of claim 9 wherein the representation is in an electronic format.

13. The system of claim 9 wherein the representation is in a hard copy format.

14. The system of claim 9 wherein the first configuration data includes a model indicator and wherein the computer automatically determines whether the component data satisfies the selected vehicle assembly configuration definition based on the model indicator.

15. The system of claim 9 wherein the component data includes component geometry.

16. The system of claim 9 wherein the computer is further configured to receive second configuration data defining a second vehicle assembly configuration and to receive the vehicle assembly configuration definition selected.

17. A computer-implemented component selection system comprising: a computer configured to receive first configuration data including a model indicator, the first configuration data defining a first vehicle assembly configuration,receive category data defining a component category,receive component data defining a vehicle component,store the configuration data and the category data in memory,automatically determine whether the component data satisfies a selected vehicle assembly configuration definition based on the model indicator,automatically determine whether the component data satisfies a selected component category definition, andoutput a representation of the vehicle component if the component data satisfies the selected vehicle assembly configuration definition and the selected component category definition thereby automatically selecting the component.