Feedlot computer network installation for managing feedlot operations5867820Abstract A computer network and method for feeding animals in a feedlot, in which discretion and direct control over the various suboperations of the feed ration assignment and delivery process are distributed among the individual operators in the system, while the feedlot manager is capable of indirectly monitoring the performance of the various suboperations. Claims What is claimed is: Description BACKGROUND OF INVENTION
______________________________________
VARIABLE TABLE
Variable Name
Quantity Identified
______________________________________
ID Tag number for the animal being
processed.
WT(ID,D) A doubly indexed variable rep-
resenting the weight of the
animal with identification ID
animal D-days ago (current
weight residing in D(ID,O)).
WD(ID) The weight trend for the animal ID
showing whether he is currently losing
or gaining weight and at what rate.
TP(ID,D) A doubly indexed variable rep-
resenting the temperature of
the animal ID D-days ago (cur-
rent temperature residing in
TP(ID,O)).
TD(ID) The current temperature trend of
animal ID.
R(ID) The current regimen administered to
the animal ID.
D(ID) The number of days the animal ID has
been on a regimen R(ID).
DIAG(ID) The diagnosis of the animal ID.
S(ID) The severity of the diagnosed
disease DIAG(ID).
DG(K) The ensemble of k drugs to be admin-
istered for the operative regimen
R(ID).
DS(K) The dose per 100 pounds of drug DG(K).
DS(K,ID) The dosage or the like indexed
drug DG(K) to be given animal ID.
WTH(K) The withdrawal time to purge the k
drug from an animal's system.
TMKT(ID) The scheduled time to market
for the animal ID.
______________________________________
To begin processing (FIG. 21A), for the next encountered animal, its tag number identification (ID) is read or keyed in (step 110) and compared with the identification variable, ID for all stored animal records in RAM 1104. If a file already exists ("YES" branch from test 112), processing proceeds to step 116. If no record is found for the animal one is established with all data fields cleared (step 115). The currently measured weight (WT(ID,0)); measured temperature (TP(ID,0)); diagnosed disease (DIAG(ID)) and observed disease severity (S(ID)) are then entered (step 116)--all indexed for the subject animal ID. The system next calculates several factors meaningful to determine a suitable treatment for the animal. In functional block 118, the current weight measurement (WT(ID,0)) is combined with one or more past readings (WT(ID,1)) . . . (WT(ID,N)) to determine the direction (polarity) and amplitude of the animal's weight trend (WD(ID)). The weight trend (WD(ID)) may most simply be done on a day-to-day basis, employing WD(ID=WT(ID,0)-WT(ID,1); Equation 1. or by employing any well known regression algorithm over a longer period but which emphasizes current data. Functional block 123 similarly determines the animal's temperature trend TD(ID). Test 125 next examines the animal's weight and temperature trends WD(ID) and TD(ID), its day-on-regimen count D(ID) and its specific regimen R(ID) to determine if the current treatment program should be changed. A change would be in order ("YES" test 125 branch) for example for a large weight loss trend (above threshold negative WD(ID)) or high temperature increase (large positive TD(ID)) indicating an animal in serious trouble needing an immediate, more stringent remedy. A change is also indicated for a high day-on-regimen (D(ID)) value absent favor-able trending (WD(ID)) and/or (TD(ID)) values, indicating that the current regimen R(ID) is of no further help. Conversely, favorable weight/temperature trends with lower day-on-regimen counts indicate that the current regimen is effective and therefore need not be changed ("NO" branch of test 125). The test 125 (and regimen updating) changing step 130 may be affected, for example, by storing regimen codes in the regimen change memory 1107 which is addressed (accessed) by rounded integer values of weight change divided (normalized) by weight increments, e.g., INT-(WD(ID)/15) for 115 pound increments; similarly rounded integer values for the temperature trend, and the day-on-regimen variable D(ID). Severity S(ID) may also be used in place of or to supplement the truncated, normalized weight and temperature trend variables to signify animal condition improvement or the lack of it. Alternatively, the regimen changing test 112 and imple-ment-ation 130 may be effected under software control, by such as 100IF-(WD(ID)/15)>1OR(TD(ID) >1GOTO200 Equation 2. 105IF D>3GOTO200 Equation 3. 200R(ID)=R(ID)+1 Equation 4. Test instruction 100 increases the regimen level responsive to an above-acceptable weight decrease -(WD(ID)/15)>1 (i.e., more than 15 pounds during the one day period, or sharp (as 1.degree. F.) temperature increases TD(ID)>1 by program transfer to instruction 200. Similarly, an instruction like equation 4 unconditionally increases the regimen level after three days although the test criteria can include coincidence logic such as D>3AND-WT(ID)>5. When a new regimen is appropriate ("YES" test 125 branch), the new regimen identification is extracted from memory or computed as above described and loaded into R(ID) (step 130). The day-on-regimen counter D(ID) is cleared to "0" (step 132). If no change in regimen is signalled by the regimen change storage table or date processing, the existent regimen is continued for one further day and thus the day counter variable D(ID) is updated (step 128) as by D(ID)=D(ID)+1 Equation 5. Step 40 next retrieves the regimen, i.e., the array and amount of drugs to be administered--per 100 animal pounds where the dose varies. This is effected by accessing the regimen tables stored in the memory 1109 using as memory accessing (selection) variables the diagnosed condition DIAG(ID), severity S(ID) regimen R(ID) and days-on-regimen D(ID). Integer, normalized values for weight and/or temperature trends may also be employed as memory access/address variables for a more precisely varied regimen selection. For example, an animal suffering a respiratory ailment of medium severity may be given the following intermediate regimen; R(ID): Day 0(D(ID)=0): a. 5 cc Aqueous Pen G./100 lbs. (IM) b. 2 cc IBR (MLV) c. 4 cc Vitamin C/100 lbs. (SQ) Day 1: a. 5 cc Aqueous Pen G./100 lbs. IM Day 2: a. 5 cc Aqueous Pen G./100 lbs. IM b. If acceptable response, administer 1 Albon SR bolus/200 lbs. Withdrawal for this regimen is 30 days. Alternatively, if after the intermediate regimen no noticeable improvement is logged, the logic will retrieve a higher order regimen: Day 0 (D(ID)=0): a. 4 cc Gallimycin/100 lbs. (IM) b. 2 cc IBR (MLV) C. 4 cc Vitamin C/100 lbs. (SQ) Day 1: a. 4 cc Gallimycin/100 lbs. IM Day 2: a. 4 cc Gallimycin/100 lbs. IM b. If acceptable response, administer 1 Albon SR bolus/200 lbs. Withdrawal for this regimen is 30 days. The dose DS(K,ID) for each of the medication(s) DG(K) to be administered to animal ID is then determined by multiplying the dose per unit weight (e.g., 100 pounds) DS(K) by the animal's weight WT(ID) and rounding to the nearest measure (e.g. to the nearest 5 cc or half bolis), as by DS(K,ID)=INT(DS(K)*WT(ID)). Equation 6 Test 143 determines if the withdrawal period for any drug WTH(K) equals or exceeds the scheduled time to market TMKT(ID) for the animal. If so, i.e. if WH(K)>, TMKT(ID), an alert is presented at display 1110 (step 144). In either event, the regimen with doses proper for the subject animal is displayed (step 145) and also printed (at printer 1115 of FIG. 20) if desired. The user will usually accept the displayed treatment regimen ("NO" branch of test 152). However, the attendant may intervene by entering an override code at test 152 ("YES" branch mandated) and enter the drug code(s) of drugs to be administered (step 154). This may occur, for example, if a displayed alert (steps 144, 145) is to be honored, thus avoiding a delay in marketing the animal (the time WTH(K)>TMKT(ID)) by avoiding nonessential antibiotics or the like for an animal which is seemingly recovering. Program flow returns to step 142 for dose amount computing when an override is in force, and to confirm that withdrawal period alerts are not necessary steps 143 and 144). The override treatment is then displayed (145). At this point, the user may opt to not institute the treatment ("NO" branch of test 160 returning program flow to the start position to examine the next animal). More typically, however, the diagnostician will elect to proceed ("YES" branching from test 160). When this occurs, step 162 decrements the inventory records for each drug administered to the animal, as by subtracting the administered amount DS(K,ID) from the inven-tory amount INV(K) as by INV(K)=INV(K)-DS(K,ID). Equation 7. Finally, a record of the treatment administered to the animal is put in his treatment record in RAM storage 1104, or more permanent storage means and processing for the animal ID terminates (END step 164). The microprocessor 1100 may be diverted to other tasks for the animal hospital application or, alternatively, may return to the start node to input the tag number of the next animal to be processed As illustrated in FIG. 2F, feedlot nutrition computer system 20 of the preferred embodiment comprises a number of subcomponents, namely: program memory (e.g. ROM) 111 for storing computer programs; data (file) storage memory 112 (e.g. RAM) for storing various data files; a central processing unit (e.g. microprocessor) 113 for processing the data elements contained in these data files; a data entry device, such as a keyboard or key pad 114 and associated interface circuitry 115; and visual display device such as a LCD panel 116, and associated driver circuitry 117. As shown, all of these system subcomponents are interfaced with system bus 118. In order that data files can be transmitted from and received by the computer system, a pair of data communication ports 19 and 20 are operably associated with microprocessor 113 by way of system bus 118. Data communication port 119 includes a multi-pin jack for physically interfacing the feedlot nutrition computer system with other computer systems within the computer network. Telecommunications port 120 comprises a data communication controller 121, modem 122, an N-channel RF transceiver 123 and an antenna 124, serially configured as shown. In this way, the feedlot nutritionist can transmit or receive data files over the N RF channels within the feedlot computer network. Preferably, feedlot nutrition computer system 20 described above is realized by a portable (e.g. laptop on palmtop) computer system commercially available from one of many possible vendors. In this way, the system can be easily moved into and out of the feedlot nutritionist's vehicle 131, as desired or required. In the illustrative embodiment, the portable feedlot nutrition computer runs a computer program having a number of different routines which carry out various data processing and transfer operations relating to the diet and nutrition of the cattle in the feedlot. With the above-described computer network installed in an animal feedlot, each computer system therein is capable of transmitting or receiving various types of data files during the progression of the feed ration assignment and delivery process of the present invention. As will be described below, the feedlot management computer system initiates this process on a daily basis, and at particular stages of the process engages the feedbunk reading, feedmill and feed delivery vehicle computer systems to commence particular subprocesses, which typically are "user-interactive" in nature. At particular stages of the feed ration assignment and delivery process, each of these computer systems will typically wait to receive particular data files before advancing the feed ration assignment and delivery process. As such, a particular degree of coordination among the individual computer systems in the network is required, as will become apparent hereinafter. Prior to describing the feed ration assignment and delivery process of the present invention, it is appropriate at this juncture to first describe the structure and function of each data file utilized within the feedlot computer network of the present invention. As schematically illustrated in FIG. 3, the Pen Master File comprises an organization of data fields associated with each pen in the feedlot. This data file is created within the feedlot management computer system and originally is transferred to the feedbunk reading computer system, the feedlot veterinary computer system, the feedlot nutrition computer system and the financial accounting/billing computer system at the beginning of each new day. During the course of each day, the Pen Master File is maintained (i.e. updated) using data contained in a number of other files which will be described hereinafter. Preferably, this updating process is performed on an on-line basis. The primary function of the Pen Master File is to store all of the current information for each pen of cattle in the feedlot. While other data fields will typically be present for each pen in this file, the Pen Master File of the illustrative embodiment contains only those data fields (and thus the data elements contained therein) which are important to the understanding of the various aspects of the present invention. As illustrated in FIG. 3, each pen within the feedlot is assigned a unique pen identification number (e.g. a numerical code) which is stored in a pen number field along column 2 of the Pen Master File shown. Within the feedlot, each pen is assigned a pen sequence number which typically is assigned on the basis of the physical location of each pen in the feedlot. These pen sequence numbers are stored in the pen sequence number field along column 1 of the Pen Master File and indicates the general order that the pens are "read" and fed. The total number of cattle deaths that occur each day in each pen are recorded in the cattle death count fields arranged in column 3 of the Pen Master File. The physical length of the feedbunk associated with each pen is stored in the pen length field along column 4 of the Pen Master File. In many of the larger feedlots, the feedlot is divided into a number of feedlot zones to simplify managerial functions. In such feedlots, each pen will be assigned a feedlot zone number which is stored in the feedlot zone field in column 5. In order to identify the owner of a group or groups of cattle contained in each pen, one or more lot numbers are assigned to each animal pen. The lot numbers of the heads of cattle in a particular pen are stored in the lot number field in column 6 of the Pen Master File. The actual number of living animals in a particular pen is indicated by the head count (i.e. number) stored in the head count field in column 7. The sex of the animals in each pen is indicated by a sex designation (e.g. alphanumeric code M or F) stored in the sex field in column 8 of the Pen Master File. The date that the group(s) of cattle were brought into the feedlot is recorded in the In-date field in column 9 of the Pen Master File. This date is typically used to calculate the number of days that the animals will be fed a particular type of feed ration. The average weight of the cattle (in a particular pen) when they are brought into the feedlot is recorded in the In-weight field in column 10. Typically, the average in-weight is used by feedlot management computer system to compute the current projected weight using a cattle weight growth simulation model well known in the art. The current ration type being fed to the animals in each pen is indicated by the ration code assigned to the cattle and recorded in the current ration type field in column 11. The number of days that the animals have been assigned the above ration is indicated by the number recorded in the days on ration field in column 12. In instances where a supplemental ration is fed to the cattle in particular pens, a supplemental ration code, indicating the assigned supplemental ration, will be recorded in the supplemental ration field in column 13. The number of days that the animals have been fed the supplemental ration is indicated by the number recorded in the days on supplemental ration field in column 14 of the Pen Master File. When the feedbunk reader visually inspects (i.e. "reads") the feedbunk of each pen in accordance with the pen sequence numbers in column 1 of the Pen Master file, he will be able to determine (i) how much of the delivered feed ration has been eaten from the feedbunk, (ii) the condition (e.g. health and weight of the animals herein) and, (iii) the condition of the pen itself (i.e. clean or requiring cleaning). During this feedbunk reading process, the feedlot manager assigns each pen a particular feeding priority index or code, which determines where each pen will reside within a prioritized feeding route produced from data contained in the Master Pen File after the feedbunk reader has completed the reading of all feedbunks in the feedlot. Typically, the feeding priority code will have a range from 0 to 4, 0 indicating the greatest feeding priority and 4 the lowest feeding priority. Using this coding scheme, each pen may be moved out of the standard pen sequence order according to the feeding priority code which has been assigned to it during the feedbunk reading process. The feeding priority code for each pen during the first feeding cycle is recorded in the feeding priority field in column 16A of the Master Pen File. The animals within each pen of the feedlot will be assigned a particular type of feed and total ration amount to be consumed on a particular day of the feeding program. The type and amount of feed ration assigned to each pen on a given day will be computed using (i) cattle weight growth simulation model, (typically selected on the advice of the feedlot nutritionist) and (ii) the feed ration consumption history of the animals in the feedlot. This animal weight growth simulation model is preferably incorporated into a Feed Ration Assignment Computation Routine which is executed within the feedbunk reading computer system in order to compute total feed ration assignments at the beginning of each new day. The total amount of feed ration assigned to each pen is automatically recorded in total daily ration assignment field in column 15 of the Pen Master file. However, depending upon the data collected during the feedbunk reading process, the feedbunk reader may decide to adjust this originally assigned total feed ration amount for each particular pen. Depending on the feedbunk reader and his style of feedbunk management, this adjusted or unadjusted total amount of feed ration may be delivered to the animals in the pen over one, two, three, four or more physically distinct feeding cycles. In the feedlot of the illustrative embodiment, three physical feeding cycles are utilized to deliver the total amount of feed ration assigned to the animals of each pen. The type of ration delivered may be the same or different during each feeding cycle, and this is indicated by recording the ration code in columns 17A, 17B and 17C, respectively, for the first, second and third feeding cycles. The feeding priority codes for the first, second and third feeding cycles are recorded in columns 16A, 16B and 16C, respectively. The partial amount of feed ration assigned for delivery during each of the three feeding cycles depends on the split percentages utilized by the feedbunk reader for each of the feeding cycles (e.g. 0.33, 0.33 and 0.33). As shown, the partial feed ration assignment are recorded in columns 18A, 18B and 18C, respectively, in the Pen Master File. The amounts of feed ration actually dispensed into the feedbunks during the first, second and third feeding cycles are recorded in the feed ration dispensed fields arranged in columns 19A, 19B and 19C, respectively. As will be described in greater detail hereinafter, the actual amount of feed ration dispensed into the feedbunk of each animal pen during each feeding cycle is measured by and recorded within the feed delivery vehicle computer system aboard the feed deliver vehicle assigned to deliver feed to the pens. Each feed delivery vehicle computer system stores this data within an associated feed ration dispensed field in its Feed Ration Dispensed File (FIG. 10). At the completion of each feeding cycle, these Feed Ration Dispensed Files are transmitted from each feed delivery vehicle computer system to the feedbunk reading computer system. The feed ration dispensed data from the feed ration dispensed fields of each Feed Ration Dispensed File received at the feedbunk reading computer system, is then copied into corresponding feed ration dispensed fields in the Pen Master File in the feedbunk reading computer system. Preferably, thereafter, the Pen Master File in the feedlot management computer system is updated by data transmitted thereto by the feedbunk reading computer system. As will be described in greater detail hereinafter, the feed ration dispensed data of a particular pen, which has been collected during the first feeding cycle, is preferably used to adjust the partial amount of feed ration assigned to that pen during the second and perhaps third feeding cycles, thus providing a feedback mechanism within the feed ration assignment process. As schematically illustrated in FIG. 4, the Ration Master File comprises a number of data fields associated with each type of feed that can be assigned to the pens, prepared at the feedmill, and then delivered to the feedbunks. This file is created and maintained in the feedlot management computer system and can be updated as required by the feedlot nutritionist. At the beginning of each new day a copy of the Ration Master File is transmitted to the feedmill computer system and the feedbunk reading computer system for storage and subsequent use. As illustrated, the Ration Master File has a feed ration type field for each animal pen, and contains a feed ration code which identifies each type of available feed ration. These fields are arranged along column 1 of the Ration Master File, as shown. In typical applications, it will be desired to treat a set of feed ration types as belonging to a particular group for purposes of feed ration assignment calculations. In such applications, a ration group identification code, assigned to a particular group of feed ration types, is written into the feed ration group field arranged in column 2 of the Ration Master File. When a supplemental ration is to supplied with a particular type of feed ration, either a "yes" or a "no" indicator is written into the supplemental ration indicator field arranged in column 3. As illustrated in FIG. 4, the type of ingredients and relative amounts thereof (per pound) comprising each feed ration are recorded in the ration ingredients field associated with each feed ration, arranged along column 5 of the Ration Master File. The dry matter content percent of each feed ration is recorded in the dry matter content percent field, arranged along column 5. If an alternative feed ration has been assigned for any particular feed ration, the ration type code for this alternative feed ration is recorded in the alternative feed ration field, arranged along column 6. The percentage values which indicate how a total amount of assigned feed ration is to be delivered over the first, second and third feeding cycles of a given day, are recorded in split percentage fields for the first, second, and third feeding cycles, arranged along columns 7, 8 and 9 of the Ration Master File. As will be described in greater detail hereinafter, this split percentage data is used by the feedlot management computer system (during the feed ration computation process) to compute the partial amounts of feed ration to be delivered to each pen during the first, second and third delivery cycles in the feedlot of the illustrative embodiment. In FIG. 5, the Feed Ration Consumption History File is schematically illustrated as comprising a number of data fields associated with each pen in the feedlot. The fields of this file contain detailed data relating to the feeding history of each pen in the feedlot for a specified period of time (e.g., to 180 days) controllable by the feedbunk reader. As will be described in greater detail hereinafter, the Feed Ration Consumption History File is originally created and maintained in the feedlot management computer system using data copied from the main data fields of the Pen Master File at the beginning of each new day. Thereafter, a copy of this file is transmitted to the feedbunk reading computer system and the feedlot veterinary computer system for storage and subsequent use. From time to time, single cattle and groups of cattle will be typically moved from one pen to another. In order to indicate which pens have been involved in cattle movement operations, during the time history of this file, a cattle movement indicator field is associated with each pen, shown arranged along column 1 of the Feed Ration Consumption History File, as shown. Arranged along columns 2 through 7, are the pen number field, the head count field, the lot number field, the sex field, the in-date field and the in-weight field, each of which have described above. For each past day of feeding (e.g. yesterday (Day No. 1), the data associated with the ration type field, the feed ration assignment field and the feed ration dispensed field can be read from columns 8, 9 and 10, respectively, in the Feed Ration Consumption History File. In FIG. 6A, a schematic representation of the Feed Delivery Driver Vehicle Master File is shown. The file is created and maintained daily in the feedlot management computer system, while a copy of the file is transmitted to the feedmill computer system at the beginning of each new day. As illustrated, this file comprises two primary types of data fields, namely; feed delivery vehicle driver name fields arranged in column 1 for recording the name, address and telephone number of each authorized driver in the feedlot; and feed delivery vehicle driver number fields arranged in column 2 for recording a identification number assigned to each such driver. In FIG. 6B, a schematic representation of the Feed Delivery Vehicle Master File is shown. This file is also created and maintained daily in the feedlot management computer system and is transmitted to the feedmill computer system at the beginning of each new day. As illustrated, this file comprises three primary types of data fields, namely; feed delivery vehicle number fields arranged in column 1 for recording identification number assigned to each feed delivery vehicle in the feedlots; feed delivery vehicle description fields arranged in column 2 for recording a description of each such vehicle; and feed delivery vehicle load capacity fields arranged in column 3 for recording the maximum load capacity of each feed delivery vehicle. In FIG. 7, a schematic representation of the Telecommunication Channel Master File is shown. This file is created and maintained within the feedlot management computer system and is then transmitted to each of computer system in the feedlot computer network. As illustrated, this file comprises two primary types of fields, namely: computer system identification number fields arranged in column 1 and assigned channel frequency fields arranged along column 2. The function of the computer system identification number field is to record the channel number assigned to each computer system in the network, whereas the function of the assigned channel frequency field is to record the number of the channel frequency assigned to each computer system. By displaying this file, each computer system in the network can readily determine the channel frequency over which each computer system can receive data files. As schematically illustrated in FIG. 8, the Feed Ration Delivery File for the first feeding cycle comprises a number of data fields selected from the updated copy of the Pen Master File in the feedbunk reading computer system. All of the data contained within these fields is present in the corresponding fields contained within the updated Pen Master File. This Feed Ration Delivery File is created in feedbunk reading computer system prior to commencing the first feeding cycle, and contains information regarding the feed ration assignments to be delivered to all the pens within the feedlot during the first feeding cycle. Arranged along columns 1 through 12 of the Feed Ration Delivery File, on a pen basis, the following previously described fields: the zone number field, the pen sequence number field, the pen number field, the head count field, the sex indicator field, the lot number field, the feedbunk length field, feeding priority field, the feed ration assignment field, the feed ration dispensed field and feed ration type field. Notably, data fields in each Feed Ration Delivery File are organized by the feeding priority code which is assigned to each pen by the feedbunk reader during the feedbunk reading process. In this way, the pen numbers and the data contained in their associated fields will appear in a prioritized feeding sequence order. This prioritized feeding sequence specifies a prioritized feeding route through the feedlot, in accordance with which the assigned feed rations are to be delivered. As will be described in greater detail hereinafter, a copy of the prioritized Feed Ration Delivery File of FIG. 6 is transmitted from the feedbunk reader computer system to the feedmill computer system and each of the feed delivery vehicle computer systems within the network. Upon reception of the transmitted Feed Ration Delivery File, it is stored in the feedmill computer system and the feed delivery vehicle computer system for future display and use. In order to deliver the feed ration assignments posted in the Feed Ration Delivery File, the feedmill computer system creates a Feed Load Assignment File from the received Feed Ration Delivery File. As schematically illustrated in FIG. 9, Feed Load Assignment File for the first feeding cycle comprising a number of data fields which contain information useful to the feedmill operator, or like personnel, during the assignment (i.e. dispatching) of feed loads and pen subsequences to feed delivery vehicles available in the feedlot. As illustrated in FIG. 9, the Feed Load Assignment File for each specified feeding cycle comprises a number of data fields associated with each pen in the prioritized pen feeding sequence which, in the illustrative embodiment, extends from 1, 2, 3 . . . N. As shown, the zone number fields, the (prioritized) pen sequence number fields, the pen number fields, the head count fields and lot number fields are arranged in columns 1 through 5 of the Feed Load Assignment File, respectively. The feedmill operator enters identification codes (e.g. numbers) into the feed delivery vehicle identification fields and the feed delivery vehicle driver identification fields provided in columns 6 and 7, in order to record the identity of each feed delivery vehicle and driver which the feedmill operator assigns (i.e. dispatches) to deliver the feed ration assignments to the pens along a specified section (i.e. subsequence) of the prioritized feeding route. During the feed load assignment process at the feedmill, a primary function of the feedmill operation is to assign (i) subsequences of pens to available feed delivery vehicles, as well as (ii) amounts of feed that must be loaded onto these vehicles so that they can deliver the feed ration assignment along these pen subsequences. Thus, for each specified pen subsequence assigned to a particular feed delivery vehicle, a total feed load amount must also be assigned thereto. Ideally, this total feed load assignment should be equal the sum of the feed ration assignments for the individual pens along the specified subsequence. The details of the feed load assignment process will be described below. There may be instances when the feedmill operator may decide to assign more or less feed to a feed delivery vehicle. When assigning a feed load amount to a particular feed delivery vehicle and associated driver, the feedmill operator calls up the Feed Delivery Vehicle Master File, reads the identification number on the feed delivery vehicle parked at the feedmill, and then determines it maximum load capacity from this file. The feedmill operator then enters (i.e. records) the elicited information into the four fields of the Feed Load/Pen Subsequence Allocation File schematically illustrated in FIG. 9B. As shown in FIG. 9B, these four fields are: (1) the next unassigned pen number field; (2) the available feed delivery vehicle identification number field; (3) the driver identification field; and (4) the maximum feed delivery vehicle load capacity field. Upon completing the entry of the above data into the Feed Load/Pen Subsequence Allocation File, the identification codes for the feed delivery vehicle and driver are automatically recorded into their respective fields along the pen subsequence in the Feed Load Assignment File which begins with the pen number entered into the next unassigned pen number field and terminates with the pen number, at which the accumulated amount of feed ration assignments equals the maximum load capacity of the feed delivery vehicle. This accumulated total amount of feed will be automatically recorded in the total feed load assigned field arranged in column 10 of the Feed Load Assignment File, and represents the total feed load amount to be prepared at the feedmill for delivery to the specified subsequence. In most feedmills, the actual preparation of the total feed load assignment will typically require mixing one or more separate batches of feed ration, which are accumulated in feed ration storage bin 76 disposed at an elevation above the height of the feed delivery vehicle. The preparation of each batch of feed ration occurs under the control of the feedmill computer system, using the data recorded in (i) the total load assigned field of the Feed Load Assignment File and (ii) the feed ration mixing table (supplied by the feedlot nutrition computer) and stored in the feed load assignment computer system. After a suitable number of batches have been prepared at the feedmill, they are then loaded into the assigned feed delivery vehicle for immediate delivery at the feedmill. In order to account for the amount of feed ration actually loaded into the assigned feed delivery vehicle, scale 75 associated with the feed ration mixing bin 11, transmits signals to the feedmill computer system, which after suitable processing, are converted into a measure representative of the actual weight of the feed ration loaded into the feed delivery vehicle under the control of the feedmill computer system. This actual feed load weight measurement is automatically recorded into the total feed load field arranged in column 11 of the Feed Load Assignment File. As schematically illustrated in FIG. 9A, indicated by ration code "A" in the Feed Load Assignment File, the above process is then repeated for the remainder of the pens in the prioritized pen sequence which are to be fed feed ration from the first feed ration group. When the pens receiving feed ration from the first ration group (e.g. indicated ration code "A") have all been assigned to a dispatched feed delivery vehicle, the feedmill operator then proceeds to assign a pen subsequence to the next available feed delivery vehicle in the feedlot. This time, however, a load of feed ration from a second ration group (e.g. ration code "B") will be assigned using the above-described procedure and the visually displayed Feed Load/Pen Subsequence Allocation File shown in FIG. 9B. Typically, a number of feed load assignments will be required to deliver the feed ration assignments to all of the pens contained within the second feed ration group. When the pens associated with the second ration group have been assigned and batches of feed prepared and loaded into the assigned feed delivery vehicles, the feedmill operator then proceeds to assign pen subsequences to the next set of available feed delivery vehicles. Typically, after pen subsequences associated with each of the feed ration groups have been dispatched there will be subsequent pen subsequences associated with the feed ration groups. These subsequent pen subsequences are then assigned to feed delivery vehicles in a manner described above until all of the pens along the prioritized pen feeding route have been dispatched to a feed delivery vehicle. At the end of this process, a copy of the completed Feed Load Assignment File is transmitted from the feedmill computer system to the feedlot management computer system for performance analysis of the feed load assignment process which is to be conducted at the end of the last feeding cycle of the day. In FIG. 10, a schematic representation of the Feed Ration Dispensed File is shown for the first feeding cycle. At the beginning of each feeding cycle, each feed delivery vehicle computer system creates a Feed Ration Dispensed File utilizing data contained in the prioritized Feed Ration Delivery File received from the feedbunk reader computer system. As shown, each Feed Ration Dispensed File comprises several types of data fields; namely: pen number fields arranged in their prioritized order along column 1; the feed ration type fields arranged in column 2; feed ration assignment fields arranged in column 3; and feed ration dispensed fields arranged in column 4. In its initial state, each feed ration type field contains a feed ration code and the feed ration assignment field contains a feed ration amount assigned by the feedbunk reader. Notably, however, the actual feed ration dispensed field is initially vacant for receipt of an actual weight measurement produced by scale 52 aboard the associated feed delivery vehicle, that is, when feed is being dispensed into the feedbunk of a particular pen along the pen sequence assigned to the vehicle. In the preferred embodiment, several pen number and associated fields in the Feed Ration Dispensed File are simultaneously displayable on the LCD screen of each feed delivery vehicle computer system. During the feed ration delivery process, the driver can then record the weight of feed ration being dispensed into a selected feed ration dispensed field by simply moving the display cursor to the corresponding pen number in the Feed Ration Dispensed File. In this way, the driver is accorded some flexibility in the relative order in which he delivers feed to pens along an assigned pen sequence. It is understood, however, that other suitable ways of displaying the fields of the Feed Ration Dispensed File may be implemented. At the end of each feeding cycle, each feed delivering computer system transmits its completed Feed Ration Dispensed File to the feedbunk reading computer system and also preferably the feedlot management computer system. In FIG. 11, a schematic representation of the Cattle Movement/Death File for a particular day, is shown. Typically, this file is created in the feedbunk reading computer system on a daily basis and is updated during the day by the feedbunk reader as he collects information relating to cattle movement and death while reading the feedbunks in the feedlot. At the end of the day, this file is transmitted to the feedlot management computer. Then, the feedlot management computer system transmits the Cattle Movement/Death File to the financial accounting computer system so that daily feed ration charges are computed on the basis of the total number of living cattle of each owner. The Cattle Movement/Death File is also utilized to update the Cattle Movement History file maintained within the feedlot management computer system. As illustrated in FIG. 11, this file contains a number of data fields, namely: the cattle movement type field in which a code is recorded to indicate a regular pen movement event, or cattle death within a pen in the feedlot; the lot number field in which the lot number of the cattle being moved (or a cattle death) is recorded; the pen number field in which the number of the pen from which cattle are moved (or in which cattle death has occurred) is recorded; the lot number field in which the lot number of moved cattle is recorded; the pen number field in which the (pen) number of the pen to which the cattle were moved is recorded; and the head count field in which the number of cattle being moved (or cattle deaths) are recorded. Using the fields provided in the Cattle Movement/Death File, it is thus possible to record cattle deaths and all other types of cattle movement within the feedlot, including the receipt of new cattle. In FIG. 12, a schematic representation of the Cattle Movement History File is shown. This file is created and maintained in the feedlot management computer system and a copy of this updated file is transmitted to the feedbunk reading computer system prior to each feedbunk reading cycle. The Cattle Movement History File contains a historical account of all cattle movements made within the feedlot over a time period equal in length to the historical time period of the Feed Ration Consumption History File described hereinabove. The Cattle Movement History File is essential to accurately interpret the Feed Ration Consumption History File during the feed ration assignment process. To appreciate the importance of this file, it will be helpful to discuss briefly how feed ration assignments are typically made for the pens in the feedlot. Prior to the first reading or feeding cycle, the Feed Ration Assignment Computation Routine is run within the feedbunk reading computer system to compute the initial total amount of feed ration to be assigned to each particular pen. This computed amount is based on (i) the prior consumption history of the cattle in the pen, and (ii) a cattle weight gain model simulated within the feedbunk reading computer system. As cattle are often moved from one pen to another pen in the feedlot during the course of their stay in the feedlot, it is essential that the Feed Ration Assignment Computation Routine have access to cattle movement and death data contained within the Cattle Movement History File. In this way, when the Feed Ration Assignment Computation Routine focuses on the prior consumption history of a particular pen, it can account for the cattle movement into and out of the pen over the historical consumption period being considered, thus reaching a total feed ration assignment which is more accurately reflected by the cattle weight gain simulation model. In FIG. 13, a schematic illustration of the Feed Ration Charge File is shown. After completion of the last feeding cycle and receipt of all Feed Ration Dispensed Files are received by the feedlot management computer system from the feed delivery vehicle computer systems, the feedlot management computer system creates the feed ration charge file and then transmit it to the financial accounting computation system for accounting and billing purposes. As illustrated, all of the fields and data contained in the Feed Ration Charge File are obtained from the Pen Master File after the Pen Master File has been updated using the Feed Ration Dispensed Files received from the feed delivery vehicle computer systems in the network. The purpose of Feed Ration Charge File is to gather together all the necessary data required by the financial accounting computer system to compute the total charges incurred by each cattle owner for the amount and type of feed ration actually delivered to (i.e. fed) his cattle during a specified day. As illustrated in FIG. 13, the Feed Ration Charge File comprises a number of data fields and the data therein selected from the Pen Master File, namely: pen number fields arranged in column 1; associated lot number fields arranged in column 2; associated ration type fields arranged in column 3; and the sequence of associated feed ration dispensed fields arranged in column 4 of the Feed Ration Charge File. In column 5, the associated feed ration cost/pound fields are arranged, while the total ration cost/pen fields are arranged in column 6. Typically, the cost per pound for each type of ration will differ, and thus a different cost/pound figure will be recorded in the ration cost/pound field associated with each pen in the feedlot. Having described the overall structure and function of the feedlot computer network and the file structures utilized therein, it is appropriate at this juncture to describe the feed ration assignment and delivery of the present invention, with reference to FIGS. 14A through 14E. In FIG. 14, there is shown a high-level flow chart which illustrates the programmed operation of the feedbunk management computer system during the feed ration assignment and delivery process of the present invention. As indicated at Block A, prior to the first feedbunk reading cycle of the day, the feedlot manager utilizes the feedlot management computer system to update a number of files maintained therein. This file updating process may be carried out as follows. The feedlot management computer system uses the data contained in the Feed Ration Dispensed Files from the last feeding cycle of the previous day, to update the Feed Ration Dispensed Fields associated with the last feeding cycle in Pen Master File of that day. The feedlot management computer system then uses the data contained in the Cattle Movement/Death File from the previous day, to update the head count and lot numbers fields in the Pen Master File of that day. Thereafter, the feedlot management computer system uses the data contained in the Pen Master File to update the Feed Ration Consumption File History File. Then, any new data available to the feedlot manager is then used to update the files associated with the feed delivery vehicles and drives in the feedlot. Notably, these files will also be updated throughout the day as required and then retransmitted to the feedmill computer system for storage and use during the feed load and pen subsequences assignment process at the feedmill. From time to time, the feedlot nutritionist may decide to change or modify either the types of feed ration (and/or the ingredients contained therein) which are fed to the cattle in the feedlot. When such a decision has been made, a Feed Ration Change File is created within the feedlot nutrition computer system by the nutritionist, and is then transmitted to the feedlot management computer system over the wireless telecommunication link established between RF transceivers 123 and 94. When such a transmission arrives at the feedlot management computer system, a "file received" indication will be preferably displayed on the menu-display screen thereof to cue the feedlot manager to update the Feed Ration Master File using data contained in the received Feed Ration Change File. If for any reason there is a change in the number or channel frequency assigned to any of the computer systems in the network, the feedlot management computer system updates the data contained in the Telecommunication Channel Master File, shown in FIG. 7. Preferably the updating process occurs at the beginning of each new day, but may also occur at any time during the day as required. When all files have been updated, the feedlot management computer system then transmits a copy of the Pen Master File, the Ration Master File, the Telecommunication Channel Master File, the Feed Ration Consumption History File and the Cattle Movement History File to the feedbunk reading computer system, as indicated at Block B in FIG. 14A. Shortly thereafter, the feedlot management computer system transmits a copy of the Pen Master File, the Ration Master File, and the Feed Ration Consumption History File to the feedlot veterinary computer system, as indicated at Block C in FIG. 14. At this stage of the process, the feedbunk reading computer system becomes active. Specifically, as indicated at Block A in FIG. 14B, the feedbunk reading computer system receives and stores in memory 24, the Pen Master File, the Ration Master File, the Feed Ration Consumption History File, and the Cattle Movement History file transmitted by the feedlot management computer system over the wireless telecommunication link established between RF transceivers 35 and 95. Then, as indicated at lock B, the feedbunk reader interacts with the feedbunk reading computer system to call up the Feed Ration Assignment Computation Routine. At this stage of the process, the Feed Ration Assignment Computation Routine Accesses data from (i) the Feed Ration Consumption History File, (ii) the Cattle Movement History File, and (iii) the cattle weight gain model, in order to compute daily feed ration assignments for each pen in the feedlot. At this stage, the total number of feeding cycles to be executed during the day is stored in the feedbunk reading computer system. In general, the feedbunk reading may read the feedbunk of each pen in the feedlot once prior to the first feeding cycle, or prior to each feeding cycle. In the illustrative embodiment, it is assumed that feedbunk reading occurs before each feeding cycle. Thus, as indicated at Block C in FIG. 15A the feedbunk reader displays the fields associated with the beginning pen numbers listed in the Pen Master File, and then drives to the pen indicated by pen sequence number "1". At this pen, the feedbunk reader visually inspects the condition of (i) the associated feedbunk, (ii) the cattle in the pen, and (iii) the pen itself. On the basis of data collected during this feedbunk reading process, the feedbunk reader enters a suitable feeding priority code in the feeding priority code field associated with pen sequence No. 1. If the feedbunk reader determines that an additional amount of ration should be assigned to the pen, e.g. because the feedbunk is "licked clean", he may change the computed feed ration assignment recorded in the feed ration assignment field to a value which reflects the desired amount to be fed to the pen during the first feeding cycle. As indicated at Block D of FIG. 15A, the feedlot management computer system uses the data in the Pen Master File to create the Feed Ration Delivery File for the first feeding cycle. Then as indicated at Block E, the feedlot management computer system transmits a copy of the Feed Ration Delivery File to (i) feedmill computer system over the wireless telecommunication link established between RF transceivers 35 and 72, and (2) each of the available feed delivery vehicle computer systems over the wireless telecommunication links established between RF transceivers 35 and 50. There may, however, be instances when the feedbunk reading computer system is rendered disabled after the Feed Ration Delivery File has been transmitted to the feedmill computer system. In such cases, the feedmill computer system may transmit the Feed Ration Delivery File to each of the feed delivery vehicle computer systems over the wireless telecommunication links established between RF transceivers 72 and 50. As will become more apparent hereinafter, the telecommunication links established among the feedmill and feed delivery vehicle computer systems are useful not only in emergency situations where the feedbunk reading computer system is disabled, but also in applications where it is desired to further lessen the degree of involvement of the feedbunk reader in the feed delivery process. As indicated at Block A in FIGS. 16A and 17, the feedmill computer system and each feed delivery vehicle computer system receives the transmitted Feed Ration Delivery File for the first feeding cycle. The feedmill computer system then proceeds to carry out the feed load assignment and preparation process described hereinabove. Specifically, as indicated at Block A' in FIG. 16A, the feedmill computer system determines whether the feedbunk reading computer system is disabled or otherwise desires the feedmill computer system to transmit its received copy of the Feed Ration Delivery File, to each of the feed delivery vehicle computer systems in the computer network. This condition or request can be simply determined by the feedmill computer system reading the request/disable condition (for file retransmission) field arranged in the upper corner portion of the received Feed Ration Delivery File, as illustrated in FIG. 8. If the feedmill computer system determines such a condition or request, it then retransmits a copy of the Feed Ration Delivery File to each of the feed delivery computer systems as indicated at Block A" in FIG. 16A. As indicated at Block B in FIG. 16A, the feedmill computer system then uses the contained in the Feed Ration Delivery File for the first feeding cycle in order to create a Feed Load Assignment File for the first feeding cycle. Thereafter, at Block C, the feedmill operator sequentially assigns a subsequence of pens and a load of feed to an available feed delivery vehicle in the feedlot, and then enters the associated feed load and pen subsequence assignment data into the Feed Load Assignment File. As indicated at Blocks D and E in FIG. 16A, the feedmill computer system controls feed ingredient metering and mixing equipment 11 during feed batch preparation operations at the feedmill, and then records the actual weight of the feed batches or portions thereof loaded onto the dispatched feed delivery vehicle. If at Block F in FIG. 16B, there are unassigned pen sequences along the prioritized feeding route for the m-th feeding cycle, the feedmill computer systems returns to Block C and performs the operations in the loop defined by Block C, D, E, C, for each unassigned pen sequence. When the feed load preparation and loading process is completed for the last pen subsequence along the prioritized feeding route, the operations in the program loop defined by Blocks A, B, C, D, E, F, G, A are performed once again for the (m+1)th feeding cycle of the day. When, as indicated at Block G, the feed load, assignment, preparation and loading process is completed for the last feeding cycle (i.e. m=M), the feedmill computer system transmits the M Feed Load Assignment Files to the feedlot management computer system. As will be described in greater detail hereinafter, the data contained in the M Feed Load Assignment Files can be used by the feedlot management computer system to produce performance reports regarding feed load and pen subsequence assignment operations performed by the feedmill operator during the course of the day. At Blocks A through E of FIG. 17, the programmed operations performed by each feed delivery vehicle computer system are schematically illustrated. As indicated at Block B, upon reception of the Feed Ration Delivery File for the first feeding cycle, each feed delivery vehicle computer system uses the data contained therein to create a Feed Ration Dispensed File for the first feeding cycle. To deliver the assigned feed rations specified in this file, the driver (i) visually displays the first several pens having the highest feeding priority listed in the Feed Ration Dispensed File, (ii) drives his feed delivery vehicle adjacent the first pen listed on his assigned pen subsequence, and (iii) then reads from the displayed Feed Ration Dispensed File, the amount of feed ration which has been assigned to the pen. As the feed delivery vehicle is driven alongside the pen's feedbunk, the Uniform Feed Delivery Control Routine in the feed delivery vehicle computer system controls feed dispensing equipment 55 aboard the vehicle so as to uniformly dispense feed along the length of the feedbunk as hereinbefore described. Simultaneously, the weight of the dispensed feed ration is automatically recorded in the feed dispensed field of the Feed Ration Dispensed File being displayed on LCD panel 43. When the amount of dispensed feed approaches the assigned amount of feed ration, preferably an audible indication is sounded from the feed delivery vehicle computer system, alerting the driver to either stop dispensing feed, or deliver additional or less feed ration than assigned, based on the judgment and field experience of the driver. When the feed dispensing process is completed, the final measured amount of dispensed feed ration is recorded in the feed ration dispensed field of the Feed Ration Dispensed File. Thereafter the driver proceeds to the next pen on his assigned pen subsequence and delivers feed ration to the feedbunk thereof, following essentially the same basic steps in the above described delivery process. When each feed delivery vehicle driver completes delivering feed to his assigned subsequence of pens, he returns to the feedmill to assist in the delivery of additional feed loads which are being sequentially assigned on a vehicle availability and load capacity basis. When delivery of feed to all pens along the prioritized feeding route is completed, the Feed Ration Dispensed File in each feed delivery vehicle computer system is transmitted to the feedlot management computer system, as indicated at Block F in FIG. 17. At Block F of FIG. 15A, the feedbunk reading computer system receives the transmitted Feed Ration Dispensed Files. Then, as indicated at Block G, the feedbunk reading computer system posts (i.e. records) the feed dispensed data from the Feed Ration Dispensed Files into the corresponding feed dispensed fields in the Pen Master File. Immediately thereafter, the feedbunk reading computer system adjusts the feed ration assignments posted for each pen during the second (and perhaps third) feeding cycles. This adjustment process is carried out on the basis of the actual amount of feed ration dispensed to the pen during the previous feeding cycle. In essence, this process involves decreasing or increasing future feed ration assignments posted for each pen using the available feed ration dispensed data collected during the previous feeding cycle. In this way, the feedbunk reader can indirectly control the actual amount of feed ration delivered to each head of cattle at the end of each day, thus ensuring compliance with the feeding program. As indicated at Block H in FIG. 14B, the feedbunk reading computer system can then either return to Block D and produce the Feed Ration Delivery File for the second feeding cycle, or return to Block C where it can function in the second feedbunk reading and ration adjustment process, as hereinbefore described. In the preferred embodiment, the program loop defined by Blocks C, D, E, F, G, H, I, J are repeated up to M-1 (or 2) times, in order to carry out the steps involved at the feedbunk reading computer system during the first, second and third feeding cycles. During each traverse through the program loop, the steps recited in FIGS. 16A, 16B and 17 will be repeated by the feedmill and feed delivery vehicle computer systems during the execution of each feeding cycle. At Block I in FIG. 15B, the feedbunk reading computer system updates the Cattle Movement Death File uses the data contained in the cattle death count field in the updated Pen Master File. Then at Block J, the feedbunk reading computer system transmits both the Feed Ration Charge File and updated Cattle Movement/Death File to the feedlot management computer system. As indicated at Block G in FIG. 14, the feedlot management computer system receives the Feed Ration Dispensed File (for the (m=M)th feeding cycle) and the Cattle Movement/Death File from the feedbunk reading computer system. At Block H in FIG. 14, the feedlot management computer system uses the feed ration dispensed data and death count data from above files to create the Feed Ration Charge (or Audit) File. Thereafter at Block I, the feedlot management computer system transmits the Feed Ration Charge File and Cattle Movement/Death File to the financial accounting computer system. At Blocks A and B in FIG. 18, the financial accounting computer system receives and stores the transmitted Feed Ration Charge File and Cattle Movement/Death Files. Then at Block C in FIG. 18, the financial accounting computer system uses the feed ration dispensed data, the feed ration cost data and the cattle death count data contained in these files, respectively, in order to compute the charge incurred by each cattle owner for the feed rations fed to their cattle during the day. These charge figures are summed up for a particular time period (e.g. a week) and printed in the form of bill, bearing other data which is of assistance in helping each cattle owner determine a number of important figures, such as the feeding cost incurred per head of cattle, the number of days on a particular ration and the like. As is well known in the art, such figures are useful in computing break-even prices and margins of return. At Block J in FIG. 14, the feedlot management computer system compares, for each pen, the data in the Pen Master File in order to evaluate the performance of the drivers of the feed ration delivery vehicles during the executed feeding cycles. Preferably at this stage, the feedlot management computer system also compares, for each feed load assignment, the data contained in corresponding feed load assignment and dispensed fields in the Feed Load Assignment File in order to evaluate the performance of the feedmill operator during executed feed load assignment operations. From such data analyses, the feedlot management computer system then produces daily reports which provide a statistical measure of the deviation between the assigned (desired) feed rations and the actual feed rations dispensed to each pen in the feedlot. Also produced are statistical measures of the deviation between assigned feed loads and actually dispensed feed loads. Having described the illustrative embodiment of the present invention, several modifications come to mind. In the illustrative embodiment, a single computer system has been disclosed for running both (i) feed load assignment related routines and (ii) feed batch preparation and loading related routines. In alternative embodiments of the present inventions, individual computer systems may be installed at the feedmill for running these two distinct types of computer software without departing from the spirit of the present invention. In such embodiments, the individual computer systems at the feedmill will be suitably interfaced with each other, and also interfaceable with the other computer systems in the feedlot computer network. In the illustrative embodiment of the present invention, two distinct mechanisms have been disclosed for facilitating data communications among the computer systems in the feedlot computer network. The first data communication mechanism involves establishing a physical data communication interface among pairs of computer systems between which data files can be transferred at particular stages of the feed ration assignment and delivery process. The second data communication mechanism involves establishing an electromagnetic (e.g. RF) type data communication interface (i.e. link) among pairs of computer systems, between which data files can be transferred at particular stages of the feed ration assignment and delivery process. In an alternative embodiment, each computer system in the feedlot computer network is interfaced within a commercially established satellite telecommunication network operating in the microwave (MW) region of the electromagnetic spectrum. In such an alternative embodiment, each computer system in the network preferably includes a multichannel satellite uplink/downlink transceiver, which is used to establish wireless data communication links among any number of computer systems in the network, for purposes of transferring data files over selected channels. In the feedlot computer network of FIG. 2, separate computer systems have been disclosed for performing the above-described feedbunk reading and feedlot management functions. However, in an alternative embodiment of the present invention, the functions implemented by the feedlot management computer system and the feedbunk reading computer system may be implemented in a single portable computer system 135 carried aboard vehicle 15 of the feedbunk reader. In this alternative embodiment of the present invention, the feedbunk reader will typically perform the general responsibilities of the feedlot manager, as well as those of the feedbunk reader, and the feedbunk computer network may have the configuration schematically illustrated in FIG. 19. In feedlot computer network 16, the data files created and used by the feedmill computer system, the feed delivery vehicle computer systems, the feedlot veterinary computer system, the feedlot nutrition computer system and the financial computer system will be substantially the same as those data files created and used in feedlot computer network 16. The major difference is that the data files created and used by the feedlot management computer system and the feedbunk reading computer system in feedlot computer network 16, will be created and used in portable computer system 135 of feedlot computer network 16'. While the preferred embodiments of the system and method of the present invention have been described in detail, it will be appreciated that numerous variations and modifications of the present invention will occur to persons skilled in the art. All such variations and modifications shall constitute the present invention as defined by scope and spirit of the appended claims.
|
Same subclass Same class Consider this |
||||||||||