Ignition Cloud Edition
User-Friendly Drivers with Strong PLC Integration and SQL Connectivity
Very User-Friendly SCADA with Great University Training
Cloud deployment has improved global collaboration and simplified pay‑as‑you‑go access
What is our primary use case?
My main use case for Ignition Cloud Edition is regarding the customer deployment of these Ignition Cloud Edition projects when they do not want to install on the on-premises servers.
My main use case for Ignition Cloud Edition is for customers that do not want to use on-premises-based services, and they want to use the pre-bundled module set, which comes with pre-loaded core high-level modules including Perspective, SQL Bridge, Tag Historian, Enterprise Administration Module, reporting, alarm notification, and Mongo DB integration. Rather than purchasing a traditional perpetual license, Ignition Cloud Edition is deployed directly via cloud marketplaces like AWS and Azure using a pay-as-you-go or user-based model and also has native MQTT and cloud connectivity, featuring native MQTT engine, transmission, and distributor modules by Cirrus Link to easily stream IoT data from local edge devices like Ignition Edge directly into the cloud. Its elasticity and enterprise analytics allow taking advantage of cloud infrastructure to scale and store dynamically for massive data historian and connect operational data directly to cloud-native tools like machine learning, AI, and big data pipelines.
What is most valuable?
The best features I have observed with Ignition Cloud Edition include the pre-bundled module set, being a cloud-native manufacturer where you do not have to pay for a license, and the reliance on OPC-UA, MQTT, or gateways to get data instead of direct PLC drivers. Additionally, it offers a cloud-based micro-subscription model where you can pay-as-you-go without the maintenance of any hardware.
The cloud-based micro-subscription and the fact that I do not have to maintain hardware have definitely affected my day-to-day work positively, as I often require global access with teams recording from different locations. When Ignition Cloud Edition and the gateway are installed on the cloud, everyone can access it based on the user role assigned, making it easier and more flexible, especially for projects involving multiple time zones. Furthermore, not having to worry about server crashes enhances reliability.
Ignition Cloud Edition has positively impacted my organization by allowing us to get more projects and also increasing our revenue. I can share that we have experienced around a five to six percent increase in revenue based on adding Ignition Cloud Edition platform to our services.
What needs improvement?
Improvements for Ignition Cloud Edition should include the addition of more traditional PLCs-based drivers.
I would also suggest that they might launch future Ignition Cloud Edition-based services, eliminating the need to rely solely on AWS, allowing Ignition Cloud Edition to perhaps manage that independently.
For how long have I used the solution?
I have been using Ignition Cloud Edition for more than three years.
What do I think about the stability of the solution?
Ignition Cloud Edition is very stable.
What do I think about the scalability of the solution?
The scalability of Ignition Cloud Edition is impressive because it allows for multiple licenses and users, making it comparable to other cloud services such as AWS, Azure, or Google Cloud, without the worry of scaling issues.
How are customer service and support?
The customer support for Ignition Cloud Edition is quite good; whenever we have a call or send a message, we receive a reply within one to two days.
Which solution did I use previously and why did I switch?
I have not previously used any other solutions similar to Ignition Cloud Edition.
What was our ROI?
I have seen a return on investment in terms of saved time and money, achieving savings around five to six percent and we are still exploring options for more improvements.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup costs, and licensing was quite good, as it was straightforward based on how many machines, what kind of hardware we wanted to use, and how many users were needed.
Which other solutions did I evaluate?
Before choosing Ignition Cloud Edition, we did not evaluate other options as we were already long-time partners of Ignition and were confident in its standard and robust capabilities; thus, no other options were a good fit for us.
What other advice do I have?
My advice to others considering Ignition Cloud Edition is to proceed with it, especially if you prefer not to have on-premises applications, as it is a very good tool.
Ignition Cloud Edition reflects that it is still missing some driver options and we require a more cost-effective solution, which is why I rate it an eight on a scale of one to ten.
Regarding Ignition Cloud Edition's governance and security, I find them to be reliable, as we have standard security and governance protocols implemented.
In terms of Ignition Cloud Edition's AI capabilities, I rate its accuracy between seventy to eighty percent, noting that some data outputs are incorrect, indicating it is not one hundred percent reliable, so it requires verification against actual flow data.
One project that stands out in my experience with Ignition Cloud Edition for a customer deployment relates to warehouse management, where I have been using Ignition Cloud Edition on the Amazon Web Services server with the customer having to pay based on the pay-per-use model, dependent on how much information needs to be processed and how many clients need access, rather than based on a standard license.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Drew hydro
Remote alerts have improved real-time monitoring of beef processing and quality issues
What is our primary use case?
My main use case for Ignition Cloud Edition was to view Tyson food plants' beef slaughter lines where they took care of the cattle. I use Ignition Cloud Edition to show the lines and all the systems and send alerts and statuses to the database.
A specific example of how I used it in that context is if there was an issue with the way a part of a cow was sliced or skinned, it would alert my phone for the admin.
What is most valuable?
The best features Ignition Cloud Edition offers are the ability to set alerts on a system and access that remotely.
Ignition Cloud Edition has positively impacted my organization as they do a ton of their work with it. They do almost all their work with it.
What needs improvement?
I think Ignition Cloud Edition could be more intuitive on how to use it.
When I'm trying to accomplish something, I pretty much have to have the certification to really know how to get it done or look it up.
For how long have I used the solution?
I have been using Ignition Cloud Edition for about three months total.
What do I think about the stability of the solution?
Ignition Cloud Edition is stable.
What do I think about the scalability of the solution?
I am not too informed on Ignition Cloud Edition's scalability, but I would say it's pretty good because it's used for a very large system.
How are customer service and support?
The customer support for Ignition Cloud Edition is good. I had an issue, and I reached out to Ignition Cloud Edition and they responded in a timely manner.
I would rate the customer support as a nine on a scale of one to ten.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that I was an intern, so I do not really know.
What other advice do I have?
My advice to others looking into using Ignition Cloud Edition is to get the certification or licensing.
By Far the Easiest Building Automation System—Simple, Streamlined Deployment
Sandbox Flexibility With an Open-Source Feel for Power Users
Cloud platform has transformed maintenance by centralizing diagnostics and improving collaboration
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?
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?
What do I think about the scalability of the solution?
How are customer service and support?
Which solution did I use previously and why did I switch?
How was the initial setup?
What about the implementation team?
What was our ROI?
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
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?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Centralized cloud monitoring has improved access to multiple industrial sites across the country
What is our primary use case?
I use Ignition Cloud Edition in industrial automation architectures that contain several sites that are separate from each other. For example, I took part in a project where we have several LNG storage and regasification units located in different locations throughout Brazil. Starting from Ignition Edge, we take this data and send it to the central SCADA in the cloud using Ignition.
Ignition Cloud Edition really helps because you end up centralizing all site data in a single place, and thus you can access it faster via the web from anywhere you are.
How has it helped my organization?
Ignition Cloud Edition has had a very positive impact on my organization. Before, I had a SCADA system for each plant, and that caused bottlenecks because I had to access each one individually. Today, by centralizing via the cloud, access is much faster.
Ignition Cloud Edition reduced costs both in terms of time. To access each system, you spent considerable time connecting to the VPN and so on. In an architecture where we have more than 100 clients, this was detrimental and took a lot of time.
What is most valuable?
The best features that Ignition Cloud Edition offers are the ease of developing screens for the web interface. In addition, the native support feature for OPC-UA, the Modbus part, and the ease of integration via MQTT are valuable. A classic differentiator of Ignition is that it has its unlimited version, which doesn't charge for tags, clients, screens, or connections, which many other systems do charge for.
What needs improvement?
Ignition Cloud Edition can be improved in the sense that it doesn't come with some drivers in the Cloud version. For example, local device drivers are not included, and you always need a local Ignition Edge there. That is a negative point that could be improved.
I believe it is still a bit difficult in terms of development, since with Ignition, to develop you need a bit of knowledge of technologies that are outside traditional automation, such as Python and HTML for screen development.
For how long have I used the solution?
I have been using Ignition Cloud Edition for almost two years.
What do I think about the stability of the solution?
Ignition Cloud Edition has not experienced any stability issues.
What do I think about the scalability of the solution?
Ignition Cloud Edition has not experienced any scalability issues.
How are customer service and support?
Customer support for Ignition Cloud Edition is very good, including the knowledge page and the courses offered for free.
Which solution did I use previously and why did I switch?
Previously, I used GE iFIX in each plant. Now, instead, I use a centralized Ignition Cloud Edition.
How was the initial setup?
The initial setup was completed.
What about the implementation team?
A partner handled the implementation.
What's my experience with pricing, setup cost, and licensing?
The prices for Ignition Cloud Edition were very affordable, compared to other traditional SCADA systems.
Which other solutions did I evaluate?
I evaluated Elipse here in Brazil. However, I realized that it was not as advanced as Ignition.
What other advice do I have?
I would recommend using Ignition Cloud Edition because of the ease of integration with the advancement of artificial intelligence. I gave this review a rating of 9.