Appian is a low-code development and business process management platform. It features drag-and-drop design for app building, automated work processes, unified data management, and cloud-based deployment.
$0
Control-M
ScoreĀ 7.2Ā outĀ ofĀ 10
N/A
Control-M from BMC is a platform for integrating, automating, and orchestrating application and data workflows in production across complex hybrid technology ecosystems. It provides deep operational capabilities, delivering speed, scale, security, and governance.
N/A
Pricing
Appian
Control-M
Editions & Modules
Appian Community Edition
$0
Application - Input-Only
$2
per month per user
Application - Infrequent
$9
per month per user
Application - Standard
$75
per month per user
Platform
Custom Quote Priced per user with unlimited apps.
minimum 100 users, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
unlimited
Platform
Custom Quote Priced per user with unlimited apps.
Minimum 100, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
Appian works great for automating manual processes and integrating multiple systems through its toolset. It gives great flexibility for establishing rules for approvals, routings, escalations, and the like. Because of the low code toolset, it's very easy to deploy and make changes as needed as processes evolve and as the organization learns to utilize the system better. Minimal maintenance is required to support the applications build on the platform. Some of the automated testing integration with tools like Jenkins is limited so that may be an issue for some.
Control-M is a reliable and well-developed product with excellent vendor support that updates and expands the software often and offers a cloud-based deployment choice. When there are many Batch processes in IT operations that need to be monitored and controlled to ensure IT services, Control-M is ideally suited for centralized workload automation and task management.
Allows at a glance workflow documentation which assists in the need we have for information readiation.
Drag and drop interface for workflow development greatly speeds our apps time to market.
Using the advanced features of Appian, we are able to create working sites in a fraction of the time it would take to do so using "traditional" development.
Control-M provides a single, centralized interface for monitoring and managing all batch processes in the organization. Nothing is hidden or left unattended in a timely manner.
The proper use of the BIM component has allowed the change of paradigm in the operation, adopting a proactive management instead of the typical reactive management in the event of production failures.
The use of Forecast and production simulations allows you to identify bottlenecks and focus first on managing those failures that have the greatest impact on production SLAs.
Control-M/Change Manager has arrived to shorten development cycles from requirements gathering to production testing. It has been a utility that monetizes the development of Jobs meshes.
The GUI is capable of efficiently handling more than 80,000 jobs per day. This is certainly a challenge in designing a good user experience. I don't know if there is a reasonable limit to this. One of my clients runs more than 80,000 Jobs daily and the GUI remains smooth all the time.
Job-As-Code is a DevOps accelerator that has just begun to be adopted. Its implementation will make workload management even more cost-effective.
Search issues when type ahead and database search are used in the same field.
Buttons implementation where user is require[d] to click on the button description - if clicks on the button outside that text - button will not work.
Problems with using certain off-the-shelf performance tools like WebLoad or Neoload. That is because of different dynamic variables being used internally in Appian - which these tools are unable to correlate. We are still investigating using other tools like Jmeter to overcome dynamic correlation problem for performance testing.
As with most of the mainframe software products, documentation seems to be the weak link for the products - written by people and for people who already know what they need to do, not for people who are trying to figure how to use the product.
We are a large JES3 mainframe shop. As with all vendors who still provide software for mainframe systems, software is generally designed and developed for JES2 and is frequently not fully tested in a JES3 environment before being shipped out.
We recently renewed our license with Appian. We are convinced that its flexibility, relative ease of use, the support they provide, there mobile advancements and their general willingness and desire to see us succeed all contributed to our reason to renew our agreement with Appian
It is a great product plain and simple. We've had Control-M for 20+ years and the support that BMC Software provides is really second to none. There is always a situation that someone can think of where I have to say, "No we can't do that", however I'm confident that we've been able to meet and most of the time exceed our end user expectations with what the product can offer them.
Appian is a low code environment, because of this, a very good visual interface is required. Appian is providing a feature-rich dashboard [that] we can use for building the dashboards and other interfaces. Appian also provides patches and releases to enhance these features. A developer can start off development just by going through a basic course from the Appian learning community.
Control-M's overall usability is very good because it is simple to use. Control-M SelfService is an easy tool to give to some of the users who want to use a web interface. The training curve for most users is very short and most of the functions are very simple to figure out.
Appian is one of the leading low code business automation platforms that support RPA, decision rules, case management, workflow automation, and machine learning all in a single bundle. But it is also harder to implement and replace the traditional business process.
Although the product is very stable there have been a few incidents when I needed support. I have worked with technicians from all around the globe because of the rolling support. This gives me the quickest support when I need it most in those early hours of the morning. The technicians I have worked with have been very knowledgeable and if necessary got help when needed.
As analyst I participated in a developer boot camp. At times it was hard to keep up but most of the time it made sense. Trainer took the time to explain and slowed pace down to answer questions etc.
Appian has enormously transformed and keeps on updating the product every quarter to meet the latest needs of the world with new innovations & technologies being integrated within the platform. What gives more pleasure than a product that keeps on continuous[ly] improv[ing]?
We last reviewed the market in 2001 (schedulers are long-term commitments!) and Control-M edged (by a very narrow margin) the Tivoli alternative, with Dollar Universe (now part of Automic) back in third place. We also tested the Tidal Software scheduler (now part of Cisco) but I cannot see that listed here. Control-M won out through reliability and cross-platform support. Since we made our choice it has become clear that Control-M has moved ahead of the alternatives.
I believe it has negatively impacted our release dates. There may have been a misunderstanding as to the learning curve, even though it is "low code."
The look and feel of the applications created using Appian have uniformity and it's easier to have "reuse" between applications.
There is less developer control when it comes to features. I think this mainly has to do with the amount of plugins available. I would think there should be many more available plugins. But again, our use case is probably different than most others.
I would expect this product to give a positive return on investment. Running jobs in cron for example would require a lot more scripting effort to ensure that the proper notifications are done on failures. With the built in functionality in Control-M the effort would be greatly reduced
