Vous êtes sur la page 1sur 8

plcscadasystems.blogspot.

com
http://plcscadasystems.blogspot.com/search?updated-min=2014-01-01T00:00:00+07:00&updated-max=2015-0101T00:00:00+07:00&max-results=3

Belajar PLC dan SCADA


Technology Update: SCADA evolves toward MES
Written by Abumessi Journey on 8:42 AM

Today's SCADA systems are evolving beyond supervisory control and data acquisition with greater functionalities
and integration capabilities.

In Food Engineering's 2001 Best Manufacturing Practices Survey (Feb., '01), only five percent of respondents
reported having SCADA systems in their plants.
We thought that surprisingly low. The problem may lie in the definition.
SCADA -- the acronym and abbreviation for Supervisory Control And Data Acquisition -- has become more difficult
to define as these systems add more production-management and manufacturing-execution functions, blurring
the distinction between SCADA and MES (Manufacturing Execution Systems).
The term SCADA emerged during the 1980s from the gas, oil and utilities industries, where it refers to remote
monitoring and control of widely distributed plcs and I/O points in facilities such as oil fields, electric-power
generating stations, water and wastewater-treatment plants. Eventually the term was applied in manufacturing
plants to operator interfaces with processes directed by plcs. A typical SCADA system integrates plcs on the plant
floor with a PC and might include some sort of man/machine interface (MMI).
Today, that integration increasingly includes HMI (human/machine interface), a PC with graphic process and
machine-status displays, alarms, messages, diagnostics, data access, reporting tools and automated process
execution, allowing operator feedback. "SCADA has become almost interchangeable with HMI," observes Mark
Richman, automation engineer at systems integrator Tri-Core, Inc., Racine, Wis.
John Blanchard, principal analyst at the ARC Advisory Group (Dedham, Mass.), Sees two trends contributing to
the growing functionality and upward evolution of HMI/SCADA systems. "First, the MMI (man/machine interface)
market is flat -- anybody can do it. So the only way for the vendor to build his business is to take-on more
functionality," Blanchard points out. "Second, by doing that, they're becoming more and more the interface to
what's usually called the ERP systems. By definition, that becomes MES. So there's a business trend evolving
here that puts them in the middle."
Process control & batch execution
Major software vendors today offer turnkey HMI/SCADA systems, and systems integrators can either install
turnkey solutions or customize systems integrating components from various vendors. Tri-Core, for example, can
install complete HMI/SCADA packages from Rockwell, Intellution and Wonderware, or provide tailored solutions
not available from any single vendor.
In determining which type of system to install, "customer requirements are the first and foremost consideration,"
says Richman. "Cost is always a consideration. And where you're trying to control certain portions of a process,
the project may not be big enough to support a full-blown HMI, so you'd probably put in something like a panelview
or Quick Panel or some other type of OIT (operator interface terminal). The HMI is often used in a lab or office, but
we put them in NEMA 4X enclosures (to resist washdown) on plant floors as well. So the basic considerations on
any project are customer requirements, cost, and the complexity of the system."
One recent example of a Tri-Core HMI/SCADA project is the installation of a Rockwell rsview32 system at the
Portion Pac, Inc. Plant in Mason, Ohio. Portion Pac, a unit of H.J. Heinz Co., Manufactures flexible and rigid
single-serving packages of ketchup, salad dressings, sauces and other condiments for food-service markets. The
plant operates three batch processes -- one for ketchup, one for salad dressings, and one for specialty
condiments -- each controlled by a separate rsview program integrating four Allen-Bradley SLC 5/05s which
govern each process from batching up to the filling machines. According to Richman, system architecture consists

