Abstract: A pedal unit for a vehicle has a sensor surface which includes at least two functional regions and is designed to detect an actuation by the driver. The pedal unit also has at least one evaluation and control unit coupled to the sensor surface and designed to evaluate an actuation of one of the at least two functional regions detected by the sensor surface and, as a function of this evaluation, control a vehicle function associated with the corresponding functional region of the sensor surface. At least one region of the sensor surface is raised or lowered and enables a haptic differentiation between the at least two functional regions of the sensor surface.

Abstract: A pillow block bearing assembly for a drivetrain assembly of a work vehicle may include a pillow block housing defining a bearing cavity, a bearing disposed within the bearing cavity, and first and second sealing devices installed within the bearing cavity. Additionally, the drivetrain assembly may include a shaft received within the pillow block bearing assembly, with the shaft extending through the bearing such that an outer circumferential surface of the shaft directly contacts an inner circumferential surface of an inner race of the bearing at a bearing/shaft interface defined between the shaft and the bearing. Moreover, a sliding fit may be defined between the outer circumferential surface of the shaft and the inner circumferential surface of the inner race at the bearing/shaft interface such that the shaft is allowed to slide axially relative to the bearing when a given axial load is applied through the shaft.

Abstract: A user specific meta application instance is launched. The user specific meta application instance inherits a pattern of display and at least one context of a meta application instance. A value for the at least one context of the user specific meta application instance is received. A selection of one or more applications from a plurality of applications provided by the user specific meta application instance is received. Each application from the one or more applications is associated with a pattern of display. One or more application contexts that match the at least one context of the user specific meta application instance are determined for each application from the selected one or more applications. The matching one or more application contexts are applied to each application from the selected one or more applications. A user specific UI based on the user specific meta application instance is displayed.

Abstract: A pillow block bearing assembly for a drivetrain assembly of a work vehicle may include a pillow block housing defining a bearing cavity, a bearing disposed within the bearing cavity, and first and second sealing devices installed within the bearing cavity. Additionally, the drivetrain assembly may include a shaft received within the pillow block bearing assembly, with the shaft extending through the bearing such that an outer circumferential surface of the shaft directly contacts an inner circumferential surface of an inner race of the bearing at a bearing/shaft interface defined between the shaft and the bearing. Moreover, a sliding fit may be defined between the outer circumferential surface of the shaft and the inner circumferential surface of the inner race at the bearing/shaft interface such that the shaft is allowed to slide axially relative to the bearing when a given axial load is applied through the shaft.

Abstract: A user specific meta application instance is launched. The user specific meta application instance inherits a pattern of display and at least one context of a meta application instance. A value for the at least one context of the user specific meta application instance is received. A selection of one or more applications from a plurality of applications provided by the user specific meta application instance is received. Each application from the one or more applications is associated with a pattern of display. One or more application contexts that match the at least one context of the user specific meta application instance are determined for each application from the selected one or more applications. The matching one or more application contexts are applied to each application from the selected one or more applications. A user specific UI based on the user specific meta application instance is displayed.

Abstract: Example systems and methods of configuring and displaying a model-based user interface are described. In one implementation, a method receives a request to configure a process model, the process model having an object type. A configuration rule associated with the object type is accessed, and a configuration instruction is received. The configuration instruction is analyzed based on the configuration rule, and if the configuration instruction is valid then the object type is modified based on the instruction. The process model is updated based on the modified object type. In another implementation, a method receives a request to display instance data of a process model, where the process model has an object type associated with the instance data. A structure rule determining placement of the instance data is accessed, and a user interface to display the instance data is generated based on the structure rule.

Abstract: Techniques for managing business process functionality by grouping process structures in a solution manager unified directory (SMUD) include defining a group for a SMUD, the defined group including a group identification (ID) and a plurality of members of the group, each member including a business process structure; defining a plurality of generic functions of the group; receive a request for an adjustment to the plurality of generic functions of a particular member of the plurality of members of the group; and based on the received request, adjusting the plurality of generic functions of members of the group other than the particular member.

