Inductive Automation News

Two new components were added in FactoryPMI 3.2.0

Wed, 18 Jun 2008 00:00:00 PST

Two new components were added in FactoryPMI 3.2.0: The Sound Player component and the Scriptable Canvas component. The Sound Player component brings first-class audio support to FactoryPMI, enabling auditory alerts with no scripting required. The Scriptable Canvas component is an advanced component that allows a designer to programmatically control how the component is drawn on the screen using vector graphics. This short guide will bring existing users up to speed on the use of these two new components.

Sound Player Component
The Sound Player component is a simple invisible component that can be found on the Misc palette. During design time, the component looks like a small speaker icon on your window, but at runtime the component will not be visible. To use the sound player component, first you need a sound clip to play. The sound player component will play any *.wav file. To add your wav file to the Sound Player component, simply browse for the file by setting the component's Sound Data property. The wav file will then be embedded into the component itself, meaning that any launched clients do not need file access to the original sound file.

Once your wav file is embedded in the Sound Player component, the only thing left to do is to configure the component by telling it when to play the sound! The Sound Player component has two modes:

On Trigger Sound will be played when the component's Trigger property is true.

Manual Sound will be played when its play() function is invoked via a script.

When the sound is prompted to play, either manually or by trigger, it can play in one of three loop modes:

Play Once The sound clip will be played once when prompted.

Loop Forever The sound clip will loop forever when triggered, or until the stop() function is called via a script.

Loop N Times The sound clip will loop for N iterations when prompted, where N is the value of the component's Loop Count property.

In most cases, it will be easiest to use the component in On Trigger mode. Suppose you have a SQLTag that represents an alarm condition. Simply drag that tag onto the Sound Player's Trigger property, and then choose if you want the alert to play once or loop. That's all there is to adding audio alerts to a FactoryPMI screen!

Paintable Canvas Component
The Paintable Panvas component was introduced by popular demand from some of our more advanced users. The component is intended for use by users who are very comfortable with FactoryPMI's embedded Python scripting engine. The component allows a designer to write programmatic commands that control with exacting detail how the Paintable Canvas appears, functions, and responds to user input during runtime. In theory, any kind of desired component could be created from this component

