ApplicationServer2012(wonderware培训).

1、 2010 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks of Invensys or its subsidiaries. All third party trademarks and service marks are the proprietary marks of their respective owners. Wonderware Application Serve

2、r 2012 Terry NG E-mail: TEL:Invensys 00/00/00Invensys proprietary & confidentialSlide 2 Daily Schedule Slide 3 8:00 AM 12:00 PM 10:00 AM 1:00 PM 3:00 PM 5:00 PMSilence your phones At the lobby Outside at smoking section On every computer Entrance hall to your left In the kitchen Course

3、Description The Wonderware Application Server course is a 4 day, instructor-led course designed to provide a fundamental understanding of the basic principles of ArchestrA and supply the knowledge necessary to develop and support applications for Wonderware Application Server 2012. The focus of this

4、 course is to illustrate the use of ArchestrA tools and services in the System Platform to develop a project utilizing connectivity to the field, data processing, scripts, alarms and history, using features and functionality such as Automation Objects, templates, template instances, ArchestrA Integr

5、ated Development Environment and QuickScript .NET. Slide 4 Requirements & Expectations Participants should have knowledge on the following topics: Manufacturing industry experience Slide 5 Application Server 2012 Agenda Contents Module 1:Introduction Module 2:Application Planning Module 3:Applicatio

6、n Infrastructure Module 4:Application Objects Module 5:Extending the Objects Module 6:Alarms and History Module 7:Security Module 8:Galaxy Maintenance Module 9:Redundancy Slide 6 1 Introduction Slide 7 Application Server 2012 Module 1: Introduction Contents Section 1: Course Introduction Section 2:

7、System Platform Overview Section 3: Application Server Overview Lab 1 Creating a Galaxy Section 4: The ArchestrA IDE Section 5: Automation Objects Lab 2 Creating Global Derived Templates Section 6: System Requirements and Licensing Slide 8 Wonderware System Platform Slide 9 Project Specific Work Mic

8、rosoft Technologies + Industry Standards System PlatformClients Functional Modules Wonderware System Platform Wonderware System Platform Application Server Historian Server Information Server Device Integration Products Wonderware Clients InTouch (Visualization) Historian Client (Analysis Client) In

9、formation Server CAL (Report Client) 3rd Party Data Sources Software Applications 3rd Party Controllers Slide 10 Concepts and Terminology ArchestrA It is an open and extensible system of components based on a distributed, object-oriented design. . Slide 11 Concepts and Terminology Application Server

10、 It provides a unified environment for visualization, plant history, device communications and automation application integration. Galaxy Application Servers application, configuration information and project database. Galaxy Repository Single computer and software where the Galaxy database is locat

11、ed. Slide 12 Wonderware Application Server Highlights Leverage the .NET Framework for the Automation World Object-based application One global networked namespace Centralized configuration and security Multi-user development environment Component-based plant application model Self documenting Advanc

12、ed system maintenance and diagnostics Slide 13 Line 1 Line 2 Production Intake Discharge System Platform Topology Slide 14 Device Integration Server Automation Object Server Automation Object Server Galaxy Repository Historian Server Information Server Visualization NodeVisualization NodeEngineering

13、 StationEngineering Station Workstation ArchestrA License Server Device Integration Server Automation Object Server Automation Object Server Galaxy Repository Historian Server Information Server Visualization NodeVisualization NodeEngineering StationEngineering Station Workstation ArchestrA License

14、Server ArchestrA Topology Slide 15 Galaxy Rep. IDE BootstrapBootstrapBootstrapBootstrap BootstrapBootstrapBootstrap Bootstrap Bootstrap Bootstrap WinPlatformWinPlatformWinPlatformWinPlatform WinPlatformWinPlatformWinPlatform WinPlatform WinPlatform WinPlatform IDEInTouchInTouch Historian Info Server

15、 IO Server ArchestrA Topology Slide 16 Unified Name Space Device Integration Server Automation Object Server Automation Object Server Galaxy Repository Historian Server Information Server Visualization NodeVisualization NodeEngineering StationEngineering Station Workstation BootstrapBootstrapBootstr

16、apBootstrap BootstrapBootstrapBootstrap Bootstrap Bootstrap Bootstrap WinPlatformWinPlatformWinPlatformWinPlatform WinPlatformWinPlatformWinPlatform WinPlatform WinPlatform WinPlatform Lab 1 Creating a Galaxy 10 min Slide 17 Automation Objects Slide 18 Alarms and events Documentation Inputs/Outputs

17、Logic/Scripting Historical Information Security Graphic symbols Automation Objects Templates and Instances Instances derived from templates and inherit all the configuration New templates can be derived from existing templates Changes to templates can be propagated to derived objects Templates allow

