Ignition SCADA

Last updated
Developer(s) Inductive Automation
Stable release
8.1.21 / September 29, 2022;2 years ago (2022-09-29)
Written inJava
Operating system Windows, macOS, Linux
Type SCADA
Website inductiveautomation.com/ignition

Ignition is an Integrated Software Platform for SCADA systems released by Inductive Automation in January 2010. It is based on a SQL Database-centric architecture. Ignition features cross-platform, web-based deployment through Java Web Start technology. The Ignition platform has three main components: the Ignition Gateway, the Designer, and the runtime clients. Independent modules provide separate functionality in any or all of the platform components. Ignition SCADA modules provide features such as: Real-Time Status Control, Alarming, Reporting, Data Acquisition, Scripting, Scheduling, MES, and Mobile support. [1]

Contents

Awards

Ignition received the 2011 Duke's Choice award at the JavaOne conference in San Francisco, CA on October 4, 2011. Oracle recognized the impact of Ignition as a significant Java-based product in Industrial Automation. [2] [3]

Ignition received a 2011 Readers Choice award from Automation World in the SCADA and Information management categories. [4]

Modules

Module Marketplace

Module Marketplace is an online store, similar in concept to: the iTunes Store or Google Play for the SCADA software. Inductive Automation opened it on March 4, 2013. [5] [6]

Some modules are free while others are paid. All are developed using the Ignition SDK. Access to core Ignition apps is made available so that third-party developers can create module apps for use with the company's systems. All of these apps can be made available for download on the Module Marketplace site. [7]

Early reviews compared the Module Marketplace to the Apple iTunes Store, [8] [9] indicated that it was disruptive [10] and that it removed proprietary boundaries among SCADA software producers. [11] Developers set their own pricing models in the marketplace, with 70% of the revenue going to the developer and 30% going to Inductive Automation. [12] All modules are required to be submitted for validation to Inductive Automation to test for stability, compatibility and memory leaks. Upon validation, the module is digitally signed by Inductive Automation and may be uploaded to the Module Marketplace. All modules are required to include a free user re-settable 2-hour trial version. [13]

SQL Bridge

SQL Bridge Architecture Diagram from Inductive Automation Web Site Ignition SQL Bridge Diagram.jpg
SQL Bridge Architecture Diagram from Inductive Automation Web Site

SQL Bridge is an OPC based Middleware product that bridges the gap between industrial PLCs and SQL Databases. It is a drag and drop application that does not require scripting or programming for configuration.

Transaction groups are used to log data, synchronize PLCs, track downtime and manage recipes. Such groups support stored procedures, flexible execution scheduling, and triggering for precise control and monitoring. [14] Data logging can be achieved with transaction groups or SQLTags History.

Store-and-Forward is an engine that buffers SQL database writes to memory and caches them to a local disk when an external database connection is unavailable. Upon reconnection the data is forwarded to the server in aggregated time-efficient batches. [15]

The SQL Bridge module was created in January 2010 to replace the final version of FactorySQL in the 4.x.x series. [16]

Vision

The Vision module is the main visualization portion of the Ignition SCADA platform. containing three main components: the runtime, gateway, and designer.

Reporting

The Reporting module creates dynamic reports. Reports may be generated from existing Adobe Acrobat (PDF) files or created from scratch. Data is introduced through the Ignition platform, providing access to any SQL database or OPC source. The Reporting Module supports: images, graphs, tables, and a variety of basic shape tools. Reports are viewed through Ignition's web-based system. [17] The Reporting Module allows data aggregation and referencing between table and chart objects as displayed in the image screenshot.

SMS Notification Module

The Ignition SMS Alarm Notification Module enables both alarm notification and acknowledgement via text messages. By adding the SMS Notification Module to Ignition, alarm notifications can be sent and acknowledged via text messaging. SMS notification is an efficient and immediate method that makes it easier for users to respond. This module requires the Alarm Notification Module and a Sierra Wireless AirLink RV50 with a data and SMS cellular plan (not included in the module). [18]

Mobile

The Mobile Module allows the full Vision module to run on devices that do not support the Java Runtime Environment. This is accomplished by the mobile client viewing a remote session on the Ignition Gateway. The mobile module requires a JavaScript compliant browser that supports the canvas element. Compatible examples include: iPad, iPhone, Android 2.2+, and VNC clients. [19]

