ISO 10303-214:2010(E)
ISO 10303 is an International Standard for the computer-interpretable representation of product information and for the exchange of product data. The objective is to provide a neutral mechanism capable of describing products throughout their life cycle. This mechanism is suitable not only for neutral file exchange, but also as a basis for implementing and sharing product databases, and as a basis for archiving.
This part of ISO 10303 is a member of the application protocol series. This part of ISO 10303 specifies an application protocol (AP) for automotive mechanical design processes.
This application protocol defines the context, scope, and information requirements for various development stages during the design of a vehicle and specifies the integrated resources necessary to satisfy these requirements. This application protocol addresses the requirements of the automotive industry covering cars, trucks, buses, and motorcycles. It may also be applicable to other forms of vehicle, such as rail, agricultural, and construction vehicles.
A typical vehicle consists of the body, power train, chassis, and interior parts.
The body describes the body shell and the body in white.
EXAMPLE 1 Typical constituents of the body are frame, doors, roof, engine hood, windshield, or bumpers.
The power train includes the engine, transmission, and drive line.
EXAMPLE 2 Typical constituents of the power train are gear box, pistons, and exhaust pipe.
The chassis includes all parts which are responsible for the vehicles' handling.
EXAMPLE 3 Typical constituents of the chassis are the front axle, rear axle, steering, suspension, wheels, shock absorbers, and brakes.
Interior parts include parts that are built into the interior of the vehicle and not related to the power train.
EXAMPLE 4 Typical interior parts are seats, instrument panel, door panels, the mechanism for power windows, air conditioning system, or stereo equipment.
Only the mechanical aspects of a vehicle and its components are covered by this AP; the functional aspects, such as electronic, hydraulic, and pneumatic, are not covered.
EXAMPLE 5 For a battery or a switch, product characteristics such as shape, material, or mass are covered but the electrical functionality is not covered.
Finite element analysis (FEA) is not supported by this AP.
Figure 1 shows the processes included in the development of a vehicle. For further explanation of the processes, some examples of significant activities or data are given. The illustrations are taken from car body development. The application activity model (AAM) given in annex F provides a further detailed graphical representation of the processes and information flows.
These processes include:Application protocols provide the basis for developing implementations of ISO 10303 and abstract test suites for the conformance testing of AP implementations.
Clause 1 defines the scope of the application protocol and summarizes the functionality and data covered by the AP. Clause 3 lists the words defined in this part of ISO 10303 and gives pointers to words defined elsewhere. An application activity model that is the basis for the definition of the scope is provided in annex F. The information requirements of the application are specified in clause 4 using terminology appropriate to the application. A graphical representation of the information requirements, referred to as the application reference model, is given in annex G.
Resource constructs are interpreted to meet the information requirements. This interpretation produces the application interpreted model (AIM). This interpretation, given in 5.1, shows the correspondence between the information requirements and the AIM. The short listing of the AIM specifies the interface to the integrated resources and is given in 5.2. Note that the definitions and EXPRESS provided in the integrated resources for constructs used in the AIM may include select list items and subtypes which are not imported into the AIM. The expanded listing given in annex A contains the complete EXPRESS for the AIM without annotation. A graphical representation of the AIM is given in annex H. Additional requirements for specific implementation methods are given in annex C.
This edition incorporates modifications that are upwardly compatible with the previous edition. Modifications to EXPRESS specifications are upwardly compatible if:
This edition corrects errors in EXPRESS, mapping tables, application object definitions, and orthography from the second edition.
© ISO 2010 — All rights reserved