WO2013148290A1 - Grain position platform manager apparatuses, methods and systems - Google Patents

Abstract

The GPPM transforms producer crop asset information via GPPM components into dynamic, automated, real-time, and/or near real-time inventory updates, comprehensive agricultural portfolio information, offers, sales and/or purchase agreements, and/or dynamic, automated, real-time and/or near real-time market updates and feeds. The GPPM also provides online producer inventory integration with internal and external sources, geo-spatial commodity sensory location and updates, and dynamic, automated, real-time, and/or near real-time market and benchmark analyses. The GPPM receives crop asset storage resource information, such as location data for crop storage resource(s). The received information is associated with a producer crop asset management account. Mobile devices may be associated with the account. The GPPM determines when an associated mobile device is within a specified distance of a storage resource location and notifies the mobile device. The GPPM receives dynamic crop volume data for the crop storage resource and associates it with the producer crop asset management account.

Description

GRAIN POSITION PLATFORM MANAGER APPARATUSES,

METHODS AND SYSTEMS

[ o o o l ] This application for letters patent disclosure document describes inventive aspects that include various novel innovations (hereinafter "disclosure") and contains material that is subject to copyright, mask work, and/or other intellectual property protection. The respective owners of such intellectual property have no objection to the facsimile reproduction of the disclosure by anyone as it appears in published Patent Office file/records, but otherwise reserve all rights.

PRIORITY CLAIM

[0002] This application is a non-provisional of and claims priority under 35 USC §119 to: United States provisional patent application serial no. 61/617,598 filed March 29, 2012, entitled "GRAIN POSITION INVENTORY TRACKING AND MOBILE UPDATE MANAGER APPARATUSES, METHODS AND SYSTEMS," attorney docket no. SCHN-ooi/ooUS 1318573-2001; United States provisional patent application serial no. 61/617,599 filed March 29, 2012, entitled "GRAIN POSITION PORTFOLIO TRACKING MANAGER APPARATUSES, METHODS AND SYSTEMS," attorney docket no. SCHN-002/00US 1318573-2002; United States provisional patent application serial no. 61/617,603 filed March 29, 2012, entitled "GRAIN POSITION SEARCH AND TRANSACTION MANAGER APPARATUSES, METHODS AND SYSTEMS," attorney docket no. SCHN-003/00USI 318573-2003; United States provisional patent application serial no. 61/617,606 filed March 29, 2012, entitled "REGIONAL REAL- TIME GRAIN MARKET POSITION MANAGER APPARATUSES, METHODS AND SYSTEMS," attorney docket no. SCHN-004/00USI 318573-2004; the entire contents of the aforementioned applications are expressly incorporated by reference herein. FIELD

[ 0003 ] The present innovations generally address apparatuses, methods, and systems for commodity inventory tracking, updating, and management, and more particularly, include GRAIN POSITION PLATFORM MANAGER APPARATUSES, METHODS AND SYSTEMS ("GPPM").

BACKGROUND

[ 0004 ] Various commercial crops may be grown on farms. Farmers typically plant seeds, and subsequently provide maintenance to the planted crop as it grows. The crop is grown until it is ready to harvest.

BRIEF DESCRIPTION OF THE DRAWINGS

[ 0005 ] The accompanying appendices and/or drawings illustrate various non- limiting, example, inventive aspects in accordance with the present disclosure: [ 0006 ] FIGURES 1A-1B show provide overview diagrams illustrating example aspects of commodity search, data updating, storage, and exports in some embodiments of the GPPM; [ 0007] FIGURES 2A-B provide diagrams illustrating examples of resource record creation and updating, including storage sensory devices communication and other aspects of the GPPM to update commodity storage data in some embodiments of the GPPM. [ 0008 ] FIGURE 3 shows a logic flow diagram illustrating an example of a GPPM resource record creation and updating for some embodiments of the GPPM; [ 0009 ] FIGURES 4A-B provide logic flow diagrams illustrating exemplary GPPM integration and profile generation/creation components, data conversion components, and external data export components and procedures in some embodiments of the GPPM; [ o o i o ] FIGURES 4C-E demonstrate exemplary user interfaces illustrating example features for integrating commodity storage from internal and external producer sources, visualizing commodity storage from internal and external producer sources, receiving market data, and providing commodity storage market and volume statistics from internal and external producer sources in some embodiments of the GPPM; [ 0011] FIGURE 5A shows an overview diagram illustrating an example of a GPPM producer prompt component and mobile application facilitating proximity commodity storage creation and update in some embodiments of the GPPM; [ 0012 ] FIGURES 5B-D show mobile user interface diagrams illustrating example features for alerting, updating, and informing a GPPM user/producer of their account data and aggregated storage for some embodiments of the GPPM; [ 0013 ] FIGURE 6A shows an overview diagram illustrating an example of a GPPM commodity geo-search inventory component and application providing a proximity commodity search for purchasers within a specified geographical region in some embodiments of the GPPM; [ 0014] FIGURE 6B shows a mobile user interface diagrams illustrating example features for informing a GPPM purchaser user of commodities for purchase within a geographical area in some embodiments of the GPPM; [ 0015 ] FIGURES 7A-7E show exemplary logic and data flow diagrams illustrating a GPPM Inventory Matching Component and facilitation of commodity transactions between GPPM accounts in some embodiments of the GPPM; [ 0016 ] FIGURE 8A shows an exemplary Livestock Feed Matching data flow diagram for some embodiments of the GPPM; [ 0017] FIGURE 9 shows a block diagram illustrating embodiments of a GPPM controller.

[ 0018 ] The leading number of each reference number within the drawings indicates the figure in which that reference number is introduced and/or detailed. As such, a detailed discussion of reference number 101 would be found and/or introduced in Figure 1. Reference number 201 is introduced in Figure 2, etc.

DETAILED DESCRIPTION GRAIN POSITION PLATFORM MANAGER (GPPM)

[0019] The GRAIN POSITION PLATFORM MANAGER APPARATUSES, METHODS AND SYSTEMS (hereinafter "GPPM") transforms producer crop asset information, via GPPM components, into dynamic, automated, real-time, and/or near real-time inventory updates; comprehensive agricultural portfolio information; agricultural commodity offers, sales and/or purchase agreements; and/or dynamic, automated, real-time and/or near real-time market updates and feeds. The GPPM also provides online producer inventory integration with internal and external sources, geo- spatial commodity sensory location and update, and dynamic, automated, real-time, and/or near real-time market and benchmark analysis for both supply and demand- side agents. [0020] In some implementations, the GPPM creates a producer crop asset management account and receives crop asset storage resource information including storage resource location data for an at least one crop storage resource. The received crop asset storage resource information is associated with the producer crop asset management account. One or more mobile devices (e.g., smartphones, tablet computers, etc.) may then be associated with the producer crop asset management account. The GPPM determines when one of the mobile devices is within a specified distance of the at least one crop storage resource location and generates a notification on the mobile device that the mobile device is within the specified distance of a crop storage resource location. The GPPM may then receive dynamic, automated, real-time and/or near-real-time crop volume data for the crop storage resource and associate it with the producer crop asset management account. [0021] In one implementation, the GPPM creates, generates, receives and/or enables an agricultural commodity asset management account for a farmer or other agricultural asset producer and receives harvested agricultural asset storage resource information and actual agricultural asset storage data for agricultural assets stored in the harvested agricultural asset storage resource, including location, volume, and crop type. The GPPM may also receive in-field agricultural asset information, along with agricultural financial instrument data. The GPPM may also receive agricultural asset market data and determine an agricultural asset portfolio value for the agricultural commodity asset management account. The GPPM may then receive real-time updates of actual agricultural asset storage data and in-field agricultural asset information and update and output the determined agricultural asset portfolio value. [ 0022 ] In some implementations, the GPPM maintains an agricultural asset tracking account for each of a plurality of agricultural asset producers, such as farmers, including asset type data, asset location data, and asset availability data. The GPPM may then receive one or more real-time updates to asset account information from agricultural asset producers. The GPPM may then determine aggregate market data for a geographic region from a set of the plurality of agricultural asset producers based on asset type data, asset location data, asset availability data and the real-time updates to asset account information and generate real-time geographic market data feeds. [ 0023 ] Figure lA illustrates exemplary aspects for some embodiments of the GPPM in which a producer may use the GPPM to integrate commodity storage/in-field storage, update commodity storage/in-field volumes both centrally and locally, view dynamic, automated, real-time and/or near real-time market and benchmark analyses, and export data into computer file formats for both personal and external end-user applications. In one embodiment, a producer 101 may use a GPPM interface 102 to input information about commodity storage/in-field storage liia-n from a location that is not in immediate proximity to the commodity storage/in-field storage. In another embodiment, a producer may use a GPPM interface to input stored commodities data/information 113 about commodity storage/in-field storage from a location that is in proximity to the commodity storage/in-field storage facility. In another embodiment, the GPPM interface may prompt 104 the producer that a commodity storage facility 111b already contained in the GPPM is nearby and ask the producer if an update to the commodity storage contents is desired. In one embodiment, a demand agent and/or purchaser ("purchaser") 110 may use a GPPM interface to search for 1 nearby commodity for purchase 105 and receive anonymous results that a commodity

2 is stored nearby that is available. In a non-limiting example, the GPPM anonymous

3 search results exemplified in 105 may contain reference to commodities 111c belonging

4 to a producer using the GPPM for commodity storage integration. In one embodiment,

5 the producer may use dynamic, automated, real-time and/or near real-time market

6 information 108 provided by the GPPM to determine integrated commodity worth. In

7 another implementation, commodity information may not be integrated within the

8 interface, with the GPPM illustrating aggregate, but separate commodity amounts and

9 value 109 to the producer. In another embodiment, the GPPM may allow the producer

10 to export information 106 contained in various GPPM components, data structures,

11 and devices to formats that may be compatible with various external sources/entities

12 107, with non-limiting examples being personal and commercial software packages,

13 institutions such as banks or other financial service providers, insurance companies,

14 and the like.

15 [ 0024] In one embodiment, a purchaser or other demand agent may use a GPPM

16 interface to request nearby commodities for sale. For example, in Figure lB, a

17 purchaser 110 may make a request, using a GPPM mobile device interface 102, to know

18 how many bushels of corn are available in a radial search of ten miles. In this

19 embodiment, the GPPM 120 may facilitate contact with supply agents ("producers")

20 loia-c who also maintain GPPM accounts and are local to the radial search area,

21 concerning the amount of corn contained in various commodity storage units I03a-c

22 and relay the amount as well as the sale price to the purchaser ("1,212,000 bushels at

23 $10 per bushel") and ask if the purchaser wishes to see further information regarding

24 the available commodities 104.

25 [ 0025 ] Figure 2A illustrates some examples of resource record creation/updating

26 features/components, such as storage facility entry generation in a GPPM Inventory

27 Component and provides further examples of updating storage facility volumes through

28 a GPPM mobile application. A producer may elect to add a commodity storage facility

29 to his or her producer profile. In one embodiment, the producer may generate the

30 commodity storage facility entry through a web portal interface to the GPPM 211a from any location providing internet access. In one embodiment, the producer may generate the commodity storage facility data entry through a mobile interface 211b. This mobile interface (e.g., a mobile device implementing the interface) may be near a commodity storage facility which, in one embodiment, may signal the GPPM mobile application to add the storage facility. The storage facility may have been previously entered, or may be identified as a potential storage facility (e.g., via a identification component of the GPPM that analyzes satellite images of a location to identify building or locations that could be resources, such as silos or storage facilities). In one embodiment, the producer may manually enter a facility's location. In some embodiments, a producer may enter any commodity storage facility through a GPPM mobile interface and/or other interfaces, even if the producer is not immediately located near the commodity storage facility being entered. For example, in one implementation, a producer may be presented with an image (e.g., a satellite image from an online map service) of his or her property, and may select or point to locations on the map to identify resource locations, and provide additional details (e.g., via a window with text prompts). [0026] In some embodiments, the commodity storage facility entry may generate a request to add the storage facility to the GPPM 211c. The request may include, by way of non-limiting example, information such as a facility identifier, the facility's latitudinal and longitudinal coordinates, the time of the entry, the date of the entry, the initial volume of the facility, stored commodity, and/or the like. In some embodiments, the add storage request 211c may be generated as an xml document to be parsed by the GPPM, as shown in the following example:

Content-Type: Application/XML

<?XML version = "1.0" encoding = "UTF-8"?>

<add storage facility producer id="3581T">

<id>52RF9</id>

<location>

<latitude>42.44</latitude>

<longitude>- 98.38</longitude>

</ location> <time stamp format="astronomical">

<hour>18</hour>

<minute>4K/minute>

</time stamp>

<date format="small endian" year length="2"> 12-05-50 </date>

<volume unit="bushels"> 10000 <\volume>

</add_storage_facility> [0027] In some embodiments, the add storage request 211c may be generated as a database insert command through a browser scripting language such as php. Fields entered into a web form may be retrieved as post variables, as shown below: <?PHP

header (' Content-Type : text/plain');

// access database server

$connex = mysql connect ( $DBserver, $user, $password) ;

// select database table to insert

mysql_select_db("GPPM_DB.SQL", $connex) ;

//create query

$query = "INSERT INTO Facilities ( Producer_id, Storage_id,

Latitude, Longitude, TimeStamp, Date, Volume)

VALUES ( ^Λ$_Ρ03Τ [producer_id] ' , ^λ$ POST [storage id] ' ,

Λ$_Ρ03Τ [latitude] , $_POST [ longitude] , ^λ$ POST [timestamp] ' ,

Λ$_Ρ03Τ [date] ' , $_POST [volume] ') ";

$result = mysql query ( $query, $connex) ; // perform the insert mysql close ( $connex) ; // close the connection

?>

[0028] The GPPM may parse and error-check the values provided by the storage request after which it may generate a storage record 212 in the Integrated Data structure 280 (e.g., database) which may contain all information generated during the producer profile creation. [ 0029 ] In some embodiments, once a storage facility has been added to the Integrated Data structure, the GPPM may allow the producer to update the data record of the storage facility. In one embodiment, the producer may manually update the storage facility data record through a GPPM web or mobile interface. In some embodiments, the GPPM may update the storage facility data record through the GPPM mobile interface as the producer approaches a storage facility. [ 0030 ] In some embodiments, various agricultural facilities, machinery and/or equipment may include precision agriculture equipment that can communicate/interface with various GPPM components to provide and/or receive data. For example, in one implementation, a storage facility may be equipped with a precision ag equipment device (PAE), and the PAE may be integrate/communicate with a GPPM component (e.g., via a GPPM mobile interface) to update the record for contents of the storage facility. Although "storage facility" is discussed herein in the context of having a fixed location, it is to be understood that, in some embodiments, the GPPM may track and interact with equipment and machines, such as combines, grain carts, in-field storage, semi-trailers, etc., having storage attributes. As discussed herein, PAE equipment may include, but is not limited to, on machine/equipment monitors/components (e.g., installed/configured/equipped on tractors, variable rate spreaders, etc.), bin monitoring/sensing equipment, grain cart scales, sensors for monitoring atmospheric data, weather information, location/position data, commodity security data, and/or the like. In one embodiment, the GPPM mobile application (or like GPPM component) wirelessly requests a volume update 214 from the PAE. The PAE reports the current commodity volume of the storage facility and wirelessly updates this data to the GPPM mobile application 215, using a wireless connection such as, by way of non-limiting example, Wi-Fi, Bluetooth, RFID, Near Field communication, other shortwave wireless connection, and/or the like. In some embodiments, the PAE may integrate with the GPPM mobile interface through a hardware connection, such as, by way of non-limiting example, USB cable, Firewire, USB drive exchange, and/or the like. In one example, a mobile device installed with the GPPM mobile application is connected by a USB cable to the PAE, engaging a volume update request 216. The PAE exchanges its volume data with the GPPM mobile application 217. [ 0031] In some embodiments, the producer may use the GPPM mobile application to determine the volume without the use of a PAE. In one such implementation, a producer may use a visual representation of the storage facility of the GPPM mobile application to make a visual representation of the storage facility volume 213 which is then passed to a GPPM Volume Calculator Component. In one example, the camera and/or other components on the mobile device may determine the approximate measurements and geometry of the storage facility (e.g., a silo could be modeled after a cylinder, with volume = 7rr²h) to determine a total volume and/or actual volume. In some implementations, features of certain storage facilities and/or packing of certain commodities may also be used in determining the volume of a particular storage facility (e.g., the bottom of a silo may be cone shaped and/or the grain in the silo may have a conical top due to loading from above). In another implementation, the storage facility may include visual or other volume markers that can be input into the mobile device. For example, the interior of the storage facility may contain QR codes, the first visible of which the GPPM mobile application may scan and communicate to the Volume Calculator Component, which process the QR code. The Volume Calculator Component then returns an approximate volume of the storage facility to the GPPM mobile application 213a. In another embodiment, satellite and/or ground imagery may be used to determine the current volume of a storage silo. For example, in one embodiment an image or images of a particular silo may be analyzed after a predetermined event (which may be a triggering event), such as change (increase/decrease) in temperature that could change the external appearance of the silo, i.e., could create a frost or condensation line corresponding to the level of commodity in the silo, the frost line visible to a satellite image and/or an image captured via mobile device, for example, as determined by relative reflectance values of the surface of the silo and/or changes in the value(s) over time. [ 0032 ] Once a storage facility volume has been updated to the local GPPM application, it may be submitted 218 to the GPPM Inventory Component for update and reintegration with existing producer inventory. The update request may contain, by way of non-limiting example, the identifier of the storage facility, the time and date the volume update was taken, the new volume amount, and/or the like.

[0033] In some embodiments, the storage volume update request 218 may be generated as an XML document to be parsed by the GPPM, as shown in the following example:

Content-Type: Application/XML

<?XML version = "1.0" encoding = "UTF-8"?>

<update storage facility producer id="3581T">

<id>13T8X</id>

<time stamp format="astronomical">

<hour>14</hour>

<minute>02</minute>

</time stamp>

<date format="small endian" year_length="2 "> 18-07-50 </date> <volume unit="bushels"> 22500 <\volume>

</update_storage_facility>

[0034] In some embodiments, the storage volume update request 218 may be generated as a database update command through a browser scripting language such as php. Fields entered into a web form may be retrieved as post variables, as shown below:

<?PHP

header (' Content-Type : text/plain');

// access database server

$connex = mysql connect ( $DBserver, $user, $password) ;

// select database table to update mysql_select_db ( "GPPM_DB . SQL" , $connex) ;

//create query $query = "UPDATE Facilities SET TimeStamp=$_POST [ timestamp] ,

Date=$_POST [date] , Volume=$_POST [volume] WHERE storage_id =

$_POST [storagelD] ";

$result = mysql query ( $query, $connex) ; // perform the insert mysql_close ( $connex) ; // close the connection

?> [0035] The GPPM Inventory Component 290 may then update the Integrated Data structure storage facility data record with the revised information 219, which may include volume, time, date, and/or the like. [0036] Figure 2B illustrates additional examples of generating storage facility and/or field entries in the GPPM Inventory Component and provides further examples of updating storage facility and/or field volumes through remote or wired communication with the GPPM or a GPPM mobile application. In some embodiments, a precision ag equipment (PAE) may be integrated with cultivation and/or harvest implements 2iie to calculate commodity volume during field cultivation and/or harvest activities. At this time, a producer may choose to generate a storage facility entry for the field. In some embodiments, harvest data may be determined from combines, grain cart/weigh wagon, semi-trailers, etc. [0037] The request may include, by way of non-limiting example, information such as a facility identifier, the type of facility, the facility's latitudinal and longitudinal coordinates, the time of the entry, the date of the entry, the initial volume of the facility, and/or the like. In some embodiments, the add storage request 211c may be generated as an xml document to be parsed by the GPPM, as shown in the following example:

Content-Type: Application/XML

<?XML version = "1.0" encoding = "UTF-8"?>

<add storage facility producer id="3581T">

<id>43RTK/id>

<facility type>field</ facility type>

<location> <latitude>46.13</latitude>

<longitude>-101.85</longitude>

</location>

<time stamp format="astronomical">

<hour>8</hour>

<minute>22</minute>

</time stamp>

<date format="small endian" year_length="2 "> 12-05-50 </date> <volume unit="bushels"> 12000 <\volume>

</add storage facility>

[0038] In some embodiments, the add storage request 211c may be generated as a database insert command through a browser scripting language such as php. Fields entered into a web form may be retrieved as post variables, as shown below: <?PHP

header (' Content-Type : text/plain');

$connex = mysql connect ( $DBserver, $user, $password) ;

// access database server

mysql_select_db("GPPM_DB.SQL", $connex) ;

// select database table to insert

//create query

$query = "INSERT INTO Facilities ( Producer_id, Storage_id,

Facility Type, Latitude, Longitude, TimeStamp, Date, Volume) VALUES ( ^Λ$_Ρ03Τ [producer_id] ' , ^λ$ POST [storage id] ' ,

Λ$_Ρ03Τ [facility_type] ' , ^Λ$_Ρ03Τ [latitude] , $_POST [ longitude ] , Λ$_Ρ03Τ [timestamp] ' , ^λ$ POST [date] ' , $_POST [volume ]')" ;

$result = mysql query ( $query, $connex) ; // perform the insert mysql close ( $connex) ; // close the connection

? > [0039] In some embodiments, the storage id may contain a code identifying the storage type. In some embodiments, the facility type may be a separate field. In some embodiments, the facility type may not be stored. [ 0040 ] The GPPM may parse and error-check the values provided by the storage request after which it may generate a storage record 212 in the Integrated Data structure 280 which may contain all information generated during the producer profile creation. [ 0041] In some embodiments, a storage facility may contain a PAE with a wired or remote connection to the GPPM. A producer may authorize the PAE to automatically generate a storage facility entry. In one such example, a commodity storage facility communicates 2nd with the GPPM Inventory Component to generate the storage facility entry, as previously described in 2iia-c. In such an embodiment, the producer may only need to provide authorization, through a GPPM mobile or web interface, for the PAE to communicate directly with the GPPM in the generation of a storage facility entry. In some embodiments, the producer may disable or otherwise limit the ability of a PAE to generate storage facility entries. In some embodiments, the GPPM may provide the producer with notification through a GPPM mobile or online interface that the PAE of a storage facility has generated an automatic storage facility entry. In such an embodiment, the producer may have the ability to override and/or modify the PAE storage facility entry. [ 0042 ] In some embodiments, once a storage facility has been added the Integrated Data structure, the GPPM may allow the PAE to update the data record of the storage facility and/or field. In one embodiment, a PAE may be authorized, as described in 2nd, to generate the initial storage facility entry in the GPPM Inventory component. In such an embodiment, the producer may further authorize the PAE to produce and/or accept update requests 218 to/from the GPPM Inventory component. In one embodiment, the GPPM Inventory Component may request that the PAE determine/calculate/provide the volume of the storage facility and send 219 the updated volume through remote and/or wired connection to the GPPM. In some embodiments, the PAE may automatically generate storage updates to the GPPM whenever the volume of the storage facility has been modified. In some embodiments, the PAE may automatically generate storage updates to the GPPM at scheduled time intervals. In some embodiments, the producer may determine the time intervals at which the PAE will generate the storage updates. In some embodiments, the PAE may have preset time intervals at which it generates storage volume updates to the GPPM. Similarly, in some embodiments, the GPPM may have preset time intervals at which it generates storage volume update requests to one or more PAE devices. In some embodiments, the PAE may have preset time intervals which the producer may override through a GPPM web or mobile interface. In some embodiments, the GPPM may provide the producer with notification through a GPPM mobile or online interface that the PAE of a storage facility has generated an automatic storage update. In such an embodiment, the producer may have the ability to override and/or modify the PAE storage update. [0043] In some embodiments, a cultivation/harvest implement, such as tractor, planter, combine, etc., may contain a PAE to measure field volume during field cultivation and/or harvest, as described in 211c. In such an embodiment, the PAE may be able to generate a field volume update to the GPPM. In some implementations, the data may be calculated and/or transmitted "on the go" while harvesting. In some embodiments, the PAE may communicate with a GPPM mobile interface, as described in 213-217. In some embodiments, the PAE may communicate directly with the GPPM Inventory Component as described in 218-219. Such embodiments may track in-field storage, for example, by tracking the amount of acreage that has been planted, the expected and/or historical growth time and/or yields, as well as, in some implementations, the amount of grain or other commodity already harvested. In some implementations, images (e.g., images from satellites and/or fly-overs) may be used to determine in-field storage, that is, identify harvested and unharvested areas of a particular field or plot of land associated with a particular producer. [0044] Commodities that are cultivated/harvested from field storage may be transferred to a storage facility, in which case an Integrated Data structure entry for the field storage may need to be converted/transferred to a storage facility entry and/or be added to an existing storage facility entry in order that commodities that began in-field are not double-counted to a producer once moved to a storage facility. In some embodiments, the cultivation/harvest implement PAE may send a volume transfer request 222 to the PAE of a storage facility, indicating that the field volume is to become part of the storage facility volume. In some embodiments, the GPPM Inventory Component receives data from various PAEs to effectuate the conversion of in-field storage volume to storage facility volume. In some embodiments, the storage facility PAE may generate a volume update request to the GPPM Inventory Component as described in 218. In such embodiments, the storage volume update 224 to the GPPM may include additional data, such as, by way of non-limited example, an external source for the update, such as a storage identifier and the amount being added from the external source. [0045] In some embodiments, the storage volume update request 224 may be generated as an XML document to be parsed by the GPPM, as shown in the following example:

Content-Type: Application/XML

<?XML version = "1.0" encoding = "UTF-8"?>

<update storage facility producer id="3581T">

<id>13T8X</id>

<time stamp format="astronomical">

<hour>14</hour>

<minute>02</minute>

</time stamp>

<date format="small endian" year_length="2 "> 18-07-50 </date> <volume unit="bushels"> 22500 <\volume>

<external source amount="9000">43RTK/external source>

</update_storage_facility> [0046] In such an embodiment, the GPPM Inventory Component in updating the storage record with revised volume information 225 may make updates to both the entry of the storage facility generating the request and to the storage facility entry from which the volume transfer occurred. Below is exemplary pseudocode in which the GPPM Inventory Component parses a storage volume update in which the source for the update is external and belonging to an existing storage facility entry: void UpdateStorageRecord (String xmlFile, Database db)

{

XMLreader parser = new XMLParser ( ) ; //create XML parser parser . Parse (xmlFile ) ; //open the file for parsing

while ( ! parser . EOF) //while not end-of-file

{

//advance through elements of type storage facility parser .Advance ("storage facility") ;

String producer = parser . GetAttribute ( "producer id") ; String storagelD =

parser . ReadElementString ("storage facility") ;

Time timeObj = parser . ReadTimeElement ( "time stamp"); Date dateObj = parser . ReadDateElement ( "date" ) ; float volume = parser . ReadElementNumeric ("volume" ) ;

String externallD =

parser . ReadElementString ("external source");

float externalVolume = parser . GetAttribute ("amount") ; //Create a command string with which to update the //database for this storage facility entry.

//Error checking for database entry may be

//handled at the database level

DBString command = CreateDBUpdateCommand (producer , storagelD, timeObj , dataObj , volume);

db . Update ( command) ; //if an external volume source existed and

//is in the database

if (externallD != NULL && db . EntryExists (externallD) ) {

// compare the amount going from the external //source to the updated storage entry.

//If all of the external source volume //is moved to the updated storage entry, //delete the external storage entry. Otherwise

// update it with the new volume.

float currentVolume = db . GetField (externallD,

"volume")

if (currentVolume == externalVolume)

db . DeleteEntry (externallD) ;

else

{

float newVolume = currentVolume - externalVolume;

db . UpdateField (externallD, newVolume);

}

}

}

} [0047] In the proceeding example, the GPPM may be responsible for resolving an update command in which the storage facility entry being updated has an external source, which may also have a storage facility entry. In this example, the GPPM resolves the update command by parsing to the storage facility update, then checking the integrated data structure for a storage facility entry which matches the external source identifier provided by the update request. If the external source storage facility entry exists, the GPPM determines if its entire volume has been transferred to the storage facility being updated. If so, the GPPM may delete the record for the external source. In some embodiments, the GPPM may not delete the record, but may update its recorded volume as "o". In some embodiments, the GPPM may flag the external source record to request an update from the PAE of the external source, and/or from the producer. In some embodiments, the GPPM may not update any records unless a specific update request has been issued from a PAE and/or producer. In some embodiments, all such examples may be settings available for the producer in updating storage entries through the GPPM. 1 [0048] Figure 3 describes one example of a logic flow diagram in which a