The mobile module allows operators and managers to respond from anywhere to critical data, such as system status, controls system alerts and provides the ability to make notations. [20]

OPC-UA

The OPC-UA Ignition module is an OPC server that supports modular drivers for PLCs and other devices and network connections. It is the first 100% native Java OPC UA stack. [21] The OPC-UA module includes a Quick Client that allows users to read and write PLC register values via an AJAX web page hosted on the Ignition Gateway.

Current drivers include A-B Suite, Modbus TCP, Siemens Ethernet, and Simple TCP/UDP, allowing users to connect to a multitude of devices such as PLCs, solar cells, lights, generators, flow meters, bar code scanners, etc.

Inductive Automation offers the Ignition OPC-UA server for free. The required license must be obtained through the company web site or by direct contact. [22]

OPC-COM

The OPC-COM Module supports connections to local and remote OPC-DA servers. It works on both 32-bit and 64-bit systems. It has been tested for interoperability with third party OPC-DA servers at several OPC Interoperability conferences. [23]

Module Architecture

Inductive Automation Ignition Platform Architecture Inductive Automation Ignition Platform diagram.png
Inductive Automation Ignition Platform Architecture

MES Module Layer

MES Modules are separately licensed Ignition plug in modules that generally provide higher level functionality with less user development. MES Modules are designed to provide specific functionality and can be industry specific. Current modules available are: Downtime OEE, SPC, and Scheduling . The Changeover Management and Track & Trace / Genealogy Modules have been announced as upcoming as of January 2013.

HMI/SCADA Module Layer

The HMI/SCADA Module Layer contains mainstay products of the Ignition Platform. Vision is the main visualization module, SQL Bridge is a bidirectional OPC to SQL database historian and transaction manager, Reporting generates dynamic Pdf reports, and Mobile allows access to HTML 5 compatible devices such as iPads, iPods, Android, Smartphone, and Tablets.

Platform Layer

The Platform Layer includes the following core functionality to all modules: OPC-UA Client, Database, Web Server, System Logging, Licensing, Unified Development Environment, Auditing, Authentication, Module API, Alerting Core Functionality, Database Connectivity, Python Scripting Engine, Realtime Tag Database, Store & Forward, and Redundancy. [24]

History

FactorySQL

FactorySQL box FactorySQL logo.gif
FactorySQL box

FactorySQL was an OPC based Middleware product by Inductive Automation that bridged the gap between industrial PLCs and SQL Databases. [25] FactorySQL was a drag and drop .NET application that ran as a Windows service. FactorySQL version 1.0 was released in 2003 and deprecated at version 4 in 2010 with the release of Ignition [26] Inductive Automation offered the OPC-UA module for free. [27]

FactorySQL was initially written to be a drag and drop OPC to SQL data logger. Functionality was introduced to become a Transaction Manager and Industrial Historian. FactorySQL introduced SQLTags support with version 4.1 in December 2007. [28]

FactorySQL configuration was done with standard Groups. This unit of configuration would morph from a historical logger, real-time status and control synchronizer, downtime tracker, recipe manager, etc. [29] The group configuration defines the database connection, table, timing options, triggering options, and "direction". Direction defines whether read or write operations come from or go to the OPC server from the SQL database. "Bidirectional" allows a change from either side to be written to the other. Groups contain Items. Items are dragged from an OPC browsing tree or manually created. Each item represents a fully qualified OPC path along with a column name in the SQL database. Items also contain scaling options, OPC information, and other modes of operation.

Features listed from vendor web site: [30]

FactoryPMI

FactoryPMI box FactoryPMI logo.gif
FactoryPMI box

FactoryPMI was a Java based SCADA product by Inductive Automation containing three main components: the runtime, gateway, and designer. [33] The FactoryPMI designer began as a form of Sun's Bean Builder. FactoryPMI version 1.0 was released in 2003 and deprecated at version 3.3 in 2010 with the release of Ignition. [34]

Features listed from vendor web site. [35]

Versions

