EP3437040A1

EP3437040A1 - Cold chain distribution data prioritization

Info

Publication number: EP3437040A1
Application number: EP17715592.6A
Authority: EP
Inventors: John Cronin; Seth Cronin
Original assignee: Carrier Corp
Current assignee: Carrier Corp
Priority date: 2016-03-28
Filing date: 2017-03-22
Publication date: 2019-02-06
Also published as: CN108885735A; WO2017172443A1

Abstract

A method for distributing cold chain data includes storing cold chain data in a cold chain database; storing user data in a network database; receiving a user identifier from a user device; retrieving a cold chain role associated with the user identifier from the network database; prioritizing the cold chain data from the cold chain database in response to the cold chain role to generate prioritized cold chain data; and sending the prioritized cold chain data to the user device.

Description

COLD CHAIN DISTRIBUTION DATA PRIORITIZATION

BACKGROUND

[0001] The embodiments disclosed herein generally relate to cold chain distribution systems, and more specifically to prioritization of data obtained throughout a cold chain distribution system.

[0002] Typically, cold chain distribution systems are used to transport and distribute perishable goods and environmentally sensitive goods (herein referred to as perishable goods) that may be susceptible to temperature, humidity, and other environmental factors. Perishable goods may include but are not limited to fruits, vegetables, grains, beans, nuts, eggs, dairy, seed, flowers, meat, poultry, fish, ice, and pharmaceuticals. Advantageously, cold chain distribution systems allow perishable goods to be effectively transported and distributed without damage or other undesirable effects.

[0003] Refrigerated trucks and trailers are commonly used to transport perishable goods in a cold chain distribution system. A transport refrigeration system is mounted to the truck or to the trailer in operative association with a cargo space defined within the truck or trailer for maintaining a controlled temperature environment within the cargo space.

[0004] Along the cold chain distribution network, data may be collected by various entities. A grower may record a product description, harvest temperature, ripening schedules, etc. The refrigerated container/truck may record locations, cargo temperatures, transport route, refrigeration system parameters, etc. A distributor may record entry and exit times for cargo, cargo condition, layover times, etc. A retailer may record arrival times, cargo condition, cargo temperatures, etc. One problem in existing cold chain distribution systems is that the large amount of data is inaccessible to parties along the distribution network. For example, the retailer cannot access the grower's data. Further, the vast amount of data can be overwhelming to those attempting to analyze the data for relevance to their own operations.

BRIEF DESCRIPTION

[0005] According to one embodiment, a method for distributing cold chain data includes storing cold chain data in a cold chain database; storing user data in a network database; receiving a user identifier from a user device; retrieving a cold chain role associated with the user identifier from the network database; prioritizing the cold chain data from the cold chain database in response to the cold chain role to generate prioritized cold chain data; and sending the prioritized cold chain data to the user device. [0006] In addition to one or more of the features described above, or as an alternative, further embodiments may include wherein prioritizing the cold chain data from the cold chain database in response to the cold chain role comprises executing a business module associated with the cold chain role.

[0007] In addition to one or more of the features described above, or as an alternative, further embodiments may include comparing the user identifier to the network database; and allowing access to the cold chain data only when the user identifier is present in the network database.

[0008] In addition to one or more of the features described above, or as an alternative, further embodiments may include sending a request to the user device for further cold chain data; and receiving further cold chain data from the user device.

[0009] In addition to one or more of the features described above, or as an alternative, further embodiments may include storing the further cold chain data in the cold chain database.

[0010] In addition to one or more of the features described above, or as an alternative, further embodiments may include retrieving a partner associated with the user identifier from the network database; providing the further cold chain data to the partner.

[0011] In addition to one or more of the features described above, or as an alternative, further embodiments may include wherein the cold chain data includes data received from at least one sensor located on a transport refrigeration system.

[0012] In addition to one or more of the features described above, or as an alternative, further embodiments may include wherein the prioritizing the cold chain data include filtering the cold chain data.

[0013] In addition to one or more of the features described above, or as an alternative, further embodiments may include wherein the prioritizing the cold chain data includes arranging the prioritized cold chain data in a sequence of most important to least important.

[0014] In addition to one or more of the features described above, or as an alternative, further embodiments may include receiving user-defined analysis of the cold chain data; storing the user-defined analysis of the cold chain data in the cold chain database.

