INTERFACE PROTOCOL PROCESSING OF EVENTS (Version … › images › stories › fantome...(Version...

Présented by Agri-Traçabilité Québec inc.

555 Roland-Therrien Blvd, Suite 050

Longueuil, Quebec, Canada

J4H 4E8

Tel.: 450-677-1757

Fax.: 450-679-6547

INS-087(A)

2011-06-02

INTERFACE PROTOCOL

PROCESSING OF EVENTS

(Version 1.11 / ANIMAL)

SYSTEM FOR THE IDENTIFICATION AND

TRACEABILITY OF FARM ANIMALS AND

OTHER AGRICULTURAL PRODUCTS

AGRI-TRAÇABILITÉ QUÉBEC

March 1st, 2011

System for the identification and traceability of

Farm animals and other agricultural products A.T.Q.

Agri-Traçabilité Québec Inc. i

INS-087

2011-06-02

TABLE OF CONTENTS

1 FOREWORD ............................................................................................................................................. 3

2 INTRODUCTION ....................................................................................................................................... 4

2.1 BACKGROUND ....................................................................................................................................... 4

2.2 TERMINOLOGY ...................................................................................................................................... 5

2.2.1 Premise ......................................................................................................................................................... 5

3 PRINCIPLES FOR DATA ENTRY OF EVENTS ....................................................................................... 6

3.1 METHODS OF DATA TRANSMISSION OF EVENTS ....................................................................................... 6

3.2 CONTROL POINTS AND OBSERVATION REPORTS ..................................................................................... 7

4 DEFINITION OF EVENTS ......................................................................................................................... 9

4.1 UNIT EVENTS (ANIMALS) ....................................................................................................................... 9

4.1.1 Observation report ....................................................................................................................................... 9

4.1.2 Slaughter ...................................................................................................................................................... 9

4.1.3 Death ............................................................................................................................................................ 9

4.1.4 Rendering ..................................................................................................................................................... 9

4.1.5 Transfer ........................................................................................................................................................ 9

4.1.6 Transport ...................................................................................................................................................... 9

4.1.7 Insemination ................................................................................................................................................. 9

4.1.8 Activation ................................................................................................................................................... 10

4.1.9 In transit ..................................................................................................................................................... 10

4.1.10 Loading-Unloading .................................................................................................................................... 10

4.1.11 Necropsy ..................................................................................................................................................... 10

4.1.12 Association ................................................................................................................................................. 10

4.1.13 Dissociation ................................................................................................................................................ 10

4.2 THE ARCHITECTURE OF EVENT TRANSACTIONS .................................................................................. 11

4.2.1 Unit transaction (Animals) ......................................................................................................................... 11

4.3 STEPS FOR IMPLEMENTATION .............................................................................................................. 12

4.3.1 Initialization of the project ......................................................................................................................... 12

4.3.2 Testing ........................................................................................................................................................ 12

4.3.3 Production .................................................................................................................................................. 12

System for the identification and traceability of

Farm animals and other agricultural products A.T.Q.

Agri-Traçabilité Québec Inc. ii

INS-087

2011-06-02

4.3.4 Post-operational follow-up ......................................................................................................................... 12

5 CONTACTS AND TECHNICAL SUPPORT ............................................................................................ 13

6 OPERATION AND CONTROLS ............................................................................................................. 14

6.1 FOLLOW-UP PROCEDURE ..................................................................................................................... 14

6.2 RE-TRANSMISSION PROCEDURE ........................................................................................................... 14

6.2.1 The e-mail was not successfully sent .......................................................................................................... 14

6.2.2 Incomplete file ............................................................................................................................................ 14

6.2.3 Missing transactions in the file ................................................................................................................... 14

6.2.4 Rejects ........................................................................................................................................................ 15

6.3 FILE COMPRESSION (ZIP).................................................................................................................... 15

7 FILE STRUCTURE FOR DATA TRANSMISSION ................................................................................. 16

7.1 STRUCTURE OF THE FILE NAME ............................................................................................................ 16

7.2 ASSEMBLY ORDER ............................................................................................................................... 17

7.3 FREQUENCY OF DATA TRANSMISSION .................................................................................................. 17

7.4 E-MAIL TRANSFERS ............................................................................................................................. 17

8 REQUIRED STRUCTURE OF EVENT TRANSACTIONS ...................................................................... 18

8.1 TYPE “A” OBSERVATION REPORT ......................................................................................................... 20

8.2 TYPE “C” SLAUGHTER ......................................................................................................................... 22

8.3 TYPE “D” DEATH ................................................................................................................................. 26

8.4 TYPE “E” RENDERING .......................................................................................................................... 28

8.5 TYPE “F” TRANSPORT AND PREMISE TRANSFER ................................................................................... 31

8.6 TYPE “G” INSEMINATION ...................................................................................................................... 39

8.7 TYPE “M” ACTIVATION ......................................................................................................................... 41

8.8 TYPE “N” IN TRANSIT ........................................................................................................................... 45

8.9 TYPE “O” LOADING – UNLOADING ........................................................................................................ 49

8.10 TYPE “P” NECROPSY .......................................................................................................................... 52

8.11 TYPE « Q » ASSOCIATION .................................................................................................................. 55

8.12 TYPE « R » DISSOCIATION .................................................................................................................. 56

8.13 TYPE “CNTLF” ................................................................................................................................... 57

Annexe A – ....................................................................................................................................................... II

Annexe B – ..................................................................................................................................................... VII

Interface’s protocol for the Identification events and

the livestock and other agricultural products traceability A.T.Q.

Agri-Traçabilité Québec Inc. 3

INS-087

2011-06-02

1 FOREWORD

AGRI-TRAÇABILITÉ QUÉBEC INC. is pleased to submit to its partners a protocol permitting the

data entry of events required for the identification and tracking of farm animals and other

agricultural products into the traceability system.

Confidentiality Notice

The information appearing in this document is legally privileged and confidential between AGRI-

TRAÇABILITÉ QUÉBEC INC. and the requesting party. Except for the requesting party‟s own use,

this document may not be reproduced or transmitted in any form whatsoever.




INS-087

2011-06-02

2 INTRODUCTION

2.1 Background

The Federal regulation governing the permanent identification of cattle came into effect on January

1st, 2001. Provincial laws regarding animal identification and traceability, along with pressure from

buyers demanding quality guarantees on agri-food products, caused the Ministère de l’Agriculture,

des Pêcheries et de l’Alimentation du Québec (MAPAQ) and the Union des producteurs agricoles

(UPA) to work together on the implementation of an identification and tracking system for

agricultural products. This system will allow government agencies and farm producers to improve

the control, quality and safety of products.

In the light of extensive media coverage on animal health, concerned stakeholders in Québec

agreed to put into place a specific Québec tracking system, which would meet the requirements of

MAPAQ, the UPA and its affiliates. The agency thus created, called AGRI-TRAÇABILITÉ QUÉBEC

INC. (A.T.Q.), is responsible for the management of the system for the identification and

traceability of agricultural products.

To this end, the traceability system used by A.T.Q. relies primarily on the quality of the information

sent by the principal stakeholders (farmers, agencies, auction barns, meat packers, etc.), from the

moment of initial identification and activation (e.g. birth) until de-activation (e.g. death, slaughter) of

an animal. Each of these stakeholders, having an important role in the production cycle, can

contribute to the entry of information into the A.T.Q. traceability system, according to their

respective types of intervention. All inputs identified as being essential for an effective identification

and tracking system are called EVENTS. Although it is possible for A.T.Q. to receive event data in

various administrative forms (by mail, fax, etc.), electronic transmission of data is favoured. In this

regard, the present document describes the protocol for the electronic transmission of data for

EVENTS supported by the A.T.Q., covering the complete cycle of animal production.




INS-087

2011-06-02

2.2 Terminology

2.2.1 Premise

A premise is a location where an animal/lot could be found at any given time during its life

cycle, as defined by regulation. A.T.Q. assigns a specific number to every premise

belonging to each primary player in the system. It is a seven-digit code, providing a unique

identification for every location where an animal could be found.




INS-087

2011-06-02

3 PRINCIPLES FOR DATA ENTRY OF EVENTS

3.1 Methods of data transmission of events

The following diagram illustrates the major premises and their interactions. The A.T.Q. maintains

six methods of data transmission of EVENTS for the purpose of traceability.

1) Electronic interface is the favoured method and is the purpose of the present document

(section 9.4)

2) Through its website at the following address: http://www.agri-tracabilite.qc.ca