FactoryPMI major release history
Date releasedVersionComments
08/09/20051.3New components.
10/18/20051.4New proprietary component layout that no longer uses springs.
01/08/20061.5Added industrial graphics library with 226 images.
06/28/20061.6Added Plugin architecture. Added new components.
08/02/20061.7Added concurrent developer support.
09/22/20061.8Added project/gateway retargeting for the FactoryPMI Runtime, with support for parameter passing and startup window specification.
12/29/20062.0Added ability to combine Gateways into clusters.
04/25/20072.1Major improvements to the Designer introducing a docking style customizable user interface.
08/14/20072.2Component Styles feature for dynamic multi-state animation.
09/17/20073.0SQLTags feature implemented.
11/21/20073.1SSL, Java 6, and "Standalone Mode" implemented.
03/06/20083.2New serialization and window management.
12/16/20083.3Status Chart and Tab Strip components.

2010 consolidation

In 2010, Inductive Automation consolidated FactorySQL and FactoryPMI with Ignition by Inductive Automation. It created a modular framework, providing a central design interface for FactorySQL and FactoryPMI. Ignition became the platform, and FactorySQL and FactoryPMI were refactored as modules. FactorySQL became the SQL Bridge Module, and FactoryPMI became the Vision Module. Two other modules included with the initial release were: the Ignition Reporting Module, and the Ignition OPC-UA Module. The OPC-UA module can also be downloaded for free, and used as a stand-alone OPC-UA server.

SQLTags

SQLTags is a proprietary technology that uses any SQL Database as a Tag Database. Tags can be derived from the following sources: OPC, expression, or constant and support various configuration options such as: alerting, scaling, and historical storage. SQLTags are stored in Tag Providers, which are automatically configured tables in an SQL database. [38]

SQLTags Historian is a proprietary data logging technology that manages historical data in any supported SQL Database. It is configured by defining an Ignition SQL database connection, then enabling the feature on a per tag basis. The system automatically creates and manages the tables without any user SQL input. Historical Scan Classes support different logging intervals by sets of tags as well as altering the logging rate dynamically. This allows the system to store high resolution history when needed, but lower resolution data for other periods. The system automatically partitions data into multiple database tables. This accomplishes two functions: ensures consistent performance over the long term, and provides a consistent mechanism for data archival and pruning. [39]

Scripting

The Ignition platform uses scripting to allow designers to add flexibility and customization. There are two major scripting languages in Ignition: Python and the Expression Language.

Python

Ignition uses an implementation of Python version 2.5 called Jython. Python script is used for component Event Handling. An example of this would be opening a popup window when a user clicks on a graphic object. Another common use are event scripts such as a timer that checks for alarms or a logon script. Java classes and methods can also be used in Jython for more specialized functionality.

Expression Language

The Ignition Expression Language is a simple language that was invented by Inductive Automation. [40] An expression language is a very simple kind of language where everything is an expression - which is a piece of code that returns a value. This means that there are no statements and no variables, just operators, literals, and functions. Consider an example from the expression language found in Microsoft_excel. Excel can calculate a cell's value dynamically by typing an expression such as "=SUM(C5:C10)", which performs the arithmetic sum of those 6 cells. The expression language in Ignition functions similarly. It is used to define dynamic values for tags and component properties.

Expressions are divided in the following categories: Aggregates, Color, Date and Time, Logic, Math, String, Type Cast, and Advanced.

Development

An Ignition Module SDK is available for anybody to develop their own modules. [41] The SDK exposes the API and classes as separate JAR resources for the following: Client, Gateway, Designer, Common, Vision module. For example, a programmer wrote an Ignition module to integrate with QuickBooks, which uses SOAP to communicate with the QuickBooks Web Connector. [42]

Modules must be submitted to Inductive Automation for testing prior to approval. Once tested, they are digitally signed and ready for distribution to production Ignition systems.

Licensing

Ignition is typically sold with an unlimited licensing structure, favoring a per server model that avoids charging for: clients, PLC or SQL Database connections, tags, or visualization screens. [43]

The most common Ignition software package is The Works which includes unlimited versions of the following modules: SQL Bridge, Vision, Reporting, and Symbol Factory. Limited versions of the SQL Bridge and Vision Modules are restricted by functionality and concurrent clients, respectively. [44]

Performance

Ignition performance is based on tag changes per second and total number of concurrent clients. Inductive Automation released a 2008 white paper benchmarking SQLTags performance. [45] Although testing was conducted on FactorySQL and FactoryPMI, Ignition performance is expected to be at least comparable. Evaluation utilized 150 Amazon EC2 virtual machines using the following databases: MySQL with MyISAM data engine, MySQL with InnoDB engine, Microsoft SQL Server 2005 Express Edition, and Oracle 10g Express Edition. As a real world point of comparison, a Surefire SCADA distillery project sustains 30,000 discrete tag changes per second on a Linux platform. [46]