[0015] According to another embodiment, a cold chain data prioritization system includes a processor; and a memory comprising computer-executable instructions that, when executed by the processor, cause the processor to perform operations, the operations including: storing cold chain data in a cold chain database; storing user data in a network database; receiving a user identifier from a user device; retrieving a cold chain role associated with the user identifier from the network database; prioritizing the cold chain data from the cold chain database in response to the cold chain role to generate prioritized cold chain data; and sending the prioritized cold chain data to the user device.

[0016] According to another embodiment, a computer program product tangibly embodied on a computer readable medium, the computer program product including instructions that, when executed by a processor, cause the processor to perform operations including: storing cold chain data in a cold chain database; storing user data in a network database; receiving a user identifier from a user device; retrieving a cold chain role associated with the user identifier from the network database; prioritizing the cold chain data from the cold chain database in response to the cold chain role to generate prioritized cold chain data; and sending the prioritized cold chain data to the user device.

[0017] Technical effects of embodiments include the collection of data along multiple portions of a cold chain distribution network and prioritizing cold chain data in response to a cold chain role of a user requesting cold chain data.

[0018] Other aspects, features, and techniques of the invention will become more apparent from the following description taken in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The subject matter which is regarded as the disclosure is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features and advantages of the disclosure are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

[0020] FIG. 1 depicts a data collection environment and data prioritization system in an exemplary embodiment;

[0021] FIG. 2 depicts a schematic view a cold chain distribution network in an exemplary embodiment;

[0022] FIG. 3 depicts a data prioritization system in an exemplary embodiment;

[0023] FIG. 4 depicts a user interface for data prioritization system setup in an exemplary embodiment;

[0024] FIG. 5 depicts a process for data prioritization system setup in an exemplary embodiment;

[0025] FIG. 6 depicts a process for data prioritization system access in an exemplary embodiment; [0026] FIG. 7 depicts a process for data prioritization in an exemplary embodiment; and

[0027] FIG. 8 depicts a business module of the data prioritization system in an exemplary embodiment.

DETAILED DESCRIPTION OF THE DISCLOSURE

[0028] Referring now to the drawings, FIG. 1 depicts a cold chain data collection environment and a data prioritization system 90 in an exemplary embodiment. Transport refrigeration system 20 is used to transport and distribute perishable goods and environmentally sensitive goods (herein referred to as perishable goods 34). It is understood that embodiments described herein may be applied to shipping goods that are not perishable. In the illustrated embodiment, a transport refrigeration system 20 includes an environmentally controlled container 14 with a transport refrigeration unit 28 for transporting perishable goods 34. The container 14 may be pulled by a tractor 12. It is understood that embodiments described herein may be applied to shipping containers that are shipped by rail, sea, or any other suitable container, without use of a tractor 12. The container 14 may define an interior compartment 18.

[0029] In the illustrated embodiment, the transport refrigeration unit 28 is associated with a container 14 to provide desired environmental parameters, such as, for example temperature, pressure, humidity, carbon dioxide, ethylene, ozone, light exposure, vibration exposure, and other conditions to the interior compartment 18. In further embodiments, the transport refrigeration unit 28 is a refrigeration system capable of providing a desired temperature and humidity range. The perishable goods 34 may include but are not limited to fruits, vegetables, grains, beans, nuts, eggs, dairy, seed, flowers, meat, poultry, fish, ice, blood, pharmaceuticals, or any other suitable cargo requiring cold chain transport.

[0030] In the illustrated embodiment, the transport refrigeration system 20 includes sensors 22. The sensors 22 may be utilized to monitor parameters internal and external to the container 14. The parameters monitored by the sensors 22 may include, but are not limited to, temperature, pressure, humidity, carbon dioxide, ethylene, ozone, light exposure, vibrations, and other conditions in the interior compartment 18. Accordingly, suitable sensors 22 are utilized to monitor the desired parameters. Sensors 22 may be selected for certain applications depending on the type of perishable goods 34 to be monitored and the corresponding environmental sensitivities. In an embodiment, temperatures are monitored. As seen in FIG. 1, the sensors 22 may be placed directly on the perishable goods 34. [0031] Further, as in the illustrated embodiment, sensors 22 may be used to monitor various parameters of the transport refrigeration system 20. These sensors 22 may be placed in a variety of locations including, but not limited to, on the transport refrigeration unit 28, on a door 36 of the container 14 and throughout the interior compartment 18. The sensors 22 may be placed directly within the transport refrigeration unit 28 to monitor the performance of the transport refrigeration unit 28. Individual components internal to the transport refrigeration unit 28 may also be monitored by sensors 22 to detect performance aspects, such as, for example usage cycles, duration, temperatures and pressure of individual components. As seen, the sensors 22 may also be placed on the door 36 of the container 14 to monitor the position of the door 36. Whether the door 36 is open or closed affects both the temperature of the container 14 and the perishable goods 34. For instance, in hot weather, an open door 36 will allow cooled air to escape from the container 14, causing the temperature of the interior compartment 18 to rise, thus affecting the temperature of the perishable goods 34. Additionally, a global positioning system (GPS) location may also be detected by the sensors 22. The GPS location may help in providing time-based location information for the perishable goods 34 that will help in tracking the travel route and other parameters along that route. For instance, the GPS location may also help in providing information from data sources 40 regarding weather 42 experienced by the container 14 along the travel route. The local weather 42 affects the temperature of the container 14 and thus may affect the temperature of the perishable goods 34.