of a server PC and a client PC in the ketchup area with another client for the salad dressing operation, and a
second client/server system for the specialty process, all linked via Ethernet.
"The former system was just mechanical relay logic, so there was no PLC control whatsoever," says Bob
Lindhorst, plant engineer at Portion Pac. "Now there are a lot of visual aids on the screen for much better operator
interface."
rsview controls recipe execution, batching, blending, heating, cooling, pasteurization, homogenization, pumps,
valves, holding-tank levels and CIP, Lindhorst continues. Process variables such as pressure are controlled to
minimize pump wear and reduce maintenance. "We can build recipes now; we couldn't do that before," he adds.
"You just click the recipe and everything is automatic." Because the programs for all three manufacturing areas
are connected via Ethernet, any process can be monitored and controlled if necessary from any station.
Rockwell describes rsview32 as "an integrated, component-based HMI software package for monitoring and
controlling automated machines and processes." The system incorporates open technologies for connectivity with
other Rockwell products, Microsoft products and third-party applications. "I would say that SCADA is a subset of
today's standard control systems," says Darryl Walther, rsview32 product manager at Rockwell Automation
(Milwaukee, Wis.)
Standards ease integration
The latest HMI/SCADA releases from major vendors are based on Windows NT, '95 or 2000 operating systems
and embed Microsoft object technology standards (which minimize the time required to customize software to
specific applications); open client/server standards (which allow integration with devices from multiple vendors);
and web-based tools for integrating with upper-level business systems and throughout the enterprise. Major
standards include:
OLE (Object Linking & Embedding);
OPC (OLE for Process Control), a client/server standard for communicating with devices from multiple
vendors;
activex, Microsoft Component Object Model (COM) controls which allow sharing objects with larger
programs or applications (called containers);
VBA (Visual Basic for Applications), a programming language for customizing applications;
ODBC (Open Data Base Connectivity) to integrate with relational databases via SQL (Structured Query
Language);
SQL Server, Microsoft's relational database.
All of these technologies are included in Windows DNA-M (Distributed internet Applications for Manufacturing),
which links "islands of information" within a manufacturing environment and "bridges the gaps" between enterprise
applications and supply-chain partners.
Several vendors have added "thin client" technology, which allows any client computer to access a SCADA (or
other systems) residing on a central server for real-time access to HMI information throughout the enterprise. In
other words, the HMI/SCADA software need not reside in client computers for a client to access all the
functionality of the server.
Upgrades & applications
Among the HMI/SCADA systems which incorporate these technologies and more are Rockwell's rsview32,
Intellution's ifix, Wonderware's intouch , Ci Technologies' Citect, National Instrument Corporations' Lookout and
Fisher-Rosemount's deltav.
Intellution (Foxborough, Mass.) On Feb. 12 released ifix 2.5, the latest HMI/SCADA solution in its Dynamics family
of automation solutions. The upgrade operates on Windows 2000 as well as NT and incorporates i clientts thinserver technology.
Dynamics, including FIX HMI/SCADA and visualbatch packages, integrates with other systems incorporating
Microsoft DNA-M standards throughout Ocean Spray Cranberries Co. To empower operators making value-added
on-line decisions and linking plant-floor automation with an SAP ERP system. As reported in Food Engineering's
1999 "New Plant Of The Year" feature (June, '99), process control at the Hunt-Wesson Snack Pack Pudding plant

in Waterloo, Iowa, consists of Allen-Bradley plcs, Intellution FIX and visualbatch software networked via Ethernet
into a SCADA system.
deltav, the HMI/SCADA component of Fisher-Rosemount's plantweb field-based solution, offers software options
for data acquisition, calculations, sequencing, regulatory control and batch. In addition to OLE and OPC, deltav
supports Foundation fieldbus and HART communications standards. Currently, Arancia Corn products is installing
plantweb at its corn wet-milling plant in San Juan del Rio, Mexico, which produces glucose, dextrose and highfructose corn syrup. In January, the Danish seafood packer Maritex selected plantweb for automating a new fish
process at its plant in Vesteralen, Norway, north of the Arctic Circle. Fisher-Rosemount is based in Austin, TX,
Wonderware's intouch Version 7.1, the HMI/SCADA upgrade to Wonderware's factorysuite 2000 manufacturingmanagement information system, can also be accessed via thin-client technology and adds Internet integration to
the plant floor, allowing execution of existing applications or design of Internet-specific applications. Tim Sowell,
Wonderware's director of marketing for factorysuite, concurs with ARC's John Blanchard about the evolution
SCADA toward the MES level. Wonderware ( Irvine, Cal.) Perceived in the mid-'90s that people wanted more out
of SCADA than supervisory control and data acquisition, says Sowell. "They want data stored for longer periods of
time, faster rates, larger volumes, uptime and downtime reports," he continues. "People want to do benchmarking,
discrete tracking and a whole lot more with plant data. If you consider what we have to offer today, the traditional
SCADA has become a commodity."
SIDEBAR 1 :
HMI/SCADA automates coffee-bean process

Lookout, a Windows NT-based HMI/SCADA software package from National Instruments Corp. (Austin, Tex.),
Automates batch processing, recipe management, reporting and statistical process control (SPC) of coffee-bean
blends while integrating with inventory management at Silocaf of New Orleans.
Silocaf, a unit of the Italian firm Pacorini Finanziaria S.p.A., Processes more than 550 million lbs. Of green coffee
per year for major U.S. coffee marketers, accounting for about one-third of all U.S. coffee imports and a market
value of $885 million.
The core of our operation is the batching system for blend production. Because coffee is a natural product and
certain supplies are seasonal, consistency of blend flavors is difficult to maintain. We therefore offer customers the
ability to blend coffee from different origins. We can achieve the desired consistencies only through accurate and
complex mixing.
In the early '90s, when we renovated a public grain elevator at the Port of New Orleans into a coffee-processing
plant, we installed bulk-handling equipment including bucket elevators, chain-drag conveyors, bulk weighing
systems, screening machines and aspiration channels to move, weigh and remove foreign material from coffee

beans. By the end of 1996, we felt the need for a new supervisory control and data acquisition (SCADA) system
which could meet the following criteria:
Exceptional recipe management, to produce custom blends;
Batch reports to match custom billing needs;
SPC control of batch processing to a blend accuracy of 0.5 percent;
Integration with our inventory management system, enabling us juggle inventories from a dozen different
countries to meet custom batch requirements.
More general criteria included networking, computer redundancy, integration with a variety of plcs, and the ability
to modify our software configuration on-line during batch production.
Lookout met these requirements and offered additional benefits. Lookout's object architecture, for example,
allowed us to configure the software to our application in less time than we expected. National Instruments also
releases new seamless upgrades every few months, allowing continuous improvement.
Our entire plant is monitored and controlled by Lookout. Screen graphics symbolize and color-code the status of
nearly 300 devices. More than 1,500 alarms alert operators to the status of any process in real time.
Three of the Lookout stations communicate over their own subnet in an NT Server LAN, which isolates the control
system from the rest of the plant. One station acts as a server, communicating with the plcs and more than 5,300
I/O points over a local Tiway network. Operators at any client station can monitor and control the entire process.
Redundancy allows one station to stand-by and take-over communication with the plcs should a fault occur in the
primary server. When not acting as a server, the stand-by unit functions as a client.
The batching system consists of 52 automatic bulk-weighing scales, of which up to 24 can operate simultaneously.
Lookout monitors and controls this system by communicating with several Siemens plcs.
Full integration of production information with our inventory-management system was achieved through object
standards such as OPC and ODPC. As newer technologies emerge, SCADA systems continue to evolve.
Edited from a report by Massimo D'Attoma, Systems & Resources Manager, Silocaf of New Orleans, Inc.
SIDEBAR 2
SCADA boosts malt quality & throughput

A Citect SCADA system supplied by Ci Technologies (Sydney, NSW) helped boost annual malt production from
20,000 metric tons after startup in 1978 to 46,000 tons today at the five-hectare Kirin Australia plant, a malting unit
of Japan's Kirin Brewery at Welshpool, Western Australia (near Perth).
Kirin in 1995 decided to replace its existing Unix-based SCADA system with Windows-based client/server Citect
software packages to achieve more accurate monitoring and control of its malting operation. Stage 1 of the project
involved upgrading controls for the steeping and germination processes. Stage 2 continued the project by
programming existing plcs to control barley receiving, barley cleaning, dry-hopper filling, malt cleaning and malt
outloading, and replacing the existing SCADA with a Citect system consisting of two redundant workstations in the
control room plus two field workstations, one at barley receiving and another at malt outloading. Stage 3 upgraded
control of the kilning process.
According to cit, the Kirin technical staff reported "marked improvement in supervision and control of all essential
variables." Additional improvements
include remote monitoring and acknowledgement of alarms in unmanned areas; centralized production

information, allowing better access and use of the information; improved inventory control and management.
According to Graig Adams of systems integrator PCT (Perth), which executed stage 2 of the project, Citect was
installed to communicate with the existing Modicon plcs, "providing a 'window' into the plcs." Temperature and
humidity were among the variables improved to encourage barley germination. Citect improved screen graphics
and dramatically reduced screen-information update time from 29 seconds to less than two seconds, Adams
added.
The Kirin plant is currently upgrading its Citect systems from Version 4 to Version 5, released last year. Standard
features include OPC client/server architecture, ODBC (Open Database Connectivity), SPC, Circode high-level
SCADA programming language, and up to 170 device drivers for I/O communications and "capable of integrating
with plcs from just about any other vendor," says Brian Preston, marketing coordinator for Ci Technologies, Inc.
(Charlotte, N.C.). On Dec. 20, cit released Citect Version 5.30, which features activex object support, alarm
filtering to define alarms by user criteria, and remote I/O enhancements.
Sumber: Food Engineering Magazine
| Posted in buku scada, scada

How do you integrate an existing WinCC project into a STEP 7


project?
Written by Abumessi Journey on 8:30 AM

Configuration Notes:The following WinCC components must be installed to be able to import a WinCC project
into a STEP 7 project:
SIMATIC Device Drivers
Object Manager
AS-OS Engineering
These components are on the WinCC Installations CD (Fig. 01). Furthermore, WinCC and STEP 7 have to be
installed on the same computer. By importing the WinCC project into a STEP 7 project you can use the existing
compression tool (packer) for archiving the WinCC project.
Fig. 01
Instructions:You have the following options for importing a previously separate WinCC project into your STEP 7
project:
Procedure for WinCC V6.0 SP4 and higher
General procedure for all versions of WinCC
1. Procedure for WinCC V6.0 SP4 and higher
No.

Procedure

In the SIMATIC Manager you execute the menu command "Options > OS Import...".
Fig. 02

Press the button marked to open the selection window shown in Fig. 04.
Fig. 03

Select the Projectname.mcp file that you wish to import and press the "Open" button.
Fig. 04

Check the project path for the OS to be imported and press the "Import OS" button.
Fig. 05

Note:
More information on importing WinCC projects with the SIMATIC Manager is available in the WinCC Information
System > Working with WinCC > The Integration of WinCC in SIMATIC Manger > Managing WinCC Projects and
Objects with SIMATIC Manager > Importing a WinCC Project with SIMATIC Manager.
2. General procedure for all versions of WinCC
No.

Procedure

Insert an Operator Station (OS) into your STEP 7 project.


Fig. 06

Change the name of the OS to the one in your WinCC project.


Fig.07

In the Windows Explorer, delete the WinCC project created in the STEP 7 project path, which is
generated because of the newly created OS.
Sample project path:
C:\Programs\Siemens\Step7\EXAMPLES\exie\wincproj\'Name of the OS'

Now store the existing WinCC project in the STEP 7 project path using the Project Duplicator via the
menu item "Save as...". You start the Project Duplicator in the Start menu under "Start > Simatic >
WinCC > Tools".

Note:
More information on importing WinCC projects with the SIMATIC Manager is available in the WinCC Information
System > Working with WinCC > The Integration of WinCC in SIMATIC Manger > Managing WinCC Projects and
Objects with SIMATIC Manager > Importing a WinCC Project with SIMATIC Manager.
| Posted in wincc

Where are Standards Headed?


Written by Abumessi Journey on 8:29 AM

The merging of EN ISO 13849 and IEC 62061 is underway. Navigate the path to unification and find out
how it will be an opportunity for clarification, simplification and resolution of known issues.
By Derek Jones, Business Development Safety, Rockwell Automation
What do you think about machinery safety standards? Are they a help or a hindrance?
There doesnt seem to be much middle ground in answers to these questions. You either love machinery safety
standards or hate them. If you have no real opinion, its probably because you never have to use them. However, if
youre reading this, youre probably among the chosen ones who must use them, and you need to know what
standards are out there and which changes are going to appear over the horizon.
That can be easier said than done, especially if youre taking a global perspective. Trying to match different
standards to various geographies can be frustrating and time-consuming. The increasing worldwide adoption of
ISO and IEC standards certainly helps. For me, theyre the first place to look when Im trying to determine a
globally acceptable solution for safety-related aspects of machinery.
Anyone who keeps abreast of whats happening in ISO and IEC machinery safety standards will know the term
functional safety. This is safety that depends on the way a machine functions. The biggest influence on the way
a machine functions is its control system. So its no surprise that some of the most significant changes occurring

in machinery safety standards are related to the safety-related aspects of their control.
We have moved from the relatively simple approach of the Categories of EN 954 to a more complex approach
encompassing PL (Performance Level) of EN ISO 13849 and SIL (Safety Integrity Level) of IEC 62061. This hasnt
exactly been greeted with universal acclaim, but most people will accept that some sort of change was necessary.
That change isnt yet complete; work has now started on merging EN ISO 13849 and IEC 62061.
However, before we all throw our hands up in despair, let me say that its my contention that we have reached the
summit in terms of difficulty and disruption. There should be no new methodologies or formulae. What we have,
we should hold. Time and money have been spent getting us to where we are now, and this definitely isnt the time
for starting over. Its the time to grasp opportunity for improvement.
Work has started in a joint ISO-IEC working group. The target date for completion was originally set at 2016, but
that was determined to be too optimistic. 2018 might be more realistic.

How Did We Get Here?


What brought us to this point? To see where we should go in the future, we must first understand the lessons of
the past.
Ten to 20 years ago, many of us were working with the Categories from the now-defunct EN 954: Safety related
parts of control systems. The EN 954 approach required the use of basic safety principles, and either the use of
simple, strong and well-tried components or fault tolerance and fault detection where necessary to prevent failure
of the safety function.
Because the system seemed to achieve Category 3, for example, in pure structural terms posed a sometimesirresistible temptation to invoke a much simplified tick-box approach.
Over time, users achieved an understanding of the full meaning of the standard as well as a reasonable
consensus on how to interpret some of the grey areas. This was due in part to learning from experience of using
it in practice and also because of the availability of instructive information such as the excellent guide produced by
the IFA (formerly the BGIA) in Germany.

Rockwell Automation Partners Help with Machine Safety


As we approached the end of the 2000s, it became clear that the use of complex electronic and programmable
technology for safety would become inevitable. It was evident that the provisions of this standard with its relatively
simple approach couldnt be counted on to cope with the next generation of machinery safety technology.
This situation lead to the publication in 2005 of IEC 62061: Safety related electrical, electronic and programmable
electronic control systems, followed shortly by the fully revised EN ISO 13849. Both standards introduced a more
complex approach that gives them both the possibility to deal with increasing complexity of safety technology and
function.
In many cases, the safety function is no longer just a simple case of switching off the power. The advent of safetycapable logic, for example, has enabled intelligent safety functions that can react to different machine conditions
and can assist productivity rather than obstruct it. However, the greater the flexibility of function, the greater the
need for provisions against mistakes and faults.
ISO 13849 and IEC 62061 both include the necessary provisions, but at the cost of an increase in complexity
including the requirement to do some calculation of the reliability. This, in turn, means that reliability data has to be
sought for the parts of the system. The fact that this data is not always forthcoming creates some understandable
frustrations. The upside is that we now have standards that can deal with complexity and which also cover some
of the gaps in the old standard that could be an issue even for low complexity systems.

Merging Brings Opportunity


In summary, we have moved from a standard that was perceived as simple to use but was restricted in terms of
the technology it enabled, to standards that are perceived as difficult to use but have enabled the confident use of
new technology.
Merging IEC 62061 and ISO 13849 will remove the complication of having two standards. As part of the merging
process, we need to make sure we dont introduce any different or additional requirements. The merging process

is as an opportunity for clarification and simplification. Its also the chance for the resolution of some known issues
such as the provision of reliability data.
I contend that weve made an overall gain, but without doubt there have been trade-offs along the way. Its now
time for some of the trade-offs to be re-examined with a view to getting the best of both worlds.
For more information, visit the Rockwell Automation Safety Resource Center at
http://discover.rockwellautomation.com/safety and the Rockwell Automation Guardman Blog at
www.guardmanblog.com.
Rockwell Automation Safety Solutions
www.rockwellautomation.com/go/tj10safety

Related Content
One Global Safety Standard is Coming Will You Be Ready? [PDF] The EN ISO 13849 and IEC
62061 safety standards for machinery control are scheduled to merge into one global standard by 2016.
Preparing now will help them take advantage of advanced technologies and eliminate trade barriers.
http://goo.gl/VlK9F
Legal Considerations in Product Liability: When it comes to safety automation, liability includes equal
portions of due diligence and common sense. Learn about the factors that can help OEMs and
manufacturers avoid the morass of injured workers, legal liability and reputation damage. http://goo.gl/tRjnD
Safety System Validation Takes the Spotlight: OEMs are focusing more on proving that a safety circuit
or design works as needed to protect workers and meet safety standards. Learn about Kimberly Clarks
best practices for safety system validation.
Subscribe to: Posts (Atom)