18、 the development of a library of standard objects Slide 19 $Valve CV101 CV102 CV103 Templates Base Template Core objects created with the ArchestrA Object Toolkit Contain the base attributes and functionality of the object Read-Only configuration Templates created from another template within the Ar

19、chestrA IDE Inherits the attributes, functionality and configuration from the parent template Writeable configuration Derived Template Slide 20 Template Slide 21 $DiscreteDevice$Valve $Inlet CV101 $Outlet CV102 CV103 CV104 Lab 2 Creating Global Derived Templates Slide 22 10 min System Requirements -

20、 Software Slide 23 Operating Systems Wonderware Application Server Components ArchestrA IDE (Development Node) ArchestrA Run time (Application Node) Galaxy Repository (GR Node) Windows XP SP3 Professional (32-bit) N Windows Vista SP2 Business or Ultimate (32/64-bit) N Windows 7 Professional or Ultim

21、ate (32/64-bit) N Windows 7 SP1 Professional or Ultimate (32/64-bit) N Windows Server 2003 SP2 Standard or Enterprise (32-bit) Windows Server 2008 SP2 Standard or Enterprise (32/64-bit) Windows Server 2008 R2 Standard or Enterprise (64-bit) Windows Server 2008 R2 SP1 (Standard, Enterprise) (64-bit)

22、System Requirements - Hardware Galaxy Repository Application Server Development or Run Time Slide 24 Hardware Requirements Small (1 - 5,000 I/O) Medium (5,000 - 20,000 I/O) Large ( 20,000 I/0) CPU (GHz)22.52.5 Minimum Cores124 RAM (Min GB)248 Hard Disk size (Available in GB) 100250500 Monitor1024 x

23、7681280 x 10241280 x 1024 Network card (MBPS)1001001000 Hardware Requirements Small (1 - 5,000 I/O) Medium (5,000 - 20,000 I/O) Large ( 20,000 I/0) CPU (GHz)22.52.5 Minimum Cores124 RAM (Min GB)244 Hard Disk size (Available in GB) 100100100 Monitor1024 x 7681280 x 10241280 x 1024 Network card (MBPS)

24、1001001000 Concepts and Terminology Galaxy This refers to the total application model that resides in the Galaxy Repository. IO Count Number of I/O points being access into the Galaxy. WinPlatform Count Number of PCs in the Galaxy that will be part of the single namespace. ArchestrA IDE Integrated D

25、evelopment Environment for configuring the Galaxy. Slide 25 Licensing A single ArchestrA.LIC file can handle all products on the DVD. InTouch Application Server Historian Historian Client Information Server NOT Server based licensingyet Slide 26 Virtualization Virtualization : “creating a virtual, r

26、ather than real, version of ArchestrA System Platform or one of its components, including servers, nodes, databases, storage devices, and network resources.” Supported VMware Products ESX 3.0, 3.5 EsXi 4.0 Vsphere 4.0 * VMware Workstation is NOT supported for production environments. Windows Server

27、2008 R2 SP1 Hyper V: High Availability Disaster Recovery Slide 27 Overall Virtualization Benefits Lower hardware costs Greater performance Greater scalability Higher availability Simpler management of software and OSs Greater reliability Greater protection against disasters Eliminates dependencies b

28、etween the physical hardware and the software, giving customers more choices to better manage their applications, servers and equipment Slide 28 Hyper V support High Availability (HA) refers to the availability of resources in a computer system following the failure or shutdown of one or more compon

29、ents of that system. Reduce downtime to a minimum Disaster Recovery (DR) can be defined as the organizational, hardware and software preparations for ArchestrA System Platform recovery or continuation of critical System Platform infrastructure after a natural or human-induced disaster. High Availabi

30、lity with Disaster Recovery -HADR The goal of this solution is to provide a means to shift data processing and retrieval to a standby system in the event of a primary system failure. Slide 29 Reduction of HW boxes. Slide 30Slide 30 Historian Server Information Server Active Factory AOS Data Server I

31、nformation Client AOS Data Server GR AOS Data Server InTouch for SP w/Trend Field Devices Defining High Availability Slide 31 Defining Disaster Recovery Slide 32 Defining High Availability and Disaster Recovery Combined Slide 33 VLAN Communications Slide 34 VLANs Supported for all Node to Node Commu

32、nications Remote Apps 2008 R2 Granular access to concentrated Server Applications using RDP. Slide 35 2 Application Planning Slide 36 Application Server 2012 Module 2: Application Planning Contents Section 1: Application Planning Overview Section 2: Case Study Slide 37 Suggested Project Workflow Sli

