Tips for Entering Events

The PULSE Platform currently supports the following events:

• Custom Events (with and without protocols)
• Embryo Transfer Event (Platform Event, EC 3000)
• EC 1 - FRESH Event
• EC 2 - OK Event
• EC 3 - RECHK (Recheck) Event
• EC 4 - HEAT Event
• EC 5 - BRED Event
• EC 6 - PREG (Pregnant) Event
• EC 7 - OPEN Event
• EC 8 - PREV (Previous) Event
• EC 9 - MOVE Event
• EC 11 - DRY Event
• EC 12 - ABORT Event
• EC 13 - Do Not Breed (DNB) Event
• EC 14 - SOLD Event
• EC 15 - DIED Event
• EC 16 - CHECK Event
• EC 17 - CALFVAC Event
• EC 18 - XID (Change ID) Event

The PULSE Platform does not yet support the following events. They are in development toward a future release:

• EC 10 - BULLPEN

1. To create a new event or edit an existing one, sign in to the VAS PULSE Platform mobile app, and tap the Events button.

   As shown in the image below #2, all available events are listed in the Events home page, with the corresponding DC305 command that is used to create them.

   I don't see the Events button. How do I find it?

   If you do not see the Events button at the bottom of your screen, tap the Back arrow at the top left of the page until you return to one of the main feature screens. From there, you'll find the feature buttons at the bottom of the screen:

   

2. Tap on any event to begin working with it.

   If you already added animals to the event but have not yet completed and/or processed them, they will still be displayed when you open the event.

   

3. If you are using a scanner, you can simply scan an animal to add it to the event. Android devices can use the scanner switch at the top right to connect to a paired scanner (see example below). iOS devices automatically connect to paired scanners. See Manage Mobile App Data for help working with scanners.

   Android devices can use the scanner switch at the top right to connect to a paired scanner (see example below). iOS devices automatically connect to paired scanners. See Manage Mobile App Data for help working with scanners

4. If you are not using a scanner, you can tap the button to search for animals to add:

   

   When you add the first animal to a new event, all details except for the animal's ID number are grayed‑out (unassigned), as shown in the example below. If you leave the other details unassigned, they will continue to be grayed‑out as you add more animals. All required fields are marked with the * (asterisk) symbol: 

   

   NOTE: For illustration purposes, the example above shows the Bred event; however, the specific details will vary depending on each event. In addition to required items, events may include fields for standard non-required items (such as the Technician Tech is short for Technician. field), as well as any custom items.
5. If you are using a scanner, you can simply scan an animal to add it to the event.

   Android devices can use the scanner switch at the top right to connect to a paired scanner. iOS devices automatically connect to paired scanners. See Work with RFID Scanners for more information.

6. If you want to leave the details for all animals undefined, you can continue adding more to the list and then define their details later when you are ready to process them. However, if you plan to use any of the same details for multiple animals in this event, we recommend that you go ahead and assign them for the first animal you add so that the app can automatically assign the same details to the rest of the animals you add to the event. See Save Time when Adding Animals in Bulk for more information.
7. When you finish adding animals to the event and have defined all of the required details in the fields marked with the * symbol, tap the Process My Changes button to send your updates back to DC305. See Processing Your Changes for more information.

   

Each time you add an animal to an event, it is automatically assigned the current date in the Event Date field. However, you can change the dates that animals were added to events. This offers you additional flexibility on those days when you're unable to finish processing all animal events, or if an event was missed and needs to be added at a later point.

When changing event dates, keep the following in mind:

• 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.

To change an animal's event date:

1. Tap the Event Date field for the animal.
2. In the screen that appears, scroll through the days, months, and years to select the date you want, then tap Done:

   

   Once you've selected the new date, the Event Date field changes to yellow if the date is prior to the current date:

   

   At this point you can process the animal, change the event date to the current date, or change the event date to a different date in the past.

Regarding the Event Date field, keep the following in mind:

• The field is always grayed-out when it contains the current date.
• Even if you add the animal on the current date, the field will display in yellow on the next day because it no longer contains the current date.
• Changing a past date back to the current date reverts the field from displaying in yellow to once again displaying as grayed-out.