[0032] As illustrated in FIG. 1, the transport refrigeration system 20 may further include a controller 30 configured to log data from the sensors 22 at a selected sampling rate. The controller 30 may be enclosed within the transport refrigeration unit 28 or separate from the transport refrigeration unit 28 as illustrated. The data may further be augmented with time, location stamps or other relevant information. The controller 30 may also include a processor (not shown) and an associated memory (not shown). The processor may be but is not limited to a single-processor or multi-processor system of any of a wide array of possible architectures, including field programmable gate array (FPGA), central processing unit (CPU), application specific integrated circuits (ASIC), digital signal processor (DSP) or graphics processing unit (GPU) hardware arranged homogenously or heterogeneously. The memory may be but is not limited to a random access memory (RAM), read only memory (ROM), or other electronic, optical, magnetic or any other computer readable medium.

[0033] In an illustrated embodiment, the transport refrigeration system 20 may include a communication module 32 in operative communication with the controller 30 and in wireless operative communication with a network 60. The communication module 32 is configured to transmit data to the network 60 via wireless communication. The wireless communication may be, but is not limited to, radio, microwave, cellular, satellite, or another wireless communication method. The network 60 may be but is not limited to satellite networks, cellular networks, cloud computing network, wide area network, or another type of wireless network. The communication module 32 may include a short range interface, wherein the short range interface includes at least one of: a wired interface, an optical interface, and a short range wireless interface.

[0034] Data may also be provided by data sources 40, as illustrated in FIG. l. These data sources 40 may be collected at any point throughout the cold chain distribution network 200, which as illustrated in FIG. 2 may include harvest 204, packing 206, storage prior to transport 208, transport to distribution center 210, distribution center 212, transport to display 214, storage prior to display 216, display 218 and consumer 220. These stages are provided for illustrative purposes and a distribution chain may include fewer stages or additional stages, such as, for example a cleaning stage, a processing stage, and additional transportation stages. It is understood that the cold chain distribution system 200 is exemplary, and a variety of other stages may be included.

[0035] Referring to FIG. 1, the data sources 40 may include, but are not limited to, weather 42, quality inspections 44, inventory scans 46, and manually entered data 48. Additional data sources are described with reference to FIG. 3. The weather 42, as discussed above, has an effect on the operation of the transport refrigeration unit 28 by influencing the temperature of the container 14 during transport (e.g., 210 and 214) but the weather 42 also has other influences on the transport refrigeration unit 28. For instance, the weather 42 prior to and at harvest 204 may have an impact on the quality of the perishable goods 34, which may be interesting for a consumer. Moreover, quality inspections 44, similar to the weather 42, may reveal data of the perishable goods 34 relevant to the consumer. For instance, a particular batch of strawberries may have the required sugar content desired by the consumer. Quality inspections 44 may be done by a machine or a human being. Quality inspections 44 performed by a machine may be accomplished using a variety of techniques including but not limited to optical, odor, soundwave, infrared, or physical probe.

[0036] Further inventory scans 46, may also reveal data about the perishable goods 34 interesting to the consumer and may help in tracking the perishable goods 34. For instance, the inventory scan 46 may reveal the time, day, truck the perishable goods arrived on, which may help pinpoint their source. While the system 10 includes sensors 22 to aid in automation, often times the need for manual data entry is unavoidable. The manually entered data 48 may be input via a variety of devices including but not limited to a cellular phone, tablet, laptop, smartwatch, a desktop computer or any other similar data input device.

