EC 13 - Do Not Breed (DNB) Event

The DNBClosed Do Not Breed event declares an animal as "Do Not Breed." It sets the animal up to be sold, and in some cases sends a DNB status to DHIAClosed The Dairy Herd Improvement Association (DHIA) is a national association that helps dairy producers create and manage records and data about their cows for use in making management decisions. See http://www.dhia.org/ for more information., removing this animal from some reproductive statistics. If the animal is later declared to be bred, pregnant, or dried, this information will also be sent to DHIA and she will lose the DNB status.

See the topics below for help with this event:

Define Details for this Event

The details listed below are typical for a DNB event; however, be aware that the details you see in the mobile app may vary based on the DC305Closed DairyComp305 - VAS Dairy Management Software command that created the event. If any fields other than the animal IDClosed Identifier are required to process an animal, they are marked with an * (asterisk) symbol in the app.

The app will not allow you to add pregnant animals to this event, and it will warn you before allowing you to add animals that are in BRED status or are already in DNB status.

The ID of the animal you are setting to DNB. This field is automatically populated with the animal ID when you add it to the list. You can tap the animal's ID number to view its CowCard.

The date that the animal was added to the event. This field can be changed based on the following:

  • The new date cannot be later than the animal's birth date.
  • The new date cannot be later than the animal's current Fresh date.
  • The new date cannot exceed 365 days in the past.

For more information about event dates and how to change them, see Changing Event Dates.

The technician who added the animal to this event. Tap this field to select from a list of available technicians.

The names and numbers in the TechnicianClosed Tech is short for Technician. list come from the Technician Table in DC305. This table is optional in DC305, so if you do not see any names here in the mobile app, you need to make sure that a DC305 admin has created this table so that it can synchronize to the PULSE Platform. Once it has been created, a code number and name can be assigned to each technician, and members with DC305 admin permissions can add and remove technician names as necessary. The mobile app requires an active data or WiFi connection to synchronize updates.

The Remark field allows you to type any notes that you would like to include about this animal when adding it to the event. The remark you enter here will be included as additional information in the animal's record.

Note that you will only see this option in the mobile event when REMClosed Remark or comment is included as a condition in the DC305 command that the PULSE Platform uses to create the event.

What Happens When I Process Changes for this Event?

When you tap the Process My Changes button in the mobile app, it sends your updates forward to DairyComp 305 (WiFi or data connection required).

When DairyComp 305 receives the updates, it completes the following actions for each animal in the event:

  • Updates the animal's record with a DNB event.
  • Records the EDAYClosed Event day as the date the DNB event was completed in the mobile app.

See Processing Your Changes for more information on how the mobile app, the PULSE Platform, and DairyComp 305 work together to process your changes.

Back to top

Need Help Adding Animals to this Event?

See the following topics:

Back to top

< Return to Event Entry OVERVIEW