Skip to main content

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

Example​

Below is a interactive and rendered sample of a Animal Processing Event. Use the Render tap to view a human-friendly and readable version of it's content. The JSON tab provides the raw data.