Appian vs. QT9 QMS

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.

Incentivized

I like using QT9 because it's easy to use, easy to train others and is very user friendly. QT9 has all that we need to be successful. Our data tracking, corrective actions, documentation tracking and the reporting of that data is extremely easy to use and implement. We also think that the EC process is very useful for updating designs

• 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.

Incentivized

• Tracks document reviews well.
• Makes creating NCP's and CARs easier than paper.
• Tracks and maintains calibration records well.

• 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.

Incentivized

• Better graphics/visually appealing and easier to navigate
• It would be nice to have a chat feature
• The interface with our vendors/customers isn't always smooth.

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

document tracking and updating has been clearer.

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.

Incentivized

ease of use and implementation. user defined fields allow customization. exporting information into excel permits the use of pivot tables to analyze data and create reports. In geneneral, the main features required by our QMS are in the software

Incentivized

QT9 QMS has always been available. Even in instances where there would be an update, notifications would be sent out to provide a heads up to the users. Any issues where QT9 QMS would have problems, glitches, or run slow, support was always available to take care of the issues.

I give it a 10 as the information is always readily available. As for speed, For the most part, loading of the sometimes takes a little longer than others. There are occasional times that it does run a little slow, but when that happens, the support team has always been there to help.

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.

Incentivized

The usability and clarity of documentation and tracking is fantastic. Calibration is always open and trackable as well.

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.

Incentivized

I had online training which was wonderful. The training was open and inviting to ask questions. I came on just after QT9 QMS was accepted in the company. SO I was in almost at the ground floor.

Very boring; hard to get through quickly, but rather effective in demonstrating the use of the platform.

Incentivized

Training was open and was able to ask any questions. This provided clarity in all the areas that I would use. There has been training readily offered by the QT9 company and provided opportunities to grow our understanding of the software and additional ways that we could utilize it.

It was really seamless. SaaS in the true definition of the word. We logged on and started using the product. Very easy.

Incentivized

It went well and is used daily.

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]?

Incentivized

We have not used any other systems Prior to QT9 QMS our systems were all manual and down through excel and email.

We have sites in many different areas within and outside of our current state. The use of QT9 QMS allows all sites to be in one database so everyone has the same information. The rollout of the software was rather easy as online training could be used for all sites and provided an excellent tool for all areas.

not sure if this is something other than the professionalism of the individuals that I worked with, but the people were Very professional. Always able to answer questions and if they did not have answers they would find out what they are and then follow up.

• 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.

Incentivized

• visiablity of controlled documents and those that are out for revision has been good
• great central hub to allow users from other facitilities to use the same documents/processes
• visiabiliy of the status of the engineering changes

Incentivized