The RMSCC Data Attribute Coding System (DACS) is a simple coding model to provide a method to structurally codify attributes utilised within industry for the purpose of passing information unambiguously along the supply chain.


The attribute coding model is made up of 5 segments:

1. Attribute Authority This identifies the authority or organisation that is responsible for the definition and maintenance of the characteristics of the attribute. An example is the Australian Business Register (ABR) which is part of the Australian Government and responsible for issuing Australian Business Numbers (ABNs).

2. Attribute Type This defines the classes of attributes types. An example "Attribute Type" is the calls of attributes used for entity (or organisation, company, business) identification attributes.

3. Attribute Function This is the individual attribute defined in general purpose or function. An example is Australian Business Number (ABN) which is an attribute with a defined purpose. The ABN can have various use cases such as the Buyer's ABN, the Seller's ABN, the transporter's ABN, etc. Each of these use cases create a unique variate of the general ABN attribute that is required to be used when passing information along a supply chain.

4. Attribute Unit, Format and or Precision This defines one or more units, formats and or precision for an attribute. Some attributes have a self evident unit, Format and or Precision such as the Australian Business Number (ABN) which by it very nature is self defining. Attributes like mass (weight), volume, length, area, date, time, etc can have one or more defined units, formats and or precision. When passing data information along a supply chain the units, formats and or precision need to be unambiguous.

5. Attribute Specific Use Case This defines the various use cases for an attribute. Many attributes may only have one use case and are easily understood. Some attributes for example the ABN can have various use cases such as the Buyer's ABN, the Seller's ABN, the transporter's ABN, etc. Each of these use cases create a unique variant of the general ABN attribute that is required to be used when passing information along a supply chain.

Each unique value of the segment has a short descriptive code allocated to allow for ease of understanding. An example for the Australian Business Number (ABN) attribute function is descriptive code is "abn". the ABN attribute is an attribute with the Attribute Type of "Country Registry Entity Identification" as the ABN is used to unique identify of a legal entity within Australia. The descriptive identifier for the "Country Registry Entity Identification" Attribute Type is "idEntityCountry". The attribute authority for the ABN attribute would be the Australian Business Register (ABR) with the descriptive code "abr". When these segments are joined the results would be the code "abrIdEntityCountryAbn". The Attribute Unit, Format and or Precision for an ABN is self evident as the ABN values are set by the Australian Business Register (ABR). The descriptive code for self evident units is "selfDefined". The number of possible Attribute Specific Use Cases can be extensive. For the attribute ABN that can be many use cases. An example is the buyer's ABN in a commercial transaction between trading partners. In this example the attribute specific use case descriptive code is "buyer". When all 5 segments are joined for this ABN example the total descriptive code would "abrIdEntityCountryAbnSelfDefinedBuyer".

The attribute coding model support representing the joined 5 segments as a fixed length 15 character hexadecimal (hex) DACS code. This provide a robust structure code to facilitate transmission of data between trading partners. Each of the 5 segments as three (3) character hexadecimal (hex) values. This provides a range of values from HEX 000 (decimal 0) through to HEX FFF (decimal 4,095) this is a total of 4,096 possible values for each of the 5 attribute coding model segments.

Data Attribute Coding System (DACS) Tool

The simple tool below provides a method to create a Data Attribute Coding System (DACS) code. NOTE: Not all combinations of the 5 segments would be realistic, usable or possible

1. Authority
2. Type
3. Function
4. Unit
5. Use Case

When the 5 segments each of three (3) character hexadecimal (hex) values are joined together they create the 15 character hexadecimal (hex) DACS code with a possible 1,152,921,504,606,846,975 unique attribute identifiers. For the ABN buyer example the attribute identifier DACS code would be "A00102022A00101".
When shown as a key value pair with an ABN value the combination would appear as A00102022A00101=51824753556.
As a JSON key-value pair (also called a "name/value pair" or "property") the basic syntax would be "A00102022A00101": "51824753556".