4. SCADA정의
Internet
Web Server
Database
(ERP, MES etc) Client
Client
3rd Party
Computing
System
Citect I/O Server
OPC Server
Alarm Server
Trend Server
Report Server Controller or Device Network
Schneider
Enterprise OPC Server
Network Process Level
5. 응용 분야
• Aerospace & Defence
• Automotive
• Building Automation
• Cement & Glass
• Chemical
• Electronics
• Food & Beverage
• Machinery & Manufacturing
• Metals & Mining
• Oil & Gas
• Pharmaceuticals
• Power, Utilities & Generation
• Pulp & Paper
• Transportation
• Water & Wastewater
Schneider Electric - EMS - JJPark – 2012.03 5
6. You need to ...
Achieve more while
using less
You Vijeo Citect
Schneider Electric - EMS - JJPark – 2012.03 6
8. 프로세스 제어 솔루션
● 분산 자동화 솔루션으로서의 통합 툴
● 프로세스 지향의 디자인과 환경설정
● 검증된 프로세스 제어와 유용한
개체라이브러리로 개발 기간 단축 -
시스템 확장 또는 신규 프로젝트 시 각
개체 재사용
● 프로그래밍 소프트웨어와의 통합
● 확장성 및 유연성
● 뛰어난 다중서버 간 데이터 갱신 성능
● 이중화 기능 기반의 신뢰성
● 알람과 트렌드 화면의 결합으로
프로세스 분석 기능 향상
Schneider Electric - EMS - JJPark – 2012.03 8
9. 주요 특징
고객의 추구 사항
개발비용과 신규사업에 안전한 자동화
의사결정 개선 자산 관리 최적화
리스크의 최소화 대한 요구 충족 시스템 구축
엔지니어링
명료성 효율적 운용 유연성 지속 성장
생산성
시스템 측면
Schneider Electric - EMS - JJPark – 2012.03 9
10. 엔지니어링
개발 비용, 시간, 리스크의 최소화 생산성
Schneider Electric - EMS - JJPark – 2012.03 10
11. 엔지니어링
비용 효율적인 프로젝트 유지관리 생산성
● 70개 이상의 준비된 템플릿
● 800개 이상의 심볼
● 개체 기반 구성: 지니, 수퍼지니
● HMI 임포팅
Schneider Electric - EMS - JJPark – 2012.03 11
12. 명료성
연결 개방성
MS SQL Server,
Oracle Server 등
기본 제공
데이터베이스와의
내장 드라이버를
연동 및 DDE / ActiveX
통한 실시간
Interface 제공
데이터 취득 CSV, Text, Rtl, html
API File Handling
(Application
Program
Interface) OPC
Server
Schneider Electric - EMS - JJPark – 2012.03 12
13. 명료성
의사결정 개선
● 운용자와 생산 관리자의 운용 의사결정 개선
● 장애 분석
● 데이터 비교: 시간대 별, 실시간 및 이력 데이터 조회
● 일련의 이벤트
● 수 개의 알람과 차트 조회로 상호 관계를 분석
● 통계적 프로세스 제어: 품질 개선 기여
● 다양한 수행 조건 설정
● 다양한 형태의 출력
- 프린터,파일, 이메일,웹
Schneider Electric - EMS - JJPark – 2012.03 13
14. 자산관리 최적화 효율적 운용
● 타 비즈니스 시스템과의 데이터
통합 Batch Control
Advanced Control Production
Quality
Scheduling
● 접근 개방성 Leak Detection
Other …..
Downtime
Maintenance
Other …..
CTAPI
OPC Server ODBC
OLE-DB OLE-DB
XML Web Service SQL Native Client
DDE XML Web Service
MS SQL Server
Oracle
IO Devices
Microsoft Excel
Web Browser
VijeoCitect Vijeo Reports
MS SQL Server
Tag Values
Historian
Alarm States
Tag History Tag Values
Alarm History Tag History
Control Functionality Alarm History
Process Network Corporate Network
Schneider Electric - EMS - JJPark – 2012.03 14
15. 퍼포먼스 향상 효율적 운용
Communication
(What we need to know)
Displays
(100 ms)
Request
Optimisation
Polled
Exception Reporting
Dial Up
Scheduled Server Cache (ms) Displays
Driver (1 second)
Data
Request
Optimisation
Polled
Controllers
Via Exception Reporting
170 protocols Dial Up Alarms
Scheduled Server Cache (ms) (2 seconds)
Driver
Data
Request
Optimisation
Polled
Exception Reporting Trends
Dial Up (5 seconds)
Server Cache (ms)
Scheduled Driver
Data
•
•
Schneider Electric - EMS - JJPark – 2012.03 15
16. 신뢰성 높은 아키텍쳐 효율적 운용
Display Display
Client Client
IO Server IO Server
(4 Paths) (4 Paths)
File Server File Server
(Primary) (Standby)
Alarm Server
Alarm Server Trend Server
Trend Server Reports Server
Reports Server Web Server
Web Server (Standby)
(Primary)
Controller Controller
(Primary/Stanby) (Primary/Stanby)
Schneider Electric - EMS - JJPark – 2012.03 16
17. 신뢰성 높은 아키텍쳐 효율적 운용
on change
polling
Schneider Electric - SCADA Activity 17
18. 신뢰성 높은 아키텍쳐 효율적 운용
transparent
client
switchover
failure of server
or network connection
Schneider Electric - SCADA Activity 18
19. 신뢰성 높은 아키텍쳐 효율적 운용
on change
polling
Schneider Electric - SCADA Activity 19
20. 신뢰성 높은 아키텍쳐 효율적 운용
Schneider Electric - SCADA Activity 20
21. 신뢰성 높은 아키텍쳐 효율적 운용
Schneider Electric - SCADA Activity 21
22. 신뢰성 높은 아키텍쳐 효율적 운용
transparent
client
switchover
Schneider Electric - SCADA Activity 22
23. 시스템 확장성 효율적 운용
: Access Size
Management Access
Advanced Systems
Large SystemSystem
MediumAnywhere,
Client/Server Servers
RedundantControl Anytime
Stand-alone Control System Web Clients
(Display or Manager)
Machine OEM Local Display Clients
(incl XP Embedded) Control Room
Web Server
Vijeo Citect
Redundant System
Batch Control or Redundant
Scheduler Vijeo Citect
Redundant
Systems
Alarm, Trend,
Report and IO Servers
Schneider Electric - EMS - JJPark – 2012.03 23
#18:Lets now take a closer look at what is offered by the redundancy components of Vijeo Citect.First we will have a look at the I/O server process data redundancy.So, here we have a SCADA system with display clients; a pair of I/O servers; and the field I/O devices.[]The clients will subscribe to the data points that they need to display.The I/O server process, will poll for the required data from the I/O devices.When the data changes are received in the I/O server process, the data point updates will be published to the clients.[^]Now we will take a look at what happens to the processing, if the primary process fails.
#19:So, here we have the primary server in the failed condition.The clients will have detected the failure and transparently switched over to the next available I/O server process.The I/O device polling, is now handled by the standby I/O server process, and the published data is forwarded to the clients.[] The failure could also have occurred with regards to the network connection of the primary I/O server process.The result is the same;The I/O process is marked as failed for an I/O device in Vijeo Citect; if it is unable to process, or maintain successful communications with the I/O device.
#20:On successfully restoring the primary IO server process, the communication path will switch back to the primary.The I/O communication redundancy, is designed to switch back, based on the redundancy priority of the server processes; with the default being, the primary, I/O server process.
#21:Lets have a look now at what is available with regards to a system, that is using more than one standby I/O server process.[]Here we have three I/O servers.The first server is set as the primary server, and it is using the Ethernet network to communicate with the I/O device.The second server is set as the first standby server, and it is able to use the Ethernet, or use serial network number 1, to communicate with the I/O device.The third server is the last standby, and it has serial network number 2, available to communicate with the I/O device.By having multiple standby’s, it ensures connectivity to the data source, by being able to use multiple paths.Network connections, especially data connections to remote field devices, can be unreliable at times; so, by being able to transparently use multiple data paths, to access remote data, it keeps the control system functional for the operator.With the first server being the primary, the default communication path will use server 1.
#22:So, if server 1 was to fail; server 2 would take over using the Ethernet communication path.In this setup example; within the server 2 configuration for the I/O device data paths; the Ethernet path has been given a higher priority than the serial network path, so that the Ethernet network is used first, if it is available for server 2, otherwise the server will use the serial path.[] Now, once we lose connection to the I/O device, over the Ethernet network; server 2 will not be able to communicate successfully using the Ethernet network; the data connection will move on server 2 to use serial network 1.[] This would be the same result if we only lost the Ethernet network connection to the I/O device; in this situation, both server 1 and server 2, would be unable to use the Ethernet network, to communicate with the I/O device; so then server 2 would use serial network 1.I should point out; in this example, we have server 1 and 3, only having a single data path option. Where with server 2, it has 2 data paths.We could also have a single PC setup that has all the 3 data paths, connected to a single I/O server process; with that I/O server process arbitrating the best data path to use.The flexibility is available, to offer you what ever data path configuration is required; to be able to offer the maximum data connectivity and reliability for your system designs.
#23:Then in the last example; we now have both the Ethernet network connection, and serial network 1 failed;So server 3 will take over communication with the I/O device using serial network 2.Throughout all the network failure and I/O server switching; it is transparent to the client display, as the client is automatically following the active process.There is no function, or selection, that has to be made on the client, by the operator; the client change over, is automatic with the required subscription data being published to the client.As the communication networks are restored; the use of the data paths will activate, using the defined redundancy priority.