Ignition SCADA

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Ignition is an Integrated Software Platform for SCADA systems released by Inductive Automation in January 2010. It is based on an 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 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]

Awards[edit]

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[edit]

Module Marketplace[edit]

Main article: Module Marketplace

Ignition modules can be purchased through the Module Marketplace. It is an online store that opened 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 are 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]

SQL Bridge[edit]

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.[8] 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.[9]

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

Vision[edit]

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

  • The Ignition Runtime or Client is a Java application typically launched from a web browser. It acts as the HMI interface for end users and can be used to view realtime or historical process data or control industrial applications. It can be launched one of three ways. As an Applet inside a web browser, via Java Web Start, or in Full Screen mode, where it occupies the whole screen without borders or toolbars, typical of an industrial Touchscreen application.
  • The Gateway is a web page configurable, customized version of the Apache that uses JGroups multicasting for clustering. It runs a servlet that uses a single port to mediate client requests. It supports SSL/TLS and compresses communication between gateway and clients.

Reporting[edit]

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.[11] The Reporting Module allows data aggregation and referencing between table and chart objects as displayed in the image screenshot.

Mobile[edit]

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.[12]

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

OPC-UA[edit]

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.[14] 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, ModbusTCP, 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.[15]

OPC-COM[edit]

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.[16]

Module Architecture[edit]

Inductive Automation Ignition Platform Architecture

MES Module Layer[edit]

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 / Geneaology Modules have been announced as upcoming as of January 2013.

HMI/SCADA Module Layer[edit]

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[edit]

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.[17]

History[edit]

In 2010, Inductive Automation consolidated FactorySQL and FactoryPMI with Ignition by Inductive Automation. It created a modular frameworks, 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[edit]

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.[18]

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.[19]

Scripting[edit]

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[edit]

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.

Expression Language[edit]

The Ignition Expression Language is a simple language that was invented by Inductive Automation.[20] 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[edit]

An Ignition Module SDK is available for anybody to develop their own modules.[21] 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. [22]

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[edit]

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.[23]

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.[24]

Performance[edit]

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.[25] 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.[26]

Security[edit]

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

  • SSL/TLS All network traffic is encrypted with SSL/TLS technology.
  • Active Directory Authentication Supports Microsoft Windows Active Directory authentication.
  • Auditing allows administrators to review logs of activity.

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.[28]

Open Source[edit]

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.

References[edit]

  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. 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. Retrieved 10 Mar 2013. 
  6. ^ Gary Mintchell (18 Feb 2013). "ARC Forum 2013: First Community-Based Industrial Automation Software Module Store". Retrieved 10 Mar 2013. 
  7. ^ Dave Greenfield (14 Feb 2013). "Consumer Technology Drives Automation". Automation World. Retrieved 10 Mar 2013. 
  8. ^ "Inductive Automation Realtime Control and Monitoring". Retrieved 5 Jan 2013. 
  9. ^ "Inductive Automation Data Acquisition". Retrieved 5 Jan 2013. 
  10. ^ "Upgrade for existing users". Retrieved 5 Jan 2012. 
  11. ^ "Inductive Automation Reporting Module Information". 8 Mar 2011. Retrieved 21 Jan 2013. 
  12. ^ "Vendor mobile module information". 8 Mar 2011. Retrieved 21 Jan 2013. 
  13. ^ Gary Mintchell (27 January 2011). "Mobile HMI/SCADA Module". Automation World. Retrieved 10 Mar 2013. 
  14. ^ Bond, Andrew Free OPC-UA Server Unlocks Linux's Potential, 3/2010
  15. ^ "Free OPC-UA Server Offers More Than a Great Price". 8 Mar 2011. Retrieved 5 Jan 2013. 
  16. ^ "Inductive Automation OPC-COM site". 8 Mar 2011. Retrieved 5 Jan 2013. 
  17. ^ "Vendor web site information". Retrieved 29 Dec 2012. 
  18. ^ "Ignition User Manual". Inductive Automation. Retrieved 16 Mar 2013. 
  19. ^ "Did You Know? SQLTags Historian Makes Storing and Charting Historical Data Fast, Efficient, and Easy". Inductive Automation. 9 Mar 2010. Retrieved 16 Mar 2013. 
  20. ^ "Ignition User Manual". Inductive Automation. Retrieved 27 Jan 2013. 
  21. ^ "Free Tools for Developers". Inductive Automation. 10 Aug 2010. Retrieved 10 Mar 2013. 
  22. ^ "Inductive Automation's Ignition". Aug 2012. Retrieved 10 Mar 2013. 
  23. ^ "Ignition Unlimited Licensing". Inductive Automation. Retrieved 27 Jan 2013. 
  24. ^ "Ignition Pricing". Inductive Automation. Retrieved 27 Jan 2013. 
  25. ^ "Inductive Automation Benchmarks 2008". Inductive Automation. 6 March 2008. Retrieved 27 January 2013. 
  26. ^ "Building SCADA on Linux-Ignition Delivers Performance and Reliability". Inductive Automation. 6 May 2010. Retrieved 27 January 2013. 
  27. ^ "Security information from vendor web site". Retrieved 21 Jan 2013. 
  28. ^ "ICSA-11-231-01—INDUCTIVE AUTOMATION IGNITION INFORMATION DISCLOSURE VULNERABILITY". 19 Aug 2011. Retrieved 21 Jan 2013. 

External links[edit]