Virtual manufacturing system
First Claim
1. A method of designing an automotive vehicle comprising:
- specifying a set of desired features to include in the vehicle model, wherein each feature defines a discrete portion of the vehicle'"'"'s functionality, and wherein the features are stored in a database;
decomposing each feature into a set of functions;
decomposing each function into a set of parts and configuration information; and
outputting a first vehicle model representing the vehicle, wherein the first vehicle model includes part and configuration information for implementing the set of desired features.
20 Assignments
0 Petitions
Accused Products
Abstract
A method and system for increasing standardization and reuse of feature driven design of automotive vehicles. An automotive vehicle is represented by a vehicle model, which includes a set of features defining vehicle functionality and information on how to implement each feature. A features database stores information on how a feature is implemented, including the physical parts it requires and the configuration of the parts. A parts database is also provided for maintaining information on vehicle parts. Coupled to the features database and the parts data base is a feature manager arranged to determine physical implementation information for each feature based on the implementation information. The physical implementation information is included in the vehicle model. A conflict manager is provided for resolving conflicts between implementations of separate features, and an optimizer for standardizing parts and implementations across multiple vehicle models.
-
Citations
20 Claims
-
1. A method of designing an automotive vehicle comprising:
-
specifying a set of desired features to include in the vehicle model, wherein each feature defines a discrete portion of the vehicle'"'"'s functionality, and wherein the features are stored in a database;
decomposing each feature into a set of functions;
decomposing each function into a set of parts and configuration information; and
outputting a first vehicle model representing the vehicle, wherein the first vehicle model includes part and configuration information for implementing the set of desired features. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A system for the feature driven design of an automotive vehicle so as to increase reusability, wherein the vehicle is represented by a vehicle model, the system including:
-
a feature database for storing feature records, wherein each feature record includes implementation information for a feature, and wherein a feature represents a piece of vehicle functionality;
a parts database including information on vehicle parts, wherein a part is a physical vehicle component, and vehicle functionality is implemented by parts; and
a feature manager coupled to the feature database and the parts database for;
(a) determining physical implementation information for each feature based on the feature record implementation information; and
(b) including the physical implementation information in the vehicle model. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A model for an automotive vehicle, the model comprising:
-
a set of features, wherein each feature includes a discrete set of vehicle functionality;
a set of functions corresponding to each feature, wherein each function defines a subset of the total feature functionality;
a set of parts corresponding to each function, wherein the parts can be used to implement the functions; and
a set of configuration information for each function, wherein the configuration information includes information on the placement and interaction of the parts;
wherein a vehicle can be implemented using the part and configuration information. - View Dependent Claims (16)
-
-
17. A data record embodied in a computer readable medium for storing automotive vehicle design information, the data record comprising:
-
at least one feature data field, wherein each feature data field includes information representing a discrete set of vehicle functionality;
at least one function data field corresponding to each feature data field, wherein each function data field includes information defining a subset of the total feature functionality; and
at least one part data field corresponding to each function data field, wherein each part data field includes information on a physical part that can be used to implement the function. - View Dependent Claims (18, 19, 20)
-
Specification