3) The A.T.Q. can be reached by telephone at

the following numbers: (450) 677-1757 / 1-866-270-4319

4) Fax transmission is also possible: (450) 679-6547 / 1-866-473-4033

5) By e-mail at the following address: [email protected]

6) By mail to the A.T.Q. office address: 555, Roland-Therrien Blvd, suite 050

Longueuil, Qc J4H 4E8

http://www.agri-tracabilite.qc.ca/mailto:[email protected]




INS-087

2011-06-02

For methods 2 through 6, the data does not have to be formatted in the form presented in this

document. In these cases, ordinary text can be used, as long as all required information is

included.

3.2 Control Points and Observation Reports

The following diagram illustrates the typical architecture of the control points (CP) and the

authorized reporters in a production cycle.




INS-087

2011-06-02

The owner of an animal or a premise must report the arrival of the animal onto the premise,

whether it originates from within or outside Québec.

In addition, the presence of an animal on a premise can be detected without the animal having to

move. In this case, an authorized reporter plays the role of a control point by issuing a declaration

of presence (an observation report) to A.T.Q.




INS-087

2011-06-02

4 DEFINITION OF EVENTS

4.1 Unit Events (Animals)

4.1.1 Observation report

An observation report is a determination of the presence of an animal on a premise by an

authorized reporter (an inseminator, for example).

4.1.2 Slaughter

Every animal slaughtered must be reported to A.T.Q. The identification number of the

animal is then withdrawn.

4.1.3 Death

If an animal dies due to age, sickness or accident, the death is reported by the producer or

the renderer that takes possession of the dead animal.

4.1.4 Rendering

Any animal destined for rendering must be reported to A.T.Q. The animal identification

number of the said animal is then withdrawn.

4.1.5 Transfer

When an animal is moved from one premise to another, belonging to the same owner or

not, the premise transfer must be reported.

4.1.6 Transport

Since 2004, all transport of animals must be reported to A.T.Q. A transport is involved in

almost every event tracked by A.T.Q.

4.1.7 Insemination

When an animal is inseminated, the insemination must be reported.




INS-087

2011-06-02

4.1.8 Activation

All activations of identification numbers must be declared to A.T.Q.

4.1.9 In transit

The temporary presence of an animal in Québec for a short period must be reported. If its

presence is longer than the delay prescribed by law, an activation of an identification

number must be declared.

4.1.10 Loading-Unloading

Occurs when an animal moves from one premise (premise number or vehicle registration

number) to another by way of a vehicle.

4.1.11 Necropsy

The presence of an animal in a pathology laboratory. The animal can arrive dead.

4.1.12 Association

An association allows for the combining of a “yellow tag” number and an ISO identifier.

4.1.13 Dissociation

Dissociation allows one to end the combination of a “yellow tag” number and an ISO

identifier.




INS-087

2011-06-02

4.2 The Architecture of EVENT Transactions

4.2.1 Unit transaction (Animals)

No matter what type of event is registered for an animal, the recording is always preceded by the

“Observation Report” portion (type A). This is because every EVENT is necessarily linked to an

authorized reporter (someone has to have noted the event). For example, a “Slaughter” event

(type C) would be preceded by a type A record. However, it is possible for a notation to be only a

type A entry, when for example, a simple determination of presence is sent (i.e. an authorized

reporter notes the presence of an animal on a premise).

The fields of this portion are almost all obligatory. They serve to properly identify the event, no

matter what its nature. The field “authorized reporter” indicates the A.T.Q. number or another alias

used to identify the reporter who is recording the event. The field “Premise/Veh” represents the

location of the reported event. It can contain either the number of the premise (as previously

designated by A.T.Q.) or the registration number of the vehicle. “ID” corresponds to the ear tag

number of the animal involved in the event. If the animal does not exist in the system, it is assumed

it is coming from “Outside Québec”. The “Date” represents the day and time (optional) when the