Security

Inductive Automation promotes IT departments supporting security using standard methodology. [47] Ignition supports the following security features:

The United States Computer Emergency Readiness Team (US-CERT) released advisory 11-231-01 that allowed malicious unauthenticated users to download sensitive information regarding project configuration. Inductive Automation responded by resolving the issue in version 7.2.8.178 and greater. [48]

Open Source

Inductive Automation is a promoter and contributor to the Open source community. FactoryPMI utilizes a number of such projects including: MySQL, Apache, JFreeChart, Jython, Hsqldb, jTDS, Bean Builder, and numerous others.

Related Research Articles

<span class="mw-page-title-main">Microsoft Access</span> Database manager part of the Microsoft 365 package

Microsoft Access is a database management system (DBMS) from Microsoft that combines the relational Access Database Engine (ACE) with a graphical user interface and software-development tools. It is a member of the Microsoft 365 suite of applications, included in the Professional and higher editions or sold separately.

SCADA is a control system architecture comprising computers, networked data communications and graphical user interfaces for high-level supervision of machines and processes. It also covers sensors and other devices, such as programmable logic controllers, which interface with process plant or machinery.

Jython is an implementation of the Python programming language designed to run on the Java platform. It was known as JPython until 1999.

Oracle Forms is a software product for creating screens that interact with an Oracle database. It has an IDE that includes an object navigator, property sheet, and code editor that uses PL/SQL. It was originally developed to run server-side in character-mode terminal sessions. It was ported to other platforms, including Windows, to function in a client–server environment. Later versions were ported to Java where it runs in a Java EE container and can integrate with Java, and web services that can be launched from a URL. Recent versions provide a means to run the forms from a desktop computer without requiring a browser.

Open Platform Communications (OPC) is a series of standards and specifications for industrial telecommunication. They are based on Object Linking and Embedding (OLE) for process control. An industrial automation task force developed the original standard in 1996 under the name OLE for Process Control. OPC specifies the communication of real-time plant data between control devices from different manufacturers.

The OPC Foundation is an industry consortium that creates and maintains standards for open connectivity of industrial automation devices and systems, such as industrial control systems and process control generally. The OPC standards specify the communication of industrial process data, alarms and events, historical data and batch process data between sensors, instruments, controllers, software systems, and notification devices.

The OPC Data Access Specification is the first of a group of specifications known as the OPC Classic Specifications.

In computing, a solution stack or software stack is a set of software subsystems or components needed to create a complete platform such that no additional software is needed to support applications. Applications are said to "run on" or "run on top of" the resulting platform.

<span class="mw-page-title-main">Uniface (programming language)</span> Low-code development platform

Uniface is a low-code development and deployment platform for enterprise applications that can run in a large range of runtime environments, including mobile, mainframe, web, Service-oriented architecture (SOA), Windows, Java EE, and .NET. Uniface is used to create mission-critical applications.

OPC Unified Architecture is a cross-platform, open-source, IEC62541 standard for data exchange from sensors to cloud applications developed by the OPC Foundation. Distinguishing characteristics are:

Citect is now a group of industrial software products sold by Aveva, but started as a software development company specialising in the Automation and Control industry. The main software products developed by Citect included CitectSCADA, CitectSCADA Reports, and Ampla. As of August 2021, Citect SCADA is now known as AVEVA Plant SCADA.

<span class="mw-page-title-main">JFire</span> Defunct accounting software system

JFire was an Enterprise Resource Planning and Customer Relationship Management system.

Inductive Automation is a supplier of web-based industrial automation software based in Folsom, California, US. The Ignition SCADA platform is the company's main product line.

<span class="mw-page-title-main">Google App Engine</span> Cloud-based web application hosting service

Google App Engine is a cloud computing platform used as a service for developing and hosting web applications. Applications are sandboxed and run across multiple Google-managed servers. GAE supports automatic scaling for web applications, allocating more resources to the web application as the amount of requests increases. It was released as a preview in April 2008 and launched officially in September 2011.

<span class="mw-page-title-main">CODESYS</span> Development environment for programming controller applications

Codesys is an integrated development environment for programming controller applications according to the international industrial standard IEC 61131-3.