[0037] Data collected throughout each stage of the cold chain distribution system 200 may include environment conditions experienced by the perishable goods 34 such as, for example, temperature, pressure, humidity, carbon dioxide, ethylene, ozone, vibrations, light exposure, weather, time and location. For instance, strawberries may have experienced an excessive shock or were kept at 34°F during transport. Data may further include attributes of the perishable goods 34 such as, for example, temperature, weight, size, sugar content, maturity, grade, ripeness, labeling, and packaging. For instance, strawberries may be packaged in 1 pound clamshells, be a certain weight or grade, be organic, and have certain packaging or labels on the clamshells. Data may also include information regarding the operation of the environmental control unit 28, as discussed above. The data may further be augmented with time, location stamps or other relevant information.

[0038] In the illustrated embodiment, the system 10 further includes a storage device 80 to store the cold chain data acquired along the cold chain distribution network. The storage device 80 may be, but is not limited to, a random access memory (RAM), read only memory (ROM), or other electronic, optical, magnetic or any other computer readable medium. Storage device 80 may be imbedded in network 60 (e.g., cloud based storage) or be a remote system accessible via network 60.

[0039] In the illustrated embodiment, the system 10 further includes a data prioritization system 90. The data prioritization system 90 may also include a processor 91 and an associated memory 92. The processor 91 may be, but is not limited to, a single- processor or multi-processor system of any of a wide array of possible architectures, including field programmable gate array (FPGA), central processing unit (CPU), application specific integrated circuits (ASIC), digital signal processor (DSP) or graphics processing unit (GPU) hardware arranged homogenously or heterogeneously. The memory 92 may be but is not limited to a random access memory (RAM), read only memory (ROM), or other electronic, optical, magnetic or any other computer readable medium. In operation, processor 91 executes computer program instructions in the memory 92 to execute the operations describe herein.

[0040] FIG. 3 depicts the data prioritization system 90 in further detail in an exemplary embodiment. The data prioritization system 90 receives cold chain data from a number of sources. As shown in Figure 1, the sources include the transport refrigeration system 20 and sources 40. FIG. 3 depicts additional cold chain data sources in the form of growers 102, logistics 104, truck drivers/distribution 106 and retail/wholesalers 108. It is understood that other sources of cold chain data may be employed, and FIG. 3 depicts examples. The cold chain data may be stored in storage device 80, which may be part of the data prioritization system 90 or a separate storage device. A user device 110 interfaces with the data prioritization system 90 to both send cold chain data to the data prioritization system 90 and to receive prioritized cold chain data from the data prioritization system 90.

[0041] The storage device 80 may include a network database 82 and a cold chain database 84. The network database 82 may store user profiles including a user identifier, user type, user partners, data types, etc. Creation of records on the network database 82 is described in further detail herein. The cold chain database 84 includes cold chain data from the various sources, such as data sources 102, 104, 106 and 108.

[0042] The data prioritization system 90 executes a plurality of business modules 94. The business modules 94 are unique to different types of users and operate to prioritize data in response to a user type. As described in further detail herein, when a user contacts the data prioritization system 90, the data prioritization system 90 determines the user identity and user type, and then launches the corresponding business module 94 for that user type. The business modules 94 provide the user with a mechanism to submit cold chain data and retrieve prioritized cold chain data. Operation of the business modules 94 is described in further detail herein with reference to FIG. 7.

[0043] The user device 110 may be implemented using a processor based device that has access to network 60. The user device may be a general-purpose computer, a tablet, smart-phone, etc. The user device executes a data prioritization module 111 which is an application that enables interaction with the data prioritization system 90. A setup module 112 on the user device 110 allows a user to create an account, specify a user type, specify data types the user can provide, specify partners, etc. The mobile device also includes a user identifier 113 which uniquely identifies the user to the data prioritization system 90. The user identifier 113 may be physically tied to the device (e.g., a MIN of a smartphone) or may be a username and password that identifies a user rather than a specific device.

[0044] The data prioritization system 90 prioritizes cold chain data reported to a user in response to a user type and other settings. FIG. 4 depicts user interfaces for data prioritization system setup in an exemplary embodiment. The user interfaces are presented during execution of the setup module 112 executing on user device 110. A first GUI 400 provides for entry of user data, such as name, company, address, etc. A second GUI 402 provides for entry of business data such as a cold chain role (e.g., grower, processor, distributor, wholesaler, retailer, custom). The second GUI 402 also allows the user to identify partners who will have access to that user's cold chain data. A third GUI 404 allows user to select data that they can provide to the data prioritization system 90. The data types presented in GUI 404 may be defined based on the cold chain role selected in GUI 402.

