Skip to main content

Traceability Events

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Digital Traceability Events​

The AATP digital traceability events are all implemented as profiles of the UNTP Digital Traceability Event (DTE). An AATP DTE profile is no different in structure to a UNTP DTE but has specific constraints regarding the identifier schemes and industry vocabularies. Implementers should familiarise with the UNTP DTE before implementing any of the AATP traceability event profiles.

The table lists each AATP traceability event type and version as well as it's UNTP version dependency.

NameCurrent VersionStatusRelease DateUNTP dependency
Animal Processing Event0.4.0Draft20-11-2024UNTP DTE v0.5.0
Animal Feeding Event0.4.0Draft20-11-2024UNTP DTE v0.5.0

Logical Model​

All AATP traceability events use the UNTP Digital Traceability Event v 0.5.0 logical model without change. AATP only applies specific vocabulary and rules.

Technical Artefacts​

Implementers must use the UNTP DTE Technical Artefacts. v0.5.0

Animal Processing Event​

The AATP Animal Processing Event represents the processing of a batch of animals at a meat processing plant. It uses the transformation event type with input as a list of identified animals and output as list of processed product types identified to batch level.

Profile Rules​

  • DigitalTraceabilityEvent.issuer CredentialIssuer.id MUST be the DID of the processor and SHOULD include a CredentialIssuer.OtherIdentifiers structure that identifies the operator of the plant using the ABN identity scheme.
  • TransformationEvent MUST be included. No other event types are required.
  • TransformationEvent.processType MUST be set to AATP_Animal_Procesing_Event
  • TransformationEvent.inputEPCList is mandatory and MUST include a list of Item.id drawn from NLIS identifier scheme. TransformationEvent.inputQuantityList is not required.
  • Outputs MUST be identified at least to batch level using TransformationEvent.outputQuantityList where QuantityElement.productId is a batch level identifier.
  • Outputs MAY be identified to serialised item level using TransformationEvent.outputEPCList where item.id is a unique serialised item idenifier.
  • Output identifiers MUST leverage a resolvable and verifiable identifier scheme. The GS1 GTIN identifier scheme is recommended but any schem may be used provided it meets the UNTP requirements for resolvable and verifiable identifiers.
  • Outputs MAY be grouped into one DTE (that would list all products from a processing lot) or across multiple seaprate DTE (eg separate DTEs for specific cuts or by-products such as hides).
  • TransformationEvent.actionCode MUST be set to add, TransformationEvent.bizStepCode MUST be set to cbv:BizStep-commissioning, and TransformationEvent.bizStepCode MUST be set to cbv:Disp-active

Working Sample​

An issued AATP Animal Processing Event (link TBD)

Animal Feeding Event​

The AATP Animal Feeding Event represents the feedlot process and records the association of a grain supply with an animal. it uses the association event because the input and output animal identifier remains unchanged. The feeding event simply connects an identified consignment of grain to the animal. When a specific consignment cannot be linked to a specific animal then feedlots should list all consignments that may have been fed to the animal.