B-Scada is a company based in Crystal River, Florida. B-Scada's product offerings include on-premises Supervisory Control and Data Acquisition (SCADA) and Human Machine Interface (HMI) software platforms, a cloud-based Internet of Things (IoT) software platform, and wireless sensing hardware. It is one of the first companies to use data modeling in SCADA systems to create virtual representations of real world physical assets.

<span class="mw-page-title-main">Seeq Corporation</span> Software company providing analytics for industrial processes

Seeq Corporation is a software company founded in 2013 and headquartered in Seattle, Washington, United States. The company creates analytics software for various industrial process manufacturing sectors, including pharmaceuticals, oil and gas, mining, pulp and paper, energy, utilities, IIoT, and chemicals.

Havex malware, also known as Backdoor.Oldrea, is a Remote Access Trojan (RAT) employed by the Russian attributed APT group "Energetic Bear" or "Dragonfly". Havex was discovered in 2013 and is one of five known ICS tailored malware developed in the past decade. These malwares include Stuxnet, BlackEnergy, Industroyer/CRASHOVERRIDE, and TRITON/TRISIS. Energetic Bear began utilizing Havex in a widespread espionage campaign targeting energy, aviation, pharmaceutical, defense, and petrochemical sectors. The campaign targeted victims primarily in the United States and Europe.

<span class="mw-page-title-main">Jam.py (web framework)</span> Python web framework

Jam.py is free and open-source low-code/no-code "full stack" WSGI rapid application development framework for the JavaScript and Python programming language.