event was noted. The “Type” is a code denoting the type of event taking place. It, in turn,

determines the format of the record (these formats are all described in section 8).




INS-087

2011-06-02

4.3 Steps for Implementation

The following paragraphs describe the principal steps involved in the setting-up and the

implementation of the interface.

4.3.1 Initialization of the project

Initial comprehension of the present document, analysis of its impact on the computing

process and the initialization of the project by the stakeholder.

Identification of contact agents.

Agreement with A.T.Q. concerning the system testing and commencement of output.

Development

Implementation phase and local tests on the required programs

4.3.2 Testing

Process identification

Transmission of first file

Debugging and adjustments

Repetition over several periods

Debugging and adjustments

4.3.3 Production

Identification of synchronization requirements

Initialization of script for start-up

Automatic or manual execution options

Verification of debugging reports

Adjustments, if necessary

4.3.4 Post-operational follow-up

Periodic verification for quality control




INS-087

2011-06-02

5 CONTACTS AND TECHNICAL SUPPORT

For our partners:

A.T.Q. wishes to have names and coordinates of the responsible parties at the following levels:

Administrative contact

o contact-person who has the responsibility of authorizing the implementation of the

interface used for the transmission of event data.

IT contact

o contact-person who has the responsibility of creating the interface used for the

transmission of event data.

Operational contact

o contact-person who has the responsibility for the day-to-day operation of the

interface used for the transmission of event data.

For A.T.Q.:

For all information concerning this document, its implementation, follow-up, revisions, etc., here are

our coordinates:

Agri-Traçabilité Québec Inc.

C/O IT Dept.

555 Roland-Therrien Blvd., suite 050

Longueuil Qc J4H 4E8

Telephone: (450) 677-1757

Fax: (450) 679-6547

E-mail: [email protected]

mailto:[email protected]




INS-087

2011-06-02

6 OPERATION AND CONTROLS

6.1 Follow-up procedure

Periodically, the person responsible for the day-to-day operations should verify that all the files in

his or her “log” have been transmitted and identify those that generated error messages. In the

case of an error message, the head of operations at A.T.Q. must be contacted to determine the

proper procedures to transmit the file successfully.

6.2 Re-transmission procedure

A module of the A.T.Q. system is designed to do nothing but identify any errors generated by each

data transmission. These errors can be of several types:

6.2.1 The e-mail was not successfully sent

At the A.T.Q. end, there is no way of knowing if an e-mail was not received. For example, the

sender‟s e-mail logon script may have certain problems and not successfully send the given file.

A.T.Q. verifies all e-mails received but they cannot know if a file should have arrived but did not.

6.2.2 Incomplete file

If a file is incomplete, its “control record” will be absent (see section 8.13). When the A.T.Q. script

tries to read the file, it will not find the control record that is supposed to be located at the end of

the file and an error message will appear in the table provided for this purpose.

6.2.3 Missing transactions in the file

The control record at the end of each file indicates the number of records that should be found. If

this number does not correspond to the number of transactions found in the file, an error message

will appear in the table provided for this purpose.




INS-087

2011-06-02

6.2.4 Rejects

If a transaction does not comply with A.T.Q.‟s logical sequence of events or if it does not conform

to the required format as described in section 8, a reject message is generated. For example, if a

“Birth” transaction is received after a “Slaughter” event (for the same animal), or if a “Transport”

event is declared for an identification number not yet activated in the system, a reject message is

generated and the status of the transaction will be labelled “ERR-“. The same would occur if data

in the file is wrongly positioned.

In all of these cases, an A.T.Q. agent would then contact the sending party that transferred the

erroneous files, in order to correct the mistakes and resend the information.

6.3 File Compression (ZIP)

A.T.Q. supports and accepts the compression of event files in the .zip extension format.




INS-087

2011-06-02

7 FILE STRUCTURE FOR DATA TRANSMISSION

7.1 Structure of the file name

Files prepared for data transmission should be in ASCII format and each file must be separated by

positioning (not by commas). The exact format required for the files is described in section 8 of the

present document.

Example:

PRO1090977 1134277 01012499077876 2002-03-0416:06:38 TEMOI

PRO1090977 1134277 01012499157642 2002-03-0416:06:57 TEMOI

Instead of:

PRO1090977,1134277,01012499077876,2002-03-04 16:06:38,TEMOI

PRO1090977,1134277,01012499157642,2002-03-04 16:06:57,TEMOI

In addition, in order to avoid identical file names, an algorithm that will not generate a duplicate

name must be used. Consequently, file names should be in the following format:

„EVENE‟ + „_‟ + Stakeholder No + „_‟ + date (YYMMDD) + „_‟ + sequence + „.DAT‟

Stakeholder No: the A.T.Q. ID number for the stakeholder sending the file

Date: The date the file is sent

Sequence: A number from 1 to N that is incremented for each file sent and brought back to

zero every day. Another method to ensure uniqueness of file names is to insert the time format

(HHMMSS) in the file name.

Example:

„EVENE‟ + PRO1897966 + 020929 + 1 + „.DAT‟ =

EVENE_PRO1897966_020929_1.DAT




INS-087

2011-06-02

„EVENE‟ + PRO1897966 + 020929 + 4 + „.DAT‟ =

EVENE_PRO1897966_020929_4.DAT

„EVENE‟ + PRO1901256 + 021201 + 172319 + „.DAT‟ =

EVENE_PRO1901256_021201_172319.DAT

7.2 Assembly order

For each file transmission, it is important to send only the prescribed fields and not to fill any empty

spaces with superfluous information. The system algorithm verifies each entry to assure that the

proper format is respected for each type of event (see section 8), and rejects any transaction that

fails the test.

At the end of each file transmitted, a control record must be inserted after the last entry, to verify

that the data transmission was successful. This control record is defined in section 8.13.

7.3 Frequency of Data Transmission

The objective of a data transmission is to obtain all of the events recorded by a stakeholder since

the last transmission, but also to avoid duplication of records. It is therefore necessary for the

stakeholder to manage his or her selection of events based on the date of the last transmission of

data. Consequently, a duplicate record transfer will create a rejection message and a follow-up by

A.T.Q.

It is important to synchronize the start-up of your extraction program with the period, date and time