The component works by responding to a special scripting event called the repaint event. This repaint event will be invoked every time that the component needs to paint itself onto the screen. The event object for this event contains some special properties only found on this event type: graphics, width, and height. The event.graphics object is an instance of a Java 2D graphics context, or more precisely, a java.awt.Graphics2D. (we warned you that this was for advanced users, didn't we?) This graphics object, can then be drawn on from the (0,0) coordinate to the (event.width, event.height) coordinate using any Java2D drawing mechanism. When you first drop a Paintable Canvas component onto a window, you'll notice that there is a bunch of code already in the repaint event. This is example code that should help users get a feel for how Java2D works. Happy scripting!

Inductive Automation
Inductive Automation pioneered the first full-featured web-launched HMI/SCADA system in the world. Its standards based, database-centric architecture receives accolades from plant managers, IT managers, and system integrators worldwide. With a commitment to software quality and technical support second to none, Inductive Automation is at the forefront of industrial software.

New software updates available, improved performance and new features

Wed, 18 Jun 2008 00:00:00 PST

FactoryPMI 3.2 offers dramatically improved window load times, improved clustered networking, and several very useful new components. The new sound component makes it extremely easy to embed sound files into screens, while the Paintable Canvas component offers savvy users unprecedented control in creating custom displays.

On the FactorySQL side, version 4.2 introduces a variety of robustness-enhancing features such as buffered data logging, which allows short bursts of rapid logging and prevents data loss when switching over to the data cache, a group failure handshake option, and the ability to request values only when the group is triggered. Additionally, new expression functions have been added that enable a range of database operations, making it easier than ever to accomplish complex operations quickly.

Additionally, FactorySQL is now compatible with the CSV ODBC driver that comes installed with nearly every copy of Windows. This means that FactorySQL can now log historical data directly to CSV. For more information, please see the HOWTO article in our Support Forum.

Inductive Automation
Inductive Automation pioneered the first full-featured web-launched HMI/SCADA system in the world. Its standards based, database-centric architecture receives accolades from plant managers, IT managers, and system integrators worldwide. With a commitment to software quality and technical support second to none, Inductive Automation is at the forefront of industrial software.

Integrator Highlight: Bow Networks

Wed, 18 Jun 2008 00:00:00 PST

This month we interviewed Deryk Yuill, Vice President Business Development, from Bow Networks, a leader in communications and automation solutions for the electric utility industry, about his experience with Inductive Automation software.

IA: Tell us a bit about your company - do you have a focus on any particular industry?

Deryk: Bow Networks is a leader in communications and automation solutions for the electric utility industry. We deliver solutions based on our own products and technologies, supplemented with select 3rd party products.

IA: Why did you choose Inductive Automation software?

Deryk: Factory PMI was appealing for several reasons. The SQL interface allowed it to work directly with our (linux based) eLAN front-end processor, which handles the data collection tasks. The web interface allows for the system to be easily used by both the primary users, and numerous occasional casual users, without needing to distribute and maintain client applications.

IA: What system features do your customers need that you can provide using Inductive Automation products?

Deryk: The delivered system is essentially a small SCADA system, for a municipal electric distribution utility. They don't have a real control center, so their operators access the system from their trucks, over CDMA modems. The FEP sends out emails to their blackberries when alarm conditions arise, signaling the operator to log into the FactoryPMI system.

IA: What have you and your customers found to be the main benefits of the software?

Deryk: The ease of integration with our existing SQL database, and the thin client.

IA: How do you plan on using IA software in the future?

Deryk: We expect to deliver more projects similar to this one, where the system provides a small distribution automation master station. In addition, we want to pursue running the FactoryPMI Gateway on our Linux based eLAN Substation Communications Server, to deliver a substation level HMI.

IA: Is there anything else you can say regarding your experience with Inductive Automation?

Deryk: Positive experience so far, particularly with the technical support team.

Inductive Automation Installation Checklist

Thu, 15 May 2008 00:00:00 PST

The installation and maintenance of FactorySQL/FactoryPMI based systems involves a wide range of technologies. Each normal installation consists of at least 4 components: FactorySQL, FactoryPMI, an OPC server and a database. Given that each component has its own set of requirements and caveats, it is important to have an organized game plan when implementing and installing a project.

For that reason, Inductive Automation has put together an installation checklist that will help you with both the installation and the startup of a project.

Click here to download the checklist

Inductive Automation
Inductive Automation pioneered the first full-featured web-launched HMI/SCADA system in the world. Its standards based, database-centric architecture receives accolades from plant managers, IT managers, and system integrators worldwide. With a commitment to software quality and technical support second to none, Inductive Automation is at the forefront of industrial software.

Inductive Automation Adds 8 New Online Videos

Thu, 15 May 2008 00:00:00 PST

Inductive Automation is pleased to announce the addition of 8 new videos to their online video library:

FactorySQL Triggers - Learn how to use triggers
FactorySQL Action Items - Learn how to use action items in FactorySQL groups
FactoryPMI Colors - Learn all about colors in FactoryPMI
FactoryPMI Properties, Binding & Expressions 5 Part Series - Learn all about FactoryPMI component properties and binding

Access to the library is free and available at http://www.inductiveautomation.com/support/videos/.

Inductive Automation
Inductive Automation pioneered the first full-featured web-launched HMI/SCADA system in the world. Its standards based, database-centric architecture receives accolades from plant managers, IT managers, and system integrators worldwide. With a commitment to software quality and technical support second to none, Inductive Automation is at the forefront of industrial software.

Integrator Highlight: PACsys, LLC

Thu, 15 May 2008 00:00:00 PST

This month we interviewed Brian Romano of PACsys, LLC about his experience with Inductive Automation software.

IA: Tell us a bit about your company - do you have a focus on any particular industry?

Brian: PACsys is a 10 year old company made up of engineers and technicians with diverse backgrounds coupled with pointed knowledge in industrial processes and automation. PACsys, an acronym for Process and Automation Control Systems, strives to provide the customer with what they want and need, nothing more nothing less. PACsys customers comprise a broad spectrum of industries.

IA: Why did you choose Inductive Automation software?

Brian: We were actually following a very, very similar path to Inductive Automation, but writing an all encompassing, configurable was not really in our business model, but the end result of the software was absolutely necessary. There were packages of software and/or software components that could do what we needed for our customer base, but at a much greater cost and very time consuming deployment. As soon as we were introduced to the packages produced by Inductive Automation, we immediately abandoned our internal efforts of development of our own package and began purchasing, learning and implementing a package that was so much more feature filled and configurable than ours might have been and for that matter, anyone else?s with similar functionality.

IA: What system features do your customers need that you can provide using FactorySQL and FactoryPMI?

Brian: FactorySQL - Acquisition of data from various sources anywhere in the plant that sits on the plant network with placement of the data into an industry standard, stable database.

FactoryPMI - the ability to view production data, downtime and efficiencies by anyone authorized with a simple web browser. No extra client software! With a thought out network WAN and LAN structure, multi-plant data is available to people from anywhere in the world via the Internet.

IA: What have you and your customers found to be the main benefits of the software?

Brian:

Relative fast implementation and deployment.
Configurable
Low up front software costs as well as quick, lower cost development

IA: How do you plan on using IA software in the future?

Brian: We will continue to use it as we have in the past and use it directly for our end customers. We also will be utilizing both packages of software in an OEM product that we are producing.

IA: Is there anything else you can say regarding your experience with Inductive Automation?

Brian: We have had nothing but extremely supportive and helpful people willing to listen to our wants and needs, with a strong emphasis in product demonstration and training. It starts at the top and that helpful spirit emanates to all levels of employees in the company. We have been involved with many hardware and software manufacturers and can honestly admit that Inductive Automation is very unique in their outstanding, outgoing customer support.

Success Story: Bronco Wine Company

Thu, 10 Apr 2008 00:00:00 PST

Bronco Wine Company, Ceres, CA (the producer of "Two-buck Chuck") uses FactoryPMI for enterprise-wide process monitoring, control, and troubleshooting. It was a business decision to use this technology, and is paying off handsomely for the Franzia family-owned business.

Click here to read the entire success story

Inductive Automation Introduces Online Video Library

Thu, 10 Apr 2008 00:00:00 PST

Inductive Automation is pleased to announce the introduction of a new online video library, available starting April 10, 2008. The library features sets of training videos geared to a specific part of Inductive Automation's software. Access to the library is free and available at http://www.inductiveautomation.com/support/videos/.

Inductive Automation
Inductive Automation pioneered the first full-featured web-launched HMI/SCADA system in the world. Its standards based, database-centric architecture receives accolades from plant managers, IT managers, and system integrators worldwide. With a commitment to software quality and technical support second to none, Inductive Automation is at the forefront of industrial software.

Inductive Automation attends 2008 North American Interop Conference; Receives 'Self-Tested' certification.

Thu, 10 Apr 2008 00:00:00 PST

Inductive Automation is pleased to announce that for the third year in a row FactorySQL was successfully tested at the OPC Foundation's North American Interoperability Conference. FactorySQL was successfully tested with a large range of industry leading OPC servers, and once again received the OPC Foundation's "Self-Tested" certification.

This year's server field included over 40 products from MatrikonOPC, Kepware, Cogent Realtime Systems, Siemens, Software Toolbox, Wonderware and more. Each server was tested for compatibility with the OPC specification, and operation with FactorySQL. Additionally, FactorySQL once again passed the OPC "Self-Tested" certification test, which is conducted by OPC officials and tests for compliance with the specification and best-practice guidelines.

FactorySQL is a full featured, bi-directional OPC to SQL databridge, providing historical logging, realtime status and control, and more. The OPC foundation is a collective of over 300 top-name companies dedicated to ensuring interoperability in automation by creating and maintaining open specifications for communication. Since the first specification was published in 1996, OPC has become the de-facto standard in the field. Through OPC, FactorySQL is able to effortlessly link nearly all industrial devices with any standard database system.

Inductive Automation
Inductive Automation pioneered the first full-featured web-launched HMI/SCADA system in the world. Its standards based, database-centric architecture receives accolades from plant managers, IT managers, and system integrators worldwide. With a commitment to software quality and technical support second to none, Inductive Automation is at the forefront of industrial software.

FactoryPMI and FactorySQL Benchmark Whitepaper

Thu, 06 Mar 2008 00:00:00 PST

Ever wondered how many clients you could really run with FactoryPMI's unlimited client licensing? How about the maximum tag throughput of SQLTags on a MySQL database? Inductive Automation has published a whitepaper detailing the results of rigorous performance tests on its products, FactoryPMI^TM and FactorySQL^TM. These benchmarks will answer these questions and more.

You can download the benchmarks here http://www.inductiveautomation.com/products/whitepapers/IABenchmarkWhitepaper2008.pdf.

For those of you who do not have the time to wade through 14 pages of technical benchmark methodology and results, here is the executive summary. The benchmarks are divided up into two major tests. The first test monitored the FactoryPMI Gateway under high concurrent load count to determine how many clients FactoryPMI can support at a time. The test was run on large and small servers, and with large and small projects. With a small server, you can expect to run between 70-100 clients at a time, depending on the size of your project. With a large server, those clients counts go up to 150+. Within these ranges, you can expect tags to update at their proper rates, and expect sub-second write-to-readback round-trip times. Note that these projects were using pure-SQLTags for data display.

The second test involved the SQLTags throughput between FactorySQL and various databases. We found that MySQL with the MyISAM data engine and Microsoft SQL Server gave the best performance. We frequently hear the question: "How many tags can I have". It turns out, the real question should be: "How many tags can I have changing per second". This is because a tag's presence in the system doesn't dramatically affect performance unless it is changing. So, systems with upwards of 250,000 tags are feasible, as long as only a small percentage of them are actively changing every second. This benchmark found that the tag throughput for a low-end server or high-end desktop computer, ranges between 2,500, and 13,000 tag changes per second. The factors that contribute to this are wide spread are explained in detail in the whitepaper.

MatrikonOPC Tunneller Now Bundled with FactorySQL

Thu, 06 Mar 2008 00:00:00 PST

Inductive Automation is pleased to announce that MatrikonOPC's popular OPC Tunneller is now included as an optional installation in their unified installer system. The OPC Tunneller is the perfect companion to FactorySQL, and allows users to easily overcome DCOM headaches to create efficient, seamlessly networked OPC solutions.

Security and configuration problems associated with DCOM have long made even the simplest remote OPC configurations a hassle. MatrikonOPC Tunneller provides the perfect answer, translating local COM based OPC calls into standard network traffic. Furthermore, it provides a range of additional features such data encryption, compression, and aggregation making it the perfect choice for someone looking to collect data from one or more remote sources. Configuration is minimal, allowing users to get up and running extremely quickly.

FactorySQL is an industry leading OPC to SQL databridge. It provides bi-directional synchronization, historical logging, e-mail alert notifications, and much more. When paired with the MatrikonOPC Tunneler, within minutes users could have data being retrieved from any number of remote sources and available in their corporate database. There truly isn't a more cost effective, powerful way to retrieve and monitor remote data.

For more information on FactorySQL or the MatrikonOPC Tunneller, contact Inductive Automation at (800) 266-7798.

End-User Highlight: Metaldyne

Thu, 06 Mar 2008 00:00:00 PST

This month we interviewed Michael Young, the Lead Process Engineering Technician for Metaldyne, a leading global designer and supplier of powertrain and chassis products for the automotive industry.

IA: What do you use Inductive Automation software for in your company or facility?

Michael: We are monitoring our process for machine status, alarm history, downtime and OEE calculations. We can now view this anytime and in real time from unlimited clients through intranet or VPN.

IA: Why did you choose Inductive Automation software?

Michael: It is the most versatile I have seen yet, and if you are imaginative, the Inductive Automation technical support staff can help you figure out how to turn those dreams into reality.

IA: What features have you found most useful to your specific process?

Michael: I have found out, while learning to use them, that all of the tools such as SQL syntax, scripting, Jython and expression language give you tremendous options and flexibility.

IA: How has the introduction of SQL affected your development and implementation?

Michael: I am still learning it, but without it some things just are not possible without a lot of extra work.

IA: What have you found to be the main benefits of the software?

Michael: The flexibility of it and after getting better at it, the freedom of it.

IA: How do you plan on using IA software in the future?

Michael: All that I can, because there is no limit to the type of information that I can save and store in the database. This makes it a great tool for all of us involved in the project.

IA: Is there anything else you can say regarding your experience with Inductive Automation?

Michael: They are in California, but we won?t hold it against them.

Screenshots:

Integrator Highlight: eGenietech Software Services

Thu, 14 Feb 2008 00:00:00 PST

This month we interviewed Vipul Shah, MES Division Head, of eGenietech Software Services about his experience with Inductive Automation software.

IA: Tell us a bit about your company - do you have a focus on any particular industry?

Vipul: eGenietech is a software solutions provider in the area of IT for manufacturing. Since we have a good domain experience in the Process Automation Domain, our focus area has been providing solutions in the area of MES and Plant to Enterprise Integration.

IA: Why did you choose Inductive Automation software?

Vipul: For quite a long time we have been using custom software development for providing solutions to our client. But as the scope and complexity of the projects started increasing we started thinking of a product based approach to reduce the implementation time and maintenance cost. We evaluated a number of products for process data logging and finally chose FactorySQL because of its flexibility, configuration capabilities and its cost advantage due to support for unlimited tags. Another factor was we got very fast response during product evaluation which increased our confidence in Inductive Automation.

IA: What system features do your customers need that you can provide using FactorySQL and FactoryPMI?

Vipul: Most of the customers and our projects demand flexibility in configuration, openness to third party integration and extensibility. I feel both FactorySQL and FactoryPMI meet these requirements.

IA: What have you and your customers found to be the main benefits of the software?

Vipul: Our project involved providing a solution for metals industry, where we needed to seamlessly integrate an Oracle Based Production Management and Scheduling System and RSView Scada and provide a bidirectional transfer of process data among these two systems. Additionally the customer needed extensive data reporting and analysis.

The most important benefit we found was that we could deploy the project in a relatively short time with all the IT friendly features of FactorySQL and also could easily incorporate new requirements given by the customer during actual implementation at the customer site.

IA: How do you plan on using IA software in the future?

Vipul: Though we were initially a bit wary of using third party products in our projects, and of a vendor who is separated from us by a 12 hour time zone, based on our initial success of using IA products we have decided to aggressively propose solutions to our clients around their products.

IA: Is there anything else you can say regarding your experience with Inductive Automation?

Vipul: The best experience was the fast turn around time both from the sales and support side. The most important thing was we didn't actually require much support during actual implementation and that is very credible. Other good thing is the continuous information on new ways to exploit the products that we get through the newsletters. In view of all this we foresee a long term relationship with IA and wish them luck to create new innovations in their products.

How To: Install and Use Click to Graph

Thu, 14 Feb 2008 00:00:00 PST

This article demonstrates how to install and use Click to Graph, a powerful way to add and remove pens from FactoryPMI's Easy Chart Component in runtime. Click to Graph allows you to add a right click menu to components, such as led displays, labels, numeric labels, etc, to add or remove that item from an Easy Chart graph dynamically. You can even save graphs and come back to them at later times. This way you choose what you want to see in a graph. Please read the instructions carefully and perform them in order.

Installing Click to Graph

Step 1: Download Click to Graph File

1) Click on the following link to download the zip file:

