Celonis is a Process Intelligence platform that helps companies improve their operations, customer experience, and sustainability. The company’s technology provides a digital twin of a company’s processes, giving everyone in the organization a common language and the ability to identify and capture value.
N/A
IBM webMethods Hybrid Integration
Score 7.9 out of 10
N/A
IBM® webMethods offers a hybrid, enterprise-grade integration platform as a service (iPaaS) that allows users to securely control applications, APIs, B2B and files across environments and locations.
$2,500
per month
Pricing
Celonis
IBM webMethods Hybrid Integration
Editions & Modules
No answers on this topic
IBM webMethods Hybrid Integration Standard Tier
$2,500
per month
Offerings
Pricing Offerings
Celonis
IBM webMethods Hybrid Integration
Free Trial
No
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Required
No setup fee
Additional Details
Snap is Celonis' free-to-use, cloud-based process mining solution, with over 3500 registrants and users. It includes most major features of Celonis, including all functionality found in common process mining tools. It also includes pre-built connectors to ServiceNow and pre-built content to get users started quickly on their process mining journey.
I believe that Celonis is a great tool to use in Uniper, as it can integrate data from different sources into a single platform, making interfaces more accurate and facilitating the monitoring of data flow from one source system to another.
In any scenario where a distributed enterprise IT landscape needs a unified approach to solve the challenges of enabling a common information supply chain where different stakeholders as well as citizen developers can be empowered to contribute, participate and own their own parts of the integration landscape - IBM webMethods offers a capable, architecturally sound and cost efficient way of supporting a wide range of enterprise system integration needs.
We had to build a custom dashboard for tracking value realization, as the transformation center was minimal in scope. For a very value-focused company, this area can be improved, which would be incredibly beneficial.
The current licensing model sometimes limits the ambitious value goals, as we can't experiment with building analyses in different areas without a long-term license for that process.
We have been able to leverage Celonis [greatly] because of the commitment and support we receive from our data scientist. I strongly believe that we would not be able to accomplish this without her assistance. Moreover, when we escalate matters, the product development is engaged and commits resources to make sure our initiatives/business cases are supported.
The webMethods platform is a fantastic tool for modernizing information systems. It's easy to use and delivers rapid results.The platform is focused on innovation and is accelerating its improvement with the acquisition by IBM.
It is a great tool but also requires a lot of work to get it into a useable fashion. Part of this is on our end as we don't have the dedicated analyst function yet to really become self-sufficient with Celonis. It also uncovers a lot of data issues or at the very least, multiple rounds of development and data validation are required before getting to a position where the business users feel comfortable with the data being reflected. This is fairly normal with any data-related development effort and perhaps not unique to Celonis.
The webMethods product has a very user-friendly and easy-to-use interface.A weak point is the My webMethods Server portal (administration and monitoring portal for the on-premise platform). This weakness has been addressed thanks to the control plane on the hybrid version of the product. This version should be highlighted and used to ensure a very fluid and functional interface.
The webMethods platform is very stable and does not cause incidents: if it is well configured and tailored at the base. Infrastructure incidents represent 20% of incidents (full disk, memory peaks, etc.) 80% of incidents come from the implementation of the code in the platform. If a code is not optimized and a high volume is observed in production, this can cause incidents. Similarly, if all error cases or conditions are not handled in the code, this can cause errors. Finally, there can be common errors if the applications connected to the platform do not return quality data or are unavailable.
The webMethods platform is designed to handle a high volume of small messages. It's a tool for continuous processing.The incidents I've seen involving application performance declines are caused by: - Code optimization issues - File size issues or fragmentation of the transmitted file - Misuse of the platform (batch processing) - Monitoring data was not purged, and the user was working with millions of data points
We submit tickets to Celonis through product support. No assistance is generally provided, have to wait and the ticket is then escalated to product support in Germany. Many times we submit the ticket and the support desk asks us the same questions back where they should already have this information.
In the majority of the tickets I've created, support has been very responsive and provided the right solutions or solutions.Resolving a ticket also depends on the information provided by the creator. It's important to provide the technical context and information about the environment, as well as information to help the support team reproduce the incident.
We received in-person training from the webMethods team. We received standard training from the vendor and custom training on specific security topics.The training sessions went well but remained very standard and did not adapt to the client's specific business. In-person training is more suitable for rapid skill development. It is necessary to practice for a few weeks to ensure familiarity with the tool.
I found clear and easy-to-follow training with realistic use cases for quick understanding and a 360° view of the features. The lesson format allows you to progress and learn by breaking down the allocated time.The technical courses are described step by step, allowing you to quickly get to grips with the products
When implementing webMethods, it's essential to have the right support and guidance.It's important to map out the interactions, document them, prepare test cases, and implement them while making maximum use of the product's native features.Additional tools must also be planned to automate deployments, visualize logs, and monitor the platform.
The major reason to choose Celonis is that it has enhanced decision-making in filtering the candidates. The frontend designer has nice graphics and has well-designed self-service. I particularly enjoy the visual editor, which allows you to create complicated PQL without having to write any code, as well as the numerous filtering choices, including process mining options.
webMethods.io IntegrationDescriptionWe uses webMethods.io Integration to solve some of our application to applications and business to business integration needs. It is the Integration Platform as a Service solution that we use in a mix with our continued use of webMethods Integration Server and Trading Networks on-premises. For any solutions that meet the use cases that we deem an appropriate fit for running in the cloud, we build those solutions using webMethods.io Integration. More specifically, we use webMethods.io Integration to synchronize changes in one application or system, in another application or system, by shipping data mutations via integration messaging and API calls. We also use webMethods.io Integration to integrate with external organizations. Our trading partners and supply chain partners provide APIs that we consume, and vice versa, to notify each other of business process events as they occur in the respective organizations. Please provide some detailed examples of things that webMethods.io Integration (webMethods Integration Cloud) does particularly well. Easy to usePriced competitivelySupports robust and resilient integration solutions please provide some detailed examples of areas where webMethods.io Integration (webMethods Integration Cloud) has room for improvement. These could be features that are hard to use, missing functionality, or just things that you'd like to see done differently. Complex logic is hard to understand in a simple diagrammatic user interface too simplistic for solutions that are complicated or go against the gain runtime observability could be improved please describe some specific scenarios based on your experience where webMethods.io Integration (webMethods Integration Cloud) is well suited, and/or scenarios where it is less appropriate. We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios. What positive or negative impact (i.e. Return on Investment or ROI) has webMethods.io Integration (webMethods Integration Cloud) had on your overall business objectives?webMethods.io Integration is a cost-effective approach to integration in isolationwebMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costswebMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic AppswebMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used describe how webMethods.io Integration (webMethods Integration Cloud) stacks up against them and why you selected webMethods.io Integration (webMethods Integration Cloud). For any organization which is already using Software AG products on-premises, such as webMethods Integration Server and Trading Networks, or Universal Messaging, evaluating and using webMethods.io Integration is the path of least resistance. It will be incredibly easy for your webMethods team to get up to speed on how to use webMethods.io Integration, and start developing new solutions on it. However in my opinion you should only add cloud to your integration product portfolio if you believe you can move 100% of your integration needs to the cloud. Otherwise, you will need to maintain an on-premises integration solution anyway, which means you end up with a more complex IT landscape by adding cloud to supplement on-premises integration for little benefit in terms of cost, complexity, and resourcing requirements. For organizations that are not already a Software AG shop, you should evaluate webMethods.io Integration on its merits, however, it's usually the right decision to double down on your existing products and vendors if you have no big issues with the current state. This is to say that if you are a Microsoft shop then adding Azure cloud products to your portfolio is pretty much inevitable, and avoiding the complexity of multiple clouds should also be something organizations consider.
The previous IFRS 9 calculation method was reaching its end of life—Celonis is a direct replacement for us.
When rebuilding our logic from the old system to the new, it gave us a much-needed opportunity to revamp and standardise company codes and, in some cases, even pick up some errors.