of your production cycle that will give the most up-to-date results. This frequency of data

transmission must be pre-arranged with A.T.Q.

7.4 E-mail Transfers

A.T.Q. prefers the electronic transmission of data by e-mail. The file containing the data is sent as

an attachment.




INS-087

2011-06-02

8 REQUIRED STRUCTURE OF EVENT TRANSACTIONS

This section describes the format that the various records of events must conform to, depending on

their type. However, several types of events can use the same format. The column “Start” indicates

the position in the ASCII file where the particular value begins. The column “End” indicates the

position where the value ends. “L/R” denotes the alignment of the field between the limits “Start”

and “End” – L for left, R for right. The column “Obl” indicates whether a value is obligatory in the

particular field: “Y” if obligatory, “N” if optional. If a field must comply with a specific format (a date,

for instance), it is noted in the “Format” column. Finally, an example for each field is shown in the

“Example” column.

# Field Start End Width L/R Obl. Format Example

1 Stakeholder No. 1 25 25 L Y PRO4621750

2 Type of location 26 26 1 L Y S or V S

3 Premise/Veh. No 27 51 25 L Y 2311842

4 Animal ID Number 52* 76* 25 L Y 124997574771341

5 Date the animal/lot was

observed 77 86 10 L Y YYYY-MM-DD 2002-05-06

6 Time the animal/lot was

observed 87 94 8 L N HH:MM:SS 15:28:53

7 Type of event 95 110 16 L Y TEMOI or D_TEMOI TEMOI

1. Stakeholder No: The A.T.Q. number (or other alias) of the authorized reporter making the

observation report.

2. Type of location: „S‟ if the event is sent from a premise; „V‟ if sent from a vehicle.

3. Premise / Veh. No: The location (premise number or vehicle registration number) where the

event occurred.




INS-087

2011-06-02

4. Animal ID Number: The A.T.Q. identification number (or other alias) of the observed animal or

lot of animals.

It can be in one of two forms:

1. 15 digits: A.T.Q. number (in bold characters)

2. 21 characters: (maximum): Alias of the animal/lot.

5. Date: Date that the event was recorded.

6. Time: Time that the event was recorded.

7. Type of event: TEMOI for a type “A” observation report.




INS-087

2011-06-02

8.1 Type “A” Observation Report

A type “A” record denotes an observation report on an animal. The same structure is used to

delete an observation report on an animal. The first block of the transaction describes the event in

general (see beginning of section 8), and the second part, the observation itself.




3 Premise / Veh. No 27 51 25 L Y 2311842

4 Animal ID Number 52* 76* 25 L Y 124997574771341

5 Date the animal /

lot was observed 77 86 10 L Y YYYY-MM-DD 2002-05-06

6 Time the animal /

lot was observed 87 94 8 L N HH:MM:SS 15:28:53

7 Type of event 95 110 16 L Y TEMOI or D_TEMOI TEMOI

8 Note 111 160 50 L N Free text Free text

9 Species code 161 176 16 L N BF

10 Weight 177 187 11 R N 99999999999 478

11 Transaction Number 188 197 10 L N Alphanumeric code AAAA1001

12 Sex 198 198 1 L N M or F F

13 Positioning method 199 208 10 L N LONG_LAT

14 Position 1 209 233 25 L N 124.12

15 Position 2 234 258 25 L N 124.12

16 Production category 259 268 10 L N Category code VLA, VLO, BOU, ...

17 Stakeholder No. 269 293 25 L N PRO4621757

18 External client No. 294 318 25 L N AAAA9999

19 Transport permit No. 319 343 25 L N Alphanumerical number ABC123

20 Electronic reader ind. 344 344 1 L N Y or N Y

21 Category 345 360 16 L N REPRO

8. Note: Free text

9. Species code: Code for the species of animal involved.

10. Weight: Weight of the observed animal in pounds.

11. Transaction Number: A number, generated by the stakeholder, identifying this transaction in a

unique manner among other transactions sent by this stakeholder.




INS-087

2011-06-02

12. Sex: The sex of the animal observed.

13. Positioning method: Type of geo-positioning used for the values in Position 1 and Position 2.

a. Accepted values:

i. LONG_LAT

Position 1: Longitude

Position 2: Latitude

14. Position 1: 1st coordinate in the positioning of the location of the event.

15. Position 2: 2nd coordinate in the positioning of the location of the event.

16. Production category: Production category code of the concerned animal.

17. Stakeholder No. : A.T.Q. number of the stakeholder for whom the transaction is being done

(Normally used by an authorized reporter).

18. External client No.: Identification number of the stakeholder‟s client (or ID number of the client‟s

client).

19. Transport permit No.: Transportation permit number.

20. Electronic reader ind.: Indicates yes (Y) or no (N) whether the identifier was read electronically.

21. Category: Code for the category of animal observed.

a. Accepted values for ovines:

i. REPRO

Use: Breeding animal




INS-087

2011-06-02

8.2 Type “C” Slaughter

A type “C” record denotes the slaughter of an animal. The same structure is used to delete the

slaughter report on an animal. The first block of information in the transaction describes the event

in general (see beginning of section 8) and the second part, the slaughter event itself.


1 Stakeholder No. 1 25 25 L Y ABA21750

2 Type of location 26 26 1 L Y S S

3 Premise No 27 51 25 L Y 2311842

4 Animal ID Number 52 76 25 L Y 124997574771341

5 Slaughter date 77 86 10 L Y YYYY-MM-DD 2002-05-06

6 Slaughter time 87 94 8 L N HH:MM:SS 15:28:53

7 Type of event 95 110 16 L Y ABATT or D_ABATT ABATT

8 Ind . if condemned 111 111 1 L Y Y or N N

9 Type of location Qc 112 112 1 L N S or V S

10 Premise / Veh. Qc 113 137 25 L N 2311842

11 Country of origin 138 153 16 L N CA

12 Prov. of origin 154 169 16 L N ON

13 Species code 170 185 16 L Y BF

14 Name 186 245 60 L N M. John Douglas

15 Address1 246 345 100 L N 2133 Maple Street

16 Address2 346 445 100 L N Trenton On M7U6T4


18 Sex 456 456 1 L N M or F F


