Abstract: Traditional food quality monitoring systems fail to monitor the variation of food quality in real-time scenarios. Existing machine learning approaches require dedicated data models for different classes of food items due to differences in characteristics of different food items. Also, to generate such data models, a lot of annotated data is required per food item, which are expensive. The disclosure herein generally relates to monitoring and shelf-life prediction of food items, and, more particularly, to system and method for real-time monitoring and shelf-life prediction of food items. The system generates a data model using a knowledge graph indicative of a hierarchical taxonomy for a plurality of categories of the plurality of food items, which in turn contains metadata representing similarities in physio-chemical degradation pattern of different classes of the food items. This data model serves as a generic data model for real-time shelf-life prediction of different food items.

Abstract: This disclosure relates generally to method and system for predicting shelf life of perishable food items. In supply chain management, current technology provides limited capability in providing relation between visual image of food item and a quality parameter value at different storage conditions. The system includes a quality parameter prediction module and a shelf life prediction module. The method obtains input data from user comprising a visual data and a storage data of each food item. The quality parameter prediction module determines a current quality parameter value of the food item from a look-up table. The shelf life prediction module predicts the shelf life of food item based on the current quality parameter value, a critical quality parameter value and the storage data. The look-up table comprising a plurality of weather zones are generated based on relationship dynamics between the visual image of food item and the quality parameter value.

Abstract: Technologies are provided for providing a dashboard interface corresponding to one or more datacenter components for information originating from one or more proprietary applications. A selection of information corresponding to the one or more datacenter components is initially received. Upon receiving the selection, an application programming interface (API) call request is made for the information corresponding to the one or more datacenter components from the one or more proprietary applications. As the information corresponding to one or more datacenter components from the one or more proprietary applications is received, it is aggregated and provided within the dashboard interface.

Abstract: This disclosure describes methods to process timing information of flows in a network. One or more processors determine a latency associated with each of one or more packets of a flow passing through a device. The one or more processors determine that the latency is greater than a baseline latency, and the one or more processors provide a message indicating at least the flow and that the latency is greater than the baseline latency.

Abstract: Technologies are provided for providing a dashboard interface corresponding to one or more datacenter components for information originating from one or more proprietary applications. A selection of information corresponding to the one or more datacenter components is initially received. Upon receiving the selection, an application programming interface (API) call request is made, in real-time, for the information corresponding to the one or more datacenter components from the one or more proprietary applications. As the information corresponding to one or more datacenter components from the one or more proprietary applications is received, it is aggregated and provided within the dashboard interface.

Abstract: Technologies are provided for providing a dashboard interface corresponding to one or more datacenter components for information originating from one or more proprietary applications. A selection of information corresponding to the one or more datacenter components is initially received. Upon receiving the selection, an application programming interface (API) call request is made, in real-time, for the information corresponding to the one or more datacenter components from the one or more proprietary applications. As the information corresponding to one or more datacenter components from the one or more proprietary applications is received, it is aggregated and provided within the dashboard interface.