Abstract: Methods and systems are disclosed for automated semantic tagging that include detecting a particular thread executed by a processor and identifying a root process of the particular thread. An object-process link may be by linking an object that executed code that called the particular thread to the root process. A thread list of thread definitions of the object may be identified. A particular thread definition that corresponds to the particular thread can be mapped. Resource types to be consumed upon executing an instance of the thread instantiated from the particular thread definition can be identified and the corresponding values of the resource types can be determined. A process specification can be generated that encapsulates the thread definition, resource types and values so as to reproduce a state of the root process at a point in which the particular thread executed.

Abstract: Methods and systems are disclosed for automated semantic tagging that include detecting a particular thread executed by a processor and identifying a root process of the particular thread. An object-process link may be by linking an object that executed code that called the particular thread to the root process. A thread list of thread definitions of the object may be identified. A particular thread definition that corresponds to the particular thread can be mapped. Resource types to be consumed upon executing an instance of the thread instantiated from the particular thread definition can be identified and the corresponding values of the resource types can be determined. A process specification can be generated that encapsulates the thread definition, resource types and values so as to reproduce a state of the root process at a point in which the particular thread executed.

Abstract: Methods and systems are disclosed for automated semantic tagging that include detecting a particular thread executed by a processor and identifying a root process of the particular thread. An object-process link may be by linking an object that executed code that called the particular thread to the root process. A thread list of thread definitions of the object may be identified. A particular thread definition that corresponds to the particular thread can be mapped. Resource types to be consumed upon executing an instance of the thread instantiated from the particular thread definition can be identified and the corresponding values of the resource types can be determined. A process specification can be generated that encapsulates the thread definition, resource types and values so as to reproduce a state of the root process at a point in which the particular thread executed.

Abstract: Methods and systems are disclosed for automated semantic tagging that include detecting a particular thread executed by a processor and identifying a root process of the particular thread. An object-process link may be by linking an object that executed code that called the particular thread to the root process. A thread list of thread definitions of the object may be identified. A particular thread definition that corresponds to the particular thread can be mapped. Resource types to be consumed upon executing an instance of the thread instantiated from the particular thread definition can be identified and the corresponding values of the resource types can be determined. A process specification can be generated that encapsulates the thread definition, resource types and values so as to reproduce a state of the root process at a point in which the particular thread executed.

Abstract: Methods and systems are disclosed for automated semantic tagging that include detecting a particular thread executed by a processor and identifying a root process of the particular thread. An object-process link may be by linking an object that executed code that called the particular thread to the root process. A thread list of thread definitions of the object may be identified. A particular thread definition that corresponds to the particular thread can be mapped. Resource types to be consumed upon executing an instance of the thread instantiated from the particular thread definition can be identified and the corresponding values of the resource types can be determined. A process specification can be generated that encapsulates the thread definition, resource types and values so as to reproduce a state of the root process at a point in which the particular thread executed.

Abstract: Methods and systems are disclosed for automated semantic tagging that include detecting a particular thread executed by a processor and identifying a root process of the particular thread. An object-process link may be by linking an object that executed code that called the particular thread to the root process. A thread list of thread definitions of the object may be identified. A particular thread definition that corresponds to the particular thread can be mapped. Resource types to be consumed upon executing an instance of the thread instantiated from the particular thread definition can be identified and the corresponding values of the resource types can be determined. A process specification can be generated that encapsulates the thread definition, resource types and values so as to reproduce a state of the root process at a point in which the particular thread executed.

Abstract: Methods and systems are disclosed for automated semantic tagging that include detecting a particular thread executed by a processor and identifying a root process of the particular thread. An object-process link may be by linking an object that executed code that called the particular thread to the root process. A thread list of thread definitions of the object may be identified. A particular thread definition that corresponds to the particular thread can be mapped. Resource types to be consumed upon executing an instance of the thread instantiated from the particular thread definition can be identified and the corresponding values of the resource types can be determined. A process specification can be generated that encapsulates the thread definition, resource types and values so as to reproduce a state of the root process at a point in which the particular thread executed.

Abstract: Disclosed and described herein are systems, methods and computer program products that enable converting a metafile to a spreadsheet file, editing the spreadsheet file, and then transforming the spreadsheet file back to an output metafile.

Abstract: Methods and systems are disclosed for automated semantic tagging that include detecting a particular thread executed by a processor and identifying a root process of the particular thread. An object-process link may be by linking an object that executed code that called the particular thread to the root process. A thread list of thread definitions of the object may be identified. A particular thread definition that corresponds to the particular thread can be mapped. Resource types to be consumed upon executing an instance of the thread instantiated from the particular thread definition can be identified and the corresponding values of the resource types can be determined. A process specification can be generated that encapsulates the thread definition, resource types and values so as to reproduce a state of the root process at a point in which the particular thread executed.

Abstract: Disclosed and described herein are systems, methods and computer program products that enable converting a metafile to a spreadsheet file, editing the spreadsheet file, and then transforming the spreadsheet file back to an output metafile.

Abstract: Systems, methods, and machine readable media are provided for dynamic delivery scheduling. In exemplary embodiments, order data and travel data is received. The travel data includes a travel service identifier related to a travel facility, an expected arrival time at the travel facility, and an identification of a destination facility. An order request is transmitted with the order data to the destination facility. The destination facility includes a geo-fence configured to detect an individual's mobile device, and the order request is processed by the destination facility upon detection of the individual's mobile device via the geo-fence. Following an updated arrival time being identified for the individual at the travel facility, a command may be transmitted to the destination facility to deliver the order to a location in the travel facility when the updated arrival time is forecasted to be outside of an operating hours' time period for the destination facility.

Abstract: Described is a system and method for warranty tracking. The system allows customers to register a purchased product in the system at the point of sale. A replacement product is automatically purchased at the end of product life and/or warranty expiration. The warranty expiration may be based on the warranty expiration date and/or the operating conditions of the purchased product. The operating conditions are recorded by the purchased product and may result in voiding of the warranty.

Abstract: A system for the grinding of unencumbered and encumbered sections of rail includes a locomotive that pulls a first and a second grinding module. The first grinding module is movable between a first and a second position. In the first position, the first grinding module is presented at angle enabling grinding of unencumbered section of rail while in the second position, the first grinding module is presented at an able enabling grinding of the encumbered section of rail. The locomotive continues in non-stop forward motion while the first grinding module is moved back and forth between its first and second positions. The second grinding module is generally used only for grinding of encumbered rail sections and is used simultaneously with the first grinding module in its second position.

Abstract: A system for the grinding of unencumbered and encumbered sections of rail includes a locomotive that pulls a first and a second grinding module. The first grinding module is movable between a first and a second position. In the first position, the first grinding module is presented at angle enabling grinding of unencumbered section of rail while in the second position, the first grinding module is presented at an able enabling grinding of the encumbered section of rail. The locomotive continues in non-stop forward motion while the first grinding module is moved back and forth between its first and second positions. The second grinding module is generally used only for grinding of encumbered rail sections and is used simultaneously with the first grinding module in its second position.