20 Position 1 467 491 25 L N 124.12

21 Position 2 492 516 25 L N 124.12


23 Electronic reader ind. 527 527 1 R N Y or N Y


25 Unused 544 545 2 L N Must contain empty spaces

26 Weight at slaughter 546 556 11 R N 99999999999 478


28 Animal alias 1 607 631 25 L N CAN-123456

29 Animal alias 2 632 656 25 L N







INS-087

2011-06-02


34 Transport permit No. 757 781 25 L N Alphanumeric number ABC123

35 Pos. method – Origin 782 791 10 L N LONG_LAT

36 Position 1 – Origin 792 816 25 L N 124.12


A slaughter event can only take place on a premise and not in a vehicle.

7. Type of event: ABATT for a type “C” report.

8. Ind. if condemned: „N‟ if the animal was accepted for slaughter (condemnation indicator=„N‟).

9. Type of location Qc: When an animal/lot originating from within Québec arrives for slaughter, its

origin must be indicated. In this case, this field is obligatory. If the origin as specified in the

field Premise / Veh. Qc is a premise number, then the type of location would be „S‟. If the origin

as specified in the field Premise / Veh. Qc is a vehicle registration number, then the type of

location would be „V‟. If the animal does not originate from Québec, the type of location Qc

should be left blank.

10. Premise / Veh. Qc: The location (premise number or vehicle registration number) where the

animal/lot is coming from, if this location is in Québec. This field is then obligatory. If not in

Québec, this space is left blank.

11. Country of origin: If the animal does not come from Québec, the country of origin must be

specified and this becomes an obligatory field. If from Québec, the space is left blank.

12. Prov. of origin: If the animal does not come from Québec, the province/state of origin must be


13. Species code: Code for the species of animal slaughtered.

14. Name: The name of a contact-person on the farm of origin (if outside Québec)

15. Address1: 1st line of the address of the farm where the animal originated (if outside Québec).

16. Address2: 2nd line of the address of the farm where the animal originated (if outside Québec).







INS-087

2011-06-02


a. Accepted values:

i. LONG_LAT









i. REPRO


25. Unused.

26. Weight at slaughter: The weight of the slaughtered animal in pounds.

27. Note: Free text.

28. Animal alias 1: Other identification found on the animal at time of slaughter. This identification

will also be withdrawn from the A.T.Q. database.







32. Stakeholder No.: A.T.Q. number of the Stakeholder for whom the transaction is being done



client).

34. Transport permit No.: Transportation permit number




INS-087

2011-06-02

35. Positioning method – Origin: Type of geo-positioning used for the values in Position 1 – Origin

and Position 2 – Origin.

a. Accepted values:

i. LONG_LAT

Position 1 – Origin: Longitude

Position 2 – Origin: Latitude

36. Position 1 – Origin: 1st coordinate in the positioning of the location of the origin.

37. Position 2 – Origin: 2nd coordinate in the positioning of the location of the origin.




INS-087

2011-06-02

8.3 Type “D” Death

A type “D” record denotes the death of an animal. The same structure is used to delete the death

report of an animal. The first block of information in the transaction describes the event in general

(see beginning of section 8) and the second part, the death event itself.




3 Premise / Veh. No 27 51 25 L Y 2311842


5 Date of death 77 86 10 L Y YYYY-MM-DD 2002-05-06

6 Time of death 87 94 8 L N HH:MM:SS 15:28:53

7 Type of event 95 110 16 L Y DECES or D_DECES DECES

8 Sex 111 111 1 L N M or F F


10 No. of Disposal premise 113 137 25 L Y 3935415



13 Weight 204 214 11 R N 99999999999 478



16 Position 1 235 259 25 L N 124.12

17 Position 2 260 284 25 L N 124.12





22 Pos. method – Disposal 370 379 10 L N LONG_LAT

23 Position 1 – Disposal 380 404 25 L N 124.12

24 Position 2 – Disposal 405 429 25 L N 124.12


7. Type of event: DECES for a type “D” report.



10. No. of disposal premise: Number of the rendering plant premise that the animal/lot is sent to, or

the number of the burial or disposal premise used.




INS-087

2011-06-02

11. Note: free text

12. Species code: Code for the species of animal involved.





a. Accepted values:

i. LONG_LAT






19. Stakeholder No. : A.T.Q. number of the Stakeholder for whom the transaction is being done



client).


22. Positioning method – Disposal: Type of geo-positioning used for the values in Position 1 –

Disposal and Position 2 – Disposal.

a. Accepted values:

i. LONG_LAT

Position 1 – Disposal: Longitude

Position 2 – Disposal: Latitude

23. Position 1 – Disposal: 1st coordinate in the positioning of the location of the disposal.

24. Position 2 – Disposal: 2nd coordinate in the positioning of the location of the disposal.



i. REPRO





INS-087

2011-06-02

8.4 Type “E” Rendering

A type “E” record denotes the rendering of an animal. The same structure is used to delete the

rendering report of an animal. The first block of information in the transaction describes the event

in general (see beginning of section 8) and the second part, the rendering event itself.


1 Stakeholder No. 1 25 25 L Y EQU46210


3 Premise No 27 51 25 L Y 2311842


5 Date of rendering 77 86 10 L Y YYYY-MM-DD 2002-05-06

6 Time of rendering 87 94 8 L N HH:MM:SS 15:28:53

7 Type of event 95 110 16 L Y EQUAR or D_EQUAR EQUAR

8 Sex 111 111 1 L N M or F F

9 Type of location Qc 112 112 1 L N S or V S

10 Premise / Veh. Qc 113 137 25 L N 2311842









19 Position 1 466 490 25 L N 124.12

20 Position 2 491 515 25 L N 124.12

21 Production category 516 525 10 L N Category code VLA, VLQ, BOU, …

22 Electronic reader Ind. 526 526 1 L N




26 Weight 596 606 11 R N 999999999 478











INS-087

2011-06-02

A rendering event can only take place on a premise and not in a vehicle.

7. Type of event: EQUAR for a type “E” report.


9. Type of location Qc: When an animal/lot originating from within Québec is destined for

rendering, their origin must be indicated. In that case, this field is obligatory. If the origin as