33、de 38 Identify Field Devices and Functional Requirements Defined Naming Conventions Defined the Plant Model Plan Templates Defined the Security Model Defined the Deployment Model The Factory Layout Slide 39 PACKAGINGPRODUCTIONRECEIVINGSHIPPING LINE 1LINE 2 3 Application Infrastructure Slide 40 Appli

34、cation Server 2012 Module 3: Application Infrastructure Contents Section 1: The Area Model Section 2: The Deployment Model Lab 3 Creating the Plant and Deployment Model Section 3: The Runtime Environment Lab 4 Using Object Viewer Section 4: Device Integration Products Lab 5 Connecting to the Field S

35、lide 41 Plant The Plant Model Section Area Production Line Manufacturing Cell Area Production Line Manufacturing Cell Section Area Production Line Manufacturing Cell Section Slide 42 Bootstrap The Deployment Model Platform AppEngine Area DI Object DI Object Area Slide 43 Bootstrap The Deployment Mod

36、el Platform AppEngine Area DI Object DI Object Area AppEngine Area DI Object DI Object Area Slide 44 Deployment Icons Slide 45 Lab 3 Creating the Plant and Deployment Model 20 min Slide 46 Lab 4 Using Object Viewer 10 min Slide 47 Application Object$DDESuiteLinkClient IO Server PLC1 PLC2 DAServerPLC

37、3 $OPCClient OPC ServerPLC4 DIObjectDAServerPLC5 Single Node Automation Object communication to PLCs Slide 48 Application Object Device Integration Object . Driver . . . Data point, register or address on PLC MX Generic DI Objects Device Specific DI Objects OPC Device Integration Products IO Server

38、and DA Servers Communications between the Galaxy and field devices is achieved through Device Integration Products Supported protocols include DDE, SuiteLink and OPC New internal architecture for DA Servers provides independency between components Slide 49 I/O Data Server ArchestrA Runtime DA Server

39、DAS EngineIO Server DDESuiteLink PLC Protocol DDESuiteLinkOPC PLC Protocol DDESuiteLinkOPC PLC Protocol DA Servers and DI Objects Slide 50 I/O Data Server PLC5_A SLC_A PLC_1 CNET DHP NIC PLC_2 SLC_B PLC5_B Connecting to the Field Legacy InTouch Node Field Device Device Driver Slide 51 Communication

40、Protocols ClientServer VTQ* DDE or SuiteLink NodeName of the computer where the server application is running. ApplicationName of the server application executable. TopicName of the topic in the server application from which to receive data. OPC NodeName of the computer where the OPC Server is runni

41、ng. ServerName of the OPC Server. Scan GroupName of the scan group in the OPC Server from which to receive data. DDEOPCSuiteLink I/O Addressing Slide 53 . Slide 54 Advanced communication management Scan modes (active on demand.active) Lab 5 Connecting to the Field 10 min Slide 55 Galaxy InControl Fi

42、eld Device Device Driver 4 Application Objects Slide 56 Application Server 2012 Module 4: Application Objects Contents Section 1: The $UserDefined Object Lab 6 Modeling the Mixer Section 2: Change Control and Propagation Lab 7 Configuring Change Control and Propagation Section 3: The $DiscreteDevice

43、 Object Lab 8 Modeling a Valve and a Motor Section 4: Containment Lab 9 Creating the Mixer Slide 57 $UserDefined Object AnalogFA AnalogFA.Input.InputSource AnalogFA.Input.Value Scaling AnalogFA.RawMin AnalogFA.RawMax AnalogFA.EngUnitsMin AnalogFA.EngUnitsMax DiscreteFA DiscreteFA.Input.InputSource D

44、iscreteFA.Input.Value Invert AnalogBoolean Slide 58 Field Attribute - Output Categories Slide 59 Calculated Calculated Retentive Object Writeable User Writeable Same Object Other Objects External Users Lab 6 Modeling the Mixer 10 min Slide 60 PUMP 1 PUMP 2 LT TT $Tank $Mixer Control and Propagation

45、of Changes Locking an attribute prevents changes to that attribute on derived templates and instances. Locking an attribute locks that attribute all the way down on the derivation hierarchy. Locking attributes helps to establish standards in the Galaxy. Unlocking an attribute releases the “locking c

46、ontrol” only one level down. Slide 61 Locked In me Unlocked Locked In parent indeterminate Control of Changes and Propagation of Changes Slide 62 $DiscreteDevice Locked Unlocked Locked In Parent $Valve $Inlet CV101 $Outlet CV102 CV103 CV104 Lab 7 Configuring Change Control and Propagation 10 min Sli