Click to Graph Goodie

2) Extract the contents of the ctg.zip to a folder. This file contains 5 files:

ctg.sql - a MySQL backup file containing all the necessary tables
ctg.py - a python script that contains all the necessary functions
ctg.fpal - a custom palette that contains a few sample components
ctg.fwin - a file that contains all the necessary FactoryPMI windows
ctg_shutdown_script.txt - a file that contains the shutdown script needed

Step 2: Import MySQL Dump File

1) Open up Command Prompt by going to Start->Program Files->Accessories->Command Prompt

2) Change directory to MySQL bin by entering in (afterwards press enter):

cd "C:\Program Files\MySQL\MySQL Server 5.0\bin"

3) Now import ctg.sql by entering in (afterwards press enter):

mysql -u root -p YourDBName < "C:\Location to\ctg.sql"

4) Enter in your MySQL root password (afterwards press enter)

5) Done. The Click to Graph tables are now successfully imported.

Step 3: Import FactoryPMI Script Module

1) Open up the FactoryPMI Gateway Configuration page from: Start->Program Files->Inductive Automation->FactoryPMI->Configuration Page

2) Open up the FactoryPMI Designer by clicking on the Launch Designer link. Login with your username and password (default is admin and password). Select the project you want to use Click to Graph in.

3) Once open, go to Project->Script Modules from the menu bar.

