What is our primary use case?
When I first consider Ignition Cloud Edition, the first word that comes to my mind is flexibility. I developed an entire SCADA platform to monitor my site, focusing on maintenance of PLCs and DCS hardware. This allows us to collect maintenance data from the controllers in the field.
We have many controllers in the field, including Siemens controllers, Rockwell controllers, and DeltaV controllers. All these controllers have diagnostics from the card, from the point in the card, such as digital input, output inputs, analog outputs, and analog inputs. Every point of the controller and every IO has a diagnostic, and I used Ignition Cloud Edition to send this data to the cloud.
How has it helped my organization?
The platform has also improved scalability and flexibility, making it easier to expand our applications as business needs evolve.
Remote access capabilities have enhanced visibility into operations and enabled faster response times for troubleshooting and decision-making. Additionally, the centralized management and high availability of the cloud environment have contributed to increased system reliability and reduced downtime.
What is most valuable?
One of the best features that Ignition Cloud Edition offers is the combination of industrial automation and modern software architecture. Traditionally, when we think about industrial automation, we think about PLCs, SCADA systems, local servers, HMIs, historians, and all of that is still extremely important.
The combination of industrial automation and modern software architecture in Ignition Cloud Edition has benefited my projects by providing improved scalability and flexibility for analytics data, dashboards, centralized data, and remote visibility.
Regarding the features of Ignition Cloud Edition, I really value the development environment. For me, a dashboard should be more than just a collection of numbers; it should tell you something. For example, if I'm looking at a production board or a dashboard, I don't just want to see production numbers; I want to understand if production is on target, if the process is stable, and other relevant factors.
Ignition Cloud Edition has had a very positive impact on our organization, especially in the way we access and use industrial data. One of the biggest benefits is that it allows us to create more centralized and accessible applications.
Centralized access through Ignition Cloud Edition has improved collaboration between automation engineering, operations, and management, as everyone can access the information they need from a different perspective depending on their role.
What needs improvement?
From my perspective, one area that Ignition Cloud Edition could be improved is the learning curve. Ignition Cloud Edition is powerful, and that is a good thing, but because it is powerful, there is a lot to learn. If you are new to the platform, you have to understand tags, databases, scripting, perspective, security, alarms, historical data, gateways, and many other concepts, which can be overwhelming for someone starting from zero. I would love to see even more guided experiences for new users.
For how long have I used the solution?
I have been using Ignition Cloud Edition for almost three or four years before I changed my job recently.
What do I think about the stability of the solution?
Is Ignition Cloud Edition stable? Can you please elaborate?
What do I think about the scalability of the solution?
Ignition Cloud Edition scales very well. As our requirements grow, we can add users, applications, and operational data without the need for significant infrastructure changes. The cloud-based architecture reduces the complexity of expansion, shortens deployment times, and provides flexibility to support future growth while maintaining reliability and performance.
How are customer service and support?
We have had a positive experience with customer service and technical support. The team has been responsive, knowledgeable, and effective in resolving issues. Combined with strong documentation and community resources, the support experience has helped us deploy and maintain the platform successfully.
Which solution did I use previously and why did I switch?
Yes, we previously used an on-premises SCADA solution. We decided to switch to Ignition Cloud Edition to reduce the infrastructure maintenance burden, improve scalability, and simplify system management.
How was the initial setup?
The initial setup was straightforward and easier than a traditional on-premises deployment. The cloud-based architecture minimized infrastructure-related tasks, allowing us to focus on application configuration and integration. Overall, deployment was fast, efficient, and required less IT effort than a self-managed environment.
What about the implementation team?
We did not use an external integrator, reseller, or consultant for the deployment. The implementation was completed internally by our team. The setup process was straightforward, and we were able to leverage our existing knowledge and resources to deploy and configure the platform successfully.
What was our ROI?
Examples of ROI include reduced time spent on server administration, faster deployment of new applications, simplified system updates, and lower infrastructure costs. These improvements have helped reduce total cost of ownership while increasing the efficiency of both operations and support teams.
What's my experience with pricing, setup cost, and licensing?
We found the pricing and licensing model to be straightforward and predictable. Setup costs were lower than a traditional on-premises deployment because there was less infrastructure to manage and maintain. Overall, the platform provides good value by reducing IT overhead, simplifying administration, and offering the scalability needed to support future growth.
Which other solutions did I evaluate?
Before choosing Ignition Cloud Edition, we evaluated Ignition on-premises deployments, AWS-hosted architectures, and other traditional SCADA platforms. While these solutions provided similar core functionality, Ignition Cloud Edition stood out because of its simplified deployment, reduced infrastructure overhead, and ease of scaling. The platform provided a faster path to implementation while maintaining the flexibility and capabilities we needed for industrial operations.
What other advice do I have?
The impact on our daily operations and maintenance workflow is significant because the operators or the company that does the maintenance can see an overall summary of the controls in the field, such as controller five, card fifty, input eight, allowing us to see the macro view.
Ignition Cloud Edition has made it easier to perform maintenance.
Regarding Ignition Cloud Edition's capabilities, I feel that it provides a strong foundation for security and governance. I wouldn't say that it removes all cybersecurity concerns, but it gives us a more structured platform to build on, which I believe is one of the important advantages of the cloud approach, as we can focus more on the application and the business or process problem while still having a professional infrastructure underneath it.
From a governance perspective, Ignition Cloud Edition also helps us control who can access applications and data and how that access is managed.
I would rate this product a ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?