47、de 63 $DiscreteDevice Object PV CLS.InputSource CLS.Value Map OLS.InputSource OLS.Value StateNames Map Cmd CmdOpen.OutputDest CmdOpen.Value BooleanBoolean Slide 64 Lab 8 Modeling a Valve and a Motor 10 min Slide 65 Containment Allows more advanced structures to be modeled as a single object All obje

48、cts are still accessible as individual objects Relationship can be build at the template or instance level Slide 66 Inlet Valve Level Meter Outlet Valve Agitator Tank Object Naming Slide 67 Hierarchical name: Valve_001 Tank_001.InletValve Reactor_001.MixerTank.InletValve Reactor_001.Tank_001.Valve_0

49、01 Reactor_001.Tank_001.InletValve Tank_001.Valve_001 Contained name: Tagname : Lab 9 Creating the Mixer 10 min Slide 68 $Motor $Valve $Mixer INLET 1 PUMP 1 INLET 2 PUMP 2 OUTLET AGITATOR LT TT 5 Extending the Objects Slide 69 Application Server 2012 Module 5: Extending the Objects Contents Section

50、1: User Defined Attributes Section 2: Extensions Lab 10 Configuring the Motor Speed Section 3: Introduction to QuickScript.NET Lab 11 Adding Auto Reconnect to DDESuiteLinkClient Lab 12 Configuring Automatic Reference Slide 70 UDA Categories Slide 71 Calculated Calculated Retentive Object Writeable U

51、ser Writeable Same Object Other Objects External Users Lab 10 Configuring the Motor Speed 30 min Slide 72 Execution types Slide 73 Start up OnScan Execute OffScan Shutdown Relative references Slide 74 Container1.AttX Object1 Object2 Att1 Att2 Me.Att1 MyContainer.Object2.Att2 MyContainer.AttX If scri

52、pt is here Lab 11 Adding Auto Reconnect to DDESuiteLinkClient 30 min Slide 75 Relative References Slide 76 Me MyContainer MyArea MyEngine MyPlatform Control Structures Slide 77 IF THEN ELSEIF ELSE ENDIF FOR TO STEP NEXT Loop FOR EACH IN NEXT WHILE Loop I/O References Slide 78 PLCSim.Tagname.M1XX_XX_

53、XX XX = student number DataSource String Lab 12 Configuring Automatic Reference 30 min Slide 79 6 Alarms and History Slide 80 Application Server 2012 Module 6: Alarms and History Contents Section 1: Alarms Overview Lab 13 Configuring Alarms Lab 14 Scripted Alarms and Events Section 2: Alarm Logger L

54、ab 15 Logging Alarms Section 3: Historization Lab 16 Configuring History Slide 81 Alarm Subsystem Slide 82 DISTRIBUTED ALARM MANAGER $AREA $WINPLATFORM $APPENGINE $DIOBJECT CLIENTS “Alarm Subscribers” $Object1 $Object2 $Object3 Report their own alarms and events Alarms Alarms are generate by the obj

55、ects Alarm providers make the alarms available to external alarm subscribers Available alarm subscribers allows: Visualization and acknowledge of alarms Logged alarms into a SQL Server database Print alarms Slide 83 Alarm Provider $WinPlatform object as the Client Alarm Provider for the galaxy. A si

56、ngle $WinPlatform can provide alarms from the whole galaxy. Alarm providers can be limited to provide alarms for specific areas of the galaxy. Slide 84 WinPlatform AppEngine Area Alarm Viewer Alarm DB Logger Alarm Printer PROV Lab 13 Configuring Alarms 40 min Slide 85 Slide 86 Lab 14 Scripted Alarms

57、 and Events 40 min Slide 87 Lab 15 Logging Alarms 40 min Slide 88 Historization $AppEngine object as the Historian client for the objects An $AppEngine historizes only the objects that it host Native support for Store & Forward Slide 89 WinPlatform AppEngine Area CLIENT Historian Lab 16 Configuring

58、History 40 min Slide 90 7 Security Slide 91 Application Server 2012 Module 7: Security Contents Section 1: Security Overview Lab 17 Using Security Slide 92 Security Slide 93 Development Security Runtime Security Develoment Testing Troubleshooting Environment Security Groups BELONGS TO ONE OR MORE OP

59、ERATIONAL PERMISSIONS ASSIGNED TO ATTRIBUTES GENERAL PERMISSIONS Roles Security Classifications Users Security Audit trail The Galaxy generates an event for every user-generated write to an attribute. Alarm DB Logger is used to log the events. Use the v_EventHistory view in the alarm database to que

60、ry events. Slide 94 Enhanced Electronic Signature Handling: Done By/Checked By Slide 95 Reason All Signed Writes present a reason for the action being signed to the user from: Field Attribute Description Object Description Custom String SignedWrite script function Comment All signed writes allow for