2 producer adds commodity storage facilities to the GPPM when the producer is detected

3 in proximity to the facility, examples of which are described in Figures 2A-B and 5A.

4 The GPPM may populate 301 its storage facility data structure 320 prior to, during,

5 and/or after the creation of a producer account. In some embodiments, a producer may

6 input the location of storage facilities into the GPPM Integration Manager 321 at any

7 time during or after initial producer account creation. In some embodiments, devices

8 or sensors, such as PAEs described in Figures 2A-B and 5A may provide their location

9 322 to the GPPM and be reflected in the storage data structure. In some embodiments,0 the GPPM may use geospatial data to determine storage locations by satellite data 323,1 in one implementation using reflectance values as determined by satellite imagery.2 There may be other methods by which the GPPM populates its storage facility data3 structure and the GPPM may populate the data structure both dependent to and4 independent of a producer account. In one example, the GPPM mobile application5 monitors a producer's position using one or more of the methods previously described6 or by similar methods 302. Once the producer nears a storage facility appearing in the7 GPPM storage data structure 303, the GPPM mobile application may determine if the8 storage facility is associated with the producer's account 304. If not, the GPPM may9 prompt the producer to add the facility to the producer's account 306. If the producer0 chooses not to add the facility to the producer's account, the GPPM may prompt the1 producer to flag the facility 310. Once flagged, the facility would not result in an2 additional notification when the GPPM mobile application was once again in proximity3 to the facility 312, otherwise the GPPM mobile application may again alert the producer4 to the facility at a future time 311. If the facility is already associated with the producer's5 account, the GPPM may display inventory levels and commodity values 305, an6 interface example of which is shown in figure 5C. The GPPM may then prompt the7 producer to update the storage facility inventory 308, such as by using methods8 previously described in Figures 2A-B and 5A. If the facility has been newly added to the9 producer's account, the GPPM may also prompt for inventory update. In some0 implementations, whether or not update occurs at this time, the GPPM may then return1 to its idle location monitoring state. In some embodiments, the GPPM mobile2 application may monitor the producer location whether or not the GPPM mobile application is currently active/in use and may provide notifications and/or alerts to the producer about storage facility proximity independent of the GPPM mobile application being active. Allowing the GPPM to monitor and report the producer's location during inactivity of the GPPM mobile application may be modifiable from the producer account settings in either /both of the GPPM online or mobile applications. [0049] In one embodiment, a producer may first interact with the GPPM by creating an account or profile. As shown in Figure 4A, a producer account or profile may be created through a GPPM web portal or mobile device interface 402. The profile may contain such information as an identifier for the producer, under which more than one business may be integrated, a central location from which the producer wishes to operate the account and/or have the account associated, the location of commodity storage facilities and/or fields belonging to the producer (and other assets associated with the producer), other commodity inventory not contained the previously mentioned commodity storage facilities, acreage, value of known inventory, and/or the like. After initial account information is obtained, the GPPM may request 403 that the producer provide access information for external accounts with which the producer is associated. In this embodiment, the GPPM may serve as an aggregator of producer accounts with, by non-limiting example, farm service agencies 430 which provide the producer with field and acreage information, co-ops and/or agribusinesses 440 with which the producer has contracted commodity storage, futures and cash bid services 450 which provide the producer with market data and analysis of commodities, financial services 460 such as banks, credit unions, or brokerages with which the producer may have personal or business accounts, insurance companies 470 which provide the producer coverage, such as for appraised value of commodity inventory, and/or the like. If the producer agrees to provide the GPPM with access to these external accounts 404, the GPPM Integration Component may request data from these external accounts through account authentication protocols 405 using producer provided account security information. Also, and/or alternatively, the GPPM may store access credentials (e.g. usernames, passwords, digital certificates, etc.), allowing it access to external data sources. [0050] For example, the GPPM Integration Component may use various authenticator modules with an authenticator token which may provide the necessary security information without the GPPM Integration manager maintaining or storing sensitive external account security information. The following example pseudocode adds an external account with the requisite security information, compiled in a "user data" binary data type which the GPPM does not interpret, requests an authenticator token from the account, and maintains the authenticator token for reauthentication when the producer exits and re-enters the GPPM interface.

class cAuthenticatedAccount

{ Account mAccount;

AuthToken mAuthToken;

} ; varBinary userData = compileAccountlnformation (textfield) ;

cAuthenticatedAccount mAccountArray = new cAuthenticatedAccount

[ ] ; for (cAuthenticatedAccount acct; mAccountArray) {

acct . mAccount = addAccount ("Farm Service X", acct . mAuthToken, userData) ; } [0051] In one embodiment, the producer may opt not to access external accounts, but may decide to provide data locally available 406 on the producer's device, which may be, by non-limiting example, a database 420, or in some embodiments, local inventory files, local financial software files, data entry provided by the producer, in- field crop, field and storage facilities as described in figures 2A-B and/or the like. The GPPM may then integrate all sources, internal and external, provided by the producer into an Integrated Data structure 480, such as a local or cloud-based database and/or the like. The GPPM may provide data security controls to keep the collected information private/ secure, allowing access only to the associated producer and/or designated agents. The GPPM may then provide all integrated data, or subsets thereof, 1 for display 408 to the producer on the producer's device, whether through a web portal

2 or mobile interface 409.

3 [0052] Once a producer has created an account or profile with the GPPM, the

4 producer may elect to update the data contained in the profile. While the producer may

5 provide initial commodity storage facility information to the GPPM at the creation of

6 the producer profile, the producer may also decide to add commodity storage facilities

7 subsequent to the profile creation as described in Figures 2A-B.

8 [0053] In some embodiments, data integrated through the GPPM Integration

9 Component and stored in the Integration Data structure may be exported to an at least

10 one file type for use in external applications and/or by external entities. Figure 4B

11 shows one example of the GPPM Integration Component displaying the integrated data

12 in a GPPM online or mobile interface. In this example, when a producer chooses to

13 export 422 the integrated GPPM data, it is passed to the GPPM Data Conversion

14 Component 410a. In this example the GPPM Data Conversion Component may

15 reformat the data 423 into an at least one file type 424 which may include, by way of

16 non-limiting example, financial software formats such as .qdf, .iif, .mny, .bin, and/or

17 web browser readable formats such as .htm, .html, .pdf, .xml, .docx, .ps and/or the like is and/or shapefile formats such as .shp, .shx, .dbf, .prj, .sbn, .sbx, .fbn, .fbx, .ain, .aih,

19 .ixs, .mxs, .atx, .shp.xml, .cpg, etc. In some embodiments, the Data Conversion

20 Component may prepare the data for transfer to an external entity. In some

21 embodiments, the Data Conversion Component may prepare the data for an insurance

22 company which provides asset coverage for the producer. In some embodiments, the

23 Data Conversion Component may prepare the data for a financial institution with

24 which the producer has personal and/or business accounts. The GPPM DCC may, in

25 some embodiments, auto-populate a form or forms for submission, for example, the

26 GPPM may auto-populate a US Department of Agriculture Farm Service Agency FSA-

27 578 form and submit or post it for processing. Various forms and templates may be

28 provided and/or imported/exported, for example, to comply with reporting

29 requirements. In the following example pseudocode, the GPPM Data Conversion Component converts data stored in one format, such as a proprietary GPPM format, to a .pdf document:

PDFDocument* ConvertGPPMtoPDF ( String pdfName, GPPMfile &gFile)

