Distributed Control Systems Vendors Respond to PAC Questions: Page 6 of 6

Error message

  • Notice: Undefined index: browser in om_preprocess_html() (line 213 of /var/www/sites/automationworld.com/sites/all/themes/om/core/template.php).
  • Notice: Undefined index: browser in om_preprocess_html() (line 214 of /var/www/sites/automationworld.com/sites/all/themes/om/core/template.php).
  • Notice: Undefined index: version in om_preprocess_html() (line 214 of /var/www/sites/automationworld.com/sites/all/themes/om/core/template.php).
Feature Article
|

Distributed Control Systems Vendors Respond to PAC Questions

Print
FILED IN:  Control
HMI, and in to information infrastructures. A main difference then lies in how those components are put together and what are the configuration and engineering tools and level of sophistication.  

Generally, a PLC/PAC requires configuration/engineering of both a controller database and an HMI database. In a DCS, this is a global database with diagnostic displays automatically created by the system. But to me the term DCS, Hybrid, PAC, PLC, doesn't mean that much - it's what functionality does the user want and what hardware and software tools does it take to get there.  

What is happening is that functionality that systems are performing with I/O, controllers, and HMI are converging, albeit still with some architectural differences, and ways the software works.
 

3) Have you enhanced your product line or added new controller products to more effectively go after the “hybrid” marketplace for integrated control? If so, please describe.  

Jensen: Yokogawa introduced its more compact controller and I/O for its CENTUM CS 3000 DCS system in 2001 and has added different varieties of I/O ever since.  

Most of these modules were analog and digital cards with different isolation characteristics and different densities. Also, a set of communication I/O modules to talk the variety of Fieldnetworks, Foundation Fieldbus, Profibus, and now even Ethernet/IP. One such recent I/O, to be released in Feb is a specific turbine control I/O module - servo module (LVDT or 1 to 5 V DC standardized signal for position feedback signal and 24V DC ON/OFF signals for quick close and outputs up to +- 50mA signal for servo control ).  

And through that period enhanced HMI and integration capability through NT, Windows 2000, XP, 2003 Server, and now Vista. In 2005, Yokogawa introduced a GB network and other augmentations include OPC client capability for subsystems and to migrate other vendor systems. In addition, a compact controller that could handle 14 additional I/O nodes for higher capacity was introduced.  

4) How would you characterize your product line’s ability to handle logic or discrete control, together with process control, on a single platform? What about motion control? Other control domains?  

Jensen: Yokogawa supplies a full range of products for varying markets and features needed for various industries: CENTUM CS 3000 - Distributed Control System; ProSafe-RS - Safety Instrumented System - using 1131-3 configuration tool set; Stardom - SCADA RTU, 1 small scale controller brick and one flexible I/O controller that can be described like a PAC; FA-M3 - a PLC for factory automation - more popular in Japan than in the U.S., which includes motion control I/O; DAQstation and MW100 - recorders and data acquisition stations.
 

Thus, Yokogawa has a line of process automation systems encompassing the full gamut of applications and user wants within different divisions of the company.
 

So the features of each system has strengths in different process industries and in different applications. So internally, we have some of the same issues as to tailor the correct product within our own portfolio to the application and industry.  

But speaking to where your questions are directed, I am assuming the DCS, so the ability to handle logic, discrete control and process control on a single platform is inherent in most DCS designs, where most DCS/hybrid suppliers have expanded the architectures to handle the multi Field networks and designed to handle integration to both subsystem and supervisory systems. PACs are also going this direction  

5) Where do you see the controls market headed in the future vis-à-vis these kinds of multi-domain controls applications?  

Jensen: DCS, Hybrid, PAC, PLC and even SCADA creates more of an emotional response in the industry where users tend to equate the terms with architectures and software that they are aware of from legacy systems that they've worked which had those names.  

Really, this is about how architectures are put together and the how software tools sets are made to create the applications more intuitive and with lesser efforts.  

Also, future network architecture and Ethernet protocols will have better security built-in instead of add-on to make configuration of architectures easier both for internal and external access.

To see the main story this sidebar was taken from - "PACs Gain Momentum" - please visit www.automationworld.com/view-3895.

Pages

FILED IN: Control

Comments(0)

Add new comment

By submitting this form, you accept the Mollom privacy policy.

Follow Us

 

 

  NEWSLETTERS

Don’t miss intelligence crucial to your job and business!
Click on any newsletter to view a sample. Enter your email address below to sign up!

News Insights

News & Analysis

Product Insights

Latest Automation Products

TalkPoints

Automation Columnists

Feed Forward

Latest from Gary Mintchell

Automation Focus

Sponsored white papers, videos and products

Process Automation

Industry Trends & Applications

Motion Control

Machine & Motion Control

Automation Skills

Improve Industry Skills

Industrial
Ethernet Review

Network Application of IE

Packaging
Automation Review

Trends in Packaging Automation

Safety
Automation Insights

The How & Why of Safety

Each newsletter ranges in frequency from once per month to a few times per month at most.
Feedback Form