4) Click on the Import a package or script button.

5) Select the ctg.py file.

6) Name the module ctg.

7) Done, you now have some global functions that we are going to use later. Press Ok to close.

Step 4: Import FactoryPMI Palette

1) With the designer still open, right click on the Component Palette and select Import Palette(s).

2) Select the ctg.fpal file.

7) Done, you now have some pre-configured components for Click to Graph that we can use.

Step 5: Import FactoryPMI Windows

1) With the designer still open, right click inside the Project Browser and select Import Window(s).

2) Select the ctg.fwin file.

7) Done, you now have some pre-configured windows for Click to Graph that we can use.

8) Lastly, you need to add the global shutdown script. Go to Project->Global Event Scripts. Next select the Shutdown tab and enter in the contents of the ctg_shutdown_script.txt. The script clears out the current graph when the user logs out or closes the client.

All done! Now let's go over how Click to Graph works.

How Click to Graph Works

The first part to understand is that Click to Graph stores pen configurations in the database. During the runtime each user picks and chooses from these pens. Picking and choosing these pens manipulates the ctg_active_client table. This table then drives the Easy Chart's pens/axes datasets dynamically. The ctg_active_client table is based on a unique Client ID created by FactoryPMI when you login to a client. This ID uniquely identifies one client from another. This way each client can have its own set of pens the user can configure. If that ID is somehow lost (possible via redirection), the user must log in again to access the graph.

