Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/TS 29002-4: Industrial Automation Systems — Data Model for Properties and Characteristics
Technical specification defining a formal data model for representing properties and characteristics of industrial components
ISO/TS 29002-4 defines a formal data model for representing properties and characteristics of industrial components in automation systems. While Part 10 of the series focuses on the overall parts library structure, Part 4 drills down into the detailed representation of individual properties — the atomic units of information that describe component capabilities, dimensions, materials, and performance limits. This standard provides the semantic foundation for all higher-level parts library operations.
The property data model in ISO/TS 29002-4 is harmonized with IEC 61360-1 (standard data element types), ensuring that component descriptions created under this standard can be used interchangeably with IEC-compliant systems in the electrical and electronic domains.
1. Property Data Model Structure
The ISO/TS 29002-4 data model structures properties into a rigorous type system. Each property is defined by its data type (string, integer, real, boolean, enumerated, or reference), its unit of measure (where applicable), its value domain (allowed values or ranges), and its constraints (dependency rules, conditional requirements, and value relationships). Properties can be simple (a single value) or compound (a structured set of sub-properties, such as a torque specification consisting of minimum, nominal, and maximum values with associated test conditions). This structured approach ensures that component properties are defined with sufficient precision for automated engineering analysis, design validation, and downstream decision-making processes.
A key innovation in the model is the concept of property classification. Properties are organized into categories such as geometric properties, material properties, electrical properties, environmental properties, and performance properties. This classification enables systems to automatically determine which properties are relevant for a given component type. For example, an electric motor would inherit properties from the electrical, mechanical, and environmental categories, while a structural beam would primarily use geometric and material properties.
Using the ISO/TS 29002-4 property classification system, a PLM system can automatically present engineers with the correct property template when creating a new component, reducing data entry errors and ensuring that all required properties are captured at the point of creation.
2. Property Definitions and Data Typing
The standard defines an extensive library of predefined property types organized by domain. The following table provides examples of property definitions across different engineering disciplines:
| Property Category | Example Property | Data Type | Unit | Typical Constraints |
|---|---|---|---|---|
| Geometric | Overall Length | Real | mm | 0 < value ≤ 10000 |
| Geometric | Thread Size | Enumerated | — | M6, M8, M10, M12, M16, M20, … |
| Material | Tensile Strength | Real | MPa | 100 ≤ value ≤ 2000 |
| Material | Material Grade | Reference | — | References ISO material standard |
| Electrical | Rated Voltage | Real | V | 12, 24, 48, 110, 230, 400, 690 |
| Electrical | Insulation Class | Enumerated | — | A, E, B, F, H, N, R, S |
| Environmental | Operating Temperature | Real (range) | degC | −40 ≤ min ≤ max ≤ +150 |
| Environmental | Ingress Protection | Enumerated | — | IP20, IP54, IP65, IP67, IP69K |
| Performance | Rated Power | Real | kW | 0.1 ≤ value ≤ 5000 |
| Performance | Efficiency Class | Enumerated | — | IE1, IE2, IE3, IE4, IE5 |
The standard also defines complex property types for representing non-scalar characteristics. These include: tabular properties (performance curves relating two or more variables, such as torque versus speed), graphical properties (dimensional drawings with tolerances), and documentary properties (references to external documents such as test reports or material certificates). Each complex property type has its own data model that captures the structure of the information while maintaining machine-readability. The separation of simple and complex property types allows systems to handle a wide variety of engineering data while keeping the core data model efficient and manageable.
A common implementation challenge is handling unit conversions correctly. ISO/TS 29002-4 requires that every numeric property explicitly specifies its unit of measure using a standardized unit code from the UN/ECE Recommendation 20 or the ISO 80000 series. Systems should implement automated unit conversion with appropriate rounding and precision handling.
3. Constraints, Dependencies, and Validation
ISO/TS 29002-4 defines a comprehensive constraint model that captures the relationships between properties. Constraints are categorized into: value constraints (allowed ranges, enumerated lists, and patterns), dependency constraints (if property A has value X, then property B must have value Y), conditional constraints (property C is required only when property D is specified), and cross-reference constraints (properties in different classes must have consistent values).
The constraint model is expressed in a formal syntax that can be compiled into validation rules for databases, XML schemas, and application logic. For example, a constraint rule might state: “If fastner_nominal_diameter = 12, then nominal_thread_pitch must be either 1.25 or 1.75.” These rules are evaluated during data entry, data import, and data exchange to ensure that component specifications are internally consistent and conform to engineering standards.
Inconsistent constraint definitions are a frequent source of data quality issues. When two related properties have contradictory constraints (e.g., one requires a maximum temperature of 85°C while another requires 105°C for the same component class), systems may accept invalid data or reject valid data. Engineers should conduct regular constraint logic reviews using automated reasoning tools.
4. FAQs
Q: How does ISO/TS 29002-4 handle properties that are measured in different units across regions (metric vs. imperial)?
A: The standard requires that each property value be stored with its unit of measure. Systems should store values in a canonical unit (typically SI) and convert for display or exchange as needed. The standard provides conversion factors for common unit pairs.
Q: Can ISO/TS 29002-4 represent tolerance information for manufactured dimensions?
A: Yes. The standard defines tolerance models for both symmetric tolerances (±X), unilateral tolerances (+X / −Y), and geometric dimensioning and tolerancing (GD&T) according to ISO 1101. Tolerance information is captured as a structured compound property.
Q: Is the ISO/TS 29002-4 property library extensible by individual organizations?
A: Yes. While the standard provides a core library of commonly used properties, organizations can define their own properties following the same data model structure. However, custom properties should be clearly distinguished from standardized ones using defined namespace conventions.