[0045] FIG. 5 depicts a process for data prioritization system setup in an exemplary embodiment. The process of FIG. 5 is launched when the user executes the setup module 112 on mobile device 110. At 502, the setup module 112 allows the user to input user data through the first GUI 400. At 504, the setup module 112 allows the user to input business data through the second GUI 402. At 506, the setup module 112 allows the user to input data they can provide through the third GUI 404. At 508, the user can go back and revise the entries in any of the prior steps 502, 504 or 506, or select a finish icon (FIG. 4) and send the data entered at 502, 504 or 506 to the data prioritization system 90 for storage in the network database 82 at 510.

[0046] FIG. 6 depicts a process for data prioritization system access in an exemplary embodiment. The process begins at 602 when a user launches the data prioritization module 111 on the mobile device 110. At 604, the data prioritization module 111 sends a user identifier 113 to the data prioritization system 90. At 606, the data prioritization system 90 accesses the network database 82 to retrieve authorization data from the network database 82. The authorization data will indicate whether the user identifier is associated with an active subscription. If the authorization data indicates the user lacks an active subscription at 608, then flow proceeds to 612 where the user device 110 may execute the setup module 112 as described with reference to FIGs. 4 and 5. If the authorization data indicates the user has an active subscription at 608, then flow proceeds to 610 where the user is allowed to send and receive cold chain data using the data prioritization system 90.

[0047] FIG. 7 depicts a process for exchanging data between the data prioritization system 90 and user device 110 in an exemplary embodiment. The process begins at 702 where user device 110 access the data prioritization system 90 and sends the user identifier 113 to the data prioritization system 90. At 704, the data prioritization system 90 attempts to match the user identifier 113 to a record in the network database 82. At 706, if the user identifier 113 does not match a record in the network database 82, flow proceeds to 708 where the user device 110 receives a message from the data prioritization system 90 that there is no active subscription for that user identifier. The user could then run the setup module 112 to create a user subscription. [0048] At 706, if the user identifier 113 does match a record in the network database 82, flow proceeds to 710 where the data prioritization system 90 authorizes sending and receiving cold chain data to and from the user device 110. At 712, the data prioritization system 90 begins the data prioritization process and at 714 the data prioritization system 90 looks up the user identifier in the network database 82 to determine which type of business module 94 should be launched for this particular user. As noted above, the business modules 94 are unique to different types of users and prioritize data in response to a user type. The data prioritization system 90 may use the cold chain role identified during the setup process to identify the business module 94 suitable for the user. Once the correct business module 94 is identified, flow proceeds to 716 where the data prioritization system 90 retrieves cold chain data associated with the business module 94 from the cold chain database 84.

[0049] Block 716 involves launching the business module 94 that corresponds to the cold chain role of the user requesting the data. In this way, different classes of users receive the cold chain data in a prioritized manner. The prioritization of the cold chain data may include filtering the cold chain data so that the prioritized cold chain only includes data of interest to that user. The prioritization of the cold chain data may include arranging the prioritized cold chain data in a sequence of most important to least important to the user. A variety of other data manipulation techniques may be used by the business module 94 to present the prioritized cold chain data in a custom format for that class of user.

[0050] At 718, the data prioritization system 90 sends the prioritized cold chain data to the user device 110. The prioritized cold chain data is derived by the business module 94 for each particular user based on cold chain role. In this manner, only data relevant to a business type is provided to the user device 110.

[0051] At 720, the data prioritization system 90 sends a request to the user device 110 for cold chain data. At 722, the user device 110 sends cold chain data collected by that user to the data prioritization system 90. The sent cold chain data at 722 corresponds to the types of cold chain data the user can send identified in the setup process of FIGs. 4 and 5. At 724, the data prioritization system 90 stores the received cold chain data from the user device 110 in the cold chain database 84 and the process ends at 726.

[0052] The data prioritization module 111 executing on the user device 110 also allows a user to load in user-defined analysis of the prioritized cold chain filtered data received from the data prioritization system 90. For instance, one distribution center may want to analyze efficiencies not only using the cold chain data from the data prioritization system 90 but also locally stored data. Another distribution center may want to not only use the cold chain data from the data prioritization system 90 for efficiencies and costs but may also want to use some end market data. In this way, each business model obtains its unique cross mapped data and filters. A user may upload user-defined analysis (thresholds, limits, etc.) and then apply that user-defined analysis to data gathered in other portions of the cold chain distribution network. For example, a grower (user A) has data regarding the minimum and maximum temperature at which a product should be stored and transported. User A uploads this user-defined analysis to data prioritization system 90 and uses it to analyze raw data (e.g. temperature sensor data from truck/container) from a distributor (User B). This informs user A if the temperature went out of range, when and how long the temperature went out of range, where the temperature went out of range, etc. This allows at least two users to cross data streams in order to calculate more meaningful analytics derived from the raw data.

