ISO 10303-214:2010(E)
This clause specifies the information required for core data for automotive mechanical design processes.
The information requirements are specified as a set of units of functionality, application objects, and application assertions. These assertions pertain to individual application objects and to relationships between application objects. The information requirements are defined using the terminology of the subject area of this application protocol.
NOTE 1 A graphical representation of the information requirements is given in annex G.
NOTE 2 The information requirements correspond to those of the activities identified as being within the scope of this application protocol in annex F.
NOTE 3 The mapping table specified in 5.1 shows how the integrated resources and application interpreted constructs are used to meet the information requirements of this application protocol.
This subclause specifies the units of functionality for the Core Data for Automotive Mechanical Design Processes application protocol.
NOTE 1 One or more UoFs, grouped together, provide a solution to identified data flows derived from the AAM (see annex F). The grouping of the UoFs is documented in clause 6.
This part of ISO 10303 specifies the following units of functionality:
NOTE 2 Following the name of each UoF, its abbreviation is shown in brackets. The abbreviations consist of one or two letters and a number. The letters indicate a logical group to which the UoF belongs. The logical groups identified are shown in table 1.
Figure 5 gives an overview for the UoFs, their logical groups, and the interdependencies among the UoFs and the logical groups.
Table 1 — Logical grouping of UoFs
Information type | Abbreviation |
surface condition | C |
draughting | D |
external reference | E |
form features | FF |
geometry | G |
kinematics | K |
measured data | MD |
property | PR |
presentation | P |
product structure | S |
tolerance | T |
This subclause specifies the application objects for the Core data for automotive mechanical design processes application protocol. Each application object is an atomic element that embodies a unique application concept and contains attributes specifying the data elements of the object. The application objects and their definitions are given below.
NOTE 1 The following conventions apply for the definition text:
The attribute names ’id’, ’name’, and ’description’ imply the following meanings:
NOTE 2 The id is not a system generated identifier used by an implementation to distinguish between the various objects but it is an identifier that has a certain meaning in an application and that may be meaningful to a human being as well.
NOTE 3 In cases where unique identifiers are required, identifiers with a format according to ISO 6523 [16]may be used.
In this clause, a permissive list approach for attributes with suffix ’_type’ or with name ’role’ is used consistently, i.e., there is a list of standardized values with the specific semantics defined. However, the usage of other non-standardized values is also allowed.
NOTE 4 Especially many relationship objects are defined in a general way where the attribute ’relation_type’ defines the standardized usages with a definition of the meaning of the other attributes, like ’relating’ and ’related’.
Go to index of Application objects (select 'Application object definition')
This subclause specifies the application assertions for the Core data for
automotive mechanical design processes application protocol. Application assertions specify the relationships between application objects, the cardinality of the relationships, and the rules required for the integrity and validity of the application objects and UoFs. The application assertions and their definitions are given below.
Application assertions can be accessed from the specific left in the subclauses for the assertion type attributes within the Application object definition
© ISO 2010 — All rights reserved