Let's take a look at the databases tables needed for Click to Graph to work (there are 4 of them):

ctg_pens - table stores all possible pens for the graph.
ctg_axes - table stores all the available axes for the pens.
ctg_saved_pens - table stores the saved graphs.
ctg_active_client - table stores all the pens the clients have selected.

The ctg_pens table can be manipulated using the CTG_Pen_Edit window that we imported into our FactoryPMI project earlier. Here you can add/edit/remove pens. These pens correspond to tag or item that FactorySQL (or another historian) is already trending. Attached to a pen is a Point ID, which uniquely identifies one pen from another. Every FactoryPMI component that we want to use as a Click to Graph item must also contain the Point ID, so that it knows how to add or remove that specific pen. Let's go over a small example to get started.

Next, the actual Easy Chart, located on the CTG_Graph window, has two expert properties called pens and axes which are both bound to a SQL query. The pens dataset is bound to a join of the ctg_active_client table and the ctg_pens table. The axes dataset is bound to the ctg_axes table.

Let's go over a small example to understand how everything relates.

Example 1: Using a Click to Graph Component

1) Open up the FactoryPMI Designer.

2) Open up or create a window.

3) From the Component Palette under CTG Palette, drag and drop the Multi-State Indicator pre-configured component into the window.

4) You will notice there is a Dynamic Property called PointID attached to the component with a value of HOA. This Point ID must match the Point ID of a pen in the ctg_pens table.