Abstract: Structural information of a process is stored as an instance hierarchy (e.g. parent-child relation) between occurrence nodes comprising occurrence identifications (IDs) and links to objects of an object pool. Efficient management of process versions (e.g. design, build, test, productive, archive) is accomplished by handling occurrences and corresponding linked objects so that a minimum set of data is physically copied. An algorithm governing the physical copying of process data, is described.

Abstract: Example systems and methods of configuring and displaying a model-based user interface are described. In one implementation, a method receives a request to configure a process model, the process model having an object type. A configuration rule associated with the object type is accessed, and a configuration instruction is received. The configuration instruction is analyzed based on the configuration rule, and if the configuration instruction is valid then the object type is modified based on the instruction. The process model is updated based on the modified object type. In another implementation, a method receives a request to display instance data of a process model, where the process model has an object type associated with the instance data. A structure rule determining placement of the instance data is accessed, and a user interface to display the instance data is generated based on the structure rule.

Abstract: A method includes using a computer to derive a design stage directory model based on a core directory model, using the computer to derive a production stage directory model based on the core directory model, adding an extension to one of the models including an activation flag to activate the extension, and saving the models and extension to a computer readable storage device.

Abstract: A method includes obtaining an existing process structure for multiple life cycle stages of a process lifecycle instance, using a release version matrix to represent the process structures, receiving a release change indication, copying the existing process structures into new release process structures to represent a new version of the process in response to the release change, and updating the release version matrix to identify the new version of the process structures.

Abstract: Structural information of a process is stored as an instance hierarchy (e.g. parent-child relation) between occurrence nodes comprising occurrence identifications (IDs) and links to objects of an object pool. Efficient management of process versions (e.g. design, build, test, productive, archive) is accomplished by handling occurrences and corresponding linked objects so that a minimum set of data is physically copied. An algorithm governing the physical copying of process data, is described.

Abstract: A system and method to maintain versions of an object for each lifecycle stage of the object are described. The system maintains versions and archives of objects in memory. The system includes an object repository to maintain new objects. The system has a lifecycle stage module to manage lifecycle stages, an origin matrix builder to build origin matrices, an archive version manager to manage archives. The system further retrieves usages of objects across lifecycle stages using a usage logic module and compares the content of objects from different stages using a comparison module.

Abstract: A structure object is locked to prevent changes to the structure object in previous phases of a software life cycle. When a request to change the structure object in a previous phase is received, a change request file is opened. The changed request is approved or denied based at least in part on the previous phase. If the changes request is approved, a document is generated for the change request. Any changes made to the structure object are integrated into the previous phase of the structure object and are also stored in the document. If the change request is denied, the change request file is closed.

Abstract: A system and method to maintain versions of an object for each lifecycle stage of the object are described. The system maintains versions and archives of objects in memory. The system includes an object repository to maintain new objects. The system has a lifecycle stage module to manage lifecycle stages, an origin matrix builder to build origin matrices, an archive version manager to manage archives. The system further retrieves usages of objects across lifecycle stages using a usage logic module and compares the content of objects from different stages using a comparison module.

Abstract: A structure object is locked to prevent changes to the structure object in previous phases of a software life cycle. When a request to change the structure object in a previous phase is received, a change request file is opened. The changed request is approved or denied based at least in part on the previous phase. If the changes request is approved, a document is generated for the change request. Any changes made to the structure object are integrated into the previous phase of the structure object and are also stored in the document. If the change request is denied, the change request file is closed.

Abstract: System-level information is retrieved from a remote system and a request is automatically sent to an update agent for a list of software updates for the remote system. The request includes the retrieved system-level information. The update agent provides a list of available software updates that is filtered based at least in part on the system-level information. The filtered list of software updates is then sent to the remote system. The enterprise system receives user input indicating a selection of one or more software updates from the filtered list. Selected software updates are incorporated into a business action.

Abstract: The degradation of harmful substances in water by compounds, such as hydrogen peroxide, which form hydroxyl radicals under UV irradiation in continuous reactors is improved when the irradiation is carried out in a reactor with a specific reactor volume of at least 10 liters per kW of the UV radiator or radiators, and if the amount of water to be treated is 0.25 to 25 times the amount of the intrinsic volume of the reactor flows through the reactor per hour. It is particularly preferred that the water volume per hour to be treated is 0.25 to 10 times the intrinsic reactor volume.