Abstract: Computer-implemented systems and methods for data harmonization in engineering simulation. The method may comprise receiving application preferences defining attributes associated with input data to be delivered to one or more applications from one or more data sources. A first set of attributes may be associated with data to be delivered to a first application. Application preferences may be provided to a handler in communication with the data sources. Raw data received by the handler may arrive in a variety of formats and packet sizes from the one or more data sources. Raw data may be packaged by the handler into one or more data packets having a size or format that satisfies the application preferences. One or more attributes associated with input data to be delivered to the first application may be defined. Packaged data may be transmitted over one or more data transmission channels satisfying the application preferences.

Abstract: Computer-implemented systems and methods for data harmonization in engineering simulation. The method may comprise receiving application preferences defining attributes associated with input data to be delivered to one or more applications from one or more data sources. A first set of attributes may be associated with data to be delivered to a first application. Application preferences may be provided to a handler in communication with the data sources. Raw data received by the handler may arrive in a variety of formats and packet sizes from the one or more data sources. Raw data may be packaged by the handler into one or more data packets having a size or format that satisfies the application preferences. One or more attributes associated with input data to be delivered to the first application may be defined. Packaged data may be transmitted over one or more data transmission channels satisfying the application preferences.

Abstract: Computer-implemented systems and methods for data harmonization in engineering simulation. The method may comprise receiving application preferences defining attributes associated with input data to be delivered to one or more applications from one or more data sources. A first set of attributes may be associated with data to be delivered to a first application. Application preferences may be provided to a handler in communication with the data sources. Raw data received by the handler may arrive in a variety of formats and packet sizes from the one or more data sources. Raw data may be packaged by the handler into one or more data packets having a size or format that satisfies the application preferences. One or more attributes associated with input data to be delivered to the first application may be defined. Packaged data may be transmitted over one or more data transmission channels satisfying the application preferences.

Abstract: Systems and methods for defining application preferences for one or more attributes associated with data communicated between one or more applications and one or more data sources. A first set of attributes may be associated with data communicated with a first application. At least the first application, in an application framework implemented over an abstract service layer and a real service layer, may be deployed. The abstract service layer may comprise a first set of services including at least one of a data ingestion service, a time series storage service and event handling service. The real service layer may comprise a second set of services including at least one of a local file system, a cloud-based file system, and a streaming data resource for communicating data with at least the first application via a streaming mechanism over one or more data channels.

Abstract: Systems and methods for defining application preferences for one or more attributes associated with data communicated between one or more applications and one or more data sources. A first set of attributes may be associated with data communicated with a first application. At least the first application, in an application framework implemented over an abstract service layer and a real service layer, may be deployed. The abstract service layer may comprise a first set of services including at least one of a data ingestion service, a time series storage service and event handling service. The real service layer may comprise a second set of services including at least one of a local file system, a cloud-based file system, and a streaming data resource for communicating data with at least the first application via a streaming mechanism over one or more data channels.

Abstract: Computer-implemented systems and methods for data harmonization in engineering simulation. The method may comprise receiving application preferences defining attributes associated with input data to be delivered to one or more applications from one or more data sources. A first set of attributes may be associated with data to be delivered to a first application. Application preferences may be provided to a handler in communication with the data sources. Raw data received by the handler may arrive in a variety of formats and packet sizes from the one or more data sources. Raw data may be packaged by the handler into one or more data packets having a size or format that satisfies the application preferences. One or more attributes associated with input data to be delivered to the first application may be defined. Packaged data may be transmitted over one or more data transmission channels satisfying the application preferences.

Abstract: Various embodiments of systems and methods for executing a customized business process in a business process framework are described herein. A user selection of a solution type corresponding to a business process is received from a user interface. In response to the user selection, a query is executed to retrieve application types and corresponding sub-application types from a business logic stored in a database. Configurable attributes are generated based upon the application types and the corresponding sub-application types. Based upon the application types, the sub-application types and the configurable attributes, the business process is customized to create a customized business process. Based upon a configuration information, a user input to the customized business process is captured from the user interface. The user input is validated by comparing the user input with the business logic. The customized business process that is validated is further executed in the business process framework.

Abstract: Various embodiments of systems and methods for executing a customized business process in a business process framework are described herein. A user selection of a solution type corresponding to a business process is received from a user interface. In response to the user selection, a query is executed to retrieve application types and corresponding sub-application types from a business logic stored in a database. Configurable attributes are generated based upon the application types and the corresponding sub-application types. Based upon the application types, the sub-application types and the configurable attributes, the business process is customized to create a customized business process. Based upon a configuration information, a user input to the customized business process is captured from the user interface. The user input is validated by comparing the user input with the business logic. The customized business process that is validated is further executed in the business process framework.

Abstract: Various embodiments of systems and methods for executing a customized business process in a business process framework are described herein. A user selection of a solution type corresponding to a business process is received from a user interface. In response to the user selection, a query is executed to retrieve application types and corresponding sub-application types from a business logic stored in a database. Configurable attributes are generated based upon the application types and the corresponding sub-application types. Based upon the application types, the sub-application types and the configurable attributes, the business process is customized to create a customized business process. Based upon a configuration information, a user input to the customized business process is captured from the user interface. The user input is validated by comparing the user input with the business logic. The customized business process that is validated is further executed in the business process framework.

Abstract: Various embodiments of systems and methods for executing a customized business process in a business process framework are described herein. A user selection of a solution type corresponding to a business process is received from a user interface. In response to the user selection, a query is executed to retrieve application types and corresponding sub-application types from a business logic stored in a database. Configurable attributes are generated based upon the application types and the corresponding sub-application types. Based upon the application types, the sub-application types and the configurable attributes, the business process is customized to create a customized business process. Based upon a configuration information, a user input to the customized business process is captured from the user interface. The user input is validated by comparing the user input with the business logic. The customized business process that is validated is further executed in the business process framework.

Abstract: Embodiments of the present invention may provide a method for process management. The method may comprise reading information about sub-processes and their respective sub-steps of a main process and displaying a process overview diagram for the main process. The process overview diagram may display a tab for each sub-process and sub-step respectively. Each tab may include an icon indicating the status of a respective sub-process or sub-step. The tab for each sub-step may be displayed underneath and linked to the respective sub-process. The method may further comprise, responsive to a click to select a view level, expanding the tabs for sub-steps to show the person responsible for the respective sub-step, detailed contact information of the responsible person, a description of what needs to be performed and a link to send a quick reminder to the responsible person when the status for the respective sub-step is “in process”.