ApplicationServer2012(wonderware培训).ppt

1、Wonderware Application Server 2012,Terry NG E-mail: TEL: Invensys 00/00/00,Invensys proprietary & confidential,Slide 2,Daily Schedule,Slide 3,8:00 AM,12:00 PM,10:00 AM,1:00 PM,3:00 PM,5:00 PM,Silence your phones,At the lobby,Outside at smoking section,On every computer,Entrance hall to

2、your left,In the kitchen,Course Description,The Wonderware Application Server course is a 4day, 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

3、 Server 2012. The focus of this 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, templ

4、ate instances, ArchestrA Integrated 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:Applicati

5、on Planning Module 3:Application 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:C

6、ourse Introduction Section 2: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

7、 9,Project Specific Work,System Platform,Clients,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),Information Serve

8、r 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 It provides a

9、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 located.,Slide 12,Wo

10、nderware Application ServerHighlights,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 Advanced system mainte

11、nance and diagnostics,Slide 13,System Platform Topology,Slide 14,ArchestrA Topology,Slide 15,Galaxy Rep.,IDE,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,WinPlatform,WinPlatform,WinPlatform,WinPlatform,WinPlatform,WinPlatform,WinPlatform,WinPlat

12、form,WinPlatform,WinPlatform,IDE,InTouch,InTouch,Historian,Info Server,IO Server,ArchestrA Topology,Slide 16,Unified Name Space,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,Bootstrap,WinPlatform,WinPlatform,WinPlatform,WinPlatform,WinPlatform,WinPlatform,

13、WinPlatform,WinPlatform,WinPlatform,WinPlatform,Lab 1Creating a Galaxy,10 min,Slide 17,Automation Objects,Slide 18,Alarms and events,Documentation,Inputs/Outputs,Logic/Scripting,Historical Information,Security,Graphic symbols,Automation Objects,Templates and Instances Instances derived from template

14、s and inherit all the configuration New templates can be derived from existing templates Changes to templates can be propagated to derived objects Templates allow the development of a library of standard objects,Slide 19,$Valve,CV101,CV102,CV103,Templates,Base Template,Core objects created with the

15、ArchestrA Object Toolkit,Contain the base attributes and functionality of the object,Read-Only configuration,Templates created from another template within the ArchestrA IDE,Inherits the attributes, functionality and configuration from the parent template,Writeable configuration,Derived Template,Sli

16、de 20,Template,Slide 21,Lab 2Creating Global Derived Templates,Slide 22,10 min,System Requirements - Software,Slide 23,System Requirements - Hardware,Galaxy Repository,Application Server Development or Run Time,Slide 24,Concepts and Terminology,Galaxy This refers to the total application model that

17、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 Development Environment for configuring the Galaxy.,Slide 25,Licensing,A single ArchestrA.LI

18、C 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, rather than real, version of ArchestrA System Platform or one of its components, including

19、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 2008 R2 SP1 Hyper V: High Availability Disaster Recovery,Slide 27,Overall Virtualization Be

20、nefits,Lower hardware costs Greater performance Greater scalability Higher availability Simpler management of software and OSs Greater reliability Greater protection against disasters Eliminates dependencies between the physical hardware and the software, giving customers more choices to better mana

21、ge 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 components of that system. Reduce downtime to a minimum Disaster Recovery (DR) can be defined as

22、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 Availability with Disaster Recovery -HADR The goal of this solution is to provide a means to shift

23、data processing and retrieval to a standby system in the event of a primary system failure.,Slide 29,Reduction of HW boxes.,Slide 30,Slide 30,Defining High Availability,Slide 31,Defining Disaster Recovery,Slide 32,Defining High Availability and Disaster Recovery Combined,Slide 33,VLAN Communications

24、,Slide 34,VLANs Supported for all Node to Node Communications,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:

25、Case Study,Slide 37,Suggested Project Workflow,Slide 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,PACKAGING,PRODUCTION,RECEIVING,SHIPPING,LIN

26、E 1,LINE 2,3,Application Infrastructure,Slide 40,Application 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 In

27、tegration Products Lab 5 Connecting to the Field,Slide 41,Plant,The Plant Model,Section,Area,Production Line,Manufacturing Cell,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 M

28、odel,Platform,Slide 44,Deployment Icons,Slide 45,Lab 3Creating the Plant and Deployment Model,20 min,Slide 46,Lab 4Using Object Viewer,10 min,Slide 47,Single Node,Automation Object communication to PLCs,Slide 48,MX,Generic DI Objects,Device Specific DI Objects,OPC,Device Integration Products,IO Serv

29、er 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,DA Server,DAS Engine,IO Server,DDE,Suite

30、Link,PLC Protocol,DDE,SuiteLink,OPC,PLC Protocol,DDE,SuiteLink,OPC,PLC Protocol,DA Servers and DI Objects,Slide 50,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 Protocols,Client,Server,VTQ*,DDE,OPC,Sui

31、teLink,I/O Addressing,Slide 53,.,.,Slide 54,Advanced communication managementScan modes (active on demand.active),Lab 5Connecting to the Field,10 min,Slide 55,Galaxy,Field Device,Device Driver,4,Application Objects,Slide 56,Application Server 2012,Module 4: Application Objects,Contents Section 1:The

32、 $UserDefined Object Lab 6 Modeling the Mixer Section 2:Change Control and Propagation Lab 7 Configuring Change Control and Propagation Section 3: The $DiscreteDevice Object Lab 8 Modeling a Valve and a Motor Section 4: Containment Lab 9 Creating the Mixer,Slide 57,$UserDefined Object,AnalogFA,Analo