{

PDFDocument* pdfFile = NULL;

PDFDocument : : Openfile (pdfName, pdfFile);

gFile. Open (GPPMfile: :READ_ONLY) ;

if (pdfFile != NULL)

{

pdfFile->SetTitle ( "OutputDATA" , ANSI);

pdfFile->Compres sion ( FLATE ) ;

PDFDocument : :WriteText (gFile, pdfFile) ;

pdfFile->CloseFile (pdfFile) ;

return pdfFile;

} [0054] Figure 4C shows an example embodiment of an online portal interface for the GPPM, generally following producer account creation and integration as described in Figure 4A. In this example, the interface comprises a "My Dashboard" tab 451 which may offer both integrated and discrete displays of a producer's commodity storage and value. An identifier of the producer may be displayed prominently 454, which in some embodiments may reflect the internal identifier used by the GPPM to distinguish the producer throughout GPPM components and data structures. In some embodiments, the displayed identifier may be separate from the internal identifier used by the GPPM. In some embodiments, the interface user may be able to log out of their account or change the settings of their account below the producer identifier 454. In some embodiments, the settings may include display preferences, which data is visible to external sources, how often data from external sources is updated, and/or the like. In some embodiments, "logging out" of the GPPM by the interface user would result in access to the account being restricted until such time as the user "logged in", but might allow data of the producer's account to continue to be visible to external sources - for example, commodity amounts available for sale. In some embodiments, logging out may restrict both access to the producer account and cause data from the producer's account to become invisible to external sources. In some embodiments, how the visibility of data is handled during the time in which a user is "logged out" may be modifiable in the settings. In some embodiments, the GPPM may control this access. [0055] The interface may show the integrated value of the producer's commodity assets 455 and may split the asset value into "contracted" and "remaining", indicating, for example, which of the producer's commodity assets have been contracted for sale by a purchaser and which assets are not yet be under contract. In some embodiments, the uncontracted assets may be made visible in some format to external sources, that is, shown as available for sale and/or trading. The asset value split discussed above is illustrative and non-limiting. In some implementations, additional categories may be utilized, such as: offered (transaction initiated by making an offer but the transaction has not been completed); spot sale (e.g., grain was sold on the current cash price with no special contracts but does turn into a contract between the producer & agribusiness); un-priced sale (the final price of the sale/transaction has not been determined, for example, seasonal average price contracts, etc., but the offer/intent to sale was made); contracted (may include spot sale, forward contract, seasonal average price, minimum price contract, futures only (HTA), and basis contract); delivered (e.g., the grain for the contract/transaction has been delivered); unsettled (the payment for the grain has not been finalized); remaining (e.g., do nothing - no activity/action around transactions have been made on the physical grain); and/or the like. Commodities may be further broken up into multiple categories 456-458 in the interface, providing the interface user an integrated and discrete picture of where commodities are stored, for example "in field", "on farm", with external agribusinesses, and/or the like, as well as what commodities the producer may have, for example corn, soybeans, hard red winter (HRW) wheat, and/or the like. According to some embodiments, in an instance where a producer may have commodities stored with external agribusiness sources, the interface may display the discrete storage facilities in which commodities are contained 458, for example in grain elevators, co-ops, and/or the like. [0056 ] The interface may also display a financial summary of the producer's commodity assets 459, with both current asset values and comparative asset values for previous years 461. This display may be graphic or text or some combination thereof. The interface may provide a "click through", or an interactive mouse button element, of the display 456-461 to more detailed financial information including but not limited to forecasting, benchmarks, contracts, offers, and/or the like. This "click through" may be associated with the "Daily Positions" tab 452 as described in Figure 4E, or may be a distinct interface. The "click through" may also allow the online portal interface user to send updated financial information to the GPPM mobile interface, an email address, a social network, asset export options, and/or the like. [0057] The example of a producer GPPM online interface shown in Figure 4D integrates both graphical and text elements to provide integrated and discrete information about where a producer's commodities are stored. In this embodiment, the producer selects the "Map Overview" tab 462 to view commodity storage by geography. On the left hand side, the GPPM online interface lists commodities by type, giving volume and value 463 per commodity, as well as in total. In some embodiments, the producer may choose to place certain commodities on a "Watch List" 464 which may, depending on the implementation, provide futures information, cash bid prices, commodity basis data, and/or the like. In some embodiments, a scheduler may be used to update this information at regular intervals. In some embodiments, the producer may refresh the interface to see updated information. In some embodiments, the producer may set the refresh intervals in the application settings. In some embodiments any or all of these refresh options may be available to a producer user. [0058 ] Continuing the example interface of Figure 4D, both "corn" and "soybeans" appear on the producers watch list, reflecting the type of commodities the producer has in storage. In some embodiments, the GPPM may populate this watch list automatically based on the type of commodities the producer has stored. In some embodiments, the producer may choose the type of commodities to add to the list. In some embodiments, the GPPM may initially populate the list and then allow the producer to modify the list in the application settings. 1 [ 0059 ] In this example of the producer GPPM online interface, cash grain bids

2 465 are also displayed, here sorted by storage facility.

3 [ 0060 ] The GPPM online interface may also provide a maps display 469

4 illustrating storage facility locations and statistical information, as well as a legend

5 listing the markers and the storage facility to which they correspond. In some

6 embodiments, the GPPM may use an external maps widget and populate it with

7 markers and identifying information from the GPPM Inventory and Storage

8 Components. In some embodiments, the GPPM may create its own maps widget. In

9 some embodiments, the GPPM may include detailed statistical analysis of each visible0 storage facility, including by way of non-limiting example, the storage facility identifier,1 its capacity, its current inventory, the inventory current value, how much of the2 inventory is contracted, the type(s) of inventory stored, when the storage facility was3 last updated, and/or the like. 4 [ 0061] In some embodiments, storage facilities may be associated with the5 producer but may be owned by an external entity, such as an agribusiness, coop, and/or6 the like. In this example, the ABC Elevator 466 is owned by an external agribusiness. In7 such an instance, the GPPM online interface maps widget may include a "contact"s button, facilitating an exchange between the producer and the agribusiness which may9 own the storage facility. In some embodiments, this "contact" button may link to a0 contact page, open an external messaging, video, or VOIP application and/or the like.1 In some embodiments, the GPPM may maintain its own messaging system between2 account holders. 3 [ 0062 ] For storage facilities that are owned by the producer user, the maps widget4 may include an "update" button, in which the producer may update the inventory of the5 storage facility remotely. In this example, "Storage Bin #5" 467 is owned by the produce6 user. In some embodiments, the GPPM online interface may allow the producer to7 update the interface by manual entry. In some embodiments, the storage facility may8 contain a PAE which may be accessed through wired or wireless communication and9 provide the update information automatically, as described in Figures 2A-B and 5A. [ 0063 ] For in field storage, the maps widget may display an identifier, the type of commodity, acreage, bushels, current value of the commodity and/or the like 468. In some embodiments, the GPPM online interface may provide "update" and "yield" buttons for in field storage. In this example, an "update" button may allow the producer to update statistical information about the field storage. The update for a field may be based on manual entry and/or on data the utilizes current measurements modeled on expected or historical models for growth. A "yield" button may provide the expected long-term yield of the field acreage, in some embodiments based on previous and/or current data, and modeled to determine anticipated yield. [ 0064] One example of a producer GPPM online interface in Figure 4E allows producer users to select the "Daily Positions" tab to see integrated and discrete financial and market analysis information for each of the producer's commodities. In this example, commodities are organized by location and contain dynamic, automated, real-time and/or near real-time value data 470. In some embodiments, data displayed may include by way of non-limiting example, the bushels sold, total bushels, bushels remaining to be sold, the current cash price, current bid, total value, contracted amounts, remaining contracted amounts unsold, and/or the like. The GPPM online interface may also provide aggregated totals of the aforementioned data fields 471. In some embodiments, a scheduler component internal to the GPPM may provide up to date market information at regular intervals. In some embodiments, the producer user may refresh the data manually. In some embodiments any or all of these refresh options may be available to the producer user. [ 0065 ] Figure 5 demonstrates how the PAE 507 also described in Figure 2A-B may interact with a GPPM mobile application in proximity to a commodity storage unit belonging to a producer. In this example, a producer 501 is associated with a mobile device 502 which may be enabled to receive Global Positioning Satellite (GPS) 506 communication and/or a wireless tower transmissions for the purpose of determining the location of the mobile device. In one embodiment, the GPPM mobile application may use the location information available to the mobile device in conjunction with the GPPM Inventory Component 590 and Integrated Data structure 580 to determine the proximity of a producer to a commodity storage facility. In some embodiments, proximity to a PAE 507 associated with a storage facility may be detected by the GPPM mobile application. In these instances where the GPPM mobile application determines that the mobile device is in proximity to a storage facility, it may notify the producer of facility proximity and prompt for facility update, which may include volume, value, and/or the like. In this example, the producer may then decide to update the commodity storage facility information using one of the methods, or some such similar method, as described in Figure 2A, such as hardware connection, wireless connection, visual representation, and/or the like. In some instances, the storage facility may not yet have been identified by the producer as a commodity storage to be managed by the GPPM Inventory component and may have been recognized by the GPPM mobile application or by the GPPM Inventory component, as described in more detail in Figure 3. In this example, the GPPM mobile application may prompt the producer to add the storage facility to the GPPM Inventory component. In some embodiments, the PAE may be able to communicate with the GPPM 520 through a wireless or wired connection 530 and do storage facility updates independent of a producer being in proximity to the storage facility. In these embodiments, updating independent of producer location may be scheduled through a GPPM online or mobile application. In some embodiments, this ability may be done through the settings options as described in Figure 4C. The updated inventory information may then be displayed automatically in the GPPM online or mobile interface 508. [0066] Figures 5B-D provide several non-limiting mobile interface examples of the GPPM application. In one example, a non-active GPPM application for producers with enabled proximity alerts 501 displays an update dialog. In this embodiment, the producer has approached a storage facility that is already associated with the account and which has the identifier "Storage Bin #5", which may or may not be how the GPPM internally identifies the storage facility. The producer is notified of the previous update and what volume was recorded then. In this example the producer may opt to update the storage bin again by pressing the "Update" button or may "snooze" the alert, or cause it to temporarily disappear, by pressing the "Not Now" button. In some embodiments, the GPPM may schedule how often alerts will reappear when "snoozed". 1 In some embodiments, the alert may not reappear until the producer has left a specific

2 geographic proximity to the storage facility and then reentered the geographic

3 proximity. In some embodiments, the alert may not reappear until the producer

4 explicitly selects the bin in the active GPPM online or mobile interface for updating. In

5 some embodiments, the producer may set schedule or eliminate the alerts manually

6 through the GPPM application settings.

7 [0067] One example of an active producer GPPM mobile application shows how

8 the GPPM may graphically display the contents of a storage facility associated with a

9 producer account. In this embodiment, the storage facility is shown as an orange

10 cylinder 502 with a darker orange section alongside text indicating commodity levels

11 503. An approximate percentage may be displayed alongside the storage facility

12 graphical representation along with a slider 504 that may allow a producer to manually

13 update commodity levels. In this embodiment, below the graphical facility

14 representation, the mobile application may provide text featuring detailed statistics of

15 the stored commodity 505, such as by way of non-limiting example, the type of

16 commodity stored "Corn", the current bid value of the commodity "$126,060", and

17 dynamic, automated, real-time and/or near real-time market data of the commodity. In is this example, icons tab the application into separate functionalities 506, allowing the

19 producer user to switch between interfaces.

20 [0068] An active producer GPPM mobile application may also inform the

21 producer of integrated and aggregated commodity storage, in a similar manner to the

22 GPPM online "Dashboard" interface described in Figure 4C. The producer is identified

23 and the current integrated value of all the producer's stored commodities is displayed

24 506. The producer may then scroll through discrete stored commodities defined by

25 location, type, internal inventory, external sources, and/or the like 507. In some

26 embodiments, selecting one of the discrete commodities may provides a "click through"

27 where detailed statistics on listed commodities may be available. In one example, this

28 information interface of the GPPM mobile application may be available through one of

29 the tab icons at the bottom of the application. 1 [0069] In some embodiments of the GPPM, online and mobile applications may

2 be created for demand agents ("purchasers") for use in determining nearby

3 commodities available for sale. In some embodiments, producers may make

4 information about available saleable commodities visible to external sources, as

5 described in Figure 2A and Figure 4C. In some embodiments, an external source may

6 be the GPPM itself, which may provide the information to account holders which are

7 purchasers. In Figure 6A, a GPPM online or mobile interface may allow a purchaser

8 601 to search for nearby commodities for sale. In this example, the GPPM application

9 may communicate with GPPM components to determine commodities in the

10 purchaser's proximity. In some embodiments, the purchaser's proximity may be

11 determined via GPS 608 or through wireless provider towers 609 if the purchaser's

12 GPPM application is mobile. In some embodiments, through either an online or mobile

13 GPPM application, the purchaser may be able to specify the search parameters. By way

14 of non-limiting example, the purchaser may opt for a radial or postal code search 606

15 out of the location of the GPPM application, or from some other location. In some

16 embodiments, the purchaser may specify a geographic region to search which may use

17 city, county, state, or other specified boundaries with which to define the searchable is region. In this example, once a search region has been specified by the GPPM

19 application, the GPPM Inventory Component 620 may use its integrated data structure

20 630 to determine storage facilities 6o4a2, 604b, and 604ε have commodities available

21 for purchase by producer account holders. In one example, the GPPM may issue a

22 database query to determine commodities marked for sale and within a specific

23 geographic region. In the exemplary pseudocode example below, a procedure uses

24 point/circle intersection to simulate the location of a storage facility within a radial

25 search 606. In some embodiments, by way of non-limiting example, searches may be

26 done as point in polygon intersections, the GPPM may pre-order storage facilities by

27 location to allow for faster querying, the GPPM may store postal and/or geographic

28 region information in addition to location coordinates with storage facilities in the

29 integrated data structure, and/or the like.

30

31 CREATE PROCEDURE radial intersect (IN rad DECIMAL) BEGIN

DECLARE location_x DECIMAL;

DECLARE location_y DECIMAL;

DECLARE radius DECIMAL;

Radius = rad;

SELECT Latitude, Longitude

INTO location_x, location_y FROM Purchasers

WHERE Purchaser_id = "5643TSA";

SELECT Storage_id

FROM Facilities

WHERE External_Visibility="true" and EXISTS (power (Latitude - location x, 2) + power (Longitude - location y, 2) <

power ( radius , 2);

END [ 0070 ] In this example, however, the purchaser may not be notified directly of nearby facilities. In some embodiments, the GPPM may preserve the anonymity of local saleable commodities by committing to a minimum number of search results before displaying any available amounts, as described in Figures 7B-7D. In this example, the proximity search 606 may return insufficient results to relay those results to the purchaser. In this embodiment, an expanded search 607 would add storage facilities 6o4ai, 6o4d, 605c, and 6osfi. In some embodiments, the GPPM may determine that a sufficient number of search results to preserve anonymity of producers has been provided and may return the anonymous results to the purchaser. In some embodiments, the GPPM may support advanced search criteria, for example, allowing searches to include limitations or relative weightings for different criteria. Such identifiers or criteria include hard surface roads - relevant for various truck resources (i.e., can the roads support a heavy truck) particularly during certain times of the year, auger capacity, previous (positive/negative) business history, "favorited", etc., in some embodiments while still maintaining relative anonymity. [ 0071 ] Figure 6B provides one example of a mobile interface displaying the results of a purchaser-initiated search, as just described in Figure 6A. In this example, the interface is visually similar to the purchaser commodity information interface described in Figure 5D. The purchaser has specified a commodity search for "corn" and indicated the GPPM query its inventory in a radius of 25 miles from the purchaser's location 651. In this example, nine results have been returned. In some embodiments, the results may be ordered according to shortest path enhancements as described in Figure 7C. In this example, the results are shown in a scrollable list 652 with approximate commodity amounts available for purchase and a text providing the purchaser with the ability to "contact this grower" by selecting a list item. In some embodiments, selecting a list item would immediately generate a purchase order through the GPPM which may appear as a blind offer to a producer. In some embodiments, selecting a list item may lead to a dialog asking the purchaser if they would like to make an offer to the producer of this commodity. In some embodiments, selecting the a list item may lead a secondary interface in which additional information about the commodity might be displayed and/or the like. [0072] In some embodiments, the GPPM facilitated transaction between supply ("producer") and demand-side ("purchaser") parties may be expressed in a data flow diagram, such as Figure 7A wherein both the producers and purchasers may request commodity volumes and prices: the purchasers within a specified region 722 as described in Figures 7B-7D, and the producers with GPPM profile account data 721. These requests 723 are filtered through the GPPM which may use GPPM inventory data to return dynamic, automated, real-time and/or near real-time volume and price data to both producers and purchasers 724a-b. The below example HTTP(S) GET message includes an XML-formatted storage facility data record response 724a from a GPPM server:

GET /facilities+id=3581T .php HTTP/1.1

Host: GPPMserverl

Content-Type: Application/XML

Content-Length: 1200

<?XML version = "1.0" encoding = "UTF-8"?>

< storage_facility producer_id="3581T"> <id>43RTK/id>

<facility type>field</ facility type>

<location>

<latitude>46.13</latitude>

<longitude>-101.85</longitude>

</location>

<time stamp format="astronomical">

<hour>8</hour>

<minute>22</minute>

</time stamp>

<date format="small endian" year_length="2 "> 12-05-45 </date> <volume unit="bushels"> 12000 <\volume>

</ storage facility>

< storage facility producer id="3581T">

<id>43RT2</id>

<facility type>silo</facility type>

<location>

<latitude>46.14</latitude>

<longitude>-101.88</longitude>

</location>

<time stamp format="astronomical">

<hour>14</hour>

<minute>35</minute>

</time stamp>

<date format="small endian" year_length="2 "> 12-07-45 </date> <volume unit="bushels"> 11000 <\volume>

</ storage_facility>

[0073] The below example volume purchase HTTP(S) POST request 723 to the GPPM Inventory Component may also return an XML-formatted storage facility data record response 724b from a GPPM server, an example of which is above. A GPPM online or mobile interface may then present the data records in an anonymous format that may require further interaction from a purchaser to result in an order request: 1

2 POST /facilities/locations .php HTTP/1.1

3 User-Agent: GPPMClient

4 Content-Type: application/x- -form-urlencoded

5 Content-Length: 70

6

7 latitude=45.12 &longitude=-

8 96.54&radius=25&unit=miles&min bushels=20000

9

10 [0074] Purchasers may then make a purchase requests through the GPPM online

11 or mobile interface 725, and may specify necessary components of the purchase such as

12 by way of non-limiting example, volume, price, delivery date, and/or the like. The

13 GPPM application may pass the request 726 to the GPPM components which may

14 notify the producer of purchase request through a GPPM online or mobile interface

15 728. In some embodiments, the GPPM facilitates competition/negotiation, for

16 example, allowing a producer to negotiate with multiple offers.

17 [0075] The following pseudocode demonstrates how a purchaser may select from

18 a list of immediate purchase options generated in 724b which may have been

19 anonymized in a GPPM interface. A mobile interface listview may call a function when

20 an item in the list has been selected. The selected item returns a specific facility from

21 the database:

22

23 CFacilityRecord onltemSelected (ListVie view, int pos, long id)

24 {

25 //an item in the generated anonymous list has been selected.

26 //It corresponds to storage in the GPPM facilities db. Respond

27 // with additional information

28 int facilityID= mFacilitiesArray [pos ] ;

29 CFacilityRecord newRec = new CFacilityRecord () ;

30 SQLDatabase db= this . getReadableDatabase ("Facilities") ;

31 Cursor c = db. select (facilitylD) ;

32 //The cursor is now at the row in the db where the correct // facility is located. If it is not null, extract the // data and return it.

if (c != NULL) {

CFacilityRecord ne Rec = CFacilityRecord: : Convert (c) ;

}

else{

GenerateError () ;

}

return newRec; }

[0076 ] The purchaser may request further information from the GPPM interface and then may issue a purchase order 726, based on the further information provided. The following example POST request shows a pending purchase order generated:

POST /inventory/produce/inventorymatch . asp HTTP/1.

User-Agent: GPPMClient

Content-Type : application/x-www-form-urlencoded

Content-Length: 73 id=45FT6&facility=23RQ8&volume=24500&

price=13.21 &deliverydate=2 &unit=days [0077] The GPPM application may or may not be currently active to allow notifications or alerts to be generated for the producer in case of a pending GPPM purchase transaction. Allowing the GPPM to alert the producer of a pending transaction during inactivity of the GPPM online or mobile application may be modifiable from the producer account settings in either/both of the GPPM online or mobile applications. A producer may then approve or deny the commodity sale 729 through a GPPM application interface which communicates the order response to the GPPM components 730. In this example if the producer has agreed to the transaction, the GPPM may further facilitate the transaction 731 as described above. In this example, the GPPM may act as a purchase order service with delivery details 732. In some embodiments, the GPPM may facilitate the purchase order through a third party, through a separate transactional service, and/or the like. In some embodiments, the GPPM may, based on transaction data (e.g., transaction acceptance/execution) execute, prompt and/or provide one or more actions, such as triggering a sale, updating a producer's and/or purchaser's inventory, generating a purchase agreement/ticket/contract, prompt pickup/delivery, etc. Parallel to transaction facilitation, an automated scheduling service such as Cron, or some other such service, may be requesting and receiving market data updates 733. Market data may include information such as, but not limited to: market data/market feed source/ID (e.g., AMEX, CBOT, KCBOT, MGE, CME, NASDAQ, NYMEX, NYSE, Bloomberg, ddf, etc.); agricultural asset type (corn, soybean, wheat, etc.) and/or corresponding symbol(s); spot price; bid price; ask price; and/or the like. [0078 ] The GPPM may determine how often market data updates are received or GPPM account holders may modify scheduling in their account settings. In this example, if the GPPM becomes a transactional center for a significant portion of supply and demand-side agents, the GPPM may have a significant data set of transactional and market information due to its account base and may be able to provide a feed of market data updates 734 to account holders and/or external sources. [0079 ] Figures 7B -7C describe examples of a flowchart wherein a purchaser 720 begins a new search for saleable produce available through the GPPM from producer accounts that have made such produce visible. In Figure 7B, the search may be considered radial, by postal code, or by geographic region 706, which is then filtered by producer commodity visibility settings. In Figure 7C, the GPPM may further improve proximity searches by introducing a shortest path ordering to the results 708. In this example, the GPPM would determine not just nearby saleable commodities, but take into account access to these commodities along common travel paths. As demonstrated in Figure 7C, some commodity facilities may be equidistant from the purchaser, but one may be more accessible to the purchaser than another by common travel paths, including but not limited to roads, railway lines, access paths, and/or the like. In this 1 example, the GPPM may rank commodities 7o8b-c first by absolute distance and then

2 by shortest path access. In both examples, search results may be subject to a minimum

3 quantity in order to preserve the anonymity of producers 709. If the purchaser elects to

4 expand the search parameters, the search repeated with a larger region, in which the

5 GPPM may or may not include shortest path enhancements. Shortest path

6 enhancements may be available as a setting in the GPPM application or may be

7 automatic to the GPPM search system. If the purchaser elects not to expand the search

8 results, the GPPM may display in either its online or mobile interface that there is no

9 inventory within the specified parameters for sale or that there is insufficient inventory

10 within the specified parameters 712. If there are sufficient search results to preserve

11 anonymity, the GPPM may display the search results in either its online or mobile

12 application interface 711.

13 [0080] Continuing the examples of Figures 7B-C, Figure 7D expands the example

14 to demonstrate how multiple purchasers 720 may be using the GPPM search system

15 through their accounts either serially or in parallel. In this example, many purchasers

16 are simultaneously performing searches for saleable commodities through the GPPM

17 712. Purchasers with sufficient search results may select a commodity for purchase 713. is Because of the anonymous nature of the search results, purchasers may not be able to

19 determine the location or producer of the commodity in advance of selecting a

20 commodity for purchase. The purchaser submits a purchase request to the GPPM

21 Inventory Matching Component 740 which may then tie the anonymous search result

22 to data within its inventory data structure. In this example, the GPPM notifies the

23 producer of a "blind" offer or offers for the producer's commodities 714, "blind"

24 indicating that the purchaser may be, at this time, also anonymous to the producer.

25 Although exemplary blind offers are discussed herein, it is to be understood that the

26 GPPM facilitates blind offers and/or blind bids, depending on the implementation. In

27 some embodiments, the GPPM may allow producers to solicit bids. Because searches

28 may be parallel, more than one purchaser may submit offers for the same commodity.

29 The producer, through the GPPM Integration Component 740, may be receiving

30 automatic updates 715 about the producer's assets, current market values, previous

31 benchmarks, sale targets and/or the like. The GPPM Integration Component may 1 continue to access external sources and accounts of the producer to provide dynamic,

2 automated, real-time and/or near real-time asset value to the producer, sources and

3 accounts including, by way of non-limiting example, producer inventory sales data 780,

4 agribusiness producer sales data 790, university benchmarks 770, outside vendor

5 market strategies 760, and/or the like. The producer may then accept a contract offer

6 716 through the GPPM Inventory Matching Component. In some embodiments, the

7 GPPM may then offer other services to the purchaser and producer account holders to

8 further facilitate the sale, such as electronic funds transfer, shipping resources,

9 insurance resources, the ability to attach ratings to the transaction, and/or the like. In0 some embodiments, the GPPM may provide purchase/agribusiness components with1 additional analysis functionality. These tools may allow a user to integrate user- and2 GPPM-supplied data in net price/break-even calculators, customer and prospect3 database(s), producer behaviors, public records, producer and agribusiness ratings. In4 some embodiments, tools may be provided to allow forecasting (e.g., forecasting profit5 based on different scenarios and choices), and such tools may allow for inputting or6 selection of different thresholds and goals, such as risk tolerance, balance sheet items,7 etc. s [ 0081 ] Figure 7E shows one example of how a producer 701 may make saleable9 commodities visible to external sources through the GPPM. In this example, using0 either an online or mobile GPPM interface, the producer enters inventory values1 through GPPM systems 702, in which GPPM systems refers to the methods and2 apparatuses and systems by which inventory can be associated with a producer's3 account through the GPPM. The GPPM Inventory Component 730 may then store the4 inventory in an inventory data structure 710, which may or may not be associated with5 other GPPM data structures previously described. In this example, subsequent to the6 association of inventory with the producer, the producer may choose to allow external7 sources— in this example, a purchaser— to view saleable inventory 703. If the producer8 agrees, the producer's saleable inventory will appear in purchaser searches 704,9 otherwise it will not 705. In some embodiments, the GPPM may add information to0 inventory stored in the inventory data structure that indicates it is saleable and visible. In some embodiments, the GPPM may place saleable/visible inventory into a separate data structure from nonsaleable/invisible inventory. [0082] In some embodiments, a position tracker (PT) component may provide additional management and oversight options within the GPPM. In some implementations, a PT component is configured to receive data regarding futures, options, and/or other related financial instrument positions associated with one or more producers. The GPPM may utilize such positions in providing account overviews to users, such as producers, for example, incorporating a producer's futures and options positions and aggregating them with a producer's cash grain inventory. In some embodiments of the GPPM, a PT or other component may use option delta factors to deliver a bushel equivalent in position equations. As discussed above, market data, including dynamic, automated, real-time and/or near real-time market data, may be received by the GPPM, and in some implementations, instruments may be weighted and valued based on the received data. For example, in one embodiment, options may not all be treated as equal, as deep in the money options price behavior may be very close to that of grain futures contracts, but deep out of the money options may be insulated from futures price movement. In some implementations of the GPPM, the PT or like component may provide an notification or other alerting mechanism when aggregated futures, options, and/or cash positions are outside of a single hedge quantity. In a corresponding example interface, a red light/green light display may be provided to alert users when they are out of position. In one such embodiment, bushel equivalents may be dynamically updated in real-time or near real-time according to which positions are held in a producer (or other customer) account. [0083] As discussed above, some implementations of the GPPM may provide an integrated online and mobile facility that allows a user, such as producer/farmer to understand his or her current agricultural asset (e.g., grain) inventory and positions across his or her planted fields, his or her on-farm storage, and his or her agribusiness storage and positions. In some embodiments, a producer may additionally or alternatively refer to a producer representative, such as a farm manager, and/or a producer management entity, such as a farm management company. Position data may be updated, periodically or on the fly, with market pricing to provide an accurate understanding of current values. In some embodiments, historical information, portfolio plans/strategies, and/or benchmark data may also be integrated into the provided information. For example, in some implementations the GPPM facilitates a producer comparing his or her sales on old crop and new crop commodities as a percentage against outside market strategies promoting better grain sales/marketing decisions. The GPPM may provide feedback and tracking for particular sales strategies, and/or may provide suggested pricing or marketing. For example, if a producer has sold 20% of an old crop or other agricultural asset, and a particular business strategy (e.g., as previously selected by the producer) indicates the producer's sales should be approximately 40%, a variance report or other notification may be generated. [0084] As discussed above, in some embodiments, the GPPM provides integration of producer (e.g., farmer) accounts, production and inventory data, which may include data available from one or more agribusinesses, thus providing comprehensive information on which producers may make marketing and business decisions with consolidated account data. In one implementation, a producer may view consolidated agribusiness account data combined with yields, inventory levels and commodity futures and local cash bid price data to track total inventory values. The GPPM may allow a producer to share selected data with necessary stakeholders to simplify recordkeeping and allow better management of his or her businesses with consolidated near real time data. For example, in one embodiment, a producer signs up with a GPPM account via a website application and provides necessary credentials for all third party accounts they wish to pull data from, with some manual data entry. GPPM components aggregate all data into one location and ties in commodity futures and localized cash bid data nearest the producer's geographic location(s). The producer may then view reports of near real time inventory values with combined data to better understand sales and marketing decisions. The producer may, in some implementations, share various reports from the GPPM with key stakeholders, such as banker and insurance companies. [0085] As discussed above, some embodiments of the GPPM provide users (e.g., agribusiness users) to conduct area (e.g., radius) searches of on-farm commodity (e.g., grain) inventory. For example, in one implementation, GPPM features allow an agribusiness to view local (e.g., in concentric circles in a radius from their facilities) the aggregate amount of on-farm commodities that are available for purchase. In some such implementations, the GPPM data provides for increasing accuracy with respect to price determination to originate grain. In some implementations, producer data may only be shown in aggregate form with minimum number of producers listing to ensure anonymity. In some implementations, a producer may have the ability to choose to share inventory through a GPPM matching engine or like component (e.g., SCHNEIDER ELECTRIC/TELVENT DTN matching engine and/or the like), thus increasing the chance for a better bid. In some implementations, the GPPM provides agribusinesses and/or end-users purchasing grain a view of available inventory in aggregate form within a geographical radius from their grain receiving location. In one implementation, producers may have the ability voluntarily to share actual inventory levels (e.g., via a matching engine component) and potentially receive a better price, depending upon immediate grain inventory needs of the agribusiness. [0086 ] For example, in one implementation, if an agribusiness, such as a grain company, is loading a unit train at a particular location and comes up short of grain, the GPPM can provide the closest location(s) of available inventory. Distance of available grain inventory may determine what the agribusiness has to pay (bid) for such grain. Producer on-farm grain may be shown in aggregate form (providing producer anonymity) to the agribusiness and the agribusiness can request from the GPPM, e.g., via an inventory application/component, to match up producers who wish to share inventory for sale. The GPPM may then compile producer grain inventory levels with a specified minimum of producers per geographic area (e.g., a minimum of 6 producers per zip code, thus providing anonymity), in aggregate form with no producer names shared. The agribusiness may then access grain inventory data with zip code or latitude/longitude search in concentric circles from their location. The agribusiness may, if specified, be matched up with producers who previously selected option to be made inventory visible to purchasers for potential sale. In such embodiments, an agribusiness or other purchaser is provided with visibility to grain inventory levels located on farms to fulfill grain merchandising and sales needs while allowing producers, to share said inventory levels to potentially obtain a better price bid. [ 0087] As discussed above, in some embodiments, the GPPM notifies users, such as farm producers, when they are near storage, such as a grain bin or field, containing stored or growing inventory, allowing them to update inventory and yield levels for total crop portfolio valuation. By providing this information, the GPPM facilitates improved business decisions, and may provide improved grain sales techniques, accurate insurance coverage and achievement of agricultural lending requirements. [ 0088 ] In some such implementations, the GPPM provides remote update with a mobile smartphone to track stored and growing commodity grain inventory data. The GPPM may also remind a producer to update inventory/yield levels when near or at the exact location of commodities stored or growing. This implementation facilitates tracking and updating inventory and yield values remotely, and maintains accurate up- to-date inventory levels by making adjustments when a producer is at a bin/field site. [ 0089 ] In some embodiments, the GPPM may be configured for livestock. In such an embodiment, a purchaser may be a livestock raiser and/or a feedlot, and a seller may be an agribusiness, feed processor, and/or elevator. A livestock raiser may input standing orders (and offers) for feed to purchase to keep their inputs steady and not disrupt their feeding schedule (e.g., 1000 bushels of corn or 2 tons of soybean meal needs to be delivered every week). A seller (e.g., feed processor) can search for nearby orders/offers submitted by a livestock raiser of feed to purchase, providing visibility regarding who needs feed and when. Such embodiments of the GPPM improve scheduling and delivery efficiencies. Additionally, in some embodiments, bin storage is used for feed also (e.g., bulk bins, feed/commodity sheds, etc). Some implementations may utilize PAEs or other devices to provide updates (e.g., "running low - need feed now"). Efficiencies may be provided by competitive pricing, scheduling and delivery. [ 0090 ] In some embodiments, the transaction between one or more livestock raisers and/or feedlots ("purchasers") and agribusinesses, feed processors, and/or elevators (producers) is facilitated by a GPPM Livestock Feed Matching ("LFM") Component, for example as shown in the data flow diagram of Figure 8A, wherein both the livestock raisers and/or feedlots and agribusinesses, feed processors, and/or elevators may request commodity volumes and prices: the purchasers within a specified region 822, and the producers with GPPM profile account data 821. These requests relating to feed 823 are filtered through the GPPM which may use GPPM inventory data to return dynamic, automated, real-time and/or near real-time volume and price data to both producers and purchasers 824a-b. The below example HTTP(S) GET message includes an XML-formatted storage facility data record response 824a from a GPPM server:

GET /facilities+id=3581T .php HTTP/1.1

Host: GPPMserverl

Content-Type: Application/XML

Content-Length: 1200

<?XML version = "1.0" encoding = "UTF-8"?>

< feed storage facility producer id="3581T">

<id>42RTK/id>

<facility type>field</ facility type>

<location>

<latitude>46.16</latitude>

<longitude>-101.9</longitude>

</ location>

<time stamp format="astronomical">

<hour>7</hour>

<minute>12</minute>

</time stamp>

<date format="small endian" year_length="2 "> 12-06-45 </date> <volume unit="bushels"> 1500 <\volume>

</ feed_storage_facility>

< feed storage facility producer id="3581T">

<id>42RT2</id>

<facility_type>silo</ facility_type> 1 <location>

2 <latitude>46.14</latitude>

3 <longitude>-101.88</longitude>

4 </location>

5 <time stamp format="astronomical">

6 <hour>14</hour>

7 <minute>35</minute>

8 </time stamp>

9 <date format="small endian" year_length="2 "> 12-05-15 </date>

10 <volume unit="bushels"> 1000 <\volume>

11 </ feed storage facility>

12

13

14 [0091] The below example volume purchase HTTP(S) POST request 823 to the

15 GPPM Inventory Component may also return an XML-formatted storage facility data

16 record response 824b from a GPPM server, an example of which is above. A GPPM

17 online or mobile interface may then present the data records in an anonymous format

18 that may require further interaction from a purchaser to result in an order request:

19

20 POST /facilities/locations .php HTTP/1.1

21 User-Agent: GPPMClient

22 Content-Type: application/x- -form-urlencoded

23 Content-Length: 70

24

25 latitude=45.12 &longitude=-

26 96.54&radius=25&unit=miles&min bushels=2000

27

28 [0092] Purchasers may then make a purchase requests through the GPPM online

29 or mobile interface 825, and may specify necessary components of the purchase such as

30 by way of non-limiting example, volume, price, delivery date, and/or the like. The

31 GPPM application may pass the request 826 to the GPPM components which may

32 notify the producer of purchase request through a GPPM online or mobile interface

33 828. [0093] The following pseudocode demonstrates how a purchaser may select from a list of immediate purchase options generated in 824b which may have been anonymized in a GPPM interface. A mobile interface listview may call a function when an item in the list has been selected. The selected item returns a specific facility from the database:

CFacilityRecord onltemSelected (Listview view, int pos, long id) {

//an item in the generated anonymous list has been selected.

//It corresponds to storage in the GPPM facilities db. Respond

// with additional information

int facilityID= mFacilitiesArray [pos ] ;

CFacilityRecord newRec = new CFacilityRecord () ;

SQLDatabase db= this . getReadableDatabase ("Facilities") ;

Cursor c = db. select (facilitylD) ;

//The cursor is now at the row in the db where the correct

// facility is located. If it is not null, extract the

// data and return it.

if (c != NULL) {

CFacilityRecord newRec = CFacilityRecord: : Convert (c) ;

}

else{

GenerateError ( ) ;

}

return newRec; }

[0094] The purchaser may request further information from the GPPM interface and then may issue a purchase order 826, based on the further information provided. The following example POST request shows a pending purchase order generated: POST /inventory/produce/inventorymatch . asp HTTP/ 1.1

User-Agent: GPPMClient

Content-Type: application/x- -form-urlencoded

Content-Length: 73 id=45FT6&facility=23RQ8&volume=24500&

price=13.54&deliverydate=2&unit=days [0095] The GPPM application may or may not be currently active to allow notifications or alerts to be generated for the producer in case of a pending GPPM purchase transaction. Allowing the GPPM to alert the producer of a pending transaction during inactivity of the GPPM online or mobile application may be modifiable from the producer account settings in either/both of the GPPM online or mobile applications. A producer may then approve or deny the commodity sale 729 through a GPPM application interface which communicates the order response to the GPPM components 830. In this example if the producer has agreed to the transaction, the GPPM may further facilitate the transaction 831 as described above. In this example, the GPPM may act as a purchase order service with delivery details 832. In some embodiments, the GPPM may facilitate the purchase order through a third party, through a separate transactional service, and/or the like. In some embodiments, the GPPM may, based on transaction data (e.g., transaction acceptance/execution) execute, prompt and/or provide one or more actions, such as triggering a sale, updating a producer's and/or purchaser's inventory, generating a purchase agreement/ticket/contract, prompt pickup/delivery, etc. [0096] In some embodiments, the GPPM may provide various crop purchase management/agribusiness tools. For example, the GPPM may provide net price/break- even tools, where a user (e.g., agribusiness/purchaser) of the GPPM receives tools and information including an agribusiness' own pricing data (e.g., margin and destination bids), net price calculators (including but not limited to standard and customized freight tables/schedules), break even calculators with margin, storage and carry costs (which may be customizable by the user), competitive pricing tools (e.g., bid and basis analysis) providing visibility of the competitive landscape of the competing prices. The 1 GPPM may also allow the user to utilize their current customer and prospect

2 database(s) within the systems/tools, an allowing a purchaser/agribusiness to create a

3 business relationship with the producers before finalizing the transaction (e.g.,

4 validating the operator is credible, for example via credit check, background check, etc.)

5 to address counter-party risk. In some embodiments, the GPPM may provide a risk

6 management component (e.g., Risk component 952) to address counter-party risk, for

7 example, to deal with the threat of "phantom farms" selling physical grain or selling

8 physical grain more than once.

9 [0097] Users may also leverage the GPPM tools, such as geo-search and

10 transaction tools, with their own customers and prospects databases. In some

11 implementations, customer databases may be integrated manually (e.g., spreadsheets

12 uploaded), updated, provided via web service(s)/APIs. The tools may provide actual

13 coordinates of customers' bins, allowing automated inventor identification via address

14 entry as discussed above. The tools may also assign an average overall grain sales range

15 to forecast the amount of grain (and storage location) for a producer.

16 [0098] The GPPM may also provide tools for producer behavior

17 monitoring/analysis and buyer/seller ratings on experiences. Once enough integration is has been established, anonymous behaviors may be analyzed, e.g., Producer A counters

19 50% of the time, Producer B sells 100% of grain each year, Producer C has 20% of his or

20 her grain left to sell, etc. Some tools may also allow buyers and sellers to rate their

21 experience with the other party, and those rating may be made available, including, but

22 not limited to, ratings on overall experience, customer service, prices, and/or the like.

23 FIGURES 8B-8F provide example interfaces of a web portals in which the GPPM may

24 be implemented.

25 [0099] In some embodiments, the GPPM transforms producer crop asset

26 information via GPPM components into dynamic, automated, real-time, and/or near

27 real-time inventory updates. In one implementation, the GPPM creates a producer

28 crop asset management account and receives crop asset storage resource information

29 including storage resource location data for an at least one crop storage resource. The

30 received crop asset storage resource information is associated with the producer crop asset management account. One or more mobile devices may then be associated with the producer crop asset management account. The GPPM determines when one of the mobile devices is within a specified distance of the at least one crop storage resource location and generates a notification on the mobile device that the mobile device is within the specified distance of a crop storage resource location. The GPPM receives dynamic, automated, real-time and/or near real-time crop volume data for the crop storage resource and associates it with the producer crop asset management account.

[ooloo ] Additional embodiments of the GPPM may include and/or comprise:

[ooioi] l. A crop asset tracking processor-implemented method, comprising: providing, creating and/or enabling access to a producer crop asset management account for a producer; receiving crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; associating received crop asset storage resource information with the producer crop asset management account; associating an at least one mobile device with the producer crop asset management account; determining via a processor when the at least one mobile device is within a specified distance of the location of the at least one crop storage resource; generating a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one crop storage resource, the notification including a request to provide real-time crop state data for the at least one crop storage resource; receiving real-time crop state data for the at least one crop storage resource; and associating the received real-time crop state data with the producer crop asset management account.

[00102] 2. The method of embodiment 1, wherein the at least one crop storage resource is a crop field.

[00103] 3. The method of embodiment 1, wherein the at least one crop storage resource is a harvested crop storage facility.

[00104] 4. The method of embodiment 3, wherein the harvested crop storage facility is a storage bin. [ 00105 ] 5. The method of any of embodiments 1-4, further comprising monitoring the location of the at least one mobile device.

[ 00106 ] 6. The method of any of embodiments 1-5, wherein receiving real-time crop state data comprises receiving an at least one image captured by the mobile device.

[ 00107] 7. The method of any of embodiments 1-5, wherein receiving real-time crop state data comprises receiving precision agricultural equipment data.

[ 00108 ] 8. The method of any of embodiments 1-7, wherein the crop state data comprises volume data.

[ 00109 ] 9. The method of any of embodiments 1-7, wherein the crop state data comprises an indication that the crop is ready for harvest.

[ 00110 ] 10. A crop asset tracking apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: create a producer crop asset management account for a producer; receive crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; associate received crop asset storage resource information with the producer crop asset management account; associate an at least one mobile device with the producer crop asset management account; determine when the at least one mobile device is within a specified distance of the at least one crop storage resource location; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the at least one crop storage resource location, the notification including a request to provide real-time crop volume data for the at least one crop storage resource; receive real-time crop volume data for the at least one crop storage resource; and associate the received realtime crop volume data with the producer crop asset management account.

[ 00111 ] 11. The apparatus of embodiment 10, wherein receiving real-time crop volume data comprises receiving an at least one image captured by the mobile device. [ 00112 ] 12. A processor-readable non-transitory tangible medium storing processor-issuable crop asset tracking instructions to: create a producer crop asset management account for a producer; receive crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; associate received crop asset storage resource information with the producer crop asset management account; associate an at least one mobile device with the producer crop asset management account; determine when the at least one mobile device is within a specified distance of the at least one crop storage resource location; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the at least one crop storage resource location, the notification including a request to provide real-time crop volume data for the at least one crop storage resource; receive real-time crop volume data for the at least one crop storage resource; and associate the received real-time crop volume data with the producer crop asset management account.

[ 00113 ] 13. A crop asset tracking apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: provide, create and/or enable access to a producer crop asset management account for a producer; receive crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; associate received crop asset storage resource information with the producer crop asset management account; associate an at least one mobile device with the producer crop asset management account; determine when the at least one mobile device is within a specified distance of the location of the at least one crop storage resource; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one crop storage resource, the notification including a request to provide real-time crop state data for the at least one crop storage resource; receive real-time crop state data for the at least one crop storage resource; and associate the received real-time crop state data with the producer crop asset management account. [ 00114 ] 14. The apparatus of embodiment 13, wherein the at least one crop storage resource is a crop field. [ 00115 ] 15. The apparatus of embodiment 13, wherein the at least one crop storage resource is a harvested crop storage facility. [ 00116 ] 16. The apparatus of embodiment 15, wherein the harvested crop storage facility is a storage bin. [ 00117] 17. The apparatus of any of embodiments 13-16, further comprising instructions to monitor the location of the at least one mobile device. [ 00118 ] 18. The apparatus of any of embodiments 13-17, wherein receiving real- time crop state data comprises receiving an at least one image captured by the mobile device. [ 00119 ] 19. The apparatus of any of embodiments 13-17, wherein receiving real- time crop state data comprises receiving precision agricultural equipment data. [ 00120 ] 20. The apparatus of any of embodiments 13-17, wherein receiving real- time crop state data comprises receiving satellite data. [ 00121] 21. The apparatus of any of embodiments 13-17, wherein receiving real- time crop state data comprises receiving satellite image data. [ 00122 ] 22. The apparatus of any of embodiments 13-21, wherein the crop state data comprises volume data. [ 00123 ] 23. The apparatus of any of embodiments 13-21, wherein the crop state data comprises an indication that the crop is ready for harvest. [ 00124] 24. A processor-readable non-transitory tangible medium storing processor-issuable crop asset tracking instructions to: provide, create and/or enable access to a producer crop asset management account for a producer; receive crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; associate received crop asset storage resource information with the producer crop asset management account; associate an at least one mobile device with the producer crop asset management account; determine when the at least one mobile device is within a specified distance of the location of the at least one crop storage resource; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one crop storage resource, the notification including a request to provide real-time crop state data for the at least one crop storage resource; receive real-time crop state data for the at least one crop storage resource; and associate the received real-time crop state data with the producer crop asset management account. [ 00125 ] 25. The medium of embodiment 24, wherein the at least one crop storage resource is a crop field. [ 00126 ] 26. The medium of embodiment 24, wherein the at least one crop storage resource is a harvested crop storage facility. [ 00127] 27. The medium of embodiment 26, wherein the harvested crop storage facility is a storage bin. [ 00128 ] 28. The medium of any of embodiments 24-27, further comprising instructions to monitor the location of the at least one mobile device. [ 00129 ] 29. The medium of any of embodiments 24-28, wherein receiving real- time crop state data comprises receiving an at least one image captured by the mobile device. [ 00130 ] 30. The medium of any of embodiments 24-28, wherein receiving real- time crop state data comprises receiving precision agricultural equipment data. [ 00131 ] 31. The medium of any of embodiments 24-28, wherein receiving real-time crop state data comprises receiving satellite data. [ 00132 ] 32. The medium of any of embodiments 24-28, wherein receiving real- time crop state data comprises receiving satellite image data. [ 00133 ] 33. The medium of any of embodiments 24-32, wherein the crop state data comprises volume data. [ 00134] 34. The medium of any of embodiments 24-32, wherein the crop state data comprises an indication that the crop is ready for harvest. [ 00135 ] 35. A crop asset tracking system, comprising: means to provide, create and/or enable access to a producer crop asset management account for a producer; means to receive crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; means to associate received crop asset storage resource information with the producer crop asset management account; means to associate an at least one mobile device with the producer crop asset management account; means to determine when the at least one mobile device is within a specified distance of the location of the at least one crop storage resource; means to generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one crop storage resource, the notification including a request to provide real-time crop state data for the at least one crop storage resource; means to receive real-time crop state data for the at least one crop storage resource; and means to associate the received real-time crop state data with the producer crop asset management account. [ 00136 ] 36. The system of embodiment 35, wherein the at least one crop storage resource is a crop field. [ 00137] 37. The system of embodiment 35, wherein the at least one crop storage resource is a harvested crop storage facility. [ 00138 ] 38. The system of embodiment 37, wherein the harvested crop storage facility is a storage bin. [ 00139 ] 39. The system of any of embodiments 35-38, further comprising means to monitor the location of the at least one mobile device. [ 00140 ] 40. The system of any of embodiments 35-39, wherein receiving real-time crop state data comprises receiving an at least one image captured by the mobile device.

[ 00141 ] 41. The system of any of embodiments 35-39, wherein receiving real-time crop state data comprises receiving precision agricultural equipment data.

[ 00142 ] 42. The system of any of embodiments 35-39, wherein receiving real-time crop state data comprises receiving satellite data.

[ 00143 ] 43. The system of any of embodiments 35-39, wherein receiving real-time crop state data comprises receiving satellite image data.

[ 00144 ] 44. The system of any of embodiments 35-43, wherein the crop state data comprises volume data.

[ 00145 ] 45. The system of any of embodiments 35-43, wherein the crop state data comprises an indication that the crop is ready for harvest.

[ 00146 ] 46. An agricultural commodity asset management processor-implemented method, comprising: providing, creating, maintaining, and/or enabling access to an agricultural commodity asset management account for an agricultural asset producer; receiving harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receiving actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; receiving in-field agricultural asset information for an at least one agricultural asset associated with the agricultural asset producer, the infield agricultural asset information including agricultural asset crop type and agricultural asset location data; receiving agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; receiving agricultural asset market data; determining via a processor an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; receiving real-time update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; updating the determined agricultural asset portfolio value based on the received real-time update information; and outputting the updated agricultural asset portfolio value for the agricultural commodity asset management account.

[ 00147] 47. The method of embodiment 46, wherein the real-time update information is provided via a mobile device associated with the agricultural asset producer.

[ 00148 ] 48. The method of embodiment 46 or 47, wherein the at least one harvested agricultural asset storage resource is on-farm storage.

[ 00149 ] 49. The method of any of embodiments 46-48, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer.

[ 00150 ] 50. An agricultural commodity asset management apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: provide, create, maintain and/or enable access to an agricultural commodity asset management account for an agricultural asset producer; receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; receive in-field agricultural asset information for an at least one agricultural asset associated with agricultural asset producer, in-field agricultural asset information including agricultural asset crop type and location data; receive agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; receive agricultural asset market data; determine an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; receive real-time update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; update the determined agricultural asset portfolio value based on the received real-time update information; and output the updated agricultural asset portfolio value for the agricultural commodity asset management account.

[ 00151] 51. The apparatus of embodiment 50, wherein the real-time update information is provided via a mobile device associated with the agricultural asset producer.

[ 00152 ] 52. The apparatus of embodiment 50 or 51, wherein the at least one harvested agricultural asset storage resource is on-farm storage.

[ 00153 ] 53. The apparatus of embodiment 50, 51 or 52, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer.

[ 00154] 54. A processor-readable tangible medium storing processor-issuable agricultural commodity asset management instructions to: provide, create, maintain and/or enable access to an agricultural commodity asset management account for an agricultural asset producer; receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; receive in-field agricultural asset information for an at least one agricultural asset associated with agricultural asset producer, in-field agricultural asset information including agricultural asset crop type and location data; receive/request agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; receive/request agricultural asset market data; determine an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; receive/request real-time update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; update the determined agricultural asset portfolio value based on the received real-time update information; and output the updated agricultural asset portfolio value for the agricultural commodity asset management account.

[ 0 0 155 ] 55. The medium of embodiment 54, wherein the real-time update information is provided via a mobile device associated with the agricultural asset producer.

[ 0 0 156 ] 56. The medium of embodiment 54 or 55, wherein the at least one harvested agricultural asset storage resource is on-farm storage.

[ 0 0 157] 57. The medium of embodiment 54, 55, or 56, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer.

[ 0 0 158 ] 58. An agricultural commodity asset management system, comprising: means to provide, create, maintain and/or enable access to an agricultural commodity asset management account for an agricultural asset producer; means to receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; means to receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; means to receive in-field agricultural asset information for an at least one agricultural asset associated with agricultural asset producer, in-field agricultural asset information including agricultural asset crop type and location data; means to receive agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; means to receive agricultural asset market data; means to determine an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; means to receive real-time update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; means to update the determined agricultural asset portfolio value based on the received real-time update information; and means to output the updated agricultural asset portfolio value for the agricultural commodity asset management account. [ 00159 ] 59. The system of embodiment 58, wherein the real-time update information is provided via a mobile device associated with the agricultural asset producer. [ 00160 ] 60a. The system of embodiment 58 or 59, wherein the at least one harvested agricultural asset storage resource is on-farm storage. [ 00161 ] 60b. The system of embodiment 58, 59 or 60a, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer. [ 00162 ] 61. A crop purchase management processor-implemented method, comprising: receiving crop storage resource information for each of a plurality of crop producers, the crop storage resource information including crop storage resource location data, stored crop type data, and stored crop volume data; receiving a location- based, crop-specific purchase inquiry from an at least one purchaser; determining via a processor an aggregate crop volume available for purchase from the received crop storage resource information based on the location-based, crop-specific purchase inquiry and the crop storage resource location data, stored crop type data, and stored crop volume data, the determination comprising accessing and/or utilizing data from at least a threshold number of crop producers; providing the determined aggregate crop volume available for purchase to the at least one purchaser in response to the received location-based, crop-specific purchase inquiry; receiving a purchase request from the purchaser based on the provided aggregate crop volume available for purchase, the purchase request specifying at least one of a crop type, a crop purchase volume and crop purchase price; and facilitating a transaction for the specified crop type between the purchaser and at least one of the plurality of crop producers based on the received purchase request. [ 00163 ] 62. The method of embodiment 61, wherein the received location-based, crop-specific purchase inquiry includes initial boundary parameters defining a geographic search area. [ 00164 ] 63. The method of embodiment 62, wherein the initial geographic boundary parameters include a geographic search radius. [ 00165 ] 64. The method of embodiment 62 or 63, further comprising: modifying the initial boundary parameters to provide data from at least the threshold number of crop producers. [ 00166 ] 65. A crop purchase management apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor- issuable instructions to: receive crop storage resource information for each of a plurality of crop producers, the crop storage resource information including crop storage resource location data, stored crop type data, and stored crop volume data; receive an at least one location-based, crop-specific purchase inquiry from an at least one purchaser; determine an aggregate crop volume available for purchase from received crop storage resource information based on the location-based, crop-specific purchase inquiry and the crop storage resource location data, stored crop type data, and stored crop volume data, the determination comprising accessing and utilizing data from at least a threshold number of crop producers; provide the determined aggregate crop volume available for purchase to the at least one purchaser in response to the received location-based, crop-specific purchase inquiry; receive a purchase request from the purchaser based on the provided aggregate crop volume available for purchase, the purchase request specifying at least two of a crop type, a crop purchase volume, and crop purchase price; and execute a transaction for the specified crop type between the purchaser and at least one of the plurality of crop producers based on the received purchase request. [ 00167] 66. The apparatus of embodiment 65, wherein the received location-based, crop-specific purchase inquiry includes initial boundary parameters defining a geographic search area. [ 00168 ] 67. The apparatus of embodiment 66, wherein the initial geographic boundary parameters include a geographic search radius. [ 00169 ] 68. The apparatus of embodiment 66 or 67, further comprising processor- issuable instructions to: modify the initial boundary parameters to provide data from at least the threshold number of crop producers. [ 00170 ] 69. A processor-readable tangible medium storing processor-issuable crop purchase management instructions to: receive crop storage resource information for each of a plurality of crop producers, the crop storage resource information including crop storage resource location data, stored crop type data, and stored crop volume data; receive a location-based, crop-specific purchase inquiry from an at least one purchaser; determine an aggregate crop volume available for purchase from received crop storage resource information based on the location-based, crop-specific purchase inquiry and the crop storage resource location data, stored crop type data, and stored crop volume data, the determination including data from at least a threshold number of crop producers; provide the determined aggregate crop volume available for purchase to the at least one purchaser in response to the received location-based, crop-specific purchase inquiry; receive a purchase request from the purchaser based on the provided aggregate crop volume available for purchase, the purchase request specifying a crop type and at least one of a crop purchase volume and crop purchase price; and execute a transaction for the specified crop type between the purchaser and at least one of the plurality of crop producers based on the received purchase request. [ 00171] 70. The medium of embodiment 69, wherein the received location-based, crop-specific purchase inquiry includes initial boundary parameters defining a geographic search area. [ 00172 ] 71. The medium of embodiment 70, wherein the initial geographic boundary parameters include a geographic search radius. [ 00173 ] 72. The medium of embodiment 70 or 71, further comprising instructions to: modify the initial boundary parameters to provide data from at least the threshold number of crop producers. [ 00174] 73. A crop purchase management system, comprising: means to receive crop storage resource information for each of a plurality of crop producers, the crop storage resource information including crop storage resource location data, stored crop type data, and stored crop volume data; means to receive an at least one location-based, crop-specific purchase inquiry from an at least one purchaser; means to determine an aggregate crop volume available for purchase from received crop storage resource information based on the location-based, crop-specific purchase inquiry and the crop storage resource location data, stored crop type data, and stored crop volume data, the determination comprising accessing and utilizing data from at least a threshold number of crop producers; means to provide the determined aggregate crop volume available for purchase to the at least one purchaser in response to the received location-based, crop-specific purchase inquiry; means to receive a purchase request from the purchaser based on the provided aggregate crop volume available for purchase, the purchase request specifying at least two of a crop type, a crop purchase volume, and crop purchase price; and means to execute a transaction for the specified crop type between the purchaser and at least one of the plurality of crop producers based on the received purchase request. [ 00175] 74. The system of embodiment 73, wherein the received location-based, crop-specific purchase inquiry includes initial boundary parameters defining a geographic search area. [ 00176 ] 75. The system of embodiment 74 , wherein the initial geographic boundary parameters include a geographic search radius. [ 00177] 76. The system of embodiment 75 or 76, further comprising: means to modify the initial boundary parameters to provide data from at least the threshold number of crop producers. [ 00178 ] 77. The method of any of embodiments 61-64, wherein the purchaser is livestock raiser or a feedlot. [ 00179 ] 78. The apparatus of any of embodiments 65-68, wherein the purchaser is livestock raiser or a feedlot. [ 00180 ] 79. The medium of any of embodiments 69-72, wherein the purchaser is livestock raiser or a feedlot. [ 00181] 80. The system of any of embodiments 73-76, wherein the purchaser is livestock raiser or a feedlot. [ 00182 ] 81. A real-time geographic market data feed processor-implemented method, comprising: maintaining an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; receiving an at least one real-time update to the agricultural asset account information associated with at least one of the plurality of agricultural asset producers; determining via a processor aggregate market data for at least one geographic region from a set of the plurality of agricultural asset producers based on the respective asset type data, asset location data, asset availability data and the at least one real-time update to the respective agricultural asset account information; and generating a real-time geographic market data feed from the determined aggregate market data for the at least one geographic region. [ 00183 ] 82. The method of embodiment 1, wherein maintaining an agricultural asset tracking account for an agricultural asset producer of the plurality of agricultural asset producers comprises: receiving harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receiving actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; and receiving in-field agricultural asset information for an at least one agricultural asset associated with the agricultural asset producer, the in-field agricultural asset information including asset crop type and asset location data. [ 00184] 83. The method of embodiment 81 or 82, wherein agricultural asset account information includes in-field asset data. [ 00185] 84. The method of embodiment 81, 82 or 83, wherein agricultural asset account information includes harvested asset data. [ 00186 ] 85. The method of any of embodiments 81-84, wherein agricultural asset account information includes asset storage data. [ 00187] 86. The method of any of embodiments 81-85, wherein the at least one real-time update to agricultural asset account information is received from a mobile device associated with an agricultural asset producer from the plurality of agricultural asset producers. [ 00188 ] 87. The method of any of embodiments 81-86, wherein the at least one real-time update to asset account information is based on a transaction between an asset producer and an asset purchaser. [ 00189 ] 88. A real-time geographic market data feed apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: maintain an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; receive an at least one real-time update to asset account information from at least one of the plurality of agricultural asset producers; determine aggregate market data for a geographic region from a set of the plurality of agricultural asset producers based on asset type data, asset location data, asset availability data and the at least one real-time update to asset account information; and generate a real-time geographic market data feed from the determined aggregate market data for the geographic region.

[ 00190 ] 89. The apparatus of embodiment 88, wherein asset account information includes in-field asset data.

[ 00191 ] 90. The apparatus of embodiment 88 or 89, wherein asset account information includes harvested asset data.

[ 00192 ] 91. The apparatus of any of embodiments 88-90, wherein asset account information includes asset storage data.

[ 00193 ] 92. The apparatus of any of embodiments 88-91, wherein the at least one real-time update to asset account information is received from a mobile device associated with an asset producer.

[ 00194 ] 93. The apparatus of any of embodiments 88-92, wherein the at least one real-time update to asset account information is based on a transaction between an asset producer and an asset purchaser.

[ 00195 ] 94. A processor-readable tangible medium storing processor-issuable realtime geographic market data feed instructions to: maintain an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; receive an at least one real-time update to asset account information from at least one of the plurality of agricultural asset producers; determine aggregate market data for a geographic region from a set of the plurality of agricultural asset producers based on asset type data, asset location data, asset availability data and the at least one real-time update to asset account information; and generate a real-time geographic market data feed from the determined aggregate market data for the geographic region. [ 00196 ] 95. The medium of embodiment 94, wherein asset account information includes in-field asset data. [ 00197] 96. The medium of embodiment 94 or 95, wherein asset account information includes harvested asset data. [ 00198 ] 97. The medium of any of embodiments 94-96, wherein asset account information includes asset storage data. [ 00199 ] 98. The medium of any of embodiments 94-97, wherein the at least one real-time update to asset account information is received from a mobile device associated with an asset producer. [ 00200 ] 99. The medium of any of embodiments 94-98, wherein the at least one real-time update to asset account information is based on a transaction between an asset producer and an asset purchaser. [ 00201 ] 100. A real-time geographic market data feed system, comprising: means to maintain an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; means to receive an at least one real-time update to the agricultural asset account information associated with at least one of the plurality of agricultural asset producers; means to determine aggregate market data for at least one geographic region from a set of the plurality of agricultural asset producers based on the respective asset type data, asset location data, asset availability data and the at least one real-time update to the respective agricultural asset account information; means to generate a real-time geographic market data feed from the determined aggregate market data for the at least one geographic region; wherein maintaining an agricultural asset tracking account for an agricultural asset producer of the plurality of agricultural asset producers comprises: means to receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; means to receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; and means to receive in-field agricultural asset information for an at least one agricultural asset associated with the agricultural asset producer, the in-field agricultural asset information including asset crop type and asset location data.

[00202] In one implementation, the GPPM creates an agricultural commodity asset management account for a farmer or other agricultural asset producer and receives harvested agricultural asset storage resource information and actual agricultural asset storage data for agricultural assets stored in the harvested agricultural asset storage resource, including location, volume, and crop type. The GPPM may also receive infield agricultural asset information, along with agricultural financial instrument data. The GPPM may also receive agricultural asset market data and determine an agricultural asset portfolio value for the agricultural commodity asset management account. The GPPM may then receive real-time updates of actual agricultural asset storage data and in-field agricultural asset information and update and output the determined agricultural asset portfolio value.

[00203] In some embodiments, the GPPM transforms real-time or near real-time agricultural commodity data via GPPM components into agricultural commodity offers, sales and/or purchase agreements. In one implementation, the GPPM receives crop information from a plurality of crop producers, including crop location data. The GPPM may then receive a location-based, crop-specific purchase inquiry from an at least one purchaser, and in response, determine an aggregate crop volume available for purchase, including data from at least a threshold number of crop producers. The determined aggregate crop volume available for purchase may then be provided to the at least one purchaser. If the purchase is interested, the purchaser may submit a purchase request, specifying a crop type and at least one of a crop purchase volume and crop purchase price. The GPPM may then execute a transaction for the specified crop type between the purchaser and at least one of the plurality of crop producers based on the received purchase request. [ 00204 ] In some embodiments, the GPPM transforms regional, automated, dynamic, real-time or near real-time producer agricultural asset information via GPPM components into real-time market updates and feeds. In some implementations, the GPPM maintains an agricultural asset tracking account for each of a plurality of agricultural asset producers, such as farmers, including asset type data, asset location data, and asset availability data. The GPPM may then receive one or more real-time updates to asset account information from agricultural asset producers. The GPPM may then determine aggregate market data for a geographic region from a set of the plurality of agricultural asset producers based on asset type data, asset location data, asset availability data and the real-time updates to asset account information and generate real-time geographic market data feeds. GPPM Controller

[ 00205] FIGURE 9 shows a block diagram illustrating embodiments of a GPPM controller 901. In this embodiment, the GPPM controller 901 may serve to aggregate, process, store, search, serve, identify, instruct, generate, match, and/or facilitate interactions with a computer through various technologies, and/or other related data. [ 00206 ] Typically, users, e.g., 933a, which may be people and/or other systems, may engage information technology systems (e.g., computers) to facilitate information processing. In turn, computers employ processors to process information; such processors 903 may be referred to as central processing units (CPU). One form of 1 processor is referred to as a microprocessor. CPUs use communicative circuits to pass

2 binary encoded signals acting as instructions to enable various operations. These

3 instructions may be operational and/or data instructions containing and/or referencing

4 other instructions and data in various processor accessible and operable areas of

5 memory 929 (e.g., registers, cache memory, random access memory, etc.). Such

6 communicative instructions may be stored and/or transmitted in batches (e.g., batches

7 of instructions) as programs and/or data components to facilitate desired operations.

8 These stored instruction codes, e.g., programs, may engage the CPU circuit components

9 and other motherboard and/or system components to perform desired operations. One

10 type of program is a computer operating system, which, may be executed by CPU on a

11 computer; the operating system enables and facilitates users to access and operate

12 computer information technology and resources. Some resources that may be

13 employed in information technology systems include: input and output mechanisms

14 through which data may pass into and out of a computer; memory storage into which

15 data may be saved; and processors by which information may be processed. These

16 information technology systems may be used to collect data for later retrieval, analysis,

17 and manipulation, which may be facilitated through a database program. These is information technology systems provide interfaces that allow users to access and

19 operate various system components.

20 [ 00207] In one embodiment, the GPPM controller 901 may be connected to and/or

21 communicate with entities such as, but not limited to: one or more users from user

22 input devices 911; peripheral devices 912; an optional cryptographic processor device

23 928; and/or a communications network 913. For example, the GPPM controller 901

24 may be connected to and/or communicate with users, e.g., 933a, operating client

25 device(s), e.g., 933b, including, but not limited to, personal computer(s), server(s)

26 and/or various mobile device(s) including, but not limited to, cellular telephone(s),

27 smartphone(s) (e.g., iPhone®, Blackberry®, Android OS-based phones etc.), tablet

28 computer(s) (e.g., Apple iPad™, HP Slate™, Motorola Xoom™, etc.), eBook reader(s)

29 (e.g., Amazon Kindle™, Barnes and Noble's Nook™ eReader, etc.), laptop computer(s),

30 notebook(s), netbook(s), gaming console(s) (e.g., XBOX Live™, Nintendo® DS, Sony

31 PlayStation® Portable, etc.), portable scanner(s), and/or the like. [00208] Networks are commonly thought to comprise the interconnection and interoperation of clients, servers, and intermediary nodes in a graph topology. It should be noted that the term "server" as used throughout this application refers generally to a computer, other device, program, or combination thereof that processes and responds to the requests of remote users across a communications network. Servers serve their information to requesting "clients." The term "client" as used herein refers generally to a computer, program, other device, user and/or combination thereof that is capable of processing and making requests and obtaining and processing any responses from servers across a communications network. A computer, other device, program, or combination thereof that facilitates, processes information and requests, and/or furthers the passage of information from a source user to a destination user is commonly referred to as a "node." Networks are generally thought to facilitate the transfer of information from source points to destinations. A node specifically tasked with furthering the passage of information from a source to a destination is commonly called a "router." There are many forms of networks such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc. For example, the Internet is generally accepted as being an interconnection of a multitude of networks whereby remote clients and servers may access and interoperate with one another. [00209] The GPPM controller 901 may be based on computer systems that may comprise, but are not limited to, components such as: a computer systemization 902 connected to memory 929. Computer Systemization

[00210] A computer systemization 902 may comprise a clock 930, central processing unit ("CPU(s)" and/or "processor(s)" (these terms are used interchangeable throughout the disclosure unless noted to the contrary)) 903, a memory 929 (e.g., a read only memory (ROM) 906, a random access memory (RAM) 905, etc.), and/or an interface bus 907, and most frequently, although not necessarily, are all interconnected and/or communicating through a system bus 904 on one or more (mother)board(s) 1 902 having conductive and/or otherwise transportive circuit pathways through which

2 instructions (e.g., binary encoded signals) may travel to effectuate communications,

3 operations, storage, etc. The computer systemization may be connected to a power

4 source 986; e.g., optionally the power source may be internal. Optionally, a

5 cryptographic processor 926 and/or transceivers (e.g., ICs) 974 may be connected to

6 the system bus. In another embodiment, the cryptographic processor and/or

7 transceivers may be connected as either internal and/or external peripheral devices 912

8 via the interface bus I/O. In turn, the transceivers may be connected to antenna(s) 975,

9 thereby effectuating wireless transmission and reception of various communication0 and/or sensor protocols; for example the antenna(s) may connect to: a Texas1 Instruments WiLink WL1283 transceiver chip (e.g., providing 802.1m, Bluetooth 3.0,2 FM, global positioning system (GPS) (thereby allowing GPPM controller to determine3 its location)); Broadcom BCM4329FKUBG transceiver chip (e.g., providing 802.1m,4 Bluetooth 2.1 + EDR, FM, etc.); a Broadcom BCM4750IUB8 receiver chip (e.g., GPS);5 an Infineon Technologies X-Gold 618-PMB9800 (e.g., providing 2G/3G6 HSDPA/HSUPA communications); and/or the like. The system clock typically has a7 crystal oscillator and generates a base signal through the computer systemization's8 circuit pathways. The clock is typically coupled to the system bus and various clock9 multipliers that will increase or decrease the base operating frequency for other0 components interconnected in the computer systemization. The clock and various1 components in a computer systemization drive signals embodying information2 throughout the system. Such transmission and reception of instructions embodying3 information throughout a computer systemization may be commonly referred to as4 communications. These communicative instructions may further be transmitted,5 received, and the cause of return and/or reply communications beyond the instant6 computer systemization to: communications networks, input devices, other computer7 systemizations, peripheral devices, and/or the like. It should be understood that in8 alternative embodiments, any of the above components may be connected directly to9 one another, connected to the CPU, and/or organized in numerous variations employed0 as exemplified by various computer systems. [ 00211 ] The CPU comprises at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests. Often, the processors themselves will incorporate various specialized processing units, such as, but not limited to: integrated system (bus) controllers, memory management control units, floating point units, and even specialized processing sub-units like graphics processing units, digital signal processing units, and/or the like. Additionally, processors may include internal fast access addressable memory, and be capable of mapping and addressing memory 929 beyond the processor itself; internal memory may include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1, 2, 3, etc.), RAM, etc. The processor may access this memory through the use of a memory address space that is accessible via instruction address, which the processor can construct and decode allowing it to access a circuit path to a specific memory address space having a memory state. The CPU may be a microprocessor such as: AMD's Athlon, Duron and/or Opteron; ARM's application, embedded and secure processors; IBM and/or Motorola's DragonBall and PowerPC; IBM's and Sony's Cell processor; Intel's Celeron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or the like processor(s). The CPU interacts with memory through instruction passing through conductive and/or transportive conduits (e.g., (printed) electronic and/or optic circuits) to execute stored instructions (i.e., program code) according to conventional data processing techniques. Such instruction passing facilitates communication within the GPPM controller and beyond through various interfaces. Should processing requirements dictate a greater amount speed and/or capacity, distributed processors (e.g., Distributed GPPM), mainframe, multi-core, parallel, and/or super-computer architectures may similarly be employed.Alternatively, should deployment requirements dictate greater portability, smaller Personal Digital Assistants (PDAs) may be employed. [ 00212 ] Depending on the particular implementation, features of the GPPM may be achieved by implementing a microcontroller such as CAST'S R8051XC2 microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or the like. Also, to implement certain features of the GPPM, some feature implementations may rely on embedded components, such as: Application-Specific Integrated Circuit ("ASIC"), Digital Signal Processing ("DSP"), Field Programmable Gate Array ("FPGA"), and/or the like embedded technology. For example, any of the GPPM component collection (distributed or otherwise) and/or features may be implemented via the microprocessor and/or via embedded components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like. Alternately, some implementations of the GPPM may be implemented with embedded components that are configured and used to achieve a variety of features or signal processing. [00213] Depending on the particular implementation, the embedded components may include software solutions, hardware solutions, and/or some combination of both hardware/ software solutions. For example, GPPM features discussed herein may be achieved through implementing FPGAs, which are a semiconductor devices containing programmable logic components called "logic blocks", and programmable interconnects, such as the high performance FPGA Virtex series and/or the low cost Spartan series manufactured by Xilinx. Logic blocks and interconnects can be programmed by the customer or designer, after the FPGA is manufactured, to implement any of the GPPM features. A hierarchy of programmable interconnects allow logic blocks to be interconnected as needed by the GPPM system designer/administrator, somewhat like a one-chip programmable breadboard. An FPGAs logic blocks can be programmed to perform the operation of basic logic gates such as AND, and XOR, or more complex combinational operators such as decoders or simple mathematical operations. In most FPGAs, the logic blocks also include memory elements, which may be circuit flip-flops or more complete blocks of memory. In some circumstances, the GPPM may be developed on regular FPGAs and then migrated into a fixed version that more resembles ASIC implementations. Alternate or coordinating implementations may migrate GPPM controller features to a final ASIC instead of or in addition to FPGAs. Depending on the implementation all of the aforementioned embedded components and microprocessors may be considered the "CPU" and/or "processor" for the GPPM. Power Source

[00214] The power source 986 may be of any standard form for powering small electronic circuit board devices such as the following power cells: alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium, solar cells, and/or the like. Other types of AC or DC power sources may be used as well. In the case of solar cells, in one embodiment, the case provides an aperture through which the solar cell may capture photonic energy. The power cell 986 is connected to at least one of the interconnected subsequent components of the GPPM thereby providing an electric current to all subsequent components. In one example, the power source 986 is connected to the system bus component 904. In an alternative embodiment, an outside power source 986 is provided through a connection across the I/O 908 interface. For example, a USB and/or IEEE 1394 connection carries both data and power across the connection and is therefore a suitable source of power. Interface Adapters

[00215] Interface bus(ses) 907 may accept, connect, and/or communicate to a number of interface adapters, conventionally although not necessarily in the form of adapter cards, such as but not limited to: input output interfaces (I/O) 908, storage interfaces 909, network interfaces 910, and/or the like. Optionally, cryptographic processor interfaces 927 similarly may be connected to the interface bus. The interface bus provides for the communications of interface adapters with one another as well as with other components of the computer systemization. Interface adapters are adapted for a compatible interface bus. Interface adapters conventionally connect to the interface bus via a slot architecture. Conventional slot architectures may be employed, such as, but not limited to: Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and/or the like. [00216] Storage interfaces 909 may accept, communicate, and/or connect to a number of storage devices such as, but not limited to: storage devices 914, removable disc devices, and/or the like. Storage interfaces may employ connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like. [00217] Network interfaces 910 may accept, communicate, and/or connect to a communications network 913. Through a communications network 913, the GPPM controller is accessible through remote clients 933b (e.g., computers with web browsers) by users 933a. Network interfaces may employ connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 8o2.na-x, and/or the like. Should processing requirements dictate a greater amount speed and/or capacity, distributed network controllers (e.g., Distributed GPPM), architectures may similarly be employed to pool, load balance, and/or otherwise increase the communicative bandwidth required by the GPPM controller. A communications network may be any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like. A network interface may be regarded as a specialized form of an input output interface. Further, multiple network interfaces 910 may be used to engage with various communications network types 913. For example, multiple network interfaces may be employed to allow for the communication over broadcast, multicast, and/or unicast networks. [00218] Input Output interfaces (I/O) 908 may accept, communicate, and/or connect to user input devices 911, peripheral devices 912, cryptographic processor devices 928, and/or the like. I/O may employ connection protocols such as, but not limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE I394a-b, serial, universal serial bus (USB); infrared; joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface: Apple Desktop Connector (ADC), BNC, coaxial, component, composite, digital, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like; wireless transceivers: 8o2.na/b/g/n/x; Bluetooth; cellular (e.g., code division multiple access (CDMA), high speed packet access (HSPA(+)), high-speed downlink packet access (HSDPA), global system for mobile communications (GSM), long term evolution (LTE), WiMax, etc.); and/or the like. One typical output device may include a video display, which typically comprises a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD) based monitor with an interface (e.g., DVI circuitry and cable) that accepts signals from a video interface, may be used. The video interface composites information generated by a computer systemization and generates video signals based on the composited information in a video memory frame. Another output device is a television set, which accepts signals from a video interface. Typically, the video interface provides the composited video information through a video connection interface that accepts a video display interface (e.g., an RCA composite video connector accepting an RCA composite video cable; a DVI connector accepting a DVI display cable, etc.). [ 00219 ] User input devices 911 often are a type of peripheral device 912 (see below) and may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the like. [ 00220 ] Peripheral devices 912 may be connected and/or communicate to I/O and/or other facilities of the like such as network interfaces, storage interfaces, directly to the interface bus, system bus, the CPU, and/or the like. Peripheral devices may be external, internal and/or part of the GPPM controller. Peripheral devices may include: antenna, audio devices (e.g., line-in, line-out, microphone input, speakers, etc.), cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like), external processors (for 1 added capabilities; e.g., crypto devices 928), force-feedback devices (e.g., vibrating

2 motors), network interfaces, printers, scanners, storage devices, transceivers (e.g.,

3 cellular, GPS, etc.), video devices (e.g., goggles, monitors, etc.), video sources, visors,

4 and/or the like. Peripheral devices often include types of input devices (e.g., cameras).

5 [00221] It should be noted that although user input devices and peripheral devices

6 may be employed, the GPPM controller may be embodied as an embedded, dedicated,

7 and/or monitor-less (i.e., headless) device, wherein access would be provided over a

8 network interface connection.

9 [00222] Cryptographic units such as, but not limited to, microcontrollers,

10 processors 926, interfaces 927, and/or devices 928 may be attached, and/or

11 communicate with the GPPM controller. A MC68HC16 microcontroller, manufactured

12 by Motorola Inc., may be used for and/or within cryptographic units. The MC68HC16

13 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz

14 configuration and requires less than one second to perform a 512-bit RSA private key

15 operation. Cryptographic units support the authentication of communications from

16 interacting agents, as well as allowing for anonymous transactions. Cryptographic units

17 may also be configured as part of the CPU. Equivalent microcontrollers and/or is processors may also be used. Other commercially available specialized cryptographic

19 processors include: the Broadcom's CryptoNetX and other Security Processors;

20 nCipher's nShield, SafeNet's Luna PCI (e.g., 7100) series; Semaphore Communications'

21 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators (e.g., Accelerator 6000

22 PCIe Board, Accelerator 500 Daughtercard); Via Nano Processor (e.g., L2100, L2200,

23 U2400) line, which is capable of performing 500+ MB/s of cryptographic instructions;

24 VLSI Technology's 33 MHz 6868; and/or the like.

25 Memory

26 [00223] Generally, any mechanization and/or embodiment allowing a processor to

27 affect the storage and/or retrieval of information is regarded as memory 929. However,

28 memory is a fungible technology and resource, thus, any number of memory

29 embodiments may be employed in lieu of or in concert with one another. It is to be 1 understood that the GPPM controller and/or a computer systemization may employ

2 various forms of memory 929. For example, a computer systemization may be

3 configured wherein the operation of on-chip CPU memory (e.g., registers), RAM, ROM,

4 and any other storage devices are provided by a paper punch tape or paper punch card

5 mechanism; however, such an embodiment would result in an extremely slow rate of

6 operation. In a typical configuration, memory 929 will include ROM 906, RAM 905,

7 and a storage device 914. A storage device 914 may be any conventional computer

8 system storage. Storage devices may include a drum; a (fixed and/or removable)

9 magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD

10 ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); an

