( The date entered i s that of the f i na l da� of t h e per i od b e i ng entered . ) Date
/ /
Tota l • i l k vo l for per i o d Av Fat Av Prote i n
____8 1 i tres
BMSCC ( 888 ) ce l l s/• l
___.11
ETURH to enter data , ESC to i gnore ,
Cow Data
This is the largest of the three data sections and is the most heavily u sed by the program in calculations. The data is based on i ndividual events with an associated date of occurrence. The events may be loosely grouped as
reproduction, health, and production in type. This allows raw data to be
used in calculations made by the program, a n d avoids prior manipulation of the data which would result in a restriction of the possible analyses. Each cow also has a signature which contains information on the cow's identification, age, breed, genetic worth and within herd phenotypic ran king.
The farmer can supply the majority of the information relating to cow details, reproductive events, animal health treatments, body weights, condition scores, drying off dates and cow fates (figure 4. 1 8).
The veterinarian can supply information on the results of reproductive and health examinations, and treatments used.
The New Zealand Dairy Board, via the Livestock Improvement Division, collects information on individual cows for its sire progeny testing scheme, the artificial insemination service and the milk recording service it
provides. lt may therefore be a source of information on cow details,
ancestry, breeding index, production index, some reproductive events and
cow fate. Also herd test results, both production figures and individual
somatic cell counts, may be obtained.
The requirement for cow data will depend on the use of the program.
If it is intended to use the management aids and to have current reports on performance then the data will need to be collected on a regular basis. Retrospective analyses at specified times of the year may be u ndertaken with batch collection and entry of data at these times.
!Apyright ICl 1987 ICuwy iJIIiW"'ity
Uctl'!Rd to Y.t. Clin. Sc1. Dltpt, lluuy Uoi..,..ity
COW EVENT H I STORY
Sort ed by Numb•r 1 2 / 1 0/87 7 0 4yr F BI 100 PI 1 00 .Spr i n g cow C u l l ad Test Em p t y 30/ 8 / 86 Ca l vad 1 '3 / 1 1 / 86 Hea l t h Vat 1 1 / 1 2/ 86 Hea l t h V a t '3 / 3 / 87 Hea l t h Vet 3/ 5/87 Dr i ed off 10 / ::i / 87 C u l l ed 8 83:5 3yr F 6 / '3 / 86 Ca l ved 24 / 1 0 / 86 Mat ad 1 6 / 1 1 / 86 Ma t ed 3 / 5 / 87 Dr i ad o f f 9 832 3yr F 1 5 / 8 / 86 C a l ved 1 '3 / 1 1 / 8 6 Hea l t h Vet 1 1 / 1 2 / 86 Mat ed 3 1 ::i / 87 Dr i ad o f f B I B I H e i fer V i s i t Repe M am Event V i s i t RepeM ... m Empty 1 02 P I H e i fer S i re S i re 1 00 P I Bu l l V i s i t Repe x • m Trea t ed S i re Re ... red ca l f i d : Anoest rus A c t i vR ov Treat ment 1 P r e g nancy t est Empt y 1 0:5 Spring cow Reared ca l f 82266 8 1 22 1 1 09 Spri n g COW So l d Anoest rus Cyc l ad •:.v Prost ag 1 ar•d i ns 82263 Dry i d : Dry
Figure 4 . 1 8 Cow events history - reports screen.
3 '3 C2, U N , F 1 0 , I C I OR i rosert �td
Non Ret urn
46
Tech n i c i an FGGM Tech n i c i an FGGM
Non Ret urn
C 3 , UN, F l O , CL 1 0 4 m l s g l ar•d i n-N Tech n i c i an DWBL
DATA SOURCE AND COli..ECllON METHODS
The method of data collection will depend largely on the source of the data
being collected. In summary the major sources of data are listed as
follows:
Farmer
Veterinarian Farm advisor
New Zealand Dairy Board
Dairy Factory
The location of the computer will also have a large influence on the collection methods adopted.
Farmer
Most of the data comes from the farmer and the successful adoption of a data collection system is rudimentary to the success of the entire system.
The ideal system would have the data recorded once, at the time of
occurrence. The service organizations would each use this information for
their own objectives. However until the technology is developed which
allows this to occur, com promises will have to be made.
The majority of New Zealand dairy farmers already have some form of record-keeping system. The most common is a field diary into which events are entered as they occur. The diary is carried at all times and serves as a ready sou rce of information in the field. The transfer of information from the diary into another more permanent recording system is commonly done later, at the milking shed or office. This system has stood the test of time and field use, and works well especially in large herds where more than one field diary may be in use supplying the permanent records. In the initial stages of the introduction to the program it is important not to alter existing successful data collection systems.
If the computer is located on the farm a step in the collection process m ay be missed out, namely transcription of the field diary into a formal
records system. The data is entered directly into the program from the
field diary.
If the computer is not located on the farm the data has to be
collected and transferred to the bureau or veterinarian's office. The data
from the farmer may be collected in a variety of ways: field dairies, shed sheets, wall charts, mating wheels or formal diary systems. The last is the m ost reliable and tends to promote an even flow of data into the program.
A formal diary has been designed to collect farm data, cow and herd events for the project. Events are written into the diary and a copy sent
to the computer office at predetermined intervals. The self-carboning paper allows the farmer to keep the bottom of the duplicate sheets for his own records (figure 4. 1 9). So that each event is recorded only once the formal
diary would have to replace the existing recording systems. U ntil the
various service organizations can interchange information this is unlikely to happen, and what has tended to happen is that both recording systems are run concurrently.
The information is hand delivered, posted or phoned into the computer
centre to be entered i nto the program. The flow of data is also very
seasonal, with the peak of data entry occurring in the spring and early summer periods.
Hand delivery has proved to be the favoured method of data collection ; this has developed because the busiest periods for data collection and veterinary activity coincide.
Although the formal diary increases data accuracy and keeps the program up to date it is not an essential requirement for the program to be used effectively. Data may be collected using existing recording systems at intervals throughout the year.
Farmers who have their own computers and keep the i nformation up to-date remove the burden of data e ntry from the veterinarian and his
staff. The farmer may simply hand-deliver the data disk to the
veterinarian, who can then analyze performance on his own computer. This has proven to be successful in the field.
Veterinarian
The information collected by the veterinarian can be loosely grouped into two types:
DAIRYMAN EVENT DIARY
COW EVENT RECORDS NAME/CODE: . � .
.,..,r-:--,.�
. . . ?.O 'L REPRODUCTIONDATE CALVINGS HEATS (HNS) MATINGS (SIRE CODE)
Cow No. SexJFate Call ID Comments Cow No Sue Teen Cooe
2"2� et> ( \ I f .... 'b"d.. \ (.,(? �FA. HEAL THIEVENTS
Date Cow No
I
FN Event - F•nd,ngs I T tea:ment -CommentS I RV ror :1",�-T cl ... �t-...
i
I
I J 'b l"i'f --out on the farm.
2. Results from laboratory investigative work, on samples collected by the veterinarian in the course of on-farm i nvestigations.
As the examinations are performed the results are generally recorded by the
herd manager on to a prepared form. The results can then be entered
directly from these forms into the computer, whether the computer is on the farm or in the veterinarian's office. This differs from the collection of laboratory results; these come directly to the veterinarian's office from the laboratory. If the computer is located in the office the resu lts can be entered immediately, but if the computer is on the farm the results have to be sent to the farmer for entry.
satisfactory method of data entry.
New Zealand Board
The latter has not proven to be a
The New Zealand Dairy Board uses i nformation which contains a lot of the same items required by DairyMAN. The data is collected manually for the most part, but the Livestock Improvement Division of the New Zealand Dairy Board has an automatic data collection facility for milk recording. Currently no data collection links exist between DairyMAN and the New Zealand Dairy Board; each system has distinct objectives although some overlap does occur. At present data derived from the New Zealand Dairy
Board may be re-entered manually i nto DairyMAN if desired. This has
occurred only to a limited degree, because the time taken to re-enter this data is prohibitive.
useful, and is quickly and easily entered into the program. The shed sheets may be entered in batch format at the end of the season or regularly entered during the season. The mailing of copies of the production sheets by the factory directly to the computer bureau makes the task even easier.
Farm Advisor
Information from the farm advisor such as soil and pasture analyses and financial reports may be collected as required and entered in batch lots. This information is not necessary for day-to-day management and is used for medium to long term decisions.
DATA ENTRY
The users of the program (farmers, advisors, and veterinarians) will have had varying levels of experience with computers. If the program is to gain acceptance it is essential that the use of the program be as simple, as accurate, and as "friendly" as possible. Because of time constraints in any busy enterprise, the time required to enter the data and to run the program must be kept at a realistic l evel, or the acceptance of the program will be restricted to the enthusiasts.
Menu
The program is structured such that the requirement for prior computing skills is minimal. DairyMAN is designed around a system of menu choices which allow the user to m ove to the required area of the program (figure
4.20). Prompts are displayed on the screen to aid the user in these
choices. To move to the desired area single letter choices are made from the screen. The data i nput section of the program is divided into three broad categories relating to the type of data being entered; Farm data,
Herd data and Cow data (figure 4.2 1 ).
of Events
No coding of events is required at data collection and, because of the data
input system, only minimal coding is required at data entry. There are
separate i nput screens for each of the major types of cow events. Because of this the coding required is reduced since the program knows which screen is being used. When entering health events the health codes used to
describe the event are abbreviated alpha codes. These codes resemble
closely the full code form, so they are easy to remember and hence simplify the data entry procedure. The codes are chosen from a list of 200 possible codes shown in Appendices I to VI.
of Event Detail
The structure of the system is such that compulsory data is mini mal. This was done intentionally for the author foresees a major use of the program in the solving problems of a reproductive or health nature. For example the problem may be one of a poor non-return rate in the cows, a particular sire may be incriminated, the data required to answer this q uestion are the mating details and pregnancy test results for the herd. The mating details need only encompass the date and the sire of the matings. The system does however allow, and by its nature encourages, the collection of as complete a data set as is practicable, thus allowing a full investigation into the problem. Beginning simply and adding to the program is possible, as the addition of data at a later date presents no particular problems.
Defaults
The seasonal nature of New Zealand dairy farms dictates that each cow in the herd i s at a similar stage of lactation. Therefore the reproductive data being entered into the program is of a similar type. This allows a system
of defaults to be used to greatly enhance data entry speed. The system
operates by defaulting to the previous entry made into the files. This
reduces the number of key strokes required and drastically reduces the time required to enter the data. A 1 50 cow herd can be created and have the mating dates, sire codes and technician codes entered in about 40-50 minutes, provided the data is presented in chronological order.
Error
The keyboard operator should not need to have detailed knowledge of what data is acceptable and what is not. There has been developed a system of data validation that either rejects the data if it is too absurd or warns the operator that this is unusual but acceptable data. The system operates by comparin g the newly entered event with events currently existing in the cow's file, both before and after the added event. If it is found that the new event is not biologically consistent with the cow's history the program notifies the operator at one of two levels. The addition of an unusual but not impossible event to the record will generate a warning message. The addition of unacceptable data will generate an error message and the data,
in its c u rrent form, will not be accepted by the program. A common
example is where a recording error leads to an attempt to e nter a second calving for a cow which calved a month earlier.
A . F I LE MAHAGEMENT Se l ect Far11 Create Far�� Backup Far11 D . AHALVSI S 1 Reproduct ion B. DATA ENTJIV Fa I'll Her cl Cow E. AHALVS I S 2 De��o graph ics Hea l th Product i on
X . EX I T Da i rlj1AH
Inter cho i ce (A . . F , X J
Figure 4.20 DairyMAN m a i n menu.
FARM DATA HERD DATA
( A J Fa I'll Prof 11 e [ FJ I n i t ia l Stock
[ B J Fert i I i zer [ GJ S tock Transact i ons [ C J So i ! /Pasture [ H J Herd Hea l th
[ D J M i I k i n g equ i p . [ I J Herd LWtiCS
[ I] Econ011 ics [ JJ Herd M i l k Pro d .
l PJ Far�� Defau l ts £XJ Return
( Inter] Your Cho i ce
I
Figure 4.2 1 DairyMAN data Input menu.
C. PERFORMAHCE SUMM