Adobe Workfront, acquired by Adobe in late 2020, is a web-based project-management tool. It is designed for both IT and marketing teams, but can be implemented for any kind of project. Workfront offers all the features standard to project management platforms, as well as resource allocation, automation, and agile workflow.
N/A
IBM Business Automation Workflow
Score 10.0 out of 10
N/A
IBM Business Automation Workflow is a solution that helps users automate digital workflows to increase productivity, efficiency and insights — on premises or on cloud.
IBM was the old system. When the time came for a new contract, better products - like Workfront - were considered. As an online business, the interface and the ability to sync up with Agile workflows was a big plus.
Having requests for immediate work being routed directly to the team members who perform the function. Proofreading needs to happen fast and turnaround quickly while retaining visibility everywhere. Through reporting and statuses, we can show progress at every stage. A large campaign organization means multiple requests and documents going between departments. By using requests alongside related rejects, we have everything in one place.
Have your process first on paper Its important to first document the process before venturing into BPMS. It will save a lot of pain and heartaches. A BPM tool is no magic bullet, it merely automates your process. Its upto you to put visibility and tracking on top of it. Provide monitoring so that you get a chance to improve your process continously. BPM is not an application If you are trying to build an application with BPM, chances are that your are alraedy failing. BPM must be a strategic initiative for an organization. Yes, you build Dashboards, Reports and other software in BPMS, however you do it at a process level not at an application level. http://bpmstech.blogspot.com/2011/05/bpm-initiative.htmlKnow the difference between process data and business datahttp://bpmstech.blogspot.com/2011/05/lombardi-best-practices.htmlhttp://bpmstech.blogspot.com/2012/02/bpm-system-architecture.html
System does a great job normalizing business process and automating order processing tasks. Before TeamWorks, the process was much more manual and more expensive staff ($65k to $70K) were required to manage the process. Since implementing TeamWorks, we need much lower-skilled workers to manage order processing.
System ensures that we have consistent data across all systems.
Rules engine is really the “company playbook” – it is the heart and soul of how the company works. It handles thousands of orders per day
The system gets crashed when many instances go into the queue stage. The system even crashes and sometimes restarts automatically when the load on the server increases. We had to develop a separate software for this and maintain the same.
We cannot manipulate the data during run time. It is difficult to develop user-interfaces with complex functionality.
In order to consume external services that follow HTTP protocol, we need to use IDE for that, and consuming services from IDE takes a lot of time to give a response.
Workfront is sometimes a bit clunky to use, but overall it works well for our teams when it comes to project management and collaboration across multiple, involved teams. It also has flexibility that allows us to adapt it to diverse use cases, some of which aren't necessarily always the first things that one would think of using workfront for.
This particular decision will be made by other people. Overall IBM BPM is the best BPM engine that I have worked with. It is implemented at our company and IT and business are already somewhat familiar with it. Therefore if asked I will recommend renewal as long as the price is reasonable.
Workfront is overly complex, but it is functional as a tool to keep track of projects. It is a shame that sometimes it takes a lot of clicks to find anything. Workfront is slowly modernizing its interface but at the same time, hides certain information away thus making the experience feels worse.
• The system is easy enough to use but, by definition, is a complex tool. However, they have done a good job generally balancing tool complexity / capability with usability. When comparing to MS Biz Talk, for example, Biz Talk has less functionality but is actually harder to use. • Software is very flexible. For somebody with the right technical background, it’s quite easy to write some Java code to overcome any hurdles or make the product do what is needed
I have found that Adobe Workfront is a reliable resource, because in the post 6 years of using it, rarely has it been unavailable to our team. I think I could count on one hand the number of times the site has been down over my time using it with my team.
I think overall, Adobe Workfront performs well. There have been some times when it doesn't load or run as quickly as our team would like. This is frustrating when it is such a crucial tool that our team utilizes on a daily basis. It can show our workflow when it lags.
I know that this particular company has it's own Adobe Workfront employee that builds out things they need from the software, and meets with them regularly to troubleshoot. I'm not part of this process, but it's refreshing to see Adobe provide this level of customer service to people, and they're expedient.
Issues can be raised through tickets and it works based on the priority of the issue. The Support Team response is also good and the solution is provided in a short span of time. In a case where the issue is serious, they try to find out the root cause and provide an alternative for it.
• Attended on premise sysadmin training for 4 days, 8 hours per day. Although further follow-up training was available, I never felt the need to go back. Training was very hands-on with real modeling (rather than just following a manual). Very effective.
The training is very easy to use and you can simply choose the topics included in the course(s) that are most important to your training needs. After each training course, you are tested on what you have learned. If you need a refresher course, they provide Course Catalogs as well as instructor-led courses & workshops.
Most people learn as you go, a lot of this stuff requires trial and error throughout so my suggestion is to provide as much information in the upfront and keep it as simple as possible. You can add other tools and features as you go but everyone should have the basics down so no bad habits can start to develop. Be persistent with everyone, and don't be afraid to correct and talk through steps again so everyone is on the same page
• Very satisfied – not too difficult at all. • We had a consultant available as part of our contract, but we didn’t really need to use (except for some advice on ActiveDirectory and single sign-on)
Adobe Workfront blows the other systems out of the water. It just delivers more - out of the gate, and at every quarterly update. Innovation is top of mind, and meeting customers' needs is key. We have been extremely satisfied with Workfront and look forward to all the new features on the horizon, especially AI.
Pega Pega is a comprehensive suite which offers a unique theme of BPM development in the market. A no-coding approach based on rules with inheritance makes Pega a very powerful product. However Pega, falls short on integration centric capabilities and very rigid to customize. On the other hand IBM comes with array of products which suits needs of varying degree. Advanced integration is solved by BPEL Process Server which has support for state based patterns and mediation. Dynamic rules and event management can be solved with WODM, Cloud to on-premise connectivity with Cast Iron, Enterprise gateway and security usecases with DataPower, Social BPM with IBM BPM , WODM, mobify with Worklight. Pega has a little bit of eveything here and there. It solves the dynamic rule management, brings out the flavor of Social BPM and mobility with Antenna ( I guess) and predictive analytics as well in one single suite. There are certain usecases which needs to have a little bit of everything, however this little bits and pieces of functionality when its blows, Pega would have problems to scale. With IBM its a bit nightmare to maintain a variety of technologies, however you can wish to go for one without the other and go for something only when you truly need it. Pega vs IBM Its difficult to pick a winner. In nutshell when you want a full scale BPM with rich integration capabilities go for IBM BPM. On the other hand if you hava mature integration capability already, Pega can yield quick results for you as well. Pega's strength is its methodology. IBM BPM's strength is integration. Actually you can't go wrong with both in terms of implementation. My strong recommendation is to invest time to process analysis and pick a good vendor to support consulting and implementation.
As I stated earlier, I didn't have to pay for Workfront myself- I'm a user under a large organization. I know it's not cheap to implement, I don't know how the price scales for a small-business, but I do like the product enough that I'm going to look into it in the future for my own company.
Our organization has thousands of users that use Workfront and it seems to hold up very well. I have not encountered any issues using it and I think it makes it very easy for multiple people to be involved in a project and keep things organized and clear for everyone involved.
It scales from small team interactions to business processes serving thousands of employees, as well as straight-through-processing needs that go well beyond. Of course, scale is always in the eye of the beholder, but IBM BPM does a good job of giving you all of the hooks, APIs, and data that you need to take on whatever scaling approaches you need to meet the load
Resource Management - Year over year, we were able to validate time and money saved by the implementation of Workfront by more than 2%, saving in non-working dollars and 9% savings in working media dollars.
Organization Restructuring and Automation- We also restructured our teams and implemented automation based on our analysis of how and what we spend our time on and the ROI for our respective business units.
