— ABB University Symphony Plus S+ Operations 3.x with S+ Engineering 2.x C ourse S 321R3 Chapter 1 Course Overview 1 1 Course Description S321R3 SPlus Operation Version 3.x Basic Configuration Course Overview: The purpose of this course is to demonstrate the configuration process for SPlus Operations Version 3.3. In this course, we will be utilizing three VMs: • A Master SPO Server • A Redundant SPO Server • A Single SPE Server. We will use the HTS software to simulate dynamic process data to populate various displays. SPE Control Engineering will be used to create the tag database. The tag database will then be read into the Signal Manager for further editing of the tag properties. Once the tag editing process is complete, the tag database will be validated and synchronized with Operations Engineering and Control Engineering. We will perform SPlus backup and restore in SPE's Project Manager tool. We will create new users for SPO in the User Management tool. We will review the Topology diagram tool used to define SPO’s services and installed applications. We will deploy the tags from SPE's Operations Engineering to SPO and confirm that the tags have live data. We will perform other configuration changes in the Operation Engineering database such as creating trend displays and alarm group displays. We will utilize the difference viewer to compare Offline databases to the Running Databases on the SPO Server. We will make any necessary changes, then deploy them to SPO. After SPO servers are populated with all the needed database information, we will utilize many of the Operations Explorer tools. We will configure and access graphic displays, access Tag Summaries, configure and view Alarm and Event pages, and set custom filters for each. We will open and utilize the Trend tool, SPO Navigational tools, user log-on tools, and access the Event Explorer displays and diagnostic displays. 1 2 Learning Path 1.2.1 Symphony Plus Training Path This course focuses on the regular use and configuration of the S+ Operations software. The configuration of the S+ Operations is now done in the S+ Engineering software, so several portions of this course will take place in the S+ Engineering program. This training is supplemental to the existing S+ Engineering training and has been designed to minimize overlap between the courses. This course will discuss and utilize topics such as opening a project in the S+ Engineering software, the relationship of the HMI to the Harmony Rack and Symphony DIN Hardware, and using Automation Architect to assign tags to Harmony Function Codes. The appropriate Hardware and Engineering classes are listed as prerequisites for this class in the course description. If attending this course out of sequence , here is a summary to help you find which classes have the appropriate material you wish to learn. 1.2.1.1 Hardware Class Description Prerequisite M111 Harmony Rack I/O None M112B Harmony Rack I/O (Blended Learning) None S311 Symphony DIN I/O None M113B Symphony DIN I/O (Blended Learning) None The following topics are covered in the relevant hardware classes: Control System architecture Communication paths Configuring the ICI connection General controller functionality An introduction to function codes Performing offline and online configurations Adding I/O to a controller Other hardware-related configurations Diagnostic tools and reports 1.2.1.2 Engineering Class Description Prerequisite M202 Composer Engineering Any Hardware Class M202v Composer Engineering (Online) Any Hardware Class US909 Transitioning from Composer to S+ Engineering M202 US909v Transitioning from Composer to S+ Engineering (Online) M202 or M202v S312 S+ Engineering Any Hardware Class S312V S+ Engineering (Online) Any Hardware Class The following topics are covered in the relevant Engineering Classes: Note: The S312 and S312v are for users new to S+ Engineering or who have no previous formal ABB training. The US909 or US909v classes are for users who have completed M202 for Composer class and just need to learn what has changed. Building CLDs Using and configuring Automation Architect (Drawings) Creating and using CLD Shapes, Macros, and Templates. Identifying and assigning available block addresses Using the verify tool Configuring the ICI connection Using the Bulk Engineering tool Using the Field Engineering tool Other diagnostic tools 1.2.1.3 Application Engineering Class Description Prerequisite M304 Harmony Function Code Strategies Any Engineering Class M114B Harmony Function Code Strategies (Blended Learning) Any Engineering Class The Application Engineering classes (M304 or M114b) are not prerequisites for this class, but those are the classes that cover adding, configuring, and troubleshooting the function codes that tags are assigned to, such as: Basic PID Loops Bumpless Transfer Feedforward and Ratio PID Loops Analog and Digital Function Codes Adapt Blocks Totalizers Redundant I/O Multi-State Device Drivers Sequence Generators Alarm Engineering Strategies Configuring and Troubleshooting Execution Segments 1 3 References ABB Ability™ Symphony® Plus Document S+ Engineering 2.3 Release Notes 8VZZ002503T2300 S+ ENGINEERING 2.3 Automation Architect User Manual 2VAA000813-230_A S+ Engineering 2.3 Automation interface user manual 2VAA001978-230_A S+ Engineering 2.3 Bulk engineering user manual 8VZZ000133T2300_A S+ Engineering 2.3 Connectivity engineering user manual 8VZZ000132T2300_A S+ Operations 3.3 Operations User Manual 2VAA001150-330 S+ Engineering 2.3 Field engineering user manual 2VAA001570-230_A S+ ENGINEERING 2.3 Harmony Engineering User Manual 2VAA000812-230_B S+ Engineering 2.3 Operations Engineering User Manual 8VZZ002960T2300 S+ Engineering 2.3 Project administration user manual 8VZZ000130T2300_A S+ Engineering 2.3 System topology user manual 8VZZ000131T2300_A S+ Engineering 2.3 User management user manual 2VAA003209-230_A S+ ENGINEERING 2.3 View and Monitor User Manual 2VAA000828-230_A S+ Engineering Function code reference user manual 2VAA000844R0001_N S+ System Installation user manual 2VAA008303 S+ Control VPNI Virtual PNI Server User Manual 2VAA003419_I S+ Operations 3.3 Database Reference User Manual 2VAA000830-330 S+ Operations 3.3 Release Notes 8VZZ003160T3300_A S+ Operations 3.3 Harmony Connectivity User Manual 2VAA001550-330 1 4 Terminology Term / Acronym Description ActiveX Microsoft standard for user interface components, based on the definition of software interfaces. Alarm An alarm is an abnormal state of a condition associated with an Exception Reporting Tag. For example, the Manual Auto Station, FC80, may have the following conditions associated with it; High Alarm, High Deviation Alarm, Normal, Low Deviation Alarm, Low Alarm, and Bad Quality. An alarm is active as long as the abnormal state of the corresponding condition persists. An alarm is visible until a user has acknowledged it and it returns to a normal condition. AO/L (FC30) Analog Output Loop – a simple analog indicating exception reporting function code. Authentication The process by which the system validates the user's login information. A user's name and password are compared against an authorized list. If the system detects a match, access is granted to the extent specified in the permissions list for that user. BRC Bridge Controller – The most recent generation of Harmony process controllers CIU Computer Interface Unit – Harmony communications hardware that allows a computer to communicate on the CNet. Client A client is a node that subscribes to data from a server. Client/Server network A client/server network is used for communication between client and server computer nodes. CLS Central Licensing System CO Control Output CNet Proprietary, redundant control network of the Harmony system (also called InfiNet) Control network A control network is a local area network (LAN) that is optimized for high performance and reliable communication with predictable response times in real time. Control network devices and servers are connected to the control network. DD (FC123) Device Driver – a digital control exception reporting function code with feedback indication. DNS Domain Name System DO/L (FC45) Digital Output Loop – a simple digital indicating exception reporting function code. EU Engineering Unit Event An event is a detectable occurrence, which is of significance to the system. An event may or may not be associated with a condition. For example, the transitions into High Alarm and Normal conditions are events, which are associated with conditions. However, operator actions, system configuration changes, and system errors are examples of events, which are not related to specific conditions. EWS Engineering Work Station Faceplate A graphical representation of a specific Tag Object, with the presentation of certain properties related to the object, and mechanisms for operator interaction such as on/off, increase/decrease, etc... Fieldbus A fieldbus is used to interconnect field devices, such as I/O modules, smart sensors, actuators, variable speed drives, PLCs, or small single loop devices, and connect these devices to the SPlus system. Function Code (FC) A pre-programmed algorithm used to configure Harmony process controllers. Graphic display A file that provides a visual presentation. It consists of static graphics representing for example tanks, pipes, etc., and graphic elements that present dynamic information. Graphic displays are often used to present the state of a process or a part of a process but are useful in any context where dynamic graphical information needs to be presented. HCU Harmony Control Unit – Harmony cabinet that contains power supplies, communication modules, process controllers, and IO modules. HSI Human System Interface ICI InfiNet to Computer Interface (see CIU) IP address A 32-bit address assigned to each host/node connected to the network. LAN Local Area Network M/A Station (FC80) Manual/Auto Control Station – a complex analog control exception reporting function code with CO, PV, and SP indications. MSDD (FC129) Multi-State Device Driver – a complex digital control exception reporting function code with feedback indication and multiple outputs. Node A computer communicating on a network e.g. the Internet, Plant, Control, or I/O network. Each node typically has a unique node address. OPC OLE (Object Linking and Embedding) for Process Control, a standard interface for real-time data, alarm and event data, and history access based on COM. OPC item OPC items represent connections to data sources, i.e. object properties. An OPC item is identified by a string <object path>:<property name>. Associated with each OPC item are Value, Quality, and Time Stamp. Note that OPC items are not identical to the data sources – they represent connections to them. Operator Workplace Provides a user interface for efficient control and supervision of processes. PCU Process Control Unit – Harmony cabinet that contains power supplies, communication modules, process controllers, and IO modules. PGIM Power Group Information Manager – Historian Server PV Process Variable RCM (FC62) Remote Control Memory – a simple digital control exception reporting function code. RMCB (FC136) Remote Motor Control Block – a complex digital control exception reporting function code with permissive, interlock, and feedback indication. RMSC (FC68) Remote Manual Set Constant – a simple exception reporting function code for inputting an analog value RNRP Redundant Network Routing Protocol. An ABB protocol for redundancy handling and routing in LANs. Router A computer/device that forwards IP data between the networks to which it is connected. Service A software component that provides a certain set of functions in the system, typically for use by various client applications. SER Sequence of Events Recorder SP Set Point SPlus (S+) Client Symphony Plus Client Node SPlus (S+) Historian Symphony Plus Historian (PGIM) SPlus (S+) Operations Symphony Plus Operations SPlus (S+) Server Symphony Plus Server Node Tag Any controlled or indicated object in the SPlus system that has a faceplate attached. Thin client Web browser connected to the Internet (or Intranet). It does not require any ABB-related pre-loaded software. It supports ActiveX controls but communicates with the SPlus system using Internet Explorer as the browser. Lab Activity: Exercise 1.1 Go to Exercise 1.1 Chapter 2 Architecture and Sizing 2 1 General Information 2.1.1 Objectives On completion of this chapter you will be able to: Understand the meaning of S+ Operations for SCADA Know the different types of nodes that can be configured with S+ Identify the different kinds of S+ Operations Configurations available Correctly configure the Size & Options of the system depending on the different architectures 2.1.2 Legend < Indicates when you go from one menu to a sub-menu Italic Indicates object and file names " " Indicates dialog box buttons, tabs, menus, etc. Bold Indicates important topics Indicates start/explanation of student activity 2.1.3 ABB Ability™ Symphony® Plus Documents Document Number Document Title 8VZZ003160T3300_A S+ Operations 3.3 Release Notes 2VAA008303 S+ System Installation user manual 2 2 Symphony Plus System Architecture 2.2.1 Architecture Overview and Components S+ Operations for DCS provides full integration with ABB control system products and a wide range of protocols and drivers to interface field devices. S+ Operations supports a unique system architecture that provides flexible and scalable configurations for SCADA applications. S+ Operations is a comprehensive human system interface that provides advanced and intuitive functionalities. S+ Operations is also flexible to adapt evolving needs of the DCS applications. Switching between different configurations is easy and fast. Some of the major features are: Management of distributed server architectures Interfaces to a wide selection of devices, including RTU, PLC, and IED (Protections) Management of flexible security and distributed operating teams Fully redundant and complex architectures support Calculation engine Web server Flexibility Scalable Architecture: Ability to maximize performance, minimize costs, and provides future requirements of the plant. The plant control and monitoring system is easily adaptable to constant changes in industrial processes and methodologies. Centralized Processing: All operators can control and monitor the whole plant. Full redundancy (increases system availability) Easy maintenance: Only one computer needs to be updated when the plant configuration changes to maintain overall plant data integrity. When the startup is complete, the workbench will open to the default home screen. The schema represents a Symphony Plus SCADA System regarding the following software and hardware components: S+ Engineering Server & Client Operator Stations & Workplaces S+ Operations Server S+ Historian Server DCS, PLCs, RTUs, touch panels, and field devices ERP / CMMS layer / Web Server The flexibility of the system allows you to design the architecture of Servers and Clients to meet specific customer requests as follows: Flexible sizes range from a full-featured single Server (standalone) to multiple redundant Servers connected to multiple Clients. Complex architecture with front-end Servers related to field data acquisition. Main Servers for collection of all plant data. Client connection at main or front-end Servers. Historian for full historical data management (LTA alarms, events, and plant values displayed in different formats - trends, and reports). Web server to remotely view all plant information and export data to other databases. 2 3 Server, Components & Application for SPO The S+ Operations architecture distinguishes between the following node types: Node Type Description S+ Operations Server : These are referred to as Real-time Servers (RT servers). S+ Operations Historian : Referred to as the History Server. S+ Operations Workplaces : Local and remote Client machines. S+ Operations Application Server : Used for S+ Operations Office Clients, S+ Operations ThinWebClients, and providing applications on API. S+ Operations Front- end Servers : Reads process data from a DCS, and offers an interface to an application and an OPC Server. The default configuration for all S+ Operations components can be present in one single computer. Components such as History Server, Application Server, or Client can be moved to another computer’s hardware to fulfill specific requirements. Note: Network Redundancy can be achieved using PRP 2.3.1 S+ Operations Server (SPO) The S+ Operations Server is a real-time database that reads through a scanner and scans driver interfaces to process data from the connected DCSs/PLCs. The process data is stored together with status and time stamp details and made available for Clients to read and visualize it. The RT database also generates alarm messages, creates audible alarms, performs calculations, and other features. Each S+ Operations Server also holds its own license for all features that are within the license scope. S+ Operations RT Servers support Multi-Master Redundancy (MMR) Clients can have a Server Access List. If communication with a Server is lost, then the client reconnects to the next Server. Each Server can acquire data in parallel or if parallel paths are not available, then data can be acquired from other Servers, based on configuration. One Server is designated as master for actions to the field. Backfill of data and configuration changes are possible. Another feature of S+ Operations’ MMR is the capability of multi-redundancy as displayed in the following figure Each Server can have a maximum of 64 redundant partners. They can replicate either the whole data points (tags) of the first Server or from a selected redundant partner. This setting is individually configurable by tag. The real-time Server is licensed by tags and accommodates the license for the History Server. Clients connect to selected servers based on configuration. Many options are available regarding features, applications, and connectivity.