specified in the field Premise / Veh. Qc is a premise number, then the type of location would be

„S‟. If the origin as specified in the field Premise / Veh. Qc is a vehicle registration number,

then the type of location would be „V‟. If the animal does not originate from Québec, the type of

location Qc should be left blank.


animal/lot is coming from, if this location is in Québec. This field is then obligatory. If not in

Québec, this space is left blank.

11. Country of origin: If the animal does not come from Québec, the country of origin must be


12. Prov. of origin: If the animal does not come from Québec, the province/state of origin must be


13. Species code: Code for the species of animal rendered.







a. Accepted values:

i. LONG_LAT





21. Production category; Production category code of the concerned animal.




INS-087

2011-06-02




i. REPRO


24. Unused.

25. Note: Free text


27. Unused.




client).




a. Accepted values:

i. LONG_LAT








INS-087

2011-06-02

8.5 Type “F” Transport and Premise Transfer

A type “F” record denotes either the transport of an animal or the transfer of the animal to another

premise. The same structure is used to delete the transport/transfer of an animal. The first block

of information in the transaction describes the event in general (see beginning of section 8) and the

second part, the transport/transfer event itself.

Premise transfer (TRANS)




3 Premise No 27 51 25 L Y 2311842


5 Date of transfer 77 86 10 L Y YYYY-MM-DD 2002-05-06

6 Time of transfer 87 94 8 L N HH:MM:SS 15:28:53

7 Type of event 95 110 16 L Y TRANS or D_TRANS TRANS

8 P / D Code 111 111 1 L Y P or D P

9 Type of location Qc 112 112 1 L N S or V V

10 Premise / Veh. Qc 113 137 25 L N HDL990

11 Country 138 153 16 L N US

12 Province 154 169 16 L N TX


14 Name 186 245 60 L N Mr. John Douglas





19 Position 1 466 490 25 L N 124.12

20 Position 2 491 515 25 L N 124.12


22 -- Electronic reader ind. 526 526 1 L N Y or N Y


24 -- Unused 543 545 3 L N Must contain empty spaces

25 Sex 546 546 1 L N M or F M

26 -- Date of tagging 547 556 10 L N YYYY-MM-DD 2002-05-06

27 Time of tagging 557 564 8 L N HH:MM:SS 09:44:32

28 Ind. if real birth date 565 565 1 L N* Y or N N

29 Weight* 566 576 11 R N* 99999999999 110




INS-087

2011-06-02

30 Age in months 577 586 10 R N 9999999999 24



33 Original ID 622 646 25 L N 124997574711348

34 Animal alias 647 671 25 L N AA-11299311164

35 Date of birth 672 681 10 L N* YYYY-MM-DD 2002-05-01

36 Time of birth 682 689 8 L N* HH:MM:SS 13:01:30

37 Ind. if in transit 690 690 1 L N Y or N N




41 Pos. method – O/D 791 800 10 L N LONG_LAT

42 Position 1 – O/D 801 825 25 L N 124.12

43 Position 2 – O/D 826 850 25 L N 124.12

A transfer event can only take place on a premise and not in a vehicle.

7. Type of event: TRANS (premise transfer) or TRPRT (transport) for a type “F” report.

8. P / D Code: „P‟ in the case where the origin is noted (in the fields premise no., country,

province, name, address1…); „D‟ when it is the destination that is noted.

9. Type of location Qc: When the origin or destination of an animal/lot is situated in Québec, this

field is obligatory. If the origin or destination as specified in the cell Premise / Veh. Qc is a

premise number, then the type of location would be „S‟. If the origin or destination as specified

in the field Premise / Veh. Qc is a vehicle registration number, then the type of location would

be „V‟. If the animal does not originate from Québec or the destination isn‟t in Québec, the type

of location Qc should be left blank.


animal/lot is coming from or going to, if this location is in Québec. This field is then obligatory.

If not in Québec, this space is left blank.

11. Country: Code for the country that the animal/lot is coming from or going to, if not in Québec.

In this case, the field is obligatory. If in Québec, the space is left blank.

12. Prov.: Code for the province/state that the animal/lot is coming from or going to, if not in

Québec. In this case, the field is obligatory. If in Québec, the space is left blank.

13. Species code: Code for the species of animal transported/transferred.





INS-087

2011-06-02

15. Address1: 1st line of the address of the farm where the animal originated or going to (if outside

Québec).

16. Address2: 2nR line of the address of the farm where the animal originated or going to (if outside

Québec).




a. Accepted values:

i. LONG_LAT





21. Production category: Production category code of the observed animal.




i. REPRO


24. Unused.

Fields used for activation of an Animal ID Number by auction barns

25. Sex: Sex of the observed animal.

26. Date of tagging*: Date that the observed animal was tagged.

27. Time of tagging* : Time that the observed animal was tagged

28. Ind. if real birth date*: Determines whether the birth date was provided and valid “O” (or “Y”) or

whether the A.T.Q must estimate the date of birth of the animal “N”.

29. Weight*: Weight of the observed animal in pounds, at the time the animal was tagged. This

field is obligatory if the field “Ind. if real birth date*” is marked „N‟.

30. Age in months: Age of the observed animal, in months.




INS-087

2011-06-02



32. Unused.




INS-087

2011-06-02

Fields used for activation of an Animal ID Number by auction barns

33. Original ID: A.T.Q. identification number previously worn by the animal/lot.

34. Alias: number: an identification number not originating with the A.T.Q. for the animal/lot. This

information, if provided, creates a field “alias_anilot” of the type „ALACT – Alias activation‟

35. Date of birth*: Date of birth of the observed animal/lot.

36. Time of birth*: Time of birth of the observed animal/lot.

37. Ind. if in transit: Indicates if an anilot is in transit or not. If no information is provided, the value

„N‟ is assumed by default.



client).


41. Positioning method – Origin/Destination: Type of geo-positioning used for the values in

Position 1 – Origin/Destination and Position 2 – Origin/Destination.

a. Accepted values:

i. LONG_LAT

Position 1 – Origin/Destination: Longitude

Position 2 – Origin/Destination: Latitude

42. Position 1 – Origin/Destination: 1st coordinate in the positioning of the location of the origin or

destination.