[0053] FIG. 8 depicts content of a business module 94 of the data prioritization system 90 in an exemplary embodiment. FIG. 9 depicts a distributor module 94, which is just one example of a type of business module 94 in data prioritization system 90. The distributor priority data component shows a hierarchical list of cold chain data the distributor would like to receive from the data prioritization system 90. The input cold chain data component shows the data types the distributor has agreed to provide to the data prioritization network 90. The active subscriptions component shows users who are currently authorized to use the distributor module 94. The partners component shows a list of partners, or other businesses, that receive cold chain data from the distributor.

[0054] The data prioritization network 90 uses different business modules to prioritize cold chain data based upon relevancy to a user's business issues. For example, a driver may be more interested in specific weather patterns and how they correlate to the current route and condition of the vehicle. A logistics manager may be more interested in a prediction about how long a weather pattern may delay a shipment, and what costs might incur. Specifically, if distribution centers want efficiencies and costs, the cold chain data is filtered and reported that way. For a different customer, the data is filtered and reported (e.g., prioritized) in their customized way. In this manner, the data prioritization network 90 provides prioritized cold chain data to different users.

[0055] As described above, the exemplary embodiments can be in the form of processor- implemented processes and devices for practicing those processes, such as data prioritization system 90. The exemplary embodiments can also be in the form of computer program code containing instructions embodied in tangible media, such as floppy diskettes, CD ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes a device for practicing the exemplary embodiments. The exemplary embodiments can also be in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into an executed by a computer, the computer becomes an device for practicing the exemplary embodiments. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.

[0056] While the disclosure has been described in detail in connection with only a limited number of embodiments, it should be readily understood that the disclosure is not limited to such disclosed embodiments. Rather, the disclosure can be modified to incorporate any number of variations, alterations, substitutions or equivalent arrangements not heretofore described, but which are commensurate with the scope of the disclosure. Additionally, while various embodiments of the disclosure have been described, it is to be understood that aspects of the disclosure may include only some of the described embodiments. Accordingly, the disclosure is not to be seen as limited by the foregoing description, but is only limited by the scope of the appended claims.

Claims

CLAIMS: What is claimed is:

1. A method for distributing cold chain data, the method comprising:

storing cold chain data in a cold chain database;

storing user data in a network database;

receiving a user identifier from a user device;

retrieving a cold chain role associated with the user identifier from the network database;

prioritizing the cold chain data from the cold chain database in response to the cold chain role to generate prioritized cold chain data; and

sending the prioritized cold chain data to the user device.

2. The method of claim 1 wherein prioritizing the cold chain data from the cold chain database in response to the cold chain role comprises executing a business module associated with the cold chain role.

3. The method of claim 1 further comprising:

comparing the user identifier to the network database; and

allowing access to the cold chain data only when the user identifier is present in the network database.

4. The method of claim 1 further comprising:

sending a request to the user device for further cold chain data; and

receiving further cold chain data from the user device.

5. The method of claim 4 further comprising:

storing the further cold chain data in the cold chain database.

6. The method of claim 4 further comprising:

retrieving a partner associated with the user identifier from the network database; providing the further cold chain data to the partner.

7. The method of claim 1 wherein the cold chain data includes data received from at least one sensor located on a transport refrigeration system.

8. The method of claim 1 wherein the prioritizing the cold chain data include filtering the cold chain data.

9. The method of claim 1 wherein the prioritizing the cold chain data includes arranging the prioritized cold chain data in a sequence of most important to least important.

10. The method of claim 1 further comprising:

receiving user-defined analysis of the cold chain data; storing the user-defined analysis of the cold chain data in the cold chain database.

11. A cold chain data prioritization system, the system comprising:

a processor; and

a memory comprising computer-executable instructions that, when executed by the processor, cause the processor to perform operations, the operations comprising:

storing cold chain data in a cold chain database;

storing user data in a network database;

receiving a user identifier from a user device;

sending the prioritized cold chain data to the user device.

12. A computer program product tangibly embodied on a computer readable medium, the computer program product including instructions that, when executed by a processor, cause the processor to perform operations comprising:

storing cold chain data in a cold chain database;

storing user data in a network database;

receiving a user identifier from a user device;

sending the prioritized cold chain data to the user device.