AWS OpsWorks vs. PowerDMS by NEOGOV

AWS Opsworks is good for linking AWS services and setting up and maintaining webservers using Chef. However, it will become EOL soon so we would not recommend starting new projects using it and instead go for the recommended Systems Manager setup

Incentivized

Getting 100% signature compliance on policy updates used to take months but since automating out policy management updates in PowerDMS, we can get 100% compliance in as little as 2 weeks. Internal requests for things such as training, purchases, etc used to be pushed up the chain of command via a paper copy and would often get misplaced or lost in a full mailbox. Using PowerDMS to automate those requests put the power back in the requester's hands and increased transparency and accountability across the organization.

Incentivized

• The interface is quite intuitive and allows you to discover and easily find what you want to do and what other features are within OpsWorks.
• Chef integration is pretty seamless and there are a good set of options and operating systems to choose from
• It makes things like auto scaling set up, either via load or time, more straight forward and intuitive than what you'd typically see via the EC2 console

Incentivized

• PDMS is extremely user-friendly from both the administrator aspect and the user.
• The workflow process is awesome and easy to set up.
• PDMS's support team is barred none. We've never had issues with reaching out to find a simple solution to our challenges.

• integrating with newer AWS services (ie. ALB)
• keeping up with Chef releases (ie. locked at 12 currently)

Incentivized

• The Workflow process in PowerDMS is not as easy to grasp as some of the other concepts and requires a little more explaination, especially for non-administrative background users.
• Users are unable to view the steps in a Workflow template in order to determine which Workflow would work best for their needs when routing documents.
• It would be great to have multiple message options for past due inbox notifications in addition to the options for past due tasks to encourage users to go to their inbox to review their messages.

Incentivized

I have had nothing but positive experiences with PowerDMS from day one. If we ever run into a situation we are unsure of, PowerDMS support has ALWAYS been able to answer us basically immediately. I really love that they are constantly seeking to improve and expand.

While not necessarily user-intuitive, with a small amount of dedication to training and learning how the system functions, it becomes very usable. I would say that the usability scale is quite user-dependent. For a standard user that just needs to review and sign documents, it is very easily used. On the other end, management does a bit more of a learning curve.

Never had an issue with PowerDMS not being available. Speed is an issue from time to time

We use PowerDMS in the cloud so our performance might be different from other users who use on-premise. The program has always been up with very minimal downtime and always seems responsive and snappy when navigating the UI and searching documents. We don't currently have any integrations with other software.

Unless you pay for a pricey support package getting support on OpsWorks will be pretty slow. Documentation is also relatively limited and sometimes hard to follow when compared to competitors. Generally, we've been able to get the answers we need from OpsWorks support when we run into problems but don't expect rapid responses.

Incentivized

I just wish we had some in-state support. The contacts I have had with customer support have been great. Awesome communication, problem-solving, and support. I have talked to and met Stephanie Williams (CSA for Power DMS) at the most recent Entrust conference. She was professional and devoted time to addressing our agency needs.

In-person training works really well.

Online training works well and keeps from having to have classroom training

Implementation of PowerDMS was near seamless. The product was able to input existing policies and procedures within a few hours, which helped to lay the foundation for future use. Having PowerDMS on-boarding readily available was also a huge benefit.

OpsWorks isn't really a direct competitor to Terraform/Cloudformation, but it does allow you to do some of the more simple things on offer quite quickly and effectively. Opsworks was used for this reason, along with existing internal knowledge of Chef. Along with some of the other services on offer from AWS, it is good to use as a stepping stone along the way when building your systems - or perhaps it would be entirely suitable for a fairly simple project.

Incentivized

Our previous document product was Image Silo. It was a stable-enough product, but was strictly an indexed filing system. PowerDMS goes well beyond indexing (which it does very well) and provides countless more features and functions as described above. I would describe the difference between our previous product and PowerDMS like the difference between the library and the Internet. Both contain information, but on is limited, while the other has it all.

Because of features and functions.

• OpsWorks allowed us to access the AWS infrastructure with a considerably lower time investment than we would have otherwise needed when we first implemented it.
• Since we've been running with OpsWorks we've experienced very little downtime and it's required relatively little maintenance.
• The main downside of using OpsWorks for us is that it has locked us into a very specific infrastructure that doesn't have the flexibility of many of the newer infrastructure management tools, this may lead to a painful migration down the road. We also run a risk of long outage if it ever does introduce breaking changes as the skillset needed to work with the OpsWorks tooling is very specific not widely available in our company.

Incentivized

• Created efficient processes for approving document revision
• Migrated what originally was a paper system to electronic
• Accessible for any employee by logging in, employees do not have to seek out policy and procedure binders, and updated documents can be automatically sent to inboxes when updated.

Incentivized