11 array of devices (e.g., Redundant Array of Independent Disks (RAID)); solid state

12 memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable

13 storage mediums; and/or other devices of the like. Thus, a computer systemization

14 generally requires and makes use of memory.

15 Component Collection

16 [00224] The memory 929 may contain a collection of program and/or database

17 components and/or data such as, but not limited to: operating system component(s)

18 915 (operating system); information server component(s) 916 (information server);

19 user interface component(s) 917 (user interface); Web browser component(s) 918 (Web

20 browser); database(s) 919; mail server component(s) 921; mail client component(s)

21 922; cryptographic server component(s) 920 (cryptographic server); the GPPM

22 component(s) 935; and/or the like (i.e., collectively a component collection). These

23 components may be stored and accessed from the storage devices and/or from storage

24 devices accessible through an interface bus. Although non-conventional program

25 components such as those in the component collection, typically, are stored in a local

26 storage device 914, they may also be loaded and/or stored in memory such as:

27 peripheral devices, RAM, remote storage facilities through a communications network,

28 ROM, various forms of memory, and/or the like. 1 Operating System

2 [00225] The operating system component 915 is an executable program

3 component facilitating the operation of the GPPM controller. Typically, the operating

4 system facilitates access of I/O, network interfaces, peripheral devices, storage devices,

