» What are the benefits to using automationX over conventional technology?
» How can it be secure considering the reliability of my PC?
» automationX is run on a PC server so can it be used for safety?
» Aren’t all PC Based SCADA/HMI basically the same thing?
» How do I connect the automationX server to I/O?
» What are the communication protocols and networks used to connect to I/O?
» How do I get started with automationX?
» How is automationX priced?
Q: What are the benefits to using automationX over conventional technology?
A: Like many innovations the benefits of using automationX emanate from its advanced system design concept. automationX replaces hardware components with software. The immediate physical benefits are a reduction in hardware costs, power, and space requirements.
But more important to business performance, automationX is built on a fully capable global database. There are no internal or external barriers to creating outstanding applications and to fulfilling e-business strategies. automationX elegantly performs the tasks required plus drives quality and profitability simply and effectively within the one software tool.
All critical data from the factory or plant floor is freely available in the automationX global database for things like quality analysis, SPC tools, production status and control, and factory or plant optimization. The automationX global database is freely and openly accessible for shared access to industry-specific programs outside of automationX as well.
The global data structure also spawns the advanced features of automationX such as deep levels of object orientation, smart alarm management, corporation wide production and communication tools, instant help routines for interlocks or lock-outs, and on-line expert documentation to name a few.
automationX enables our OEM’s and users to experience higher standards of factory and plant performance. Application development engineering, start-up periods and maintenance time is reduced up to 80% as well, when compared to conventional methods.
Q: Since control is server based in automationX how can it be secure considering the reliability of my PC?
A: automationX operates in the same room as legacy DCS and PLC systems every day. automationX servers are as reliable as any DCS or PLC system. Servers with properly designed and tested software, quality hardware run for years without interruption. Major corporations all over the world stake their business on the reliability of IT servers, running Linux, NT or Windows 2000. Simply check or visit our reference sites.
Q: automationX is run on a PC server so can it be used for safety?
A: A PC, PLC or DCS shouldn’t be used as the safety system! Servers, just like a PLC and DCS are processor based. The power requirements for PLC and DCS are more demanding and complex therefore at greater risk of problems. PLC and DCS programs are often corrupted by power surges, drop-outs, grounding faults, noise, or error. No safety system should rely on a processor-based device for core operation. The process and equipment system must be designed safe first, in the event of a control processor failure whether PLC, DCS or automationX is doing the job.
Q: Aren’t all PC Based SCADA/HMI basically the same thing?
A: Yes and no. Systems with their guts based on Windows and Microsoft’s foundation classes, and the Windows GUI are collectively handicapped. So these products tend to follow the same core model, lack performance and advanced features.
automationX is derived on a POSIX or Linux base, and has features that far exceed the Windows competitors – blistering control performance, responsive world class thin-client HMI, deep levels of Object Orientaiton, and sophisticated data processing, just to name a few. automationX operates through the POSIX subsystem of NT and Windows 2000, so you have the best of both worlds.
otis movie Q: How do I connect the automationX server to I/O?
A: Communication interface cards are installed on the server, and high-speed I/O buses wired to the ports. To open a communication channel to I/O, a graphical communication “class” is dropped onto a page of an automationX program. Then graphical I/O blocks (also classes) are added to the program to connect individual points, such as DO, DI, AI , AO, Counters, etc. Save & install and these points are now part of the system. It takes only minutes. i m reed fish movie
Q: What are the communication protocols and networks used to connect to I/O?
A: As with any system of unencumbered flexibility, the answer sometimes comes back as a question: Which way do you want to connect I/O?
Performance and cost usually determine the boundaries. The vast majority of automationX installations use Profibus to link to I/O cabinets located throughout a plant, factory floor or on a machine. I/O can be purchased from Siemens, Rockwell, VIPA, Opto, Wago, to name a few. DeviceNet can also be used in place of Profibus.
Modbus is often used to communicate to PLC’s or DCS systems. Modbus TCP is used for the new breed of Ethernet I/O such as offerings from Opto, VIPA, Wago and others. Other serial interfaces include Rockwell’s DF-1. Please see our interface page for an expanded list.
There are a host of popular protocols to choose from. To interface to new or special protocols a new class can be developed. Dependent on the interface requirements communications classes can be built in as little as a day or two.
Q: How do I get started with automationX?
A: Since automationX is a sophisticated program, it takes training, a suitable investment of resources and some planning to fully realize the benefit. automationX is flexible and is customized for OEM’s, or specific applications. While systems can be up and running in a short period of time, expect to get assistance from the factory for tight schedules.
The learning curve to master large DCS systems such as those from Honeywell, Foxboro and others is very steep. In contrast, while automationX combines all of the operating features of large DCS, with the processing power and price of PLC systems, traning time is drastically reduced. Allow you or your team one week of engineering training and a month or two of working with the system to become fully qualified.
Implementation begins with the delivery of licensed software, an optional kick-off meeting, and training of personnel. The next step is to design the system, plan the application and determine what classes are to be used, modified, or created. Once the the classes are in place the applicaiton is built in a short period of time. Full simulation testing, and installation phases will wrap up a successful project.
A: automationX is priced on system size. Whether you are running 50 I/O or pumping 5000 I/O in milliseconds on a dual air-cooled CPU power server, you have the same tools, features, reliability and performance.To start off a project, the application is estimated based on connected I/O and interface points via communication links. This determines the license points and price. A second or backup server may also be added. There is a license charge for client terminals that are X or web-based.
An internal program in automationX monitors global resourses and license point consumption. In the event an upgrade is required a warning is generated and a license file upgrade is purchased.