When you add the first animal to a new event, all details except for the animal's ID number are grayed‑out (unassigned), as shown in the example below. If you leave the other details unassigned, they will continue to be grayed‑out as you add more animals. All required fields are marked with the * (asterisk) symbol: 

Once you define details for the current animal, the app automatically reuses them for the next animals you add, which makes it much quicker to add animals in bulk. Note that the last details you selected are the ones that the app will use for the next animals you add. So if you need to define different details for a set of animals in the event (for instance, maybe in a Bred event, you need to define different breeding codes for several animals), simply change the details for the first animal in that set and then continue adding the rest of the animals that use that same breeding code.

If you need to change any details for a specific animal, simply tap the field and choose a different option.

If you need to remove an animal from an event, swipe left on it until you see the red Remove option:

The app prompts you to confirm before removing the animal.

Before you can process an animal in an event, all required details (marked with an asterisk) must be defined.

The examples below illustrate how the app labels animals that are complete (meaning all required details are defined) or incomplete (meaning you still need to define one or more required details before you can process the changes).

As you add animals to an event, the app numbers them in the order they were added. As shown in the examples below, each number is displayed with either a gray or a blue background:

• Numbers in a GRAY bar indicate that some required details are missing for that animal.
• Numbers in a BLUE bar indicate that all required details are complete for that animal, and it can be processed.

As you add animals to a VAS PULSE Platform event, the mobile app checks whether each animal is eligible to add to that specific event. So based on the type of event you are working with, you may receive system prompts that warn you about an animal's status or its details before adding them to the event.

For example, let's consider a Bred event...

When you add an animal to a Bred event, the app is designed specifically to add females. It will not allow you to add a male animal to the event:

Likewise, because the app expects you to add females that are eligible to breed, it will display a warning before allowing you to add a female that is dry, already pregnant, younger than the minimum breeding age, recently freshened, or flagged as "do not breed" (see example below). The app will not restrict you from adding these animals; it simply warns you of their status so that you can determine whether to continue:

The event descriptions beneath Event Entry in this online help define the checks that are in place for each event.

Before you can process an animal in an event, all required details (marked with an asterisk) must be defined.

As soon as you define the required details for at least one animal on the list, the Process My Changes button will become active (i.e., change from gray to green). As shown in the example here, the Process My Changes button also indicates how many animals are complete and ready to be processed.

Here's how your changes move forward after you tap the Process My Changes button in the mobile app:

1. The mobile app sends the updates to on‑premise DairyComp 305 (WiFi or data connection required).
2. DairyComp 305 processes the event and updates all animal records.
3. Once all animal details are updated on‑premise, they are then synchronized back out to the PULSE Platform during the next scheduled data sync.
4. When the synchronization is complete, you can then see the updates within your Platform and mobile CowCards.

The VAS PULSE Platform mobile app supports all events listed under Events Currently Supported by the PULSE Platform. See the guidelines below when locating an event. If you are still not able to find a supported event in the mobile app, please contact VAS PULSE Platform Support to make sure that the DairyComp 305 event command is formatted properly and is being received by the PULSE Platform.

As shown in this example, all available events are listed in order by their Event Code (EC) on the Events page in the mobile app: 

• Events with lower EC numbers are at the top of the list, so if you are looking for an event with a higher number, be sure to scroll down in the list to locate it.
• Event codes 1–18 are DairyComp 305 system events that perform standard operations. Each of these are defined in this online help as the PULSE Platform begins supporting them. DC305 allows you to edit the name of these events, but not the EC, so if you do not see the name of the event you are looking for, try locating it by its EC number. If you still cannot locate the event, either the mobile app does not support it, or DC305 is not programmed to send it to the mobile app. Please contact VAS PULSE Platform Support for further assistance.
• Event codes 19 and above can be used for custom events either with or without protocols. If you do not see a custom event in the mobile app, then either DC305 is not programmed to send it or it’s a custom event with protocols, which is not yet supported by the PULSE Platform. See Custom Events for more information.
• Event codes higher than 19 may also be used for events that are specific to the VAS PULSE Platform, such as the Embryo Transfer Event. These events will also be defined in this online help as they are introduced in the PULSE Platform.
• Below each event name, you can find the DC305 command that was used to create the event. The options that are available in a PULSE Platform event depend on the options defined in the DC305 command.