43. Position 2 – Origin/Destination: 2nd coordinate in the positioning of the location of the origin or

destination.

* For A.T.Q.:

If the field “Ind. if real birth date” = „Y‟), then

- Date of birth is obligatory and taken into consideration

- Weight at activation is considered for information only.

If the field “Ind. if real birth date” = „N‟, then

- Weight at activation is obligatory and taken into consideration

- Date of birth is ignored

- Date of birth is calculated according to the weight at activation

and the date of tagging.




INS-087

2011-06-02

Transport (TRPRT)


1 Stakeholder No. 1 25 25 L Y TRA46217

2 Type of location 26 26 1 L Y V V

3 Veh. No 27 51 25 L Y BGY283


5 Date of transport 77 86 10 L Y YYYY-MM-DD 2002-05-06

6 Time of transport 87 94 8 L N HH:MM:SS 15:28:53

7 Type of event 95 110 16 L Y TRPRT or D_ TRPRT TRPRT

8 P / D Code 111 111 1 L Y P or D P

9 Type of location Qc 112 112 1 L N S or V V

10 Premise / Veh. Qc 113 137 25 L N HDL990

11 Country 138 153 16 L N US

12 Province 154 169 16 L N TX






18 Sex 456 456 1 L N M or F F


20 Position 1 467 491 25 L N 124.12

21 Position 2 492 516 25 L N 124.12




25 Unused 544 545 2 R N Must contain empty spaces


27 Weight 596 606 11 R N 99999999999 478





32 Position 1 – O/D 692 716 25 L N 124.12

33 Position 2 – O/D 717 741 25 L N 124.12

A transport event can only take place in a vehicle and not on a premise.




INS-087

2011-06-02

7. Type of event: TRANS (premise transfer) or TRPRT (transport) for a type “F” report.

8. P / D Code: „P‟ in the case where the origin is noted (in the fields premise no., country,

province, name, address1…); „D‟ when it is the destination that is noted.

9. Type of location Qc: When the origin or destination of an animal/lot is situated in Québec, this

field is obligatory. If the origin or destination as specified in the cell Premise / Veh. Qc is a

premise number, then the type of location would be „S‟. If the origin or destination as specified

in the field Premise / Veh. Qc is a vehicle registration number, then the type of location would

be „V‟. If the animal does not originate from Québec or the destination isn‟t in Québec, the type

of location Qc should be left blank.


animal/lot is coming from or going to, if this location is in Québec. This field is then obligatory.

If not in Québec, this space is left blank.

11. Country: Code for the country that the animal/lot is coming from or going to, if not in Québec.

In this case, the field is obligatory. If in Québec, the space is left blank.

12. Prov.: Code for the province/state that the animal/lot is coming from or going to, if not in

Québec. In this case, the field is obligatory. If in Québec, the space is left blank.

13. Species code: Code for the species of animal transported/transferred.



Québec).

16. Address2: 2nR line of the address of the farm where the animal originated or going to (if outside

Québec).



18. Sex.


a. Accepted values:

i. LONG_LAT







INS-087

2011-06-02






i. REPRO


25. Unused.


27. Weight*: Weight of the observed animal in pounds, at the time the animal was tagged. This

field is obligatory if the field “Ind. if real birth date*” is marked „N‟.




client).


31. Positioning method – Origin/Destination: Type of geo-positioning used for the values in

Position 1 – Origin / Destination and Position 2 – Origin / Destination.

a. Accepted values:

i. LONG_LAT

Position 1 – Origin/Destination: Longitude

Position 2 – Origin/Destination: Latitude

32. Position 1 – Origin/Destination: 1st coordinate in the positioning of the location of the origin or

destination.

33. Position 2 – Origin/Destination: 2nd coordinate in the positioning of the location of the origin or

destination.




INS-087

2011-06-02

8.6 Type “G” Insemination

A type “G” record denotes the insemination of an animal. The same structure is used to delete

insemination of an animal. The first block of information in the transaction describes the event in

general (see beginning of section 8) and the second part, the insemination event itself.




3 Premise No 27 51 25 L Y 2311842


5 Date of insemination 77 86 10 L Y YYYY-MM-DD 2002-05-06

6 Time of insemination 87 94 8 L N HH:MM:SS 15:28:53

7 Type of event 95 110 16 L Y INSEM or D_INSEM INSEM

8 Sex 111 111 1 L N M or F F


10 Semen No. 113 137 25 L Y SEM-02-04-2001908



13 Weight 204 214 11 R N 99999999999 478



16 Position 1 235 259 25 L N 124.12

17 Position 2 260 284 25 L N 124.12






An insemination event can only take place on a premise and not in a vehicle

7. Type of event: INSEM for a type “G” report.



10. Semen No: Number of the semen used to inseminate the animal.




INS-087

2011-06-02

11. Note: Free text

12. Species code: Code for the species of animal inseminated.





a. Accepted values:

i. LONG_LAT









client).




i. REPRO





INS-087

2011-06-02

8.7 Type “M” Activation

A type “M” record denotes the activation of an animal‟s tag. The same structure is used to delete

the activation of an animal. The first block of information in the transaction describes the event in

general (see beginning of section 8) and the second part, the activation event itself.




3 Premise No 27 51 25 L Y 2311842


5 Date of activation 77 86 10 L Y YYYY-MM-DD 2002-05-06

6 Time of activation 87 94 8 L N HH:MM:SS 15:28:53

7 Type of event 95 110 16 L Y ACTIV or D_ACTIV ACTIV

8 Electronic reader ind. 111 111 1 L N Y or N O





13 Category 154 169 16 L N BOUCH


15 Transaction number 186 195 10 L N

Alphanumeric code AAAA1001

16 Unused 196 201 6 L N Must contain blank spaces

17 Sex 202 202 1 L Y M or F F

18 Date of tagging 203 212 10 L N YYYY-MM-DD 2002-05-06

19 Time of tagging 213 220 8 L N HH:MM:SS 09:44:32

20 Ind. if real birth date 221 221 1 L Y Y or N N

21 Weight at tagging 222 232 11 R N* 99999999999 110

22 Type of positioning 233 242 10 L N LONG_LAT


24 Address 1 246 345 100 L N 2133 Maple Street

