Orange Enterprises, Inc.: Software: Tiger Jill
 |
|
|
|
|
|
 Tiger Jill the SPRAY HISTORY SERVER is a premier software program designed to record all field, site applications, Measurements, Cultural activities, Labor, Equipment, Inventories, Billing, Scheduling, Planning, Budgeting, Mapping, Food Safety, Lab information, Employee safety, Chemical reporting, Worker Protection Standard, Hazardous Manifest, Recommendation, Management capabilities and more.
The objective of the Server is to record all information from the soil condition, pesticide application to the end product, "from dirt to the jar"
|
Local and global consumers, growers, marketers and governments want to know "what is in our food." Tiger & Pocket Jill software will allow you to pass your food safety documentation audit. Tiger & Pocket Jill are the software tools to improve general business performance and ever shifting food safety and trade regulations. Our tools will put you in compliance with county, state, federal as well as export regulations. We at Orange Enterprises, Inc. provide customized solutions that use information technology to connect information and promote alliance in the food supply chain
|
|
Total Traceability:
As a Food Safety program you can implement a Total Traceability systems which effectively reveals the history of any
carton of fruit from the market to the orchard, and even more specifically to the block.
The ability to identify the source of a product can serve as an important complement to good agricultural and management practices intended to prevent the occurrence of food safety problems.
This is one of the methods of ensuring the customer is receiving a totally safe, excellent quality, marketable carton of fruit.
The latest Tiger Jill standards will provide crucial support for food companies wishing to achieve and demonstrate integrity of supply.
Current issues such as genetic modification and pesticide use have had a major impact on consumer confidence in food products and have
to some extent influenced the current drive to require traceability of raw materials from farm to fork.
Using Tiger Jill you maintain a permanent record of who did what, when, where, and how.
Spray History Server
The Spray History Server will make it possible to verify spray history records prior to the shipping of produce by a grower. It verifies that the pesticide applications are within the scope of the grower's - processor agreement. This validation can take place in real time.
The spray history information can be used:
- To prevent tainted produce from entering the receiving stations,
- To prevent tainted produce from reaching the market,
- To guide testing programs,
- Evaluate grower performance,
- Evaluate the potential effects of pesticide use on a specific crop,
- Understand current grower pesticide usage,
- Respond to regulatory agency inquiries,
- Answer potential questions from consumers and other groups,
The spray history records will be transmitted electronically in the form of an ASCII file or E-mail from the grower's computer to the server database. All newly imported records will be subject to validation. The validation module will include standard and/or specific validation rules. These rules will allow the flagging of possible shipments that exceed the limitations set forth in the grower's agreement. This allows further review prior to the shipment leaving the grower's facility.
Connectivity Module.
This module makes it possible to send and receive records from one Tiger Jill program to another. It can be used by growers and processors to exchange records or by a PCA to transmit recommendations to a grower, applicator or dealer.
Processor Client and Server
The Processor Client Server System is a two-way communication between growers and food processors. It uses the Internet to send information back and forth. The grower sends to the processor information about its operation sites, blocks and pesticide applications, while the processor sends the grower information about approved materials and confirmations of information received. |
Spray History validity checking procedure.
A program with the Spray history module has two modes of data entry
1. Spray History mode
2. Regular mode.
The selection of the mode is done in the Verification Tab of the Preferences. When the program is in the spray history mode a spray history caption appears at the bottom left corner of the screen.
When the program is in the regular mode it does not accept records that are not valid. When it is in the Spray History Mode it accepts all the records but if a record is not valid it will flag it i.e. in the Block Grid it sets the Valid field to N and enter the reason to the Violation Field.
Two fields are added to the application screen: The ALL VERIFIED and VALID.
Three validity tests are performed on the application records:
1. A test whether the materials are registered to the treated crop.
2. A test whether the application meets the limits defined in the material record for the treated crop. Some of the limits check amounts applied over the entire season like the total amount applied over the season. Some treated blocks may pass this test while others may not.
3. A test whether the material meets the allowed harvest interval required for the treated crop. The harvest date for this test is taken from the harvest column of the season record. This test is based only on the projected harvest date . Another test is done when an actual harvest record is entered in the Harvest Records Tab of the Block Record.
There are two flags: Valid and Verified. There are two memo fields Violation and Justification. They are all defined for each line of the block grid.
Valid determines if the application is valid for the treated block. It has two states.
Y means that the block passed the validity tests, or was deemed by the field man to pass it.
N Means that the block did not pass the test.
Verified determines if a field man checked the result and accepted the invalidity flag. It has two states:
Y means that either the application is valid or that a field man checked the record and verified that it is not a mistake. A verified not valid application means that produce from the current season of the treated block cannot be accepted in a receiving station.
N Means that the application is not valid but a Fieldman has not yet reviewed the record or did not verify its correctness.
Violation is a memo field that includes the error message or messages that explain why the block did not pass the validity test. If the block passes the validity test the Violation Memo is empty.
Justification is a memo field that is only used when the Field man overrides the N in the Valid column by changing it, manually, to Y. It includes the justification for overriding the test result.
Passing the Validity Tests:
If a block in an application passes the validity tests both Valid and Verified Flag are set to Y. The Violation and the Justification Memo are empty and the user cannot modify any flag or memo. The grid line color is set to the Valid Line Color as defined in the preferences Color tab.
Failing the Validity Tests:
If a block does not pass the test both Valid and Verified flags are set to N, and a description of the error condition is entered into the Violation memo. The grid line color is set to the Not Verified Not Valid Line Color as defined in the Preferences Color tab.
A Fieldman may override the N in the Valid field and change it to Y. When he does this, the Verified flag is also being set to Y and the Justification field must be defined. Also the grid line color is set to the Valid Line Color as defined in the preferences Color tab.
If the Fieldman verifies that the block did fail the test he sets the Verified flag to Y and the grid line color is set to the Verified Not Valid Line Color as defined in the preferences Color tab.
The ALL VERIFIED and VALID fields in the application screen are set according to the flags of the different lines in the Block Grid. If All of them are Valid the color of the screen is set to Old Record Color as defined in the Preference Color Tab.
If one line in the grid block is not valid and not verified ALL VERIFIED and VALID are set to N and the color of the screen is set to the Not Verified Not Valid Record Color as defined in the Preference Color Tab.
If one line in the grid block is not valid and all the lines are verified the ALL VERIFIED is set to Y the VALID is set to N and the color of the screen is set to Verified Not Valid Record Color as defined in the Preference Color Tab.
The default color scheme is based on the traffic light colors where a shade of Green is Valid, a shade of Red is invalid and a shade of Yellow is not valid and was not verified.
The ALL VERIFIED and VALID are designed to be used with the Filter button to make it possible to filter the group of records with any combination of validity and verification.
When the user records harvest in the Harvest Records Tab of the Block Record, the program checks to see if all the applications of the current season of this block are valid and if the harvest date meets the Harvest intervals defined for all the materials applied to this block. The same set of flags and memos of the application record (Valid, Verified, Violation and Justification) is used in the harvest line.
The Fieldman must pay special attention to two cases of Validity errors.
1. The validity error was not verified.
2. The validity error is of Allowed Harvest interval that was based on an estimate that is different than the actual. If this is the case the Fieldman will override the N in the valid field.
|
|
|
|
|
|