References

  1. "Inductive Automation Module Features" . Retrieved 5 Jan 2013.
  2. "Oracle Announces Winners of the 2011 Duke's Choice Awards". Oracle Corporation. 14 October 2011. Retrieved 29 Dec 2012.
  3. "Inductive Automation's Java-based HMI and SCADA application built on OPC-UA standard wins award from Oracle". Automation World. 11 November 2011. Archived from the original on 12 April 2013. Retrieved 29 Dec 2012.
  4. "Leadership In Automation 2011: First Team Honorees". Automation World. 21 January 2012. Retrieved 29 Dec 2012.
  5. "Inductive Automation to Launch First Community-Based Industrial Automation Software Module Store". Inductive Automation. Archived from the original on 2013-07-29. Retrieved 10 Mar 2013.
  6. Gary Mintchell (18 Feb 2013). "ARC Forum 2013: First Community-Based Industrial Automation Software Module Store". Archived from the original on 2013-04-13. Retrieved 10 Mar 2013.
  7. Dave Greenfield (14 Feb 2013). "Consumer Technology Drives Automation". Automation World. Retrieved 10 Mar 2013.
  8. Dale Peterson (22 Feb 2013). "Digital Bond Friday News & Notes" . Retrieved 10 Mar 2013.
  9. Dave Greenfield (14 Feb 2013). "Consumer Technology Drives Automation". Automation World. Retrieved 10 Mar 2013.
  10. Gary Mintchell (18 Feb 2013). "ARC Forum 2013: First Community-Based Industrial Automation Software Module Store". Gary Mintchell Feed Forward. Archived from the original on 2013-04-13. Retrieved 10 Mar 2013.
  11. Craig Resnick (15 Feb 2013). "Inductive automation to launch first community based industrial automation software module store". ARC Advisory Group. Archived from the original on 10 April 2013. Retrieved 10 Mar 2013.
  12. Don Pearson (4 March 2013). "Module Marketplace Launch Webinar" (Podcast). Inductive Automation. Event occurs at 42:10. Archived from the original on 2 July 2013. Retrieved 10 Mar 2013.
  13. Travis Cox (4 March 2013). "Module Marketplace Launch Webinar" (Podcast). Inductive Automation. Event occurs at 43:10. Archived from the original on 3 February 2023. Retrieved 3 February 2023.
  14. "Inductive Automation Realtime Control and Monitoring" . Retrieved 5 Jan 2013.
  15. "Inductive Automation Data Acquisition" . Retrieved 5 Jan 2013.
  16. "Upgrade for existing users" . Retrieved 5 Jan 2012.
  17. "Inductive Automation Reporting Module Information". 8 Mar 2011. Retrieved 21 Jan 2013.
  18. "Ignition SMS Notification Module | SMS/Text Alarm Notifications". inductiveautomation.com. Retrieved 2018-04-03.
  19. "Vendor mobile module information". 8 Mar 2011. Retrieved 21 Jan 2013.
  20. Gary Mintchell (27 January 2011). "Mobile HMI/SCADA Module". Automation World. Retrieved 10 Mar 2013.
  21. Bond, Andrew Free OPC-UA Server Unlocks Linux's Potential, 3/2010
  22. "Free OPC-UA Server Offers More Than a Great Price". 8 Mar 2011. Archived from the original on 2013-02-16. Retrieved 5 Jan 2013.
  23. "Inductive Automation OPC-COM site". 8 Mar 2011. Retrieved 5 Jan 2013.
  24. "Vendor web site information" . Retrieved 29 Dec 2012.
  25. Jeremy Pollard (17 Jan 2007). "AUTOMATION SOFTWARE - FactoryPMI: A review of web-based SCADA/HMI". Manufacturing Automation. Archived from the original on 2013-04-25. Retrieved 29 Dec 2012.
  26. Bond, Andrew Free OPC-UA Server Unlocks Linux's Potential, 3/2010
  27. "Free OPC-UA Server Offers More Than a Great Price". 8 Mar 2011. Archived from the original on 2013-02-16. Retrieved 5 Jan 2013.
  28. "Press Release: Inductive Automation Releases FactoryPMI 3.1 and FactorySQL 4.1". 11 December 2007. Archived from the original on 16 February 2013. Retrieved 21 Jan 2013.
  29. "Press Release: Inductive Automation Releases FactoryPMI 3.1 and FactorySQL 4.1". 11 December 2007. Archived from the original on 16 February 2013. Retrieved 21 Jan 2013.
  30. "Inductive Automation FactorySQL web site". Archived from the original on 2013-01-18. Retrieved 21 Jan 2013.
  31. "Press Release: Inductive Automation Announces the Release of FactorySQL 3.0 and FactoryPMI 2.0 Paving the Way for a Redundant Web Based SCADA System". 8 March 2007. Retrieved 21 Jan 2013.
  32. "Inductive Automation FactorySQL web site". Archived from the original on 2013-01-18. Retrieved 21 Jan 2013.
  33. Jeremy Pollard (17 Jan 2007). "AUTOMATION SOFTWARE - FactoryPMI: A review of web-based SCADA/HMI". Manufacturing Automation. Archived from the original on 2013-04-25. Retrieved 29 Dec 2012.
  34. Bond, Andrew Free OPC-UA Server Unlocks Linux's Potential, 3/2010
  35. "Inductive Automation FactoryPMI web site". Archived from the original on 2012-12-26. Retrieved 21 Jan 2013.
  36. "Press Release: Inductive Automation Introduces FactoryPMI, SCADA Server with Zero Cost Deployment Clients". 12 March 2006. Retrieved 21 Jan 2013.
  37. "Inductive Automation FactoryPMI web site". Archived from the original on 2012-12-26. Retrieved 21 Jan 2013.
  38. "Ignition User Manual". Inductive Automation. Retrieved 16 Mar 2013.
  39. "Did You Know? SQLTags Historian Makes Storing and Charting Historical Data Fast, Efficient, and Easy". Inductive Automation. 9 Mar 2010. Archived from the original on 2010-03-12. Retrieved 16 Mar 2013.
  40. "Ignition User Manual". Inductive Automation. Retrieved 27 Jan 2013.
  41. "Free Tools for Developers". Inductive Automation. 10 Aug 2010. Retrieved 10 Mar 2013.
  42. "Inductive Automation's Ignition". Aug 2012. Retrieved 10 Mar 2013.
  43. "Ignition Unlimited Licensing". Inductive Automation. Retrieved 27 Jan 2013.
  44. "Ignition Pricing". Inductive Automation. Retrieved 27 Jan 2013.
  45. "Inductive Automation Benchmarks 2008" (PDF). Inductive Automation. 6 March 2008. Retrieved 27 January 2013.
  46. "Building SCADA on Linux-Ignition Delivers Performance and Reliability" (PDF). Inductive Automation. 6 May 2010. Archived from the original (PDF) on March 3, 2016. Retrieved 27 January 2013.
  47. "Security information from vendor web site" . Retrieved 21 Jan 2013.
  48. "ICSA-11-231-01—INDUCTIVE AUTOMATION IGNITION INFORMATION DISCLOSURE VULNERABILITY" (PDF). 19 Aug 2011. Archived from the original (PDF) on 5 November 2012. Retrieved 21 Jan 2013.