We’re implementing comprehensive IP tracking across multiple Aras 14.0 modules (Parts, Documents, CAD, Software) and struggling with cross-module attribute standardization. IP ownership reporting requires consistent attributes across all these ItemTypes: ip_owner, license_type, patent_references, export_classification. The challenge is that each module has slightly different needs - Parts need supplier_ip_terms, Documents need author_rights, CAD files need design_patent_id, Software needs open_source_license details. We could create a common IP_Attributes ItemType that all modules relate to, but that adds relationship overhead. Alternatively, we could duplicate attributes on each ItemType, but that creates consistency problems and makes reporting complex. How do others handle cross-module attribute standardization when you need both common fields and module-specific extensions? We need data model linking that supports both IP ownership reporting across all modules and specialized attributes for each context.
From a reporting perspective, the relationship model is cleaner. You can create views that join all modules to IP_Attributes and get consistent data. With duplicated attributes, you need UNION queries across multiple ItemTypes, and ensuring data consistency becomes a nightmare. We had parts with license_type=‘MIT’ and software with license_type=‘MIT License’ - same thing, different strings, reporting broke.
We use the common IP_Attributes ItemType approach. Yes, it adds a relationship, but the benefits outweigh the overhead. Single source of truth for core IP data, and relationship properties handle module-specific extensions. For example, Part→IP_Attributes relationship has supplier_terms property, Document→IP_Attributes has author_rights property. Core IP data (owner, license, patents) lives in IP_Attributes once, module-specific stuff lives on the relationships.
The property set approach breaks down when IP ownership changes. If you discover a patent applies to 500 parts, you have to update 500 records. With a relationship model, you update one IP_Attributes item and 500 relationships point to it. For cross-module consistency, relationship overhead is worth it. Plus, you can version the IP_Attributes ItemType to track how IP ownership evolved over time.
We went the opposite direction - duplicated core IP attributes across all ItemTypes using property inheritance. Created an IP_Properties property set that includes ip_owner, license_type, patent_refs. Every ItemType that needs IP tracking includes this property set, then adds its own module-specific properties. Reporting queries union across ItemTypes. More storage overhead but simpler queries and no relationship navigation.