33、gFA.Input.InputSource,AnalogFA.Input.Value,Scaling,AnalogFA.RawMin,AnalogFA.RawMax,AnalogFA.EngUnitsMin,AnalogFA.EngUnitsMax,DiscreteFA,DiscreteFA.Input.InputSource,DiscreteFA.Input.Value,Invert,Analog,Boolean,Slide 58,Field Attribute - Output Categories,Slide 59,Calculated Calculated Retentive,Obje

34、ct Writeable,User Writeable,Same Object,Other Objects,External Users,Lab 6Modeling the Mixer,10 min,Slide 60,Control and Propagation 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 th

35、e derivation hierarchy. Locking attributes helps to establish standards in the Galaxy. Unlocking an attribute releases the “locking control” only one level down.,Slide 61,Control of Changes andPropagation of Changes,Slide 62,Lab 7Configuring Change Control and Propagation,10 min,Slide 63,$DiscreteDe

36、vice Object,PV,CLS.InputSource,CLS.Value,Map,OLS.InputSource,OLS.Value,StateNames,Map,Cmd,CmdOpen.OutputDest,CmdOpen.Value,Boolean,Boolean,Slide 64,Lab 8Modeling a Valve and a Motor,10 min,Slide 65,Containment,Allows more advanced structures to be modeled as a single object All objects are still acc

37、essible 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_001 Reactor_001.Ta

38、nk_001.InletValve Tank_001.Valve_001,Contained name:,Tagname :,Lab 9Creating the Mixer,10 min,Slide 68,5,Extending the Objects,Slide 69,Application Server 2012,Module 5: Extending the Objects,Contents Section 1:User Defined Attributes Section 2:Extensions Lab 10 Configuring the Motor Speed Section 3

39、: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,User Writeable,Same Object,Other Objects,External Users,Lab 10Configuring the Motor Speed,30 mi

40、n,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 script is here,Lab 11Adding Auto Reconnect to DDESuiteLinkClient,30 min,Slide 75,Relative Reference

41、s,Slide 76,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_XX,XX = student number,DataSource,String,Lab 12Configuring Automatic Reference,30 min,Slide 79,6,Alarms and History,Slide 80,Application S

42、erver 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 Lab 15 Logging Alarms Section 3:Historization Lab 16 Configuring History,Slide 81,Alarm Subsystem,Slide 82,DISTRIBUTED ALARM MANAGER,CLIENTS “

43、Alarm Subscribers”,Report their own alarms and events,Alarms,Alarms are generate by the objects 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,Sl

44、ide 83,Alarm Provider,$WinPlatform object as the Client Alarm Provider for the galaxy. A single $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,A

45、larm Printer,PROV,Lab 13Configuring Alarms,40 min,Slide 85,Slide 86,Lab 14Scripted Alarms and Events,40 min,Slide 87,Lab 15Logging 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

46、Store & Forward,Slide 89,WinPlatform,AppEngine,Area,CLIENT,Historian,Lab 16Configuring 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,De

47、veloment Testing Troubleshooting Environment,Security Groups,BELONGS TO ONE OR MORE,OPERATIONAL 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 Logg

48、er is used to log the events. Use the v_EventHistory view in the alarm database to query 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 Desc

49、ription Custom String SignedWrite script function Comment All signed writes allow for a user entered comment. Reason and Comment stored in the electronic record in the Alarm/Event database.,New “Can Verify Writes” Functional Permission,Role Definition,New Functional Permission,Slide 96,Smart Card Su

50、pport,Slide 97,InTouch now supports the standard Microsoft interface for secure user access to Active Directory accounts via Smart Cards. Logon using Card/PIN combination. Does not require the interactive OS user to be the same.,Multi-User Kiosk Usage,All Signed Writes allow entering a different use

51、rname than the currently logged on user. Combined with new SignedWrites, SignedAlarmAck, and/or Smart Cards, a shared Kiosk can be used where all actions are tracked to the user without having to log in/out of the application.,Slide 98,Shared Workstation,Operator1,Operator2,Operator3,Lab 17Using Sec

52、urity,40 min,Slide 99,8,Galaxy Maintenance,Slide 100,Application Server 2012,Module 8: Galaxy Maintenance,Contents Section 1:Objects Export and import Lab 18 Exporting and Importing Objects Section 2:Galaxy Dump and Galaxy Load Lab 19 Configuring Instances Through a .CSV File Section 3:System Manage

53、ment Console (SMC),Slide 101,Lab 18Exporting and Importing Objects,40 min,Slide 102,Lab 19Configuring Instances Through a .CSV File,40 min,Slide 103,9,Redundancy,Slide 104,Application Server 2012,Module 9: Redundancy,Contents Section 1:Application Redundancy Lab 20 Configuring Application Redundancy

54、 Section 2:Device Integration Redundancy Lab 21 Configuring the Redundant DI Object,Slide 105,Application Redundancy,Slide 106,ArchestrA Runtime,ArchestrA Runtime,Client/Server Architecture,Application Redundancy,Currently supported only in pairs Second network connection (RMC) necessary Configurati

55、on Terminology: Primary AppEngine Backup AppEngine Runtime Terminology Active AppEngine Standby AppEngine Active AppEngine refer to Standby AppEngine as Partner.,Slide 107,WinPlatform1,RMC,ArchestrA,WinPlatform2,AppEngine1 (Backup),Primary,Backup,AppEngine1,Active,Standby,Standby,Active,Redundant Message Channel,Automatic Synchronization Current data (