25 Address 2 346 445 100 L N Trenton On M7U6T4

26 Position 1 446 470 25 L N 124.12

27 Position 2 471 495 25 L N 124.12







INS-087

2011-06-02



33 Tag Replacement Ind. 621 621 1 L N Y or N N

34 Original ID 622 646 25 L N 124997574711348

35 Alias 647 671 25 L N AA-11299311164

36 Date of birth 672 681 10 L N* YYYY-MM-DD 2002-05-01

37 Time of birth 682 689 8 L N* HH:MM:SS 13:01:30

38 Ind. if in transit 690 690 1 L N Y or N N







An activation event can only take place on a premise and not in a vehicle.

7. Type of event: ACTIV for a type “M” report.


9. Unused

10. Prov. of origin: Code for the province the animal/lot comes from (if outside Québec).

11. Unused.

12. Country of origin: Code for the country the animal/lot comes from (if outside Québec).


a. Accepted values for bovines:

i. BOUCH

Use: Fed cattle

ii. LAITI

Use: Dairy

b. Accepted values for ovines:

i. REPRO


14. Species code: Code for the species of animal observed.




INS-087

2011-06-02



16. Unused.


18. Date of tagging*: Date that the observed animal was tagged.

19. Time of tagging*: Time that the observed animal was tagged.

20. Ind. if real birth date*: Determines whether the birth date was provided and valid “Y” or whether

the A.T.Q must estimate the date of birth of the animal “N” (see * below).

21. Weight at time of activation*: Weight of the observed animal in pounds, at the time the animal

was tagged. This field is obligatory if the field “Ind. if real birth date*” is marked „N‟.


a. Accepted values:

i. LONG_LAT



23. Unused








30. Unused.

31. Name: The name of a contact-person on the farm of origin (if outside Québec).

32. Unused.

33. Tag Replacement Ind.: Indicates yes (Y) or no (N) whether the activation is a tag replacement

declaration.

34. Original ID: The A.T.Q. identification number worn previously by the animal/lot.

35. Alias: number: an identification number not originating with the A.T.Q. for the animal/lot. This

information, if provided, creates a field “alias_anilot” of the type „ALACT – Alias activation‟




INS-087

2011-06-02

36. Date of birth* : Date of birth of the observed animal/lot.

37. Time of birth* : Time of birth of the observed animal/lot.

38. Ind. if in transit: Indicates if an anilot is in transit or not. If no information is provided, the value

„N‟ is assumed by default.



client).




a. Accepted values:

i. LONG_LAT





* For A.T.Q.:

If the field “Ind. if real birth date” = „Y‟), then

- Date of birth is obligatory and taken into consideration

- Weight at activation is considered for information only.

If the field “Ind. if real birth date” = „N‟, then

- Weight at activation is obligatory and taken into consideration

- Date of birth is ignored

- Date of birth is calculated according to the weight at activation

and the date of tagging.




INS-087

2011-06-02

8.8 Type “N” In Transit

A type “N” record denotes an animal in transit (through Québec). The same structure is used to

delete a transit event. The first block of information in the transaction describes the event in

general (see beginning of section 8) and the second part, the transit event itself.

In Transit (TRSIT)




3 Premise No 27 51 25 L Y 2311842

4 Animal ID Number 52 76 25 L N 124997574771341

5 Date of transit 77 86 10 L Y YYYY-MM-DD 2002-05-06

6 Time of transit 87 94 8 L N HH:MM:SS 15:28:53

7 Type of event 95 110 16 L Y TRSIT or D_TRSIT TRSIT

8 Code P / D 111 111 1 L Y P or D O

9 Type of location Qc 112 112 1 L N S or V

10 Premise / Veh. Qc 113 137 25 L N

11 Country 138 153 16 L N CA

12 Province 154 169 16 L N ON






18 Sex 456 456 1 L N M or F F


20 Position 1 467 491 25 L N 124.12

21 Position 2 492 516 25 L N 124.12





26 Weight 546 556 11 R N 999999999 478





31 Lot indicator. 691 691 1 L Y Y or N N




INS-087

2011-06-02



34 Position 1 – O/D 752 776 25 L N 124.12

35 Position 2 – O/D 777 801 25 L N 124.12

A transit event can only take place on a premise and not in a vehicle.

4. Animal ID Number: (optional) the A.T.Q. identification number (or another alias) of the

animal/lot observed. If unknown, leave blank.

7. Type of event: TRSIT for a type “N” report.

8. P / D Code: „P‟ in the case where the origin is noted (in the fields: premise no., country,

province, name, address1…); „D‟ when it is the destination that is noted (in the fields: premise

no., country, province, name, address1…).

9. Type of location Qc: When the origin or destination of an animal is in Québec, this field is

obligatory. If the origin or destination as specified in the field Premise / Veh. Qc is a premise

number, then the type of location would be „S‟. If the origin or destination as specified in the

field Premise / Veh. Qc is a vehicle registration number, then the type of location would be „V‟.

If the animal does not originate from Québec or the destination isn‟t in Québec, the type of

location Qc should be left blank.

10. Premise / Veh. Qc: Location (premise number or vehicle registration number) of the origin or

the destination of the animal/lot, if this location is in Québec. In that case, an entry in this field is

obligatory. If not in Québec, leave this space blank.

11. Country: Code for the country the animal/lot comes from or is traveling to (if outside Québec).

In this case, the field is obligatory. If within Québec, leave blank.

12. Province: Code for the province/state the animal/lot comes from or is traveling to (if outside

Québec). In this case, the field is obligatory. If within Québec, leave blank.

13. Species code: Code for the species of animal observed.





INS-087

2011-06-02


Québec).

16. Address2: 2nd line of the address of the farm where the animal originated or going to (if outside

Québec).





a. Accepted values:

i. LONG_LAT






23. Electronic reader ind.: Indicates yes (Y) or no (N) whether the identifier was read electronically



i. REPRO


25. Unused


27. Stakeholder No. : A.T.Q. number of the Stakeholder for

INTERFACE PROTOCOL PROCESSING OF EVENTS (Version … › images › stories › fantome...(Version...

Documents

Transcript of INTERFACE PROTOCOL PROCESSING OF EVENTS (Version … › images › stories › fantome...(Version...