5) Now, let's take a look at the Mouse Pressed and Released actions on this component. This is where the right click menu is called. So, right click on the component and select Configure Actions...

6) You will notice the script is the same for the mousePressed and mouseReleased. They both call a global script function that we imported earlier into the Script Modules. We pass the event object into the showPopup function and it knows how to retrieve the Point ID from the component. The function also takes care of creating the popup menu.

7) Now, cancel out of the action configuration and go into Preview mode in the designer by selecting Project->Preview mode from the menu. Now we can interact with the components. Right click on the indicator and you will get the following menu:

8) That's it! You can click (+) Add to Graph to add that pen to the current working graph. If the pen does not exist in the ctg_pens table the script will create one automatically with the default settings. After that, you can remove the pen and event clear out the current graph.

9) To see the current graph open up the CTG_Graph window.

How to add Click to Graph to already existing components

So, if you would like to add Click to Graph to already existing components do the following:

1) Right click on the component and select Component Customizers->Dynamic Properties and add a new property named PointID of type String.

2) Lastly, add the following script in the mousePressed and mouseReleased actions by right clicking on the component and selecting Configure Actions..:

if event.button != event.BUTTON1:
app.ctg.showPopup(event)

Have fun with this goodie and as always if you have any questions please call us at 800.266.7798.

