IBM Terraform (formerly Hashicorp Terraform) is a cloud infrastructure automation tool used to create, change, and improve production infrastructure, and it allows infrastructure to be expressed as code. It is available Open Source, and via Cloud and Self-Hosted editions.
$0
PowerDMS by NEOGOV
Score 7.0 out of 10
N/A
PowerDMS by NEOGOV is a software platform designed to recruit, train, equip, and protect employees across their careers, used for policy management, community engagement, and staff scheduling.
Anything that needs to be repeated en masse. Terraform is great at taking a template and have it be repeated across your estate. You can dynamically change the assets they're generating depending on certain variables. Which means though templated assets will all be similar, they're allowed to have unique properties about them. For example flattening JSON into tabular data and ensuring the flattening code is unique to the file's schema.
This software is very well suited for law enforcement agencies of all sizes from 5 to 5000 officers. There is a mobile app that allows officers to quickly and easily search while out in the field or on a call. They can quickly review a policy, locate a form, pull up a map and much more using either the mobile app or the desktop application.
Policy management- [Users] sign for, and can take [tests] to prove understanding of policy right in the application. As [the] policy is updated, old versions are retained, so that we not only know what a policy contains, we can track changes and provide information on what a policy was at any given time in the past.
Training- Users receive notifications when training is due and are guided to complete the training. If the training requires recertification, PowerDMS can be configured to alert the user that re-training is needed, without a supervisor needing to keep track. All documents used in training, including presentations and videos, can be contained in the PowerDMS course, so we can prove not only that an employee was trained, but exactly what curriculum was use din any given training.
Accreditation Assessment- [Our] accreditation standards manual is uploaded directly into PowerDMS. Proofs are accomplished using the actual policy and procedure, as well as the documents created during the workday. There is absolutely no duplication of effort.
Communications accountability- Email [can] be read and forgotten. With PowerDMS, a document can be distributed for user signatures, insuring that the user took affirmative action to read and understand the document.
The language itself is a bit unusual and this makes it hard for new users to get onboarded into the codebase. While it's improving with later releases, basic concepts like "map an array of options into a set of configurations" or "apply this logic if a variable is specified" are possible but unnecessarily cumbersome.
The 'Terraform Plan' operation could be substantially more sophisticated. There are many situations where a Terraform file could never work but successfully passes the 'plan' phase only to fail during the 'apply' phase.
Environment migrations could be smoother. Renaming/refactoring files is a challenge because of the need to use 'Terraform mv' commands, etc.
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.
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.
The syntax itself is pretty straightforward. The documentation is well-maintained & easy to follow. Most cloud providers, even smaller ones, maintain official provider libraries, making discovery & learning a breeze. Some, like GCP, even provide high-level libraries on top of their own more primitive provider, making building complex infra much more manageable. The language itself is cloud-agnostic, so you can literally manage resources from multiple providers in a single Terraform repo.
There is a learning curve as with any software system and I have found those users who consistently use the system more have a much higher success rate than those who only log in to sign off on documents. Now that most users have been in the system for over 2 years I consistently hear how much easier the processes are than they originally thought they would be
Terraform's performance is quite amazing when it comes to deployment of resources in AWS. Of course, the deployment times depend on various parameters like the number of resources to deploy and different regions to deploy. Terraform cannot control that. The only minor drawback probably shows up when a terraform job is terminated mid way. Then in many cases, time-consuming manual cleanup is required.
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.
I have yet to have an opportunity to reach out directly to HashiCorp for support on Terraform. However, I have spent a great deal of time considering their documentation as I use the tool. This opinion is based solely on that. I find the Terraform documentation to have great breadth but lacking in depth in many areas. I appreciate that all of the tool's resources have an entry in the docs but often the examples are lacking. Often, the examples provided are very basic and prompt additional exploration. Also, the links in the documentation often link back to the same page where one might expect to be linked to a different source with additional information.
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.
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.
Terraform is the solid leader in the space. It allows you to do more then just provisioning within a pre-existing servers. It is more extensible and has more providers available than it competitors. It is also open source and more adopted by the community then some of the other solutions that are available in the market place.
PowerDMS is a lot different than Linkedin Learnings. In PowerDMS you have to create your own courses versus in Linkedin Learnings they provide extensive content on a wide variety of subject matter. Linkedin Learnings is what we have used in our organization for Bias Training and Ethics Training. PowerDMS is the repository for documents and Trainings, so the systems work very differently
we are able to deploy our infrastructure in a couple of ours in an automated and repeatable way, before this could take weeks if the work was done manually and was a lot of error prone.
having the state file, you can see a diff of what things have changed manually out side of Terraform which is a huge plus
if state file gets corrupted, it is very hard to debug or restore it without an impact or spending hours ..
writing big scale code can be very challenging and hard to be efficient so it's usable by the whole team
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.
