ARTS Operational Data Model Overview
The ARTS Operational Data Model has been evolving since its original release in 1996.
The scope of the ARTS Operational Data Model was originally constrained to the support of business process typically performed in a retail store. Beginning with Release 4.0, the ARTS Operational Data Model has expanded in scope to address the whole retail enterprise. Release 6.0 was published in 2009 and incorporated a revised number of changes and additions covering different operation subjects:
- Merchandise flow management
- Inventory management
- Item and price maintenance
- Point of sale processing
- Tender control
- Store administration
- Customer relationship management
- Sales and productivity reporting
- Ordering (partially supported)
- Workforce Management (partially supported)
Figure 1 presents a conceptual overview of retail enterprise core business functions addressed in ARTS Data Model latest release.

The ARTS Data Dictionary offers access to ARTS standards including the Data Model and Schemas, in a fully searchable format. A work in progress and currently up-to-date only through version 5.1 of the operational model, the Data Model Committee intends to make the dictionary available through version 6.0 as quickly as possible.
The Model is provided in ERwin format with the following supplemental PDFs:
Logical Model:
- Volume 1 High-level overview of mission and purpose of the ARTS Data Model, naming conventions, for both Logical Physical and considerations to be made when implementing the Physical data model.
- Volume 2 Entities and Attributes showing the name, domain and definition for all elements
- Volume 3 A complete list of of the Entity Relationship Diagrams from the Data Model available in both PDF and HTML. The HTML version makes it easy to navigate through the Business Functions and drill into the Entity and Attribute definitions.
Near Physical Model:
- Volume 1 High Level Overview of mission and purpose of the ARTS Data Model, naming conventions for both Logical and Physical and considerations to be made when implementing the Physical data model.
- Volume 2 Reference to every Table and respective Columns showing the Table logical name, physical name and definition. Shows the column physical name (no ref to logical name), domain, data type, definition, nullability and whether the Column participate in a PK and/or FK.
- Volume 3 Definition of all relationships.
- Volume 4 List of abbreviations referenced in definitions and narratives.
Going forward It is anticipated that future releases of the ARTS Operational Data Model will develop additional retail enterprise business areas as well as improve those already in the product.
Back to Data Warehouse Model Overview
Operational Data Model Version 6.0
Data Model Version 6.0 Downloads:
>List of the changes and enhancements (PDF)
Version 6.0 Operational Data Model and Documentation
Logged in members can download all related products