FactoryPMI Adds Linux Support

Thu, 14 Feb 2008 00:00:00 PST

Inductive Automation is proud to announce that as of version 3.1.5, FactoryPMI^TM supports running on Linux/Unix operating systems. This groundbreaking change will be welcomed by many of our customers, especially international customers, who are running Linux on the plant floor. In an industry so dominated by Microsoft-dependent technologies, Inductive Automation's move towards platform-independence is a breath of fresh air.

FactoryPMI is an innovative, full-featured industrial data visualization and control product. It can be coupled with FactorySQL or other database-aware industrial tools to create robust SCADA systems. Additionally, its flat-fee server based licensing model, including unlimited tags, screens, and runtime clients, makes it the most cost-effective solution on the market.

FactoryPMI is written in Java, which is renowned for its ability to run on multiple platforms. While our FactoryPMI HMI/SCADA clients have always supported running on multiple platforms, including Linux and MacOSX, the ability to run the FactoryPMI Gateway on Linux is new. Those who know our software architecture will ask, "What about FactorySQL?" As you might have suspected, FactorySQL is tied to Microsoft Windows because of the OPC standard's reliance on DCOM, a Windows technology. However, many of our customers are using FactoryPMI by itself and have their own data-bridge that brings in their industrial data to their database. For now, these customers are the main benefactors of FactoryPMI's platform independence. In the future, Inductive Automation is committed to providing more platform independent solutions.

To download FactoryPMI for Linux, visit our downloads page at http://www.inductiveautomation.com/downloads. There you'll find the tarball for Linux. Inside is a README document that describes how to get the FactoryPMI Gateway up and running.