CCIA Events

For Canadian ranches, Herdly makes working with the CCIA really easy, automating the entire process. The basic premise is that Herdly will create CCIA and submit events in the background as you do your work. For example, a CCIA birth date event will be created automatically when you save the New Calf action. This window lets you see the current status of each CCIA event as it processes. It can also be used to manually submit events if you've used the Ranch Settings window to set things up so Herdly doesn't automatically submit events on its own.

When an event is submitted (whether manually or automatically), it will be sent to the cloud on the next sync. Once on the cloud, it will be sent to CCIA usually within a few minutes. Herdly's cloud server will check the status of the event again about 10-15 minutes later. If there were any processing errors, you will be notified so they can be corrected. All this happens without any effort on your part.

Auto Created CCIA Events

When setup properly, Herdly will automatically create CCIA events in the following situations. Note that if some required information is missing (ex. the animal doesn't have an RFID tag), Herdly will not be able to create the event and will notify you. The necessary information is explained in the documentation for each event.

• A Move In event will be created when saving the New Animal action.
• A Birth Date event will be created when saving a New Calf action.
• A Move In event will be created when saving the Move Animals action.
• A Move Out event will be created when saving the Remove From Herd action.
• A Retired event will be created when saving the Record Death action.
• A Replaced event will be created when saving the Edit Animal action if you've just given the animal an RFID tag and if it didn't have one before.
• A Cross Reference event will be created when saving the Edit Animal action if you've just given the animal a new RFID tag.

Manually Created CCIA Events

CCIA events can be manually created as well. This can be useful in a few situations including when an automatic event could not be created because of missing information. When the information has been entered, then manually create the event. It can also be used to resend corrected events to CCIA that failed during processing for some reason.

To manually create a CCIA event, use the New CCIA Event action.

Viewing CCIA Events

On the computer you can view an animal's CCIA events in the Animal List window by opening the CCIA Events child list. This list has a few actions associated with it, allowing you to inspect a CCIA event, submit it, or delete it. This works well when you want to see the events associated with a particular animal, but often you will want to look at lots of events at the same time. This is explained next.

CCIA Events Window

You can get to the CCIA Events window by going to Animals > CCIA Events on the computer. This window lists all the CCIA events based on their current status. The list on the left shows each possible status an event can be in along with the count of events currently in that status. Selecting a different status will update the list on the right to only show events that currently have that status. You can also narrow the list further by using the Event Type field and the search field. Note that each time a sync is performed, this window will update if any events have changed status.

The possible statuses are:

• Ready To Submit. In this state the event has been created in Herdly, but has not yet been submitted to the CCIA. You need to submit it when you are ready.
• Awaiting Herdly. The event has been submitted (either manually or automatically), but Herdly hasn't sent it to CCIA yet. This happens on the cloud server and usually happens within a few minutes of being submitted. It can take longer, however, if there is a large backlog of events or if there is a connection problem. The cloud server will continue trying to send the event to the CCIA until it succeeds.
• Awaiting CCIA. The event has been submitted to the CCIA successfully and the CCIA is processing the event. The cloud server will continue to check back with the CCIA until it learns the result of the event processing. An event usually stays in this state for ten minutes or so, but can be longer when there is a backlog.
• Complete. This is the desired state for all events. It means it was processed by CCIA with no errors.
• User Error. When an event is in this state, an error occurred somewhere along the line and it is thought to be an error that can be corrected by the user. Usually this means the CCIA account credentials are incorrect or a premise ID was entered wrong. Inspect the event to see the exact error message. Usually the error can be corrected and the event re-submitted.
• Final Error. This status is reserved for when an error occurs with an event that cannot be corrected without creating a brand new event. For example, the RFID tag may not have been in the proper range or a date was entered incorrectly. Inspecting the event will show you exactly what went wrong. It should be fixed and then another CCIA event should be manually created using the New CCIA Event action.

To submit events, select the ones you want to submit and click the Submit To CCIA button. Remember that when the list has the focus you can use Command-A (Mac) or Control-A (Windows) to select all the events in the list, so it is easy to submit them all at once. You can also delete an event by selecting it as clicking the Delete Event button. Note, however, that deleting a submitted event may not stop it from being sent to the CCIA. The cloud server might already be sending it when you delete it from your computer. But if the cloud server knows you've deleted it (after a sync) before it sends it, it will not send the event.

You can inspect an event by double-clicking it. All the related details will be shown.