Wonderware培训资料.ppt

System Platform 3.1,Wonderware System Platform 3.1,Agenda,Contents Module 1: Introduction Module 2: Application Infrastructure Module 3: Application Objects Module 4: Extending the Objects Module 5: Alarms and History Module 6: Security Module 7: Galaxy Maintenance Module 8: Device Integration Products Module 9: Multi-Node Applications,System Platform,Module 1: Introduction,Contents Section 1: Course Introduction Section 2: Wonderware System Platform Lab 1 Creating a Galaxy Section 3: The ArchestrA IDE Section 4: Automation Objects Section 5: System Requirements, Licensing and Support Section 6: Application Planning Lab 2 Identifying the Mixer,System Platform,Course Description and Objectives,Project Specific Work,Wonderware System Platform,Microsoft Technologies & Industry Standards,System Platform,Clients,Industry Packs,Project Specific Work,Wonderware System Platform,Microsoft Technologies & Industry Standards,System Platform,Clients,Industry Packs,Wonderware System Platform,Wonderware System Platform,Wonderware Clients,Application Server,Historian,Information Server,Device Integration Products,ActiveFactory (Analysis Client),Information Server CAL (Report Client),InTouch (Visualization),3rd Party Data Sources,Software Applications,3rd Party Controllers,It is an open and extensible system of components based on a distributed, object-oriented design.,It provides a unified environment for visualization, plant history, device communications and automation application integration.,Application Servers application, configuration information and project database.,Single computer and software where the Galaxy database is located.,Concepts and Terminology,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 Advanced system maintenance and diagnostics,Wonderware Application Server,+ Scan-based system.,10 min,LAB 1 Creating a Galaxy,Alarms and events,Documentation,Inputs/Outputs,Logic/Scripting,Historical Information,Security,Automation Objects,Graphic symbols,$Valve,CV101,CV102,CV103,Automation Objects,ArchestrA Topology,ArchestrA Topology,Bootstrap,Platform,Galaxy Rep.,Bootstrap,Platform,Bootstrap,Platform,Historian,Bootstrap,Platform,Info Server,Bootstrap,Platform,InTouch,Bootstrap,Platform,InTouch,Bootstrap,Platform,IDE,Bootstrap,Platform,IDE,Bootstrap,Platform,IO Server,Bootstrap,Platform,Galaxy Rep.,Historian,Info Server,InTouch,InTouch,IDE,IDE,IO Server,ArchestrA Topology,Bootstrap,Platform,Bootstrap,Platform,Bootstrap,Platform,Bootstrap,Platform,Bootstrap,Platform,Bootstrap,Platform,Bootstrap,Platform,Bootstrap,Platform,Bootstrap,Platform,Unified Name Space,Bootstrap,Platform,System Requirements Software,* SP3 for SQL Server 2005 is not supported,System Requirements Hardware,Galaxy Repository,ArchestrA IDE and AutomationObject Server,All Systems,This refers to the total application model that resides in the Galaxy Repository.,Number of I/O points being access into the Galaxy.,Number of PCs in the Galaxy that will be part of the single namespace.,Integrated Development Environment for configuring the Galaxy,Concepts and Terminology,Suggested Project Workflow,Identify Field Devices and Functional Requirements,Defined Naming Conventions,Defined the Plant Model,Plan Templates,Defined the Security Model,Defined the Deployment Model,10 min,LAB 2 Identifying the Mixer,Mixer System,LAB 2 Identifying the Mixer (Cont.),10 min,Heat Exchanger,Module 2: Application Infrastructure,Contents Section 1: The Plant Model Lab 3 Creating the Plant Model Section 2: The Deployment Model Lab 4 Creating the Deployment Model Section 3: The Runtime Environment Lab 5 Using Object Viewer Section 4: Connecting to the Field Lab 6 Connecting to the Field,System Platform,Plant,The Plant Model,Section,Area,Production Line,Manufacturing Cell,Area,Production Line,Manufacturing Cell,Section,Plant,The Plant Model,Section,Area,Production Line,Manufacturing Cell,Area,Production Line,Manufacturing Cell,Section,Plant,Production,LAB 3 Creating the Plant Model,Line1,Line2,10 min,ControlSystem,Bootstrap,The Deployment Model,Platform,AppEngine,Area,Area,Bootstrap,The Deployment Model,Platform,15 min,LAB 4 Creating the Deployment Model,15 min,LAB 5 Using Object Viewer,Connecting to the Field,Legacy InTouch Node,Field Device,Device Driver,Communication Protocols,Client,Server,DDE,OPC,SuiteLink,Galaxy,LAB 6 Connecting to the Field,15 min,Field Device,Device Driver,Module 3: Application Objects,Contents Section 1: Templates and Instances Section 2: The $UserDefined Object Lab 7 Modeling the Heat Exchanger Section 3: Change Control and Propagation Lab 8 Configuring Change Control and Propagation Section 4: The $AnalogDevice Object Lab 9 Modeling a Meter Section 5: The $DiscreteDevice Object Lab 10 Modeling a Valve, Pump and Motor Section 6 Containment Lab 11 Creating the Mixer,System Platform,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 ArchestrA IDE,Inherits the attributes, functionality and configuration from the parent template,Writeable configuration,Derived Template,$UserDefined Object,AnalogFA,PV.Input.InputSource,PV.Input.Value,Scaling,RawMin,RawMax,EngUnitMin,EngUnitMax,DiscreteFA,PV.Input.InputSource,PV.Input.Value,Invert,Analog,Boolean,Template,LAB 7 Modeling the Heat Exchanger,20 min,Control of Changes and Propagation,Locking Attributes,Locking an attribute prevents changes of that attribute on derived objects (templates and instances). Locking attributes helps to establish standards in the galaxy. Locking an attribute locks that attribute all the way down on the derivation hierarchy. Unlocking an attribute releases the “locking control” only one level down.,Control of Changes and Propagation,LAB 8 Configuring Change Control and Propagation,10 min,$AnalogDevice Object,PV,PV.Input.InputSource,PV.Input.Value,Scaling,RawMin,RawMax,EngUnitMin,EngUnitMax,Analog,LAB 9 Modeling a Meter,10 min,$DiscreteDevice Object,PV,CLS.InputSource,CLS.Value,Map,OLS.InputSource,OLS.Value,States,Map,Cmd,CmdOpen.OutputDest,CmdOpen.Value,Boolean,Boolean,LAB 10 Modeling a Valve, Pump and Motor,20 min,Containment,Containment,Allows more advanced structures to be modeled as a single object. Container and contained objects are still accessible as individual objects. Relationship can be build at the template or instance level.,Inlet Valve,$InletValve,Level Meter,$LevelMeter,Outlet Valve,$OutletValve,Agitator,$Agitator,$Tank,LAB 11 Creating the Mixer,30 min,Module 4: Extending the Objects,Contents Section 1: UDAs Section 2: Extensions Lab 12 Configuring the Motor Speed Section 3: Introduction to QuickScripts .NET Lab 13 Adding Auto Reconnect to DDESuiteLinkClient Lab 14 Configuring Automatic Reference,System Platform,UDA Categories,Calculated Calculated Retentive,Object Writeable,User Writeable,Same Object,Other Objects,External Users,LAB 12 Configuring the Motor Speed,10 min,Relative References,LAB 13 Adding Auto Reconnect to DDESuiteLinkClient,15 min,LAB 14 Configuring Automatic Reference,15 min,Module 5: Alarms and History,Contents Section 1: Alarms Lab 15 Configuring Alarms Section 2: Historization Lab 16 Configuring History,System Platform,Alarms,Alarm Engine,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,Alarms,Alarm Engine,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,Alarms,WinPlatform,AppEngine,Area,Alarm Viewer,Alarm DB Logger,PROV,Alarm Provider,$WinPlatform object as the InTouch 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.,Alarms,WinPlatform,AppEngine,Area,Alarm Viewer,Alarm DB Logger,Alarm Printer,PROV,Alarm Provider,$WinPlatform object as the InTouch 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.,LAB 15 Configuring Alarms,30 min,WinPlatform,AppEngine,Historization,Area,CLIENT,History Engine,$AppEngine object as the Historian client for the objects. An $AppEngine historize only the objects that it host. Native support for Store & Forward.,Historian,LAB 16 Configuring History,20 min,Module 6: Security,Contents Section 1: Security Overview Lab 17 Configuring Security,System Platform,Development Security,Runtime Security,Security,Develoment Testing Troubleshooting Environment,Users,Security Groups,BELONGS TO ONE OR MORE,OPERATIONAL PERMISSIONS,ASSIGNED TO ATTRIBUTES,Roles,Security Classifications,Development Security,Runtime Security,Security,Develoment Testing Troubleshooting Environment,Security Groups,BELONGS TO ONE OR MORE,OPERATIONAL PERMISSIONS,ASSIGNED TO ATTRIBUTES,Roles,Security Classifications,Users,LAB 17 Configuring Security,40 min,Module 7: Galaxy Maintenance,Contents Section 1: Exporting and Importing Objects Section 2: Configuring Instances Through a CSV File Section 3: System Management Console (SMC) Section 4: Network Account Utility,System Platform,Module 8: Device Integration Products,Contents Section 1: Wonderware I/O Servers Section 2: Wonderware Data Access Servers Section 3: Device Integration Objects,System Platform,DAS Engine,Device Integration Products,IO Server,DDE,SuiteLink,PLC Protocol,IO Servers 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.,DDE,SuiteLink,OPC,PLC Protocol,DA Server,DAS Engine,Device Integration Products,IO Server,DDE,SuiteLink,PLC Protocol,DDE,SuiteLink,OPC,PLC Protocol,IO Servers 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.,DDE,SuiteLink,OPC,PLC Protocol,DA Servers and DI Objects,PLC5_A,SLC_A,PLC_1,CNET,DHP,NIC,PLC_2,SLC_B,PLC5_B,Module 9: Multi-Node Applications,Contents Section 1: Application Redundancy Lab 18 Configuring Application Redundancy Section 2: DI Redundancy Lab 19 Configuring the Redundant DI Object Section 3: Multi-Node Application Lab 20 Convert to Network Environment,System Platform,Application Redundancy,ArchestrA Runtime,ArchestrA Runtime,Non-Redundant System,The server handles all the data. If server if lost, client lose connection to all data: InTouch Historian Other Application Object Servers,Application Redundancy,Platform1,Characteristics,Currently supported only in pairs Second network connection (RMC) necessary Configuration Terminology: Primary AppEngine Backup AppEngine Runtime Terminology Active AppEngine Standby AppEngine Active AppEngine refer to Standby AppEngine as Partner.,RMC,ArchestrA,Platform2,AppEngine1 (Backup),Primary,Backup,AppEngine1,Active,Standby,Standby,Active,Redundant Message Channel,Automatic Synchronization,Current data (Checkpoint) Alarm states and times History store and forward blocks Deployed objects and configuration AppEngine status,RMC,ArchestrA,Active,Standby,Supported Configuration,Platform1,Characteristics,Peer to peer architecture Each WinPlatform host a different AppEngine and Application Objects No need for dedicated backup nod