5 and/or the like. The operating system may be a highly fault tolerant, scalable, and

6 secure system such as: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix and

7 Unix-like system distributions (such as AT&T's UNIX; Berkley Software Distribution

8 (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like; Linux

9 distributions such as Red Hat, Ubuntu, and/or the like); and/or the like operating

10 systems. However, more limited and/or less secure operating systems also may be

11 employed such as Apple Macintosh OS, IBM OS/2, Microsoft DOS, Microsoft Windows

12 2000/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/or the

13 like. An operating system may communicate to and/or with other components in a

14 component collection, including itself, and/or the like. Most frequently, the operating

15 system communicates with other program components, user interfaces, and/or the like.

16 For example, the operating system may contain, communicate, generate, obtain,

17 and/or provide program component, system, user, and/or data communications, is requests, and/or responses. The operating system, once executed by the CPU, may

19 enable the interaction with communications networks, data, I/O, peripheral devices,

20 program components, memory, user input devices, and/or the like. The operating

21 system may provide communications protocols that allow the GPPM controller to

22 communicate with other entities through a communications network 913. Various

23 communication protocols may be used by the GPPM controller as a subcarrier

24 transport mechanism for interaction, such as, but not limited to: multicast, TCP/IP,

25 UDP, unicast, and/or the like.

26 Information Server

27 [00226] An information server component 916 is a stored program component that

28 is executed by a CPU. The information server may be a conventional Internet

29 information server such as, but not limited to Apache Software Foundation's Apache, Microsoft's Internet Information Server, and/or the like. The information server may allow for the execution of program components through facilities such as Active Server Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre- Processor (PHP), pipes, Python, wireless application protocol (WAP), WebObjects, and/or the like. The information server may support secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols (e.g., America Online (AOL) Instant Messenger (AIM), Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger Service, Presence and Instant Messaging Protocol (PRIM), Internet Engineering Task Force's (IETF's) Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) Instant Messaging and Presence Service (IMPS)), Yahoo! Instant Messenger Service, and/or the like. The information server provides results in the form of Web pages to Web browsers, and allows for the manipulated generation of the Web pages through interaction with other program components. After a Domain Name System (DNS) resolution portion of an HTTP request is resolved to a particular information server, the information server resolves requests for information at specified locations on the GPPM controller based on the remainder of the HTTP request. For example, a request such as http://123.124.125.126/myInformation.html might have the IP portion of the request "123.124.125.126" resolved by a DNS server to an information server at that IP address; that information server might in turn further parse the http request for the "/mylnformation.html" portion of the request and resolve it to a location in memory containing the information "mylnformation.html." Additionally, other information serving protocols may be employed across various ports, e.g., FTP communications across port 21, and/or the like. An information server may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the information server communicates with the GPPM database 919, operating systems, other program components, user interfaces, Web browsers, and/or the like. [00227] Access to the GPPM database may be achieved through a number of database bridge mechanisms such as through scripting languages as enumerated below (e.g., CGI) and through inter-application communication channels as enumerated below (e.g., CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed through the bridge mechanism into appropriate grammars as required by the GPPM. In one embodiment, the information server would provide a Web form accessible by a Web browser. Entries made into supplied fields in the Web form are tagged as having been entered into the particular fields, and parsed as such. The entered terms are then passed along with the field tags, which act to instruct the parser to generate queries directed to appropriate tables and/or fields. In one embodiment, the parser may generate queries in standard SQL by instantiating a search string with the proper join/select commands based on the tagged text entries, wherein the resulting command is provided over the bridge mechanism to the GPPM as a query. Upon generating query results from the query, the results are passed over the bridge mechanism, and may be parsed for formatting and generation of a new results Web page by the bridge mechanism. Such a new results Web page is then provided to the information server, which may supply it to the requesting Web browser. [00228] Also, an information server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. User Interface

[00229] Computer interfaces in some respects are similar to automobile operation interfaces. Automobile operation interface elements such as steering wheels, gearshifts, and speedometers facilitate the access, operation, and display of automobile resources, and status. Computer interaction interface elements such as check boxes, cursors, menus, scrollers, and windows (collectively and commonly referred to as widgets) similarly facilitate the access, capabilities, operation, and display of data and computer 1 hardware and operating system resources, and status. Operation interfaces are

2 commonly called user interfaces. Graphical user interfaces (GUIs) such as the Apple

3 Macintosh Operating System's Aqua, IBM's OS/2, Microsoft's Windows

4 2000/2003/3. i/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix's X-Windows

5 (e.g., which may include additional Unix graphic interface libraries and layers such as K

6 Desktop Environment (KDE), mythTV and GNU Network Object Model Environment

7 (GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH, Java,

8 JavaScript, etc. interface libraries such as, but not limited to, Dojo, jQuery(UI),

9 MooTools, Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any of which0 may be used and) provide a baseline and means of accessing and displaying 1 information graphically to users. 2 [00230] A user interface component 917 is a stored program component that is3 executed by a CPU. The user interface may be a conventional graphic user interface as4 provided by, with, and/or atop operating systems and/or operating environments such5 as already discussed. The user interface may allow for the display, execution,6 interaction, manipulation, and/or operation of program components and/or system7 facilities through textual and/or graphical facilities. The user interface provides a8 facility through which users may affect, interact, and/or operate a computer system. A9 user interface may communicate to and/or with other components in a component0 collection, including itself, and/or facilities of the like. Most frequently, the user1 interface communicates with operating systems, other program components, and/or2 the like. The user interface may contain, communicate, generate, obtain, and/or3 provide program component, system, user, and/or data communications, requests,4 and/or responses. 5 Web Browser 6 [00231] A Web browser component 918 is a stored program component that is7 executed by a CPU. The Web browser may be a conventional hypertext viewing8 application such as Microsoft Internet Explorer or Netscape Navigator. Secure Web9 browsing may be supplied with I28bit (or greater) encryption by way of HTTPS, SSL, and/or the like. Web browsers allowing for the execution of program components through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-in APIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or the like. Web browsers and like information access tools may be integrated into PDAs, cellular telephones, and/or other mobile devices. A Web browser may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the Web browser communicates with information servers, operating systems, integrated program components (e.g., plug-ins), and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Also, in place of a Web browser and information server, a combined application may be developed to perform similar operations of both. The combined application would similarly affect the obtaining and the provision of information to users, user agents, and/or the like from the GPPM enabled nodes. The combined application may be nugatory on systems employing standard Web browsers. Mail Server [00232] A mail server component 921 is a stored program component that is executed by a CPU 903. The mail server may be a conventional Internet mail server such as, but not limited to sendmail, Microsoft Exchange, and/or the like. The mail server may allow for the execution of program components through facilities such as ASP, ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes, Python, WebObjects, and/or the like. The mail server may support communications protocols such as, but not limited to: Internet message access protocol (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like. The mail server can route, forward, and process incoming and outgoing mail messages that have been sent, relayed and/or otherwise traversing through and/or to the GPPM. [00233] Access to the GPPM mail may be achieved through a number of APIs offered by the individual Web server components and/or the operating system. [00234] Also, a mail server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. Mail Client

[00235] A mail client component 922 is a stored program component that is executed by a CPU 903. The mail client may be a conventional mail viewing application such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or the like. Mail clients may support a number of transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the mail client communicates with mail servers, operating systems, other mail clients, and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. Generally, the mail client provides a facility to compose and transmit electronic mail messages. Cryptographic Server

[00236] A cryptographic server component 920 is a stored program component that is executed by a CPU 903, cryptographic processor 926, cryptographic processor interface 927, cryptographic processor device 928, and/or the like. Cryptographic processor interfaces will allow for expedition of encryption and/or decryption requests by the cryptographic component; however, the cryptographic component, alternatively, may run on a conventional CPU. The cryptographic component allows for the encryption and/or decryption of provided data. The cryptographic component allows for both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or decryption. The cryptographic component may employ cryptographic techniques such as, but not limited to: digital certificates (e.g., X.509 authentication framework), digital signatures, dual signatures, enveloping, password access protection, public key management, and/or the like. The cryptographic component will facilitate numerous (encryption and/or decryption) security protocols such as, but not limited to: checksum, Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data Encryption Algorithm (IDEA), Message Digest 5 (MD5, which is a one way hash operation), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS), and/or the like. Employing such encryption security protocols, the GPPM may encrypt all incoming and/or outgoing communications and may serve as node within a virtual private network (VPN) with a wider communications network. The cryptographic component facilitates the process of "security authorization" whereby access to a resource is inhibited by a security protocol wherein the cryptographic component effects authorized access to the secured resource. In addition, the cryptographic component may provide unique identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an digital audio file. A cryptographic component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. The cryptographic component supports encryption schemes allowing for the secure transmission of information across a communications network to enable the GPPM component to engage in secure transactions if so desired. The cryptographic component facilitates the secure accessing of resources on the GPPM and facilitates the access of secured resources on remote systems; i.e., it may act as a client and/or server of secured resources. Most frequently, the cryptographic component communicates with information servers, operating systems, other program components, and/or the like. The cryptographic component may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. The GPPM Database [00237] The GPPM database component 919 may be embodied in a database and its stored data. The database is a stored program component, which is executed by the CPU; the stored program component portion configuring the CPU to process the stored data. The database may be a conventional, fault tolerant, relational, scalable, secure database such as Oracle or Sybase. Relational databases are an extension of a flat file. Relational databases consist of a series of related tables. The tables are interconnected via a key field. Use of the key field allows the combination of the tables by indexing against the key field; i.e., the key fields act as dimensional pivot points for combining information from various tables. Relationships generally identify links maintained between tables by matching primary keys. Primary keys represent fields that uniquely identify the rows of a table in a relational database. More precisely, they uniquely identify rows of a table on the "one" side of a one-to-many relationship. [00238] Alternatively, the GPPM database may be implemented using various standard data-structures, such as an array, hash, (linked) list, struct, structured text file (e.g., XML), table, and/or the like. Such data-structures may be stored in memory and/or in (structured) files. In another alternative, an object-oriented database may be used, such as Frontier, ObjectStore, Poet, Zope, and/or the like. Object databases can include a number of object collections that are grouped and/or linked together by common attributes; they may be related to other object collections by some common attributes. Object-oriented databases perform similarly to relational databases with the exception that objects are not just pieces of data but may have other types of capabilities encapsulated within a given object. If the GPPM database is implemented as a data-structure, the use of the GPPM database 919 may be integrated into another component such as the GPPM component 935. Also, the database may be implemented as a mix of data structures, objects, and relational structures. Databases may be consolidated and/or distributed in countless variations through standard data processing techniques. Portions of databases, e.g., tables, may be exported and/or imported and thus decentralized and/or integrated. [ 00239 ] In one embodiment, the database component 919 includes several tables 9i9a-l. A producers table 919a may include fields such as, but not limited to: producer_id, producer_name, state, address_firstline, address_secondline, zipcode, devices_list, account_info, producer_assets, contact_info, contact_type, alt_contact_info, alt_contact_type, financial_data, and/or the like. [ 00240 ] A purchasers table 919b may include fields such as, but not limited to: purchaser_ID, purchaser_name, history, account_data, contact_data, financial_records, and/or the like. [ 00241] An accounts table 919c may include fields such as, but not limited to: account_ID, location, assets, crops, acreage, historical, history, deals, trades, instruments, devices, and/or the like. [ 00242 ] A profiles table 9i9d may include fields such as, but not limited to: profile_ID, parameters, history, location, and/or the like. [ 00243 ] A geo table 919ε may include fields such as, but not limited to: geo_id, geo_details, geo_assets, geo_accounts, and/or the like. [ 00244] A resources table 9i9f may include fields such as, but not limited to: resource_id, location, associations, parameters, history and/or the like. [ 00245 ] An equipment table 9i9g may include fields such as, but not limited to: equipment_ID, location, parameters, associations, details, model, and/or the like. [ 00246 ] A storage table 919I1 may include fields such as, but not limited to: storage_id, location, parameters, resource, type, history and/or the like. [ 00247] A commodity table 9191 may include fields such as, but not limited to: commodity_ID, type, parameters, details, market, price, trend, and/or the like. [ 00248 ] A transaction table 9i9j may include fields such as, but not limited to: transaction_ID, parties, parameters, history, details, and/or the like. [ 00249 ] A devices table 919k may include fields such as, but not limited to: device_ID, associations, history, parameters, location, owner, account, and/or the like. [ 00250 ] A Market Data table 919I may include fields such as, but not limited to: market_data_feed_ID, asset_ID, asset_symbol, asset_name, spot_price, bid_price, ask_price, and/or the like; in one embodiment, the market data table is populated through a market data feed (e.g., Bloomberg's PhatPipe, Dun & Bradstreet, Reuter's Tib, Triarch, etc.), for example, through Microsoft's Active Template Library and Dealing Object Technology's real-time toolkit Rtt.Multi. [ 00251] In one embodiment, the GPPM database may interact with other database systems. For example, employing a distributed database system, queries and data access by search GPPM component may treat the combination of the GPPM database, an integrated data security layer database as a single database entity. [ 00252 ] In one embodiment, user programs may contain various user interface primitives, which may serve to update the GPPM. Also, various accounts may require custom database tables depending upon the environments and the types of clients the GPPM may need to serve. It should be noted that any unique fields may be designated as a key field throughout. In an alternative embodiment, these tables have been decentralized into their own databases and their respective database controllers (i.e., individual database controllers for each of the above tables). Employing standard data processing techniques, one may further distribute the databases over several computer systemizations and/or storage devices. Similarly, configurations of the decentralized database controllers may be varied by consolidating and/or distributing the various database components 919a-!. The GPPM may be configured to keep track of various settings, inputs, and parameters via database controllers. [ 00253 ] The GPPM database may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the GPPM database communicates with the GPPM component, other program components, and/or the like. The database may contain, retain, and provide information regarding other nodes and data. 1 The GPPMs

2 [00254] The GPPM component 935 is a stored program component that is

3 executed by a CPU. In one embodiment, the GPPM component incorporates any

4 and/or all combinations of the aspects of the GPPM discussed in the previous figures.

5 As such, the GPPM affects accessing, obtaining and the provision of information,

6 services, transactions, and/or the like across various communications networks. The

7 features and embodiments of the GPPM discussed herein increase network efficiency

8 by reducing data transfer requirements the use of more efficient data structures and

9 mechanisms for their transfer and storage. As a consequence, more data may be

10 transferred in less time, and latencies with regard to transactions, are also reduced. In

11 many cases, such reduction in storage, transfer time, bandwidth requirements,

12 latencies, etc., will reduce the capacity and structural infrastructure requirements to

13 support the GPPM's features and facilities, and in many cases reduce the costs, energy

14 consumption/requirements, and extend the life of GPPM's underlying infrastructure;

15 this has the added benefit of making the GPPM more reliable. Similarly, many of the

16 features and mechanisms are designed to be easier for users to use and access, thereby

17 broadening the audience that may enjoy/employ and exploit the feature sets of the is GPPM; such ease of use also helps to increase the reliability of the GPPM. In addition,

19 the feature sets include heightened security as noted via the Cryptographic components

20 820, 826, 828 and throughout, making access to the features and data more reliable

21 and secure.

22 [00255] The GPPM component may transform producer crop asset information via

23 GPPM components into dynamic, automated, real-time, and/or near real-time

24 inventory updates, and/or the like and use of the GPPM. In one embodiment, the

25 GPPM component 935 takes inputs (e.g., storage requests, storage volume updates,

26 farm service agency data, agribusiness data, futures/cash bid services data, financial

27 services data, offers to buy, offers to sell, insurance data, market data, inventory data,

28 available volume requests, purchase requests, and/or the like) etc., and transforms the

29 inputs via various components (e.g., integration component 941; PAE component 942;

30 CGS inventory component 943; matching component 944; matching component 945; PP inventory component 946; profile generation component 947; RRCU component 948; publication component 949; PT component 950; LFM component 951; Risk component 952; and/or the like), into outputs (e.g., responses; updates; available volume; portfolio values; crop values; purchase orders; market data updates; and/or the like). [00256] The GPPM component enabling access of information between nodes may be developed by employing standard development tools and languages such as, but not limited to: Apache components, Assembly, ActiveX, binary executables, (ANSI) (Objective-) C (++), C# and/or .NET, database adapters, CGI scripts, Java, JavaScript, mapping tools, procedural and object oriented development tools, PERL, PHP, Python, shell scripts, SQL commands, web application server extensions, web development environments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX & FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools; Prototype; script.aculo.us; Simple Object Access Protocol (SOAP); SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/or the like. In one embodiment, the GPPM server employs a cryptographic server to encrypt and decrypt communications. The GPPM component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the GPPM component communicates with the GPPM database, operating systems, other program components, and/or the like. The GPPM may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Distributed GPPMs

[00257] The structure and/or operation of any of the GPPM node controller components may be combined, consolidated, and/or distributed in any number of ways to facilitate development and/or deployment. Similarly, the component collection may be combined in any number of ways to facilitate deployment and/or development. To accomplish this, one may integrate the components into a common code base or in a facility that can dynamically load the components on demand in an integrated fashion. [00258] The component collection may be consolidated and/or distributed in countless variations through standard data processing and/or development techniques. Multiple instances of any one of the program components in the program component collection may be instantiated on a single node, and/or across numerous nodes to improve performance through load-balancing and/or data-processing techniques. Furthermore, single instances may also be distributed across multiple controllers and/or storage devices; e.g., databases. All program component instances and controllers working in concert may do so through standard data processing communication techniques. [00259] The configuration of the GPPM controller will depend on the context of system deployment. Factors such as, but not limited to, the budget, capacity, location, and/or use of the underlying hardware resources may affect deployment requirements and configuration. Regardless of if the configuration results in more consolidated and/or integrated program components, results in a more distributed series of program components, and/or results in some combination between a consolidated and distributed configuration, data may be communicated, obtained, and/or provided. Instances of components consolidated into a common code base from the program component collection may communicate, obtain, and/or provide data. This may be accomplished through intra- application data processing communication techniques such as, but not limited to: data referencing (e.g., pointers), internal messaging, object instance variable communication, shared memory space, variable passing, and/or the like. [00260] If component collection components are discrete, separate, and/or external to one another, then communicating, obtaining, and/or providing data with and/or to other components may be accomplished through inter-application data processing communication techniques such as, but not limited to: Application Program Interfaces (API) information passage; (distributed) Component Object Model ((D)COM), (Distributed) Object Linking and Embedding ((D)OLE), and/or the like), Common Object Request Broker Architecture (CORBA), Jini local and remote application program interfaces, JavaScript Object Notation (JSON), Remote Method Invocation (RMI), SOAP, process pipes, shared files, and/or the like. Messages sent between discrete component components for inter-application communication or within memory spaces of a singular component for intra-application communication may be facilitated through the creation and parsing of a grammar. A grammar may be developed by using development tools such as lex, yacc, XML, and/or the like, which allow for grammar generation and parsing capabilities, which in turn may form the basis of communication messages within and between components. [00261] For example, a grammar may be arranged to recognize the tokens of an HTTP post command, e.g.: 3c -post http://... Valuel [00262] where Valuei is discerned as being a parameter because "http://" is part of the grammar syntax, and what follows is considered part of the post value. Similarly, with such a grammar, a variable "Valuei" may be inserted into an "http://" post command and then sent. The grammar syntax itself may be presented as structured data that is interpreted and/or otherwise used to generate the parsing mechanism (e.g., a syntax description text file as processed by lex, yacc, etc.). Also, once the parsing mechanism is generated and/or instantiated, it itself may process and/or parse structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, structured text streams, XML, and/or the like structured data. In another embodiment, inter-application data processing protocols themselves may have integrated and/or readily available parsers (e.g., JSON, SOAP, and/or like parsers) that may be employed to parse (e.g., communications) data. Further, the parsing grammar may be used beyond message parsing, but may also be used to parse: databases, data collections, data stores, structured data, and/or the like. Again, the desired configuration will depend upon the context, environment, and requirements of system deployment. [00263] For example, in some implementations, the GPPM controller may be executing a PHP script implementing a Secure Sockets Layer ("SSL") socket server via the information server, which listens to incoming communications on a server port to which a client may send data, e.g., data encoded in JSON format. Upon identifying an incoming communication, the PHP script may read the incoming message from the client device, parse the received JSON-encoded text data to extract information from the JSON-encoded text data into PHP script variables, and store the data (e.g., client identifying information, etc.) and/or extracted information in a relational database accessible using the Structured Query Language ("SQL"). An exemplary listing, written substantially in the form of PHP/SQL commands, to accept JSON-encoded input data from a client device via a SSL connection, parse the data to extract variables, and store the data to a database, is provided below: < ? PH P

header (' Content-Type : text/plain'); // set ip address and port to listen to for incoming data

$address = ^Λ192.168.0.100' ;

$port = 255; // create a server-side SSL socket, listen for/accept incoming

communication

$sock = socket_create (AF_INET, SOCK_STREAM, 0);

socket_bind ( $sock, $address, $port) or die ( ^Λ Could not bind to

address' ) ;

socket_listen ( $sock) ;

$client = socket_accept ( $sock) ; // read input data from client device in 1024 byte blocks until

end of message

do {

$input = "";

$input = socket_read ($client, 1024);

$data .= $ input;

} while ($input != ""); // parse data to extract variables

$obj = j son_decode ($data, true); // store input data in a database

mysql_connect ("201.408.185.132", $DBserver, $pas sword) ; // access

database server

mysql_select ("CLIENT_DB. SQL" ) ; // select database to append

mysql_query ("INSERT INTO UserTable (transmission)

VALUES ($data)"); // add data to UserTable table in a CLIENT

database

mysql_close ( "CLIENT_DB . SQL" ) ; // close connection to database

?>

[00264] Also, the following resources may be used to provide example embodiments regarding SOAP parser implementation: http : / / w . xav . com/perl/ site/lib/SOAP/ Parser . html

http : / /publib .boulder . ibm. com/ infocenter/tivihelp/v2rl/index . j sp? topic=/com . ibm . IBMDI .doc/referenceguide295. htm

[00265] and other parser implementations: http : / /publib .boulder . ibm. com/ infocenter/tivihelp/v2rl/index . j sp? topic=/com . ibm . IBMDI .doc/referenceguide259. htm

[00266] all of which are hereby expressly incorporated by reference herein.

[00267] In some implementations, a user may download and install a GPPM mobile component on a mobile device (e.g., an Apple iPhone, a BlackBerry, a Google Android, a Samsung Galaxy, etc.) or other portable web-enabled computing device. Integration of the mobile component reduces the number of network transactions and messages that fulfill GPPM information requests and transmissions, as well as associated services. In this way, with the reduction of network communications, the number of transactions that may be processed per day is increased, i.e., processing efficiency is improved. Additionally, by the collection and provision of real-time, near- real-time and/or dynamic crop asset data allows for more efficient and accurate pricing of grain/commodity sales, market pricing and instrument trading, and/or improved farm management. The GPPM allows a farmer to more quickly and efficiently manage his or her farm, including sales of agricultural assets, and may also provide for more efficient logistics (e.g., by allow shippers to fill up available cargo efficiently and on the fly). [ 00268 ] It is to be understood that various embodiments of the GPPM may suitably comprise, consist of, or consist essentially of, various combinations of the disclosed elements, components, features, parts, steps, means, etc. Some of the disclosed features, elements, implementation, etc., may be mutually contradictory, in that they cannot be simultaneously present in a single embodiment. Similarly, some features are applicable to one aspect of the disclosure, and inapplicable to others. [ 00269 ] The follow items provide exemplary embodiments of the GPPM: [ 00270 ] 1. A crop asset tracking processor-implemented method, comprising: providing, creating and/or enabling access to a producer crop asset management account for a producer; receiving crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; associating received crop asset storage resource information with the producer crop asset management account; associating an at least one mobile device with the producer crop asset management account; determining via a processor when the at least one mobile device is within a specified distance of the location of the at least one crop storage resource; generating a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one crop storage resource, the notification including a request to provide near-real-time crop state data for the at least one crop storage resource; receiving near-real-time crop state data for the at least one crop storage resource; and associating the received near-real-time crop state data with the producer crop asset management account. [ 00271 ] 2. The method of item 1, wherein the at least one crop storage resource is a crop field. [ 0 0 272 ] 3. The method of item 1, wherein the at least one crop storage resource is a harvested crop storage facility. [ 0 0 273 ] 4. The method of item 3, wherein the harvested crop storage facility is a storage bin. [ 0 0 274 ] 5. The method of any of items 1-4, further comprising monitoring the location of the at least one mobile device. [ 0 0 275 ] 6. The method of any of items 1-5, wherein receiving near-real-time crop state data comprises receiving an at least one image captured by the mobile device. [ 0 0 276 ] 7. The method of any of items 1-5, wherein receiving near-real -time crop state data comprises receiving precision agricultural equipment data. [ 0 0 277] 8. The method of any of items 1-7, wherein the crop state data comprises volume data. [ 0 0 278 ] 9. The method of any of items 1-7, wherein the crop state data comprises an indication that the crop is ready for harvest. [ 0 0 279 ] 10. A crop asset tracking apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: create a producer crop asset management account for a producer; receive crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; associate received crop asset storage resource information with the producer crop asset management account; associate an at least one mobile device with the producer crop asset management account; determine when the at least one mobile device is within a specified distance of the at least one crop storage resource location; generate and provide a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the at least one crop storage resource location, the notification including a request to provide near-real-time crop volume data for the at least one crop storage resource; receive near-real-time crop volume data for the at least one crop storage resource; and associate the received near-real-time crop volume data with the producer crop asset management account. [ 00280 ] 11. The apparatus of item 10, wherein receiving near-real-time crop volume data comprises receiving an at least one image captured by the mobile device. [ 00281 ] 12. A processor-readable non-transitory tangible medium storing processor-issuable crop asset tracking instructions to: create a producer crop asset management account for a producer; receive crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; associate received crop asset storage resource information with the producer crop asset management account; associate an at least one mobile device with the producer crop asset management account; determine when the at least one mobile device is within a specified distance of the at least one crop storage resource location; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the at least one crop storage resource location, the notification including a request to provide near-real -time crop volume data for the at least one crop storage resource; receive near-real-time crop volume data for the at least one crop storage resource; and associate the received near-real -time crop volume data with the producer crop asset management account. [ 00282 ] 13. A crop asset tracking apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: provide, create and/or enable access to a producer crop asset management account for a producer; receive crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; associate received crop asset storage resource information with the producer crop asset management account; associate an at least one mobile device with the producer crop asset management account; determine when the at least one mobile device is within a specified distance of the location of the at least one crop storage resource; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one crop storage resource, the notification including a request to provide near-real-time crop state data for the at least one crop storage resource; receive near-real-time crop state data for the at least one crop storage resource; and associate the received near-real -time crop state data with the producer crop asset management account.

[ 00283 ] 14. The apparatus of item 13, wherein the at least one crop storage resource is a crop field.

[ 00284 ] 15. The apparatus of item 13, wherein the at least one crop storage resource is a harvested crop storage facility.

[ 00285 ] 16. The apparatus of item 15, wherein the harvested crop storage facility is a storage bin.

[ 00286 ] 17. The apparatus of any of items 13-16, further comprising instructions to monitor the location of the at least one mobile device.

[ 00287] 18. The apparatus of any of items 13-17, wherein receiving near-real-time crop state data comprises receiving an at least one image captured by the mobile device.

[ 00288 ] 19. The apparatus of any of items 13-17, wherein receiving near-real-time crop state data comprises receiving precision agricultural equipment data.

[ 00289 ] 20. The apparatus of any of items 13-17, wherein receiving near-real-time crop state data comprises receiving satellite data.

[ 00290 ] 21. The apparatus of any of items 13-17, wherein receiving near-real-time crop state data comprises receiving satellite image data.

[ 00291] 22. The apparatus of any of items 13-21, wherein the crop state data comprises volume data. [ 00292 ] 23. The apparatus of any of items 13-21, wherein the crop state data comprises an indication that the crop is ready for harvest. [ 00293 ] 24. A processor-readable non-transitory tangible medium storing processor-issuable crop asset tracking instructions to: provide, create and/or enable access to a producer crop asset management account for a producer; receive crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; associate received crop asset storage resource information with the producer crop asset management account; associate an at least one mobile device with the producer crop asset management account; determine when the at least one mobile device is within a specified distance of the location of the at least one crop storage resource; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one crop storage resource, the notification including a request to provide near-real-time crop state data for the at least one crop storage resource; receive near-real-time crop state data for the at least one crop storage resource; and associate the received near- real-time crop state data with the producer crop asset management account. [ 00294] 25. The medium of item 24, wherein the at least one crop storage resource is a crop field. [ 00295 ] 26. The medium of item 24, wherein the at least one crop storage resource is a harvested crop storage facility. [ 00296 ] 27. The medium of item 26, wherein the harvested crop storage facility is a storage bin. [ 00297] 28. The medium of any of items 24-27, further comprising instructions to monitor the location of the at least one mobile device. [ 00298 ] 29. The medium of any of items 24-28, wherein receiving near-real-time crop state data comprises receiving an at least one image captured by the mobile device. [ 00299 ] 30. The medium of any of items 24-28, wherein receiving near-real-time crop state data comprises receiving precision agricultural equipment data. [ 00300 ] 31. The medium of any of items 24-28, wherein receiving near-real-time crop state data comprises receiving satellite data. [ 00301] 32. The medium of any of items 24-28, wherein receiving near-real-time crop state data comprises receiving satellite image data. [ 00302 ] 33. The medium of any of items 24-32, wherein the crop state data comprises volume data. [ 00303 ] 34. The medium of any of items 24-32, wherein the crop state data comprises an indication that the crop is ready for harvest. [ 00304] 35. A crop asset tracking system, comprising: means to provide, create and/or enable access to a producer crop asset management account for a producer; means to receive crop asset storage resource information, the crop asset storage resource information including storage resource location data for an at least one crop storage resource; means to associate received crop asset storage resource information with the producer crop asset management account; means to associate an at least one mobile device with the producer crop asset management account; means to determine when the at least one mobile device is within a specified distance of the location of the at least one crop storage resource; means to generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one crop storage resource, the notification including a request to provide near-real-time crop state data for the at least one crop storage resource; means to receive near-real-time crop state data for the at least one crop storage resource; and means to associate the received near-real-time crop state data with the producer crop asset management account. [ 00305] 36. The system of item 35, wherein the at least one crop storage resource is a crop field. [ 00306 ] 37. The system of item 35, wherein the at least one crop storage resource is a harvested crop storage facility. [ 00307] 38. The system of item 37, wherein the harvested crop storage facility is a storage bin. [ 00308 ] 39. The system of any of items 35-38, further comprising means to monitor the location of the at least one mobile device. [ 00309 ] 40. The system of any of items 35-39, wherein receiving near-real-time crop state data comprises receiving an at least one image captured by the mobile device. [ 00310 ] 41. The system of any of items 35-39, wherein receiving near-real-time crop state data comprises receiving precision agricultural equipment data. [ 00311 ] 42. The system of any of items 35-39, wherein receiving near-real-time crop state data comprises receiving satellite data. [ 00312 ] 43. The system of any of items 35-39, wherein receiving near-real-time crop state data comprises receiving satellite image data. [ 00313 ] 44. The system of any of items 35-43, wherein the crop state data comprises volume data. [ 00314] 45. The system of any of items 35-43, wherein the crop state data comprises an indication that the crop is ready for harvest. [ 00315 ] 46. An agricultural commodity asset management processor-implemented method, comprising: providing, creating, maintaining, and/or enabling access to an agricultural commodity asset management account for an agricultural asset producer; receiving harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receiving actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; receiving in-field agricultural asset information for an at least one agricultural asset associated with the agricultural asset producer, the infield agricultural asset information including agricultural asset crop type and agricultural asset location data; receiving agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; receiving agricultural asset market data; determining via a processor an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; receiving near-real-time update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; updating the determined agricultural asset portfolio value based on the received near-real -time update information; and outputting the updated agricultural asset portfolio value for the agricultural commodity asset management account.

[ 00316 ] 47. The method of item 46, wherein the near-real-time update information is provided via a mobile device associated with the agricultural asset producer.

[ 00317] 48. The method of item 46 or 47, wherein the at least one harvested agricultural asset storage resource is on-farm storage.

[ 00318 ] 49. The method of any of items 46-48, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer.

[ 00319 ] 50. An agricultural commodity asset management apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: provide, create, maintain and/or enable access to an agricultural commodity asset management account for an agricultural asset producer; receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; receive in-field agricultural asset information for an at least one agricultural asset associated with agricultural asset producer, in-field agricultural asset information including agricultural asset crop type and location data; receive agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; receive agricultural asset market data; determine an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; receive near-real-time update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; update the determined agricultural asset portfolio value based on the received near-real-time update information; and output the updated agricultural asset portfolio value for the agricultural commodity asset management account.

[ 00320 ] 51. The apparatus of item 50, wherein the near-real-time update information is provided via a mobile device associated with the agricultural asset producer.

[ 00321] 52. The apparatus of item 50 or 51, wherein the at least one harvested agricultural asset storage resource is on-farm storage.

[ 00322 ] 53. The apparatus of item 50, 51 or 52, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer.

[ 00323 ] 54. A processor-readable tangible medium storing processor-issuable agricultural commodity asset management instructions to: provide, create, maintain and/or enable access to an agricultural commodity asset management account for an agricultural asset producer; receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; receive in-field agricultural asset information for an at least one agricultural asset associated with agricultural asset producer, in-field agricultural asset information including agricultural asset crop type and location data; receive agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; receive agricultural asset market data; determine an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; receive near-real-time update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; update the determined agricultural asset portfolio value based on the received near-real-time update information; and output the updated agricultural asset portfolio value for the agricultural commodity asset management account.

[ 00324] 55. The medium of item 54, wherein the near-real-time update information is provided via a mobile device associated with the agricultural asset producer.

[ 00325 ] 56. The medium of item 54 or 55, wherein the at least one harvested agricultural asset storage resource is on-farm storage.

[ 00326 ] 57. The medium of item 54, 55, or 56, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer. [ 00327] 58. An agricultural commodity asset management system, comprising: means to provide, create, maintain and/or enable access to an agricultural commodity asset management account for an agricultural asset producer; receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; means to receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; means to receive in-field agricultural asset information for an at least one agricultural asset associated with agricultural asset producer, in-field agricultural asset information including agricultural asset crop type and location data; means to receive agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; means to receive agricultural asset market data; means to determine an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; means to receive near-real-time update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; means to update the determined agricultural asset portfolio value based on the received near- real-time update information; and means to output the updated agricultural asset portfolio value for the agricultural commodity asset management account.

[ 00328 ] 59. The system of item 58, wherein the at least one harvested agricultural asset storage resource is on-farm storage.

[ 00329 ] 60. The system of item 58 or 59, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer.

[ 00330 ] 61. A grain purchase management processor-implemented method, comprising: receiving grain storage resource information for each of a plurality of grain producers, the grain storage resource information including grain storage resource location data, stored grain type data, and stored grain volume data; receiving a location-based, grain-specific purchase inquiry from an at least one purchaser; determining via a processor an aggregate grain volume available for purchase from the received grain storage resource information based on the location-based, grain-specific purchase inquiry and the grain storage resource location data, stored grain type data, and stored grain volume data, the determination comprising accessing and/or utilizing data from at least a threshold number of grain producers; providing the determined aggregate grain volume available for purchase to the at least one purchaser in response to the received location-based, grain-specific purchase inquiry; receiving a purchase request from the purchaser based on the provided aggregate grain volume available for purchase, the purchase request specifying at least one of a grain type, a grain purchase volume and grain purchase price; and facilitating a transaction for the specified grain type between the purchaser and at least one of the plurality of grain producers based on the received purchase request. [00331] 62. The method of item 61, wherein the received location-based, grain- specific purchase inquiry includes initial boundary parameters defining a geographic search area. [00332] 63. The method of item 62, wherein the initial geographic boundary parameters include a geographic search radius. [00333] 64. The method of item 62 or 63, further comprising: modifying the initial boundary parameters to provide data from at least the threshold number of grain producers. [00334] 65. A grain purchase management apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor- issuable instructions to: receive grain storage resource information for each of a plurality of grain producers, the grain storage resource information including grain storage resource location data, stored grain type data, and stored grain volume data; receive an at least one location-based, grain-specific purchase inquiry from an at least one purchaser; determine an aggregate grain volume available for purchase from received grain storage resource information based on the location-based, grain-specific purchase inquiry and the grain storage resource location data, stored grain type data, and stored grain volume data, the determination comprising accessing and utilizing data from at least a threshold number of grain producers; provide the determined aggregate grain volume available for purchase to the at least one purchaser in response to the received location-based, grain-specific purchase inquiry; receive a purchase request from the purchaser based on the provided aggregate grain volume available for purchase, the purchase request specifying at least two of a grain type, a grain purchase volume, and grain purchase price; and execute a transaction for the specified grain type between the purchaser and at least one of the plurality of grain producers based on the received purchase request. [00335] 66. The apparatus of item 65, wherein the received location-based, grain- specific purchase inquiry includes initial boundary parameters defining a geographic search area. [00336] 67. The apparatus of item 66, wherein the initial geographic boundary parameters include a geographic search radius. [00337] 68. The apparatus of item 66 or 67, further comprising processor-issuable instructions to: modify the initial boundary parameters to provide data from at least the threshold number of grain producers. [00338 ] 69. A processor-readable tangible medium storing processor-issuable grain purchase management instructions to: receive grain storage resource information for each of a plurality of grain producers, the grain storage resource information including grain storage resource location data, stored grain type data, and stored grain volume data; receive a location-based, grain-specific purchase inquiry from an at least one purchaser; determine an aggregate grain volume available for purchase from received grain storage resource information based on the location-based, grain-specific purchase inquiry and the grain storage resource location data, stored grain type data, and stored grain volume data, the determination including data from at least a threshold number of grain producers; provide the determined aggregate grain volume available for purchase to the at least one purchaser in response to the received location- based, grain-specific purchase inquiry; receive a purchase request from the purchaser based on the provided aggregate grain volume available for purchase, the purchase request specifying a grain type and at least one of a grain purchase volume and grain purchase price; and execute a transaction for the specified grain type between the purchaser and at least one of the plurality of grain producers based on the received purchase request. [ 00339 ] 70. The medium of item 69, wherein the received location-based, grain- specific purchase inquiry includes initial boundary parameters defining a geographic search area. [ 00340 ] 71. The medium of item 70, wherein the initial geographic boundary parameters include a geographic search radius. [ 00341] 72. The medium of item 70 or 71, further comprising instructions to: modify the initial boundary parameters to provide data from at least the threshold number of grain producers. [ 00342 ] 73. A grain purchase management system, comprising: means to receive grain storage resource information for each of a plurality of grain producers, the grain storage resource information including grain storage resource location data, stored grain type data, and stored grain volume data; means to receive an at least one location-based, grain-specific purchase inquiry from an at least one purchaser; means to determine an aggregate grain volume available for purchase from received grain storage resource information based on the location-based, grain-specific purchase inquiry and the grain storage resource location data, stored grain type data, and stored grain volume data, the determination comprising accessing and utilizing data from at least a threshold number of grain producers; means to provide the determined aggregate grain volume available for purchase to the at least one purchaser in response to the received location-based, grain-specific purchase inquiry; means to receive a purchase request from the purchaser based on the provided aggregate grain volume available for purchase, the purchase request specifying at least two of a grain type, a grain purchase volume, and grain purchase price; and means to execute a transaction for the specified grain type between the purchaser and at least one of the plurality of grain producers based on the received purchase request. [ 00343 ] 74· The system of item 73, wherein the received location-based, grain - specific purchase inquiry includes initial boundary parameters defining a geographic search area. [ 00344] 75· The system of item 74, wherein the initial geographic boundary parameters include a geographic search radius. [ 00345 ] 76. The system of item 75 or 76, further comprising: means to modify the initial boundary parameters to provide data from at least the threshold number of grain producers. [ 00346 ] 77. The method of any of items 61-64, wherein the purchaser is livestock raiser or a feedlot. [ 00347] 78. The apparatus of any of items 65-68, wherein the purchaser is livestock raiser or a feedlot. [ 00348 ] 79. The medium of any of items 69-72, wherein the purchaser is livestock raiser or a feedlot. [ 00349 ] 80. The system of any of items 73-76, wherein the purchaser is livestock raiser or a feedlot. [ 00350 ] 81. A near-real-time geographic market data feed processor-implemented method, comprising: maintaining an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; receiving an at least one near-real-time update to the agricultural asset account information associated with at least one of the plurality of agricultural asset producers; determining via a processor aggregate market data for at least one geographic region from a set of the plurality of agricultural asset producers based on the respective asset type data, asset location data, asset availability data and the at least one near-real-time update to the respective agricultural asset account information; and generating a near-real-time geographic market data feed from the determined aggregate market data for the at least one geographic region. [00351] 82. The method of item 1, wherein maintaining an agricultural asset tracking account for an agricultural asset producer of the plurality of agricultural asset producers comprises: receiving harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receiving actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; and receiving in-field agricultural asset information for an at least one agricultural asset associated with the agricultural asset producer, the in-field agricultural asset information including asset crop type and asset location data. [00352 ] 83. The method of item 81 or 82, wherein agricultural asset account information includes in-field asset data. [00353] 84. The method of item 81, 82 or 83, wherein agricultural asset account information includes harvested asset data. [00354] 85. The method of any of items 81-84, wherein agricultural asset account information includes asset storage data. [00355] 86. The method of any of items 81-85, wherein the at least one near-real- time update to agricultural asset account information is received from a mobile device associated with an agricultural asset producer from the plurality of agricultural asset producers. [00356] 87. The method of any of items 81-86, wherein the at least one near-real- time update to asset account information is based on a transaction between an asset producer and an asset purchaser. [00357] 88. A near-real-time geographic market data feed apparatus, comprising: [00358 ] a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: maintain an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; receive an at least one near-real- time update to asset account information from at least one of the plurality of agricultural asset producers; determine aggregate market data for a geographic region from a set of the plurality of agricultural asset producers based on asset type data, asset location data, asset availability data and the at least one near-real-time update to asset account information; and generate a near-real-time geographic market data feed from the determined aggregate market data for the geographic region. [00359] 89. The apparatus of item 88, wherein asset account information includes in-field asset data. [00360 ] 90. The apparatus of item 88 or 89, wherein asset account information includes harvested asset data. [00361] 91. The apparatus of any of items 88-90, wherein asset account information includes asset storage data. [00362] 92. The apparatus of any of items 88-91, wherein the at least one near- real-time update to asset account information is received from a mobile device associated with an asset producer. [00363] 93. The apparatus of any of items 88-92, wherein the at least one near- real-time update to asset account information is based on a transaction between an asset producer and an asset purchaser. [00364] 94. A processor-readable tangible medium storing processor-issuable near-real-time geographic market data feed instructions to: maintain an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; receive an at least one near-real-time update to asset account information from at least one of the plurality of agricultural asset producers; determine aggregate market data for a geographic region from a set of the plurality of agricultural asset producers based on asset type data, asset location data, asset availability data and the at least one near-real- time update to asset account information; and generate a near-real-time geographic market data feed from the determined aggregate market data for the geographic region. [00365] 95. The medium of item 94, wherein asset account information includes in-field asset data. [00366 ] 96. The medium of item 94 or 95, wherein asset account information includes harvested asset data. [00367] 97. The medium of any of items 94-96, wherein asset account information includes asset storage data. [00368 ] 98. The medium of any of items 94-97, wherein the at least one near-real- time update to asset account information is received from a mobile device associated with an asset producer. [00369 ] 99. The medium of any of items 94-98, wherein the at least one near-real- time update to asset account information is based on a transaction between an asset producer and an asset purchaser. [00370 ] 100. A near-real-time geographic market data feed system, comprising: means to maintain an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; means to receive an at least one near-real-time update to the agricultural asset account information associated with at least one of the plurality of agricultural asset producers; means to determine aggregate market data for at least one geographic region from a set of the plurality of agricultural asset producers based on the respective asset type data, asset location data, asset availability data and the at least one near-real-time update to the respective agricultural asset account information; means to generate a near-real-time geographic market data feed from the determined aggregate market data for the at least one geographic region; wherein maintaining an agricultural asset tracking account for an agricultural asset producer of the plurality of agricultural asset producers comprises: means to receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; means to receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset crop type and agricultural asset volume; and means to receive in-field agricultural asset information for an at least one agricultural asset associated with the agricultural asset producer, the in-field agricultural asset information including asset crop type and asset location data.

[ 00371 ] A variety of implementations of the GPPM are within the scope of this disclosure, for example, the implementations provided as follows:

[ 00372 ] 1. A grain asset tracking processor-implemented method, comprising: providing, creating and/or enabling access to a producer grain asset management account for a producer; receiving grain asset storage resource information, the grain asset storage resource information including storage resource location data for an at least one grain storage resource; associating received grain asset storage resource information with the producer grain asset management account; associating an at least one mobile device with the producer grain asset management account; determining via a processor when the at least one mobile device is within a specified distance of the location of the at least one grain storage resource; generating a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one grain storage resource, the notification including a request to provide automated/dynamic grain state data for the at least one grain storage resource; receiving automated/ dynamic grain state data for the at least one grain storage resource; and associating the received automated/dynamic grain state data with the producer grain asset management account. [ 00373 ] 2- The method of implementation 1, wherein the at least one grain storage resource is a grain field. [ 00374 ] 3· The method of implementation 1, wherein the at least one grain storage resource is a harvested grain storage facility. [ 00375 ] 4· The method of implementation 3, wherein the harvested grain storage facility is a storage bin. [ 00376 ] 5. The method of any of implementations 1-4, further comprising monitoring the location of the at least one mobile device. [ 00377] 6. The method of any of implementations 1-5, wherein receiving automated/dynamic grain state data comprises receiving an at least one image captured by the mobile device. [ 00378 ] 7. The method of any of implementations 1-5, wherein receiving automated/dynamic grain state data comprises receiving precision agricultural equipment data. [ 00379 ] 8. The method of any of implementations 1-7, wherein the grain state data comprises volume data. [ 00380 ] 9. The method of any of implementations 1-7, wherein the grain state data comprises an indication that the grain is ready for harvest. [ 00381 ] 10. A grain asset tracking apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: create a producer grain asset management account for a producer; receive grain asset storage resource information, the grain asset storage resource information including storage resource location data for an at least one grain storage resource; associate received grain asset storage resource information with the producer grain asset management account; associate an at least one mobile device with the producer grain asset management account; determine when the at least one mobile device is within a specified distance of the at least one grain storage resource location; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the at least one grain storage resource location, the notification including a request to provide automated/dynamic grain volume data for the at least one grain storage resource; receive automated/dynamic grain volume data for the at least one grain storage resource; and associate the received automated/dynamic grain volume data with the producer grain asset management account. [00382 ] 11. The apparatus of implementation 10, wherein receiving automated/dynamic grain volume data comprises receiving an at least one image captured by the mobile device. [00383 ] 12. A processor-readable non-transitory tangible medium storing processor-issuable grain asset tracking instructions to: create a producer grain asset management account for a producer; receive grain asset storage resource information, the grain asset storage resource information including storage resource location data for an at least one grain storage resource; associate received grain asset storage resource information with the producer grain asset management account; associate an at least one mobile device with the producer grain asset management account; determine when the at least one mobile device is within a specified distance of the at least one grain storage resource location; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the at least one grain storage resource location, the notification including a request to provide automated/dynamic grain volume data for the at least one grain storage resource; receive automated/dynamic grain volume data for the at least one grain storage resource; and associate the received automated/dynamic grain volume data with the producer grain asset management account. [00384] 13. A grain asset tracking apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: provide, create and/or enable access to a producer grain asset management account for a producer; receive grain asset storage resource information, the grain asset storage resource information including storage resource location data for an at least one grain storage resource; associate received grain asset storage resource information with the producer grain asset management account; associate an at least one mobile device with the producer grain asset management account; determine when the at least one mobile device is within a specified distance of the location of the at least one grain storage resource; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one grain storage resource, the notification including a request to provide automated/dynamic grain state data for the at least one grain storage resource; receive automated/dynamic grain state data for the at least one grain storage resource; and associate the received automated/dynamic grain state data with the producer grain asset management account. [00385] 14. The apparatus of implementation 13, wherein the at least one grain storage resource is a grain field. [00386 ] 15. The apparatus of implementation 13, wherein the at least one grain storage resource is a harvested grain storage facility. [00387] 16. The apparatus of implementation 15, wherein the harvested grain storage facility is a storage bin. [00388 ] 17. The apparatus of any of implementations 13-16, further comprising instructions to monitor the location of the at least one mobile device. [00389 ] 18. The apparatus of any of implementations 13-17, wherein receiving automated/dynamic grain state data comprises receiving an at least one image captured by the mobile device. [00390 ] 19. The apparatus of any of implementations 13-17, wherein receiving automated/dynamic grain state data comprises receiving precision agricultural equipment data. [00391] 20. The apparatus of any of implementations 13-17, wherein receiving automated/dynamic grain state data comprises receiving satellite data. [00392] 21. The apparatus of any of implementations 13-17, wherein receiving automated/dynamic grain state data comprises receiving satellite image data. [00393] 22. The apparatus of any of implementations 13-21, wherein the grain state data comprises volume data. [00394] 23. The apparatus of any of implementations 13-21, wherein the grain state data comprises an indication that the grain is ready for harvest. [00395] 24. A processor-readable non-transitory tangible medium storing processor-issuable grain asset tracking instructions to: provide, create and/or enable access to a producer grain asset management account for a producer; receive grain asset storage resource information, the grain asset storage resource information including storage resource location data for an at least one grain storage resource; associate received grain asset storage resource information with the producer grain asset management account; associate an at least one mobile device with the producer grain asset management account; determine when the at least one mobile device is within a specified distance of the location of the at least one grain storage resource; generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one grain storage resource, the notification including a request to provide automated/dynamic grain state data for the at least one grain storage resource; receive automated/dynamic grain state data for the at least one grain storage resource; and associate the received automated/dynamic grain state data with the producer grain asset management account. [ 00396 ] 25. The medium of implementation 24, wherein the at least one grain storage resource is a grain field. [ 00397] 26. The medium of implementation 24, wherein the at least one grain storage resource is a harvested grain storage facility. [ 00398 ] 27. The medium of implementation 26, wherein the harvested grain storage facility is a storage bin. [ 00399 ] 28. The medium of any of implementations 24-27, further comprising instructions to monitor the location of the at least one mobile device. [ 00400 ] 29. The medium of any of implementations 24-28, wherein receiving automated/dynamic grain state data comprises receiving an at least one image captured by the mobile device. [ 00401] 30. The medium of any of implementations 24-28, wherein receiving automated/dynamic grain state data comprises receiving precision agricultural equipment data. [ 00402 ] 31. The medium of any of implementations 24-28, wherein receiving automated/dynamic grain state data comprises receiving satellite data. [ 00403 ] 32. The medium of any of implementations 24-28, wherein receiving automated/dynamic grain state data comprises receiving satellite image data. [ 00404] 33. The medium of any of implementations 24-32, wherein the grain state data comprises volume data. [ 00405 ] 34. The medium of any of implementations 24-32, wherein the grain state data comprises an indication that the grain is ready for harvest. [ 00406 ] 35. A grain asset tracking system, comprising: means to provide, create and/or enable access to a producer grain asset management account for a producer; means to receive grain asset storage resource information, the grain asset storage resource information including storage resource location data for an at least one grain storage resource; means to associate received grain asset storage resource information with the producer grain asset management account; means to associate an at least one mobile device with the producer grain asset management account; means to determine when the at least one mobile device is within a specified distance of the location of the at least one grain storage resource; means to generate a notification on the at least one mobile device based on the determination that the at least one mobile device is within the specified distance of the location of the at least one grain storage resource, the notification including a request to provide automated/ dynamic grain state data for the at least one grain storage resource; means to receive automated/dynamic grain state data for the at least one grain storage resource; and means to associate the received automated/dynamic grain state data with the producer grain asset management account. [ 00407] 36. The system of implementation 35, wherein the at least one grain storage resource is a grain field. [ 00408 ] 37. The system of implementation 35, wherein the at least one grain storage resource is a harvested grain storage facility. [ 00409 ] 38. The system of implementation 37, wherein the harvested grain storage facility is a storage bin. [ 00410 ] 39. The system of any of implementations 35-38, further comprising means to monitor the location of the at least one mobile device. [ 00411 ] 40. The system of any of implementations 35-39, wherein receiving automated/dynamic grain state data comprises receiving an at least one image captured by the mobile device. [ 00412 ] 41. The system of any of implementations 35-39, wherein receiving automated/dynamic grain state data comprises receiving precision agricultural equipment data.

[ 00413 ] 42. The system of any of implementations 35-39, wherein receiving automated/dynamic grain state data comprises receiving satellite data.

[ 00414 ] 43. The system of any of implementations 35-39, wherein receiving automated/dynamic grain state data comprises receiving satellite image data.

[ 00415 ] 44. The system of any of implementations 35-43, wherein the grain state data comprises volume data.

[ 00416 ] 45. The system of any of implementations 35-43, wherein the grain state data comprises an indication that the grain is ready for harvest.

[ 00417] 46. An agricultural commodity asset management processor-implemented method, comprising: providing, creating, maintaining, and/or enabling access to an agricultural commodity asset management account for an agricultural asset producer; receiving harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receiving actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset grain type and agricultural asset volume; receiving in-field agricultural asset information for an at least one agricultural asset associated with the agricultural asset producer, the infield agricultural asset information including agricultural asset grain type and agricultural asset location data; receiving agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; receiving agricultural asset market data; determining via a processor an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; receiving automated/ dynamic update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; updating the determined agricultural asset portfolio value based on the received automated/ dynamic update information; and outputting the updated agricultural asset portfolio value for the agricultural commodity asset management account.

[ 00418 ] 47. The method of implementation 46, wherein the automated/dynamic update information is provided via a mobile device associated with the agricultural asset producer.

[ 00419 ] 48. The method of implementation 46 or 47, wherein the at least one harvested agricultural asset storage resource is on-farm storage.

[ 00420 ] 49. The method of any of implementations 46-48, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer.

[ 00421] 50. An agricultural commodity asset management apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: provide, create, maintain and/or enable access to an agricultural commodity asset management account for an agricultural asset producer; receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset grain type and agricultural asset volume; receive in-field agricultural asset information for an at least one agricultural asset associated with agricultural asset producer, in-field agricultural asset information including agricultural asset grain type and location data; receive agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; receive agricultural asset market data; determine an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; receive automated/dynamic update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; update the determined agricultural asset portfolio value based on the received automated/dynamic update information; and output the updated agricultural asset portfolio value for the agricultural commodity asset management account. [ 00422 ] 51. The apparatus of implementation 50, wherein the automated/dynamic update information is provided via a mobile device associated with the agricultural asset producer. [ 00423 ] 52. The apparatus of implementation 50 or 51, wherein the at least one harvested agricultural asset storage resource is on-farm storage. [ 00424] 53. The apparatus of implementation 50, 51 or 52, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer. [ 00425 ] 54. A processor-readable tangible medium storing processor-issuable agricultural commodity asset management instructions to: provide, create, maintain and/or enable access to an agricultural commodity asset management account for an agricultural asset producer; receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset grain type and agricultural asset volume; receive in-field agricultural asset information for an at least one agricultural asset associated with agricultural asset producer, in-field agricultural asset information including agricultural asset grain type and location data; receive agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; receive agricultural asset market data; determine an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; receive automated/dynamic update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; update the determined agricultural asset portfolio value based on the received automated/dynamic update information; and output the updated agricultural asset portfolio value for the agricultural commodity asset management account.

[ 00426 ] 55. The medium of implementation 54, wherein the automated/dynamic update information is provided via a mobile device associated with the agricultural asset producer.

[ 00427] 56. The medium of implementation 54 or 55, wherein the at least one harvested agricultural asset storage resource is on-farm storage.

[ 00428 ] 57. The medium of implementation 54, 55, or 56, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer.

[ 00429 ] 58. An agricultural commodity asset management system, comprising: means to provide, create, maintain and/or enable access to an agricultural commodity asset management account for an agricultural asset producer; receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; means to receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset grain type and agricultural asset volume; means to receive in-field agricultural asset information for an at least one agricultural asset associated with agricultural asset producer, in-field agricultural asset information including agricultural asset grain type and location data; means to receive agricultural financial instrument data for an at least one agricultural financial instrument associated with the agricultural commodity asset management account; means to receive agricultural asset market data; means to determine an agricultural asset portfolio value for the agricultural commodity asset management account based on the actual agricultural asset storage data, the in-field agricultural asset information, the agricultural financial instrument data and the agricultural asset market data; means to receive automated/ dynamic update information for at least one of the actual agricultural asset storage data and the in-field agricultural asset information; means to update the determined agricultural asset portfolio value based on the received automated/dynamic update information; and means to output the updated agricultural asset portfolio value for the agricultural commodity asset management account. [ 00430 ] 59. The system of implementation 58, wherein the at least one harvested agricultural asset storage resource is on-farm storage. [ 00431] 60. The system of implementation 58 or 59, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural producer. [ 00432 ] 61. A livestock feed crop purchase management processor-implemented method, comprising: receiving livestock feed crop storage resource information for each of a plurality of livestock feed crop producers, the livestock feed crop storage resource information including livestock feed crop storage resource location data, stored livestock feed crop type data, and stored livestock feed crop volume data; receiving a location-based, livestock feed crop-specific purchase inquiry from an at least one purchaser; determining via a processor an aggregate livestock feed crop volume available for purchase from the received livestock feed crop storage resource information based on the location-based, livestock feed crop-specific purchase inquiry and the livestock feed crop storage resource location data, stored livestock feed crop type data, and stored livestock feed crop volume data, the determination comprising accessing and/or utilizing data from at least a threshold number of livestock feed crop producers; providing the determined aggregate livestock feed crop volume available for purchase to the at least one purchaser in response to the received location-based, livestock feed crop-specific purchase inquiry; receiving a purchase request from the purchaser based on the provided aggregate livestock feed crop volume available for purchase, the purchase request specifying at least one of a livestock feed crop type, a livestock feed crop purchase volume and livestock feed crop purchase price; and facilitating a transaction for the specified livestock feed crop type between the purchaser and at least one of the plurality of livestock feed crop producers based on the received purchase request. [ 00433 ] 62. The method of implementation 61, wherein the received location- based, livestock feed crop-specific purchase inquiry includes initial boundary parameters defining a geographic search area. [ 00434] 63. The method of implementation 62, wherein the initial geographic boundary parameters include a geographic search radius. [ 00435 ] 64. The method of implementation 62 or 63, further comprising: [ 00436 ] modifying the initial boundary parameters to provide data from at least the threshold number of livestock feed crop producers. [ 00437] 65. A livestock feed crop purchase management apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: receive livestock feed crop storage resource information for each of a plurality of livestock feed crop producers, the livestock feed crop storage resource information including livestock feed crop storage resource location data, stored livestock feed crop type data, and stored livestock feed crop volume data; receive an at least one location-based, livestock feed crop-specific purchase inquiry from an at least one purchaser; determine an aggregate livestock feed crop volume available for purchase from received livestock feed crop storage resource information based on the location-based, livestock feed crop-specific purchase inquiry and the livestock feed crop storage resource location data, stored livestock feed crop type data, and stored livestock feed crop volume data, the determination comprising accessing and utilizing data from at least a threshold number of livestock feed crop producers; provide the determined aggregate livestock feed crop volume available for purchase to the at least one purchaser in response to the received location-based, livestock feed crop-specific purchase inquiry; receive a purchase request from the purchaser based on the provided aggregate livestock feed crop volume available for purchase, the purchase request specifying at least two of a livestock feed crop type, a livestock feed crop purchase volume, and livestock feed crop purchase price; and execute a transaction for the specified livestock feed crop type between the purchaser and at least one of the plurality of livestock feed crop producers based on the received purchase request. [00438 ] 66. The apparatus of implementation 65, wherein the received location- based, livestock feed crop-specific purchase inquiry includes initial boundary parameters defining a geographic search area. [00439] 67. The apparatus of implementation 66, wherein the initial geographic boundary parameters include a geographic search radius. [00440 ] 68. The apparatus of implementation 66 or 67, further comprising processor-issuable instructions to: modify the initial boundary parameters to provide data from at least the threshold number of livestock feed crop producers. [00441] 69. A processor-readable tangible medium storing processor-issuable livestock feed crop purchase management instructions to: receive livestock feed crop storage resource information for each of a plurality of livestock feed crop producers, the livestock feed crop storage resource information including livestock feed crop storage resource location data, stored livestock feed crop type data, and stored livestock feed crop volume data; receive a location-based, livestock feed crop-specific purchase inquiry from an at least one purchaser; determine an aggregate livestock feed crop volume available for purchase from received livestock feed crop storage resource information based on the location-based, livestock feed crop-specific purchase inquiry and the livestock feed crop storage resource location data, stored livestock feed crop type data, and stored livestock feed crop volume data, the determination including data from at least a threshold number of livestock feed crop producers; provide the determined aggregate livestock feed crop volume available for purchase to the at least one purchaser in response to the received location-based, livestock feed crop-specific purchase inquiry; receive a purchase request from the purchaser based on the provided aggregate livestock feed crop volume available for purchase, the purchase request specifying a livestock feed crop type and at least one of a livestock feed crop purchase volume and livestock feed crop purchase price; and execute a transaction for the specified livestock feed crop type between the purchaser and at least one of the plurality of livestock feed crop producers based on the received purchase request. [00442] 70. The medium of implementation 69, wherein the received location- based, livestock feed crop-specific purchase inquiry includes initial boundary parameters defining a geographic search area. [00443] 71· The medium of implementation 70, wherein the initial geographic boundary parameters include a geographic search radius. [00444] 7²· The medium of implementation 70 or 71, further comprising instructions to: [00445] modify the initial boundary parameters to provide data from at least the threshold number of livestock feed crop producers. [00446 ] 73. A livestock feed crop purchase management system, comprising: means to receive livestock feed crop storage resource information for each of a plurality of livestock feed crop producers, the livestock feed crop storage resource information including livestock feed crop storage resource location data, stored livestock feed crop type data, and stored livestock feed crop volume data; means to receive an at least one location-based, livestock feed crop-specific purchase inquiry from an at least one purchaser; means to determine an aggregate livestock feed crop volume available for purchase from received livestock feed crop storage resource information based on the location-based, livestock feed crop-specific purchase inquiry and the livestock feed crop storage resource location data, stored livestock feed crop type data, and stored livestock feed crop volume data, the determination comprising accessing and utilizing data from at least a threshold number of livestock feed crop producers; means to provide the determined aggregate livestock feed crop volume available for purchase to the at least one purchaser in response to the received location-based, livestock feed crop-specific purchase inquiry; means to receive a purchase request from the purchaser based on the provided aggregate livestock feed crop volume available for purchase, the purchase request specifying at least two of a livestock feed crop type, a livestock feed crop purchase volume, and livestock feed crop purchase price; and means to execute a transaction for the specified livestock feed crop type between the purchaser and at least one of the plurality of livestock feed crop producers based on the received purchase request. [ 00447] 74· The system of implementation 73, wherein the received location-based, livestock feed crop-specific purchase inquiry includes initial boundary parameters defining a geographic search area. [ 00448 ] 75. The system of implementation 74, wherein the initial geographic boundary parameters include a geographic search radius. [ 00449 ] 76. The system of implementation 75 or 76, further comprising: means to modify the initial boundary parameters to provide data from at least the threshold number of livestock feed crop producers. [ 00450 ] 77. The method of any of implementations 61-64, wherein the purchaser is livestock raiser or a feedlot. [ 00451] 78. The apparatus of any of implementations 65-68, wherein the purchaser is livestock raiser or a feedlot. [ 00452 ] 79. The medium of any of implementations 69-72, wherein the purchaser is livestock raiser or a feedlot. [ 00453 ] 80. The system of any of implementations 73-76, wherein the purchaser is livestock raiser or a feedlot. [ 00454] 81. A automated/dynamic geographic market data feed processor- implemented method, comprising: maintaining an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; receiving an at least one automated/dynamic update to the agricultural asset account information associated with at least one of the plurality of agricultural asset producers; determining via a processor aggregate market data for at least one geographic region from a set of the plurality of agricultural asset producers based on the respective asset type data, asset location data, asset availability data and the at least one automated/dynamic update to the respective agricultural asset account information; and generating a automated/dynamic geographic market data feed from the determined aggregate market data for the at least one geographic region.

[ 00455 ] 82. The method of implementation 1, wherein maintaining an agricultural asset tracking account for an agricultural asset producer of the plurality of agricultural asset producers comprises: receiving harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; receiving actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset grain type and agricultural asset volume; and receiving in-field agricultural asset information for an at least one agricultural asset associated with the agricultural asset producer, the in-field agricultural asset information including asset grain type and asset location data.

[ 00456 ] 83. The method of implementation 81 or 82, wherein agricultural asset account information includes in-field asset data.

[ 00457] 84. The method of implementation 81, 82 or 83, wherein agricultural asset account information includes harvested asset data. [ 00458 ] 85. The method of any of implementations 81-84, wherein agricultural asset account information includes asset storage data. [ 00459 ] 86. The method of any of implementations 81-85, wherein the at least one automated/dynamic update to agricultural asset account information is received from a mobile device associated with an agricultural asset producer from the plurality of agricultural asset producers. [ 00460 ] 87. The method of any of implementations 81-86, wherein the at least one automated/dynamic update to asset account information is based on a transaction between an asset producer and an asset purchaser. [ 00461 ] 88. A automated/dynamic geographic market data feed apparatus, comprising: a processor; and a memory disposed in communication with the processor and storing processor-issuable instructions to: maintain an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; receive an at least one automated/dynamic update to asset account information from at least one of the plurality of agricultural asset producers; determine aggregate market data for a geographic region from a set of the plurality of agricultural asset producers based on asset type data, asset location data, asset availability data and the at least one automated/dynamic update to asset account information; and generate an automated/dynamic geographic market data feed from the determined aggregate market data for the geographic region. [ 00462 ] 89. The apparatus of implementation 88, wherein asset account information includes in-field asset data. [ 00463 ] 90. The apparatus of implementation 88 or 89, wherein asset account information includes harvested asset data. [ 00464 ] 91. The apparatus of any of implementations 88-90, wherein asset account information includes asset storage data. [ 00465 ] 92. The apparatus of any of implementations 88-91, wherein the at least one automated/dynamic update to asset account information is received from a mobile device associated with an asset producer. [ 00466 ] 93. The apparatus of any of implementations 88-92, wherein the at least one automated/dynamic update to asset account information is based on a transaction between an asset producer and an asset purchaser. [ 00467] 94. A processor-readable tangible medium storing processor-issuable automated/dynamic geographic market data feed instructions to: maintain an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; receive an at least one automated/dynamic update to asset account information from at least one of the plurality of agricultural asset producers; determine aggregate market data for a geographic region from a set of the plurality of agricultural asset producers based on asset type data, asset location data, asset availability data and the at least one automated/dynamic update to asset account information; and generate a automated/dynamic geographic market data feed from the determined aggregate market data for the geographic region. [ 00468 ] 95. The medium of implementation 94, wherein asset account information includes in-field asset data. [ 00469 ] 96. The medium of implementation 94 or 95, wherein asset account information includes harvested asset data. [ 00470 ] 97. The medium of any of implementations 94-96, wherein asset account information includes asset storage data. [ 00471 ] 98. The medium of any of implementations 94-97, wherein the at least one automated/dynamic update to asset account information is received from a mobile device associated with an asset producer. [ 00472 ] 99. The medium of any of implementations 94-98, wherein the at least one automated/dynamic update to asset account information is based on a transaction between an asset producer and an asset purchaser.

[ 00473 ] !oo. A automated/dynamic geographic market data feed system, comprising: means to maintain an agricultural asset tracking account for each of a plurality of agricultural asset producers, each agricultural asset tracking account comprising agricultural asset account information including asset type data, asset location data, and asset availability data; means to receive an at least one automated/dynamic update to the agricultural asset account information associated with at least one of the plurality of agricultural asset producers; means to determine aggregate market data for at least one geographic region from a set of the plurality of agricultural asset producers based on the respective asset type data, asset location data, asset availability data and the at least one automated/dynamic update to the respective agricultural asset account information; means to generate a automated/dynamic geographic market data feed from the determined aggregate market data for the at least one geographic region; wherein maintaining an agricultural asset tracking account for an agricultural asset producer of the plurality of agricultural asset producers comprises: means to receive harvested agricultural asset storage resource information for an at least one harvested agricultural asset storage resource associated with the agricultural asset producer, the harvested agricultural asset storage resource information including location data; means to receive actual agricultural asset storage data for an at least one agricultural asset stored in the at least one harvested agricultural asset storage resource, the actual agricultural asset storage data including agricultural asset grain type and agricultural asset volume; and means to receive in-field agricultural asset information for an at least one agricultural asset associated with the agricultural asset producer, the in-field agricultural asset information including asset grain type and asset location data.

[ 00474 ] In order to address various issues and advance the art, the entirety of this application for GRAIN POSITION PLATFORM MANAGER APPARATUSES, METHODS AND SYSTEMS (including the Cover Page, Title, Headings, Field, Background, Summary, Brief Description of the Drawings, Detailed Description, Claims, Abstract, Figures, Appendices and/or otherwise) shows by way of illustration various embodiments in which the claimed innovations may be practiced. The advantages and features of the application are of a representative sample of embodiments only, and are not exhaustive and/or exclusive. They are presented only to assist in understanding and teach the claimed principles. It should be understood that they are not representative of all claimed innovations. As such, certain aspects of the disclosure have not been discussed herein. That alternate embodiments may not have been presented for a specific portion of the innovations or that further undescribed alternate embodiments may be available for a portion is not to be considered a disclaimer of those alternate embodiments. It will be appreciated that many of those undescribed embodiments incorporate the same principles of the innovations and others are equivalent. Thus, it is to be understood that other embodiments may be utilized and functional, logical, operational, organizational, structural and/or topological modifications may be made without departing from the scope and/or spirit of the disclosure. As such, all examples and/or embodiments are deemed to be non- limiting throughout this disclosure. Also, no inference should be drawn regarding those embodiments discussed herein relative to those not discussed herein other than it is as such for purposes of reducing space and repetition. For instance, it is to be understood that the logical and/or topological structure of any combination of any program components (a component collection), other components and/or any present feature sets as described in the figures and/or throughout are not limited to a fixed operating order and/or arrangement, but rather, any disclosed order is exemplary and all equivalents, regardless of order, are contemplated by the disclosure. Furthermore, it is to be understood that such features are not limited to serial execution, but rather, any number of threads, processes, services, servers, and/or the like that may execute asynchronously, concurrently, in parallel, simultaneously, synchronously, and/or the like are contemplated by the disclosure. As such, some of these features may be mutually contradictory, in that they cannot be simultaneously present in a single embodiment. Similarly, some features are applicable to one aspect of the innovations, and inapplicable to others. In addition, the disclosure includes other innovations not presently claimed. Applicant reserves all rights in those presently unclaimed innovations, including the right to claim such innovations, file additional applications, continuations, continuations in part, divisions, and/or the like thereof. As such, it should be understood that advantages, embodiments, examples, functional, features, logical, operational, organizational, structural, topological, and/or other aspects of the disclosure are not to be considered limitations on the disclosure as defined by the claims or limitations on equivalents to the claims. It is to be understood that, depending on the particular needs and/or characteristics of a GPPM individual and/or enterprise user, database configuration and/or relational model, data type, data transmission and/or network framework, syntax structure, and/or the like, various embodiments of the GPPM may be implemented that enable a great deal of flexibility and customization. For example, aspects of the GPPM may be adapted for non-plant farm uses and/or non-agricultural uses. While various embodiments and discussions of the GPPM have been directed to commodity inventory tracking, updating, and management, however, it is to be understood that the embodiments described herein may be readily configured and/or customized for a wide variety of other applications and/or implementations.

Claims

1 CLAIMS

2 What is claimed is:

3 l. A crop asset tracking processor-implemented method, comprising:

« enabling access to a producer crop asset management account for a producer;

5 receiving crop asset storage resource information, the crop asset storage resource

6 information including storage resource location data for an at least one cro storage

7 resource;

8 associating received crop asset storage resource information with the producer

9 crop asset management account;

10 associating an at least one mobile device with the producer crop asset

11 management account;

13 determining via a processor when the at least one mobile device is within a ii specified distance of the location of the at least one crop storage resource and the at

1 least one mobile device is one of a tablet computer anda smart phone

15 generating a notification on the at least one mobile device based on the

16 determination that the at least one mobile device is within the specified distance of the

17 location of the at least one crop storage resource, the notification including a request to i» provide real-time crop state data for the at least one crop storage resource;

19 receiving real-time crop state data for the at least one crop storage resource; and

20 associating the received real-time crop state data with the producer crop asset

21 management account.

22 2. The method of claim l, wherein the at least one crop storage resource is a crop

23 field.

25 3. The method of claim 1, wherein the at least one crop storage resource is a

26 harvested crop storage facility.

27 4. The method of claim 3, wherein the harvested crop storage facility is a storage

28 bin.

1 5. The method of any of claims 1-4, further comprising monitoring the location of

2 the at least one mobile device.

3 6. The method of any of claims 1-5, wherein receiving real-time crop state data

4 comprises receiving an at least one image captured by the mobile device via a camer

5 integrated with the mobile device, wherein the image is analyzed to determine crop state

6 data.

7 7. The method of any of claims 1-5, wherein receiving real-time crop state data s comprises receiving precision agricultural equipment data.

9 8. The method of any of claims 1-7, wherein the crop state data comprises volume

10 data.

11 9. The method of any of claims 1-7, wherein the crop state data comprises an

12 indication that the crop is ready for harvest.

13 10. A crop asset tracking apparatus, comprising:

14 a processor; and

15 a memory disposed in communication with the processor and storing processor-

16 issuable instructions to:

17 create a producer crop asset management account for a producer;

te receive crop asset storage resource information, the crop asset storage is resource information including storage resource location data for an at least one crop

20 storage resource;

21 associate received cro asset storage resource information with the

22 producer crop asset management account;

23 associate an at least one mobile device with the producer crop asset

2 management account;

25 determine when the at least one mobile device is within a specified 2β distance of the at least one crop storage resource location;

27 generate a notification on the at least one mobile device based on the

28 determination that the at least one mobile device is within the specified distance of the

29 at least one crop storage resource location, the notification including a request to

30 provide real-time crop volume data for the at least one crop storage resource;

31 receive real-time crop volume data for the a least one crop storage

32 resource; and 1 associate the received real-time crop volume data with the producer crop

2 asset management account.

3 11. The apparatus of claim lo, wherein receiving real-time crop volume data comprises receiving an at least one image captured by the mobile device

5 12. A processor-readable non-transitory tangible medium storing processor-

6 issuable crop asset tracking instructions to:

7 create a producer crop asset management am unt for a producer;

& receive crop asset storage resource information, the crop asset storage

9 resource information including storage resource location lata for an at least one crop

10 storage resource;

11 associate received crop asset storage resource information with the 2 producer crop asset management account;

13 associate an at least one mobile device with the producer crop asset 4 management account;

15 determine when the at least one mobile device is withi a specified ie distance of the at least one crop storage resource location;

17 generate a notification on the at least one mobile device based on the is determination that the at least one mobile device is within the specified distance of the 9 at least one crop storage resource location, the notification including a request to

20 provide real-time crop volume data for the at least one crop storage resource;

21 receive real-time crop volume data for the at least one crop storage

22 resource; and

23 associate the received real-time crop vohime data with the producer cro

2 asset management account.

25 13. Acrop asset tracking apparatus, comprising:

26 a processor; and

27 a memory disposed in communication with the processor and storing processor-

28 issuable instructions to:

29 provide, create a nd/ enable access to a producer crop asse management

30 account for a producer; i receive crop asset storage resource information, the crop asset storage i resource information including storage resource location data for an at least one crop

3 storage resource;

4 associate received crop asset storage resource information with the

5 producer crop asset management account;

6 associate an at least one mobile device with the producer crop asset

7 management account;

» determine when the at least one mobile device is withi a specified

9 di stance of the location of the at least one crop storage resource

10 generate a notification on the at least one mobile device based on the

11 determination that the at least one mobile device is within the specified distance of the2 location of the at least one crop storage resource, the notification including a request to ij provide real-time crop state data for the at least one crop storage resource;

« receive real-time crop state data for the at least one crop storage resource; is and

16 associate the received real-time crop state data with the producer crop

17 asset management account

14 14. The apparatus of claim 13, wherein the at least one cro storage resource is a

19 crop field.

20 15. The apparatus of claim 13, wherein the at least one crop storage resource is a

21 harvested crop storage facility.

22 16. The apparatus of claim 15, wherein the harvested crop storage facility is a

23 storage bin.

24 17. The apparatus of any of claims 13-16, further comprising instructions to

25 monitor the location of the at least one mobile device.

26 18. The apparatus of any of claims 13-17, wherein receiving real-time crop state

27 data comprises receiving an at least one image raptured by the mobile device.

28 19. The apparatus of any of claims 13-17, wherein, receiving real-time crop state

29 data comprises receiving precision agricultural equipment data.

30 20. The apparatus of any of claims 13-17, wherein receiving real-time crop state ji data comprises receiving satellite data. 1 ai. The apparatus of an of claims 13-17, wherein receiving real-time cro state

2 data comprises receiving satellite image data.

3 22. The apparatus of any of claims 13-21, wherein the crop state data comprises

4 volume data.

5 23. The apparatus of an of claims 13-21, wherein the crop state data comprises β an indication that the crop is ready for harvest.

7 24. A processor-readable non-transitory tangible medium storing processor- β issuable crop asset rxaddng instructions to:

9 provide, create and/or enable access to a producer ^'crop asset management

10 account for a producer;

11 receive crop asset storage resource information, the c op asset storage

12 resource information including storage resource location data for an at least one crop

13 storage resource;

14 associate received crop asset storage resource information with the is producer crop asset management account;

16 associate an at least one mobile device with the producer crop asset

17 management account;

1a determine when the at least one mobile device is within a specified

19 distance of the location of the at least one crop storage resource;

20 generate a notification on the at least one mobile device based on the 2⁾ determination that the at least one mobile device is within the specified distance of the

22 location of the at least one crop storage resource, the notification including a request to

23 provide real-time crop state data for the at least one crop storage resource;

24 receive real-time crop state data for the at least one crop storage resource;

25 and

2S associate the received real-time crop state data with the producer crop

27 asset management account.

28 25. The medium of claim 24, wherein the at least one crop storage resource is a

29 crop field.

30 26. The medium of claim 24, wherein the at least one crop storage resource is a

31 harvested crop storage facility.

1 27. The medium of claim 26, wherein the harvested crop storage facility is a

. storage bin.

3 28. The medium of any of claims 24-27, further comprising instructions to

4 monitor the location of the at least one mobile device.

5 29. The medium of any of claims 24-28, wherein receiving real-time crop state

6 data comprises receiving an at least one image captured by the mobile device.

7 30. The medium of any of claims 24-28, wherein receiving real-rime crop state β data comprises receiving precision agricultural equipment data.

9 31. The medium of any of claims 24-28, wherein receiving real-time crop state

10 data comprises receiving satellite data.

u 32. The medium of any of claims 24-28, wherein receiving real-time crop state

12 data comprises receiving satellite image data.

13 33· The medium of an of claims 24-32, wherein the crop state data comprises u Volume data.

15 34. The medium of any of claims 24-32, wherein the crop state data comprises an

16 indication that the crop is ready for harvest.

17 35. A crop asset tracking system, comprising:

1» means to provide, create and/or enable access to a producer crop asset

19 management account for a producer;

20 means to receive crop asset storage resource information, the crop asset

21 storage resource information inchtding storage resource location data for an at least one

22 crop storage resource;

3 means to associate received crop asset storage resource information with

24 the producer crop asset management account;

25 means to associate an at least one mobile device with the producer cro

26 asset management account;

27 means to determine when the at least one mobile device is within a

28 spedfied distance of the location of the at least one crop storage resource;

29 means to generate a notification on the at least one mobile device based on

30 the determination that the at least one mobile device is within the specified distance of 3t the location of the at least one crop storage resource, the notification including a request2 to provide real-time crop slate data for the at least one crop storage resource; 1 means to receive real-time crop state data for. the at least one crop storage

2 resource; and

3 means to associate the received real-lime crop state data with the producer crop asset management account.

5 36. The system of claim 35, wherein the at least one crop storage resource is a

6 crop field.

7 37. The system of claim 35, wherein the at least one crop storage resource is a

8 harvested crop storage facility.

9 38. The system of claim 37, wherein the harvested crop storage facility- is a

10 storage bin.

11 39. The system of any of claims 35-38, further comprising means to monitor the « location of the at least one mobile device,

13 40. The system of any of claims 35-39, wherein receiving real-time crop state

14 data comprises receiving an at least one image captured by the . mobile device.

15 41. The system of any of claims 35-39, wherein receiving real-time cro state data is comprises receiving precision agricultural equipment data,

17 42. The system of any of cla ims 35*39, wherein receiving real-time cro state data is comprises receiving satellite data.

19 43. The system of any of claims 35-39, wherein receiving real-time crop state data

20 comprises receiving satellite image data.

21 44. The system of any of claims 35-43, wherein the crop state data comprises

22 volume data.

23 45. The system of any of claims 35-43. wherein the cro state data comprises an

24 indication that the crop is ready for harvest.

25 46. An agricultural commodity asset management processor-implemented

26 method, comprising:

27 providing, creating, maintaining, and/or enabling access to an agricultural

28 commodity asset management account for an agricultural assetproduoer;

29 receiving harvested agricultural asset storage resource information for an at least

30 one harvested agricultural asset storage resource associated with the agricultural asset

31 producer, the harvested agricultural asset storage resource information includin

32 location data; 1 receiving actual agricultural asset storage data for an at least one agricultural

2 asset stored in the at least one harvested agricultural asset storage resource, the actual

3 agricultural asset storage data including agricultural asset crop type and agricultural * asset volume;

5 receiving in-field agricultural asset information for an at least one agricultural

6 asset associated with the agricultural asset producer, the in- field agricultural asset

7 information including agricultural asset crop type and agricultural asset location data; β receiving agricultural financial instrument data for an at least one agricultural

9 financial instrument associated with the agricultural commodity asset management

10 account;

11 receiving agricultural asset market data;

12 determining via a processor an agricultural asset portfolio value for the u agricultural commodity asset management account based on the actual agricultural

14 asset storage data, the in-field agricultural asset information, the agricultural financial

15 instrument data and the agricultural asset market data;

16 receiving real-time update information for at least one of the actual agricultural 7 asset storage data and the in-field agricultural asset information; :

is updating the detennined agricultural asset portfolio value based on the received 1» real-time update information; and

20 outputting the updated agricultural asset portfolio value for the agricultural

2 commodity asset management account.

22 47. The method of claim 46, wherein the real-time update information is

23 provided via a mobile device associated with the agricultural asset producer.

24

25 48. The method of claim 46 or 47, wherei the at least one harvested agriculturala asset storage resource is on-farm storage.

27 49. The method of any of claims 46-48, wherein the at least one harvested8 agricultural asset storage resource is shared with an at least one other asset agricultural9 producer.

0 50. An agricultural commodity asset management apparatus, comprising:

31 a processor; and 1 a memory disposed in communication with the processor and storing processor-

2 issuable instructions to:

3 provide, create, maintain and/or enable access to an agricultural

4 commodity asset management account for an agricultural asset producer;

5 receive harvested agricultural asset storage resource information for an at

6 least one harvested agricultural asset storage resource associated with the agricultural

7 asset producer, the harvested agricultural asset storage resource information including

8 location data;

9 receive actual agricultural asset storage data for an at least one agricultural

10 asset stored in the at least one harvested agricultural asset storage resource, the actual it agricultural asset storage data including agricultural asset cro type and agricultural 12 asset volume;

is receive in-field agricultural asset information for an at least one agricultural asset associated with agricultural asset producer, in-field agricultural assetis information including agricultural asset crop type nd location data;

16 receive agricultural financial instrument data for an at least one

17 agricultural financial instrument associated with the agricultural commodity asset i« management account;

19 receive agricultural asset market data;

20 determine an agricultural asset portfolio value for the agricultural

21 commodity asset management account based on the actual agricultural asset storage

22 data, the in-field agricultural asset information, the agricultural financial instrument

23 data and the agricultural asset market data;

2 receive real-time update information for at least one of the actual 2s agricultural asset storage data and the in-field agricultural asset information;

26 update the determined agricultural asset portfolio value, based on the

27 received real-time update information; and

28 output the updated agricultural asset portfolio value for the agricultural

29 commodity asset management account.

30 51. The apparatus of claim 50, wherein the real-time update information is

31 provided via a mobile device associated with the agricultural asset producer.

1 52. The apparatus of claim 50 or 51, wherein the at least one harvested

2 agricultural asset storage resource is on-farm storage.

3 53- The apparatus of claim 50, 51 or 52, wherein the at least one harvested agricultural asset storage resource is shared with an at least one other asset agricultural

5 producer.

6 54. A processor-readable tangible medium storing processor-issuablc agricultural

7 commodity asset management instractions to:

β provide, create, maintain and/or enable access to an agricultural commodity

9 asset management account for an agricultural asset producer;

0 receive harvested agricultural asset storage resource information for an at least1 one harvested agricultural asset storage resource associated with the agricultural asset2 producer, the harvested agricultural asset storage resource information including3 location data;

4 receive actual agricultural asset storage data for an at least one agricultural assets stored in the at least one harvested agricultural asset storage resource, the actual6 agricultural asset storage data including agricultural asset crop type and agricultural7 asset volume;

8 receive in-field agricultural asset mformation for an least one agricultural asset9 associated with agricultural asset producer, in-field agricultural asset information0 including agricultural asset crop type and location data

1 receive agricultural financial instrument data for an at least one agricultural2 financial instrument associated with the agricultural commodity asset management3 account;

4 receive agricultural asset market data;

5 determine an agricultural asset portfolio value for the agricultural commodity5 asset management account based on the actual agricultural asset storage data, the in-7 field agricultural asset information, the agricultural financial instrument data and the4 agricultural asset market data;

9 receive real-time update information for at least one of the actual agricultural0 asset storage data and the in-field agricultural asset information

1 update the determined agricultural asset portfolio value based on the received2 real-time update information; and

I output the updated agricultural asset portfolio value for the agricultural a commodity asset management account.

3 55. The medium of claim 54, wherein the real-time update information is

4 provided via a mobile device associated with the agricultural asset producer.

5 56. The medium of claim 54 or 55, wherein the at least one harvested agricultural B asset storage resource is on-farm storage.

7 57. The medium of claim 54, 55, or 56, wherein the at least one harvested

8 agricultural asset storage resource is shared with an at least one other asset agricultural

9 producer.

10 58. An agricultural commodity asset management system, comprising:

II means to provide, create, maintain and/or enable access to an agricultural 12 commodity asset management account for an agricultural asset producer;

u receive harvested agricultural asset storage resource information for an at least

1 one harvested agricultural asset storage resource associated with the agricultural asset

15 producer, the harvested agricultural asset storage resource information including

16 location data;

17 means to receive actual agricultural asset storage data for an at least ones agricultural asset stored in the at least one harvested agricultural asset storage resource,

19 the actual agricultural asset storage data including agricultural asset crop type and

20 agricultural asset volume;

21 means to receive in-field agricultural asset information for an at least one

22 agricultural asset associated with agricultural asset producer, in-field agricultural asset

23 information including agricultural asset crop type and location: data

24 means to receive agricultural financial instrument data for an at least one

25 agricultural financial instrument associated with the agricultural commodity asset

26 management account;

27 means to receive agricultural asset market data;

28 means to determine an agricultural asset portfolio value for the agricultural

29 commodity asset management account based on the actual agricultural asset storage so data, the in-field agricultural asset information, the agricultural financial instrument 31 data and the agricultural asset market data;

I means to receive real-time update information for at least one of the actual z agricultural asset storage data and the in-field agricultural asset information;

3 means to update the determined agricultural asset portfolio value based on the received real-time update information; and

s means to output the updated agricultural asset portfolio value for the agricultural

6 commodity asset management account.

7 59. The system of claim 58, wherein the at least one harvested agricultural asset

5 storage resource is on-farm storage.

9 60. The system of claim 58 or 59, wherein the at least one harvested agricultural0 asset storage resource is shared with an at least one other asset agricultural producer.I 61. A crop purchase management processor-implemented method, comprising:2 receiving crop storage resource information for each, of a plurality of crop3 producers, the crop storage resource information including crop storage resource4 location data, stored crop type data, and stored crop volume data;

5 receiving a location-based, crop-specific purchuse inquir from an at least one6 purchaser;

7 determining via a processor an aggregate crop volume available for purchases from the received crop storage resource information based on the location-based, crop-9 specific purchase inquiry and the crop storage resource location data, stored crop type0 data, and stored crop volume data, the determination comprising accessing and/or1 utilizing data from at least a threshold number of crop producers;

2 providing the determined aggregate crop volume available for purchase to the at3 least one purchaser in response to the received location-based, crop-specific purchase4 inquiry;

5 receiving a purchase request from the purchaser based on the provided aggregateβ crop volume available for purchase, the purchase request specifying at least one of a? crop type, a crop purchase volume and crop purchase price; and

a facilitating a transaction for the specified crop type between the purchaser and at9 least one of the plurality of crop producers based on the received purchase request.0

1 62. The method of claim 6x, wherein the received location-based, crop-specific

2 purchase inquiry includes initial boundaiy parameters defining a geographic search

3 area.

4

s 63. The method of claim 62, wherein the initial geographic boundary parameters

6 include a geographic search radius.

7 64. The method of claim 62 or 63, further comprising:

» modifying the initial boundary parameters to provid data from at least the

9 threshold number of crop producers.

10 65. A crop purchase management apparatus, comprising:

11 a processor; and

12 a memory disposed in communication with the processor and storing processor-

13 issuable instructions to:

1* receive crop storage resource information for each of a plurality of crop

15 producers, the crop storage resource information including crop storage resource

16 location data, stored crop type data, and stored crop volume data;

17 receive an at least one location-based, crop-specific purchase inquiry from ia an at least one purchaser;

19 determine an aggregate crop volume available for purchase from received

20 crop storage resource information based on the location-based, crop-specific purchase

21 inquiry and the crop storage resource location data, stored crop type data, and stored

22 crop volume data, the determination comprising accessing and utilizing data from at

23 least a threshold number of crop producers;

24 provide the determined aggregate crop volume available for purchase to

25 the at least one purchaser in response to the received locat on-based, crop-specific M purchase inquiry;

27 receive a purchase request from the purchaser based on the provided

28 aggregate crop volume available for purchase, the purchase request specifying at least

29 two of a crop type, a crop purchase volume, and crop purchase price; and

30 execute a transaction for the specified crop type between the purchaser

31 and at least one of the plurality of crop producers based on the received purchase 52 request.

1 66. The apparatus of claim 65, wherein the received location-based, crop-specific

2 purchase inquiry includes initial boundary parameters defining a geographic search i area.

4 67. The apparatus of claim 66, wherein the initial geographic boundary

$ parameters include a geographic search radius.

6 68. The apparatus of claim 66 or 67, further comprising processor-issuable

7 instructions to:

8 modify the initial boundary parameters to provide data from at least the

9 threshold number of crop producers.

0 69. A processor-readable tangible medium storin processor-issuable crop1 purchase management instructions to:

2 receive crop storage resource information for each of a plurality of crop3 producers, the crop storage resource information including crop storage resourc4 location data, stored crop type data, and stored croi» .volume data;

5 receive a location-based, crop-specific purchase inquiry from an at least ones purchaser;

7 determine an aggregate crop volume available for purchase from received cros storage resource information based on the location-based, crop-specific purchase9 inquiry and the crop storage resource location data, stored_. crop type data, and stored0 crop volume data, the determination including data from at least a threshold number of1 crop producers;

2 provide the determined aggregate crop volume available for purchase to the at3 least one purchaser in response to the received location-based, crop-specific purchase inquiry;

5 receive a purchase request from the purchaser based on the provided aggregate6 crop volume available for purchase, the purchase request specifying cro type and at7 least one of a crop purchase volume and crop purchase price and

e execute a transaction for the specified crop type between the purchaser and at9 least one of the plurality of crop producers based on the received purchase

0 70. The medium of claim 69, wherein the received location-based, crop-specific1 purchase inquiry includes initial boundary parameters defining a geographic search2 area. ι 71. The medium of claim 70, wherein the initial geographic boundary parameters

2 include a geographic search radius.

3 72. The medium of claim 70 or 71, further comprising instructions to:

4 modify the initial boundary parameters to provide dat from at least the

5 threshold number of crop producers.

s 73. A crop purchase management system, comprising:

7 means to receive crop storage resource information for each of a plurality of crop

8 producers, the crop storage resource information including crop storage resource

9 location data, stored crop type data, and stored crop volume data;

10 means to receive an at least one location -based, crop-specific purchase inquiry

11 from an at least one purchaser;

12 means to detennine an aggregate crop volume available for purchase from

13 received crop storage resource information based on the location-based, crop-specific

14 purchase inquiry and the crop storage resource location data, stored crop type data, and is stored crop volume data, the determination comprising accessing and utilizing data ie from at least a threshold number of crop producers;

17 means to provide the determined aggregate crop volume available for purchase to

18 the at least one purchaser in response to the received location-based, crop-specific

19 purchase inquiry;

20 means to receive a purchase request from the purchaser based on the provided

21 aggregate crop volume available for purchase, the purchase request specifying at least

22 two of a crop type, a crop purchase volume, and crop purchase price; and

23 means to execute a transaction for the specified ^'.crop type between the purchaser

2 and at least one of the plurality of crop producers based on the received purchase

25 request.

26 74. The system of claim 73, wherein the received location-based, crop-specific

27 purchase inquiry includes initial boundary parameters defining a geographic search

28 area.

29 75. The system of claim 74, wherein the initial geographic boundary parameters

30 include a geographic search radius.

1 76. The system of claim 75 or 76, further comprising: 1 means to modify the initial boundary parameters to provide data from at least the

2 threshold number of crop producers.

3 77. The method of any of claims 61-64, wherein the purchaser is livestock raiser

4 or a feedlot.

5 78. The apparatus of any of claims 65-68, wherein the purchaser is livestock

6 raiser or a fccdlot.

7 79. The medium of any of claims 69-72, wherein the purchaser is livestock raiser s or a feedlot.

9 80. The system of any of claims 73-76, wherein the purchaser is livestock raiser

10 or a fccdlot.

11 81. A real-time geographic market data, feed processor-implemented method,

12 comprising:

13 maintaining an agricultural asset tracking account for each of a plurality of

14 agricultural asset producers, each agricultural asset tracking accoun comprising

15 agricultural asset account information including asset type data, asset location data, and ie asset availability data;

17 receiving an at least one real-time update to the agricultural asset account

16 information associated with at least one of the plurality of agricultural asset producers;

19 determining via a processor aggregate marke data for at least one geographic

20 region from a set of the plurality of agricultural asset producers based on the respective

21 asset type data, asset location data, asset availability data and the at least one real-time

22 update to the respective agricultural asset account information; and

23 generating a real-time geographic market data feed from the determined

24 aggregate market data for the at least one geographic region.

2$ 82. The method of claim 1, wherein maintaining an agricultural asset tracking

26 account for an agricultural asset producer of the plurality of agricultural asset producers

27 comprises:

28 receiving harvested agricultural asset storage resource information for an at least

29 one harvested agricultural asset storage resource associated with the agricultural asset M producer, the harvested agricultural asset storage resource information including 31 location data; 1 receiving actual agricultural asset storage data for an at least one agricultural

2 asset stored in the at least one harvested agricultural asset storage resource, the actual

3 agricultural asset storage data including agricultural asset crop type and agricultural

4 asset volume; and

5 receiving in-field agricultural asset information, for an at least one agricultural

6 asset associated with the agricultural asset producer, the in-field agricultural asset

7 information including asset crop type and asset location data.

a

83. The method of claim 8a or 82, wherein agricultural asset account information

9 includes in-field asset data.

0 84. The method of claim 81, 82 or 83, wherei agricultural asset account1 information includes harvested asset data.

2 85. The method of an of claims 81-84, wherein agricultural asset account3 information includes asset storage data.

86. The method of any of claims 81-85, wherein the at least one real-time update5 to agricultural asset account information is received from mobile device associated6 with an agricultural asset producer from the plurality of agricultural asset producers.7 87. The method of any of claims 81-86, wherein the at least one real-time updates to asset account information is based on a transaction between an asset producer and an9 asset purchaser.

0 88. A real-time geographic market data feed apparatus, comprising:

1 a processor; and

2 a memory disposed in communication with the processor and storing processor-3 issuable instructions to:

4 maintain an agricultural asset tracking- account for each of a plurality of5 agricultural asset producers, each agricultural asset tracking account comprising6 agricultural asset account information including asset type data, asset location data, and7 asset availability data;

β receive an at least one real-time update to asset account informa tion from9 at least one of the plurality of agricultural asset producers; . 1 determine aggregate market data for a geographic region from a set of the

2 plurality of agricultural asset producers based on asset type data, asset location data,

3 asset availability data and the at least one real-time update to asset account ♦ information; and

s generate a real-time geographic market data feed from the determined

6 aggregate market data for the geographic region.

7 89. The apparatus of claim 88, wherein asset account information includes in-

8 field asset data.

9 90. The apparatus of claim 88 or 89, wherein asset account information includes ia harvested asset data.

11 91. The apparatus of any of claims 88-90, wherein asset account information

12 includes asset storage data.

13 92. The apparatus of any of claims 88-91, wherein the at least one real-time

14 update to asset account information is received from a mobile device associated with an

15 asset producer.

ie 93. The apparatus of any of claims 88-92, wherein the ut least one real-time

17 update to asset account information is based on a transaction between an asset producer is and an asset purchaser.

19 94· A processor-readable tangible medium storing processor-issuabie real-time

20 geographic market data feed instructions to:

21 maintain an agricultural asset tracking account for each of a plurality of

22 agricultural asset producers, each agricultural asse tracking account comprising

23 agricultural asset account information including asset type data, asset location data, and 2« asset availability data;

25 receive an at least one real-time update to asset account information from at least

2fi one of the plurality of agricultural asset producers;

27 determine aggregate market data for a geographic region from a set of the

28 plurality of agricultural asset producers based on asse type data, asset location data,

29 asset availability data and the at least one real-time update to asset account

30 information; and

31 generate a real-time geographic market data feed from the determined aggregate

32 market data for the geographic region.

2 95. The medium of claim 94, wherein asset account information includes in-field

3 asset data.

4 96. The medium of claim 94 or 95, wherein asset account information includes

5 harvested asset data.

5 97. The medium of any of claims 94-96, wherein asset account information 7 includes asset storage data.

i 98. The medium of any of claims 94-97, wherein the at least one real-time update s to asset account information is received from a mobile device associated with an asset

10 producer.

11 99. The medium of any of claims 94-98, wherein the at least one real-time update

12 to asset account information is based on a transaction between an asset producer and an

13 asset purchaser.

14 100. A real-time geographic market data feed system, comprising:

15 means to maintain an agricultural asset tracking account for each of a plurality of

16 agricultural asset producers, each agricultural asset tracking account comprising

17 agricultural asset account information including asset type data, asset location data, and « asset availability data;

19 means to receive an at least one real-time update to the agricultural asset account

2a information associated with at least one of the plurality of agricultural asset producers;

21 means to determine aggregate market data for at least one geographic region

22 from a set of the plurality of agricultural asset producers based on the respective asset

23 type data, asset location data, asset availability data and the at least one real-time

24 update to the respective agricultural asset account information;

25 means to generate a real-time geographic market data feed from the determined

26 aggregate market data for the at least one geographic region;

27 wherein maintaining an agricultural asset tracking account for an 2. agricultural asset producer of the plurality of agricultural asset producers comprises:

29 means to receive harvested agricultural asset storage resource information

30 for an at least one harvested agricultural asset storage resource associated with the

31 agricultural asset producer, the harvested agricultural asset storage resource

32 information including location da a; 1 means to receive actual agricultural asset storage dat for an at least one

2 agricultural asset stored in the at least one harvested agricultural asset storage resource, i the actual agricultural asset storage data including agricultural asset crop type and

4 agricultural asset volume; and

5 means to receive in-field agricultural asset information for an at least one

6 agricultural asset associated with the agricultural asset producer, the in-field

7 agricultural asset information including asset crop type and asset location data.

8 lot. The method of claim 6, wherein the analysis includes determination of a frost or condensation line.

0 102. The method of claim 6, wherein the analysis comprises three-dimensionali analysis

2 103. The method of claim 6, wherein the analysis includes comparison of the3 image to an at least one previously-captured image.

4

5

6

7