Appian vs Winshuttle

• Allows the use of BPMN to describe and implement a business process.
• Forms can be build relatively easily and with 17.2 (which we haven't upgraded to yet - I have a copy for development) will allow for a lot of flexibility in the layout too.
• The ability to build Java plugins where needed is a huge benefit as there are very few solutions that can't be implemented using Appian.
• Can port to multiple platforms relatively easily.
• Database access is abstracted away, so trivial to move from one DB engine to another.

Read full review

• Thanks to Winshuttle we could optimize our expense reports process. In the past we needed 3 accounting analysts and 3 days to process all expense reports created. So we always were delayed. With Winshuttle, all expense reports are processed in half a day and byjust 1 accounting analyst.
• We implemented a creative development combining Winshuttle Query and Excel Macros. Winshuttle Query reads all Entry Sheets from SAP and puts the information in a Excel sheet. Then a Excel Macro process the information, groups it and send a email with a PDF per provider with all information about entry sheets. Now our providers know exactly what services and materials they have sold us and they can create the invoice without errors.
• All materials text upgrades in differents languagues were optimized thanks to Winshuttle. We have almost 200 text materials changes per day and now with Winshuttle the job is done in 10 minutes.

Read full review

• Licensing model is too restrictive both from a purchasing perspective (blocks) as well as cost for use (need license even if the only step in a process is to approve or initiate something).
• The memory database should archive process execution results to a SQL database versus needed to build this to reporting analysis and trending reports for process metrics.
• Canned reporting should be available for process metrics so these do not need to be built, i.e. this is a BPM tool so I should be able to report on metrics not just what is current or completed in the memory database but for whatever timeframe I decide to keep.
• Improved support model in which you can talk to someone versus submitting ticket and getting bogus responses.

Read full review

• While the tool is flexible you sometimes have to take unconventional routes to get your results.
• More standard templates for the less known modules such as the RE/FX module.
• Incorporating similar Excel formulas prebaked in the template for Transaction (like Query) would be great.

Read full review

• Increased Visibility - Visibility into the amount and type of work across the organization has allowed senior management to make better and more informed decisions
• Improved Efficiency - Reduced the number of different work intake processes by 85% which makes the intake, review and disposition of requests much faster
• ROI - Better decisions, more efficient processing of work requests improves resource management and allocation ultimately reducing costs
• Workload Reduction - Many of the organization's processes were still be managed via spreadsheets and email. This required talented personnel to spend more time shuffling papers than focusing on more meaningful and rewarding work.

Read full review

• Employee efficiency is a great improvement.
• Some tasks just litterallly cannot be performed manually at such volumes.
• Employee erros can be reduced by checking input prior to import where manual keying could not as easily be checked.

Read full review