This notice is being ed to our complete customer list and also being published on our web site.

Transcription

1 ABB Totalflow WinCCU 6.0 Release Notice Introduction This is to inform you that WinCCU 6.0 is now released. Since WinCCU 6.0 has several new lookand-feel differences from previous versions we thought it would be helpful to put out this notice prior to its release; to give you a heads-up. This notice is being ed to our complete customer list and also being published on our web site. What s Behind The Changes We decided to change WinCCU s architecture for several reasons 1. To improve navigation capability by allowing the user to define relationships between groups and devices in a new way, resulting in a visual / graphical representation of those relationships in a tree view. 2. To more readily support application specific plug-in software modules to meet unique customer requirements. 3. To allow sub-portions of WinCCU functions to be plugged-in to other software systems. 4. To allow the user to have more control over what WinCCU functions are made available at run time. 5. To migrate all WinCCU reports to a commercial report generator. WinCCU s New Architecture Our first task was to consolidate functionality related to Devices and Groups into a single, reusable application. We refer to this portion of WinCCU 6.0 as the Shell. You can think of it as an overarching framework into which all other WinCCU applications are inserted. Pictorially, it might look something like this. The Shell is composed of the functions shown here. ID Manager Scheduler Admin WinCCU Shell Tree View Application Navigation Invocation WinCCU 6.0 Release Notice page 1 8/10/2005

2 The ID Manager : Serves basically the same function as in the past. Only difference is that it is always right there in front of you as part of the shell. Try right clicking on portions of the new tree view and you ll see what we mean. Scheduler : Redesigned to be included with the Shell, rather than as a separate program. More on this later. Tree View Navigation : Once the relationships between groups and devices are defined, then these relationships are shown on a tree view which can be used to navigate to a group of devices. Application Invocation: Navigating to a specific group simply selects a group of Devices upon which to perform WinCCU familiar functions. If you have used the power of Groups in previous versions of WinCCU, you will catch onto this new look quickly. Once a group has been selected, then normal WinCCU functions you are familiar with can be performed on the selected device(s) within that group. So, basically we have tried to improve the top level look and feel for better navigation, but once you look under the hood, most everything else will look familiar. To further develop our picture, we show that WinCCU applications plug-in to the Shell ID Manager Scheduler Admin WinCCU Shell Tree View Application Navigation Invocation Remote Comm Archive Utilities WinCCU Applications Long Term Database Utilities Standard Plug-ins Application Specific Plug-ins Remote Comm, Archive Utilities and Long Term Database Utilities generally represent the same functionality you are accustomed to. New features will be detailed later in this document. WinCCU 6.0 Release Notice page 2 8/10/2005

3 When WinCCU 6.0 starts up it presents a view into the Shell that looks like this. Toolbar Buttons Tree View Grid View This is the tree view we mentioned earlier. It presents Groups that have been defined. As in previous versions of WinCCU, a group can reference some number of devices. In WinCCU 6.0 devices are shown in the right hand pane (called the Grid View) of the example above. In this example the devices shown are those that are contained in the Pod2_1 Group which is selected on the tree view. The new twist with WinCCU 6.0 is that a group can also reference other groups. In that case, the tree view shows a parent/child relationship between the groups. For example, the Pod2_1 group, which is selected, is actually a child of the parent group named Zone_2, which is itself a child of the parent group Zones. That is, when the group named Zones was defined, it was defined as including two other groups named Zone_1 and Zone_2. Therefore, that relationship is shown on the tree view. In like manner, when the group Zone_2 was defined, it was defined to include two groups Pod2_1 and Pod2_2, therefore that relationship is also shown on the tree view. You are free to define these group relationships in any way you want. For example, there is another group named Pumpers shown above. This group simply references other groups that have been given the names of personnel (Billy, Bob, George, Jack and Jim), responsible for certain facilities. Each of those groups might then simply contain the device IDs that are associated with the facilities assigned to each person. WinCCU 6.0 Release Notice page 3 8/10/2005

4 Once the desired devices have been selected WinCCU applications can be invoked to operate on those devices. The screen capture shown below, depicts the fact that 4 devices within the Pod2_1 group have been selected. They are shaded in blue. It further depicts that one the Archive Utilities Reporting Application will be invoked, to produce Reports on the selected IDs. (Mouse pointer is selecting Archive Toolbar Menu Selection of Reports). The Archive Utilities Menu Items shown below (View, Reports, Outputs, etc), should look familiar to anyone who has used these functions on older versions of WinCCU. That is because they are the same. We ve just changed the way you select the devices that will be operated on. Some of us have taken to calling WinCCU 6.0 s Shell The ID Picker to describe its main function, which is to pick the device IDs upon which to execute a WinCCU application. Toolbar Buttons Tree View Grid View Neat new feature: You can sort the grid view by any of the parameters shown in the column headers. For example, if you want to sort the grid by Com Type just click on the Com Type header. You can also filter the grid based on unique values within any of the grid headers. For example if you want to only see the ID s of Com Type click on the down arrow in the Com Type header and pick the value. Customized Toolbars and Menus As mentioned in the introduction, WinCCU 6.0 allows you to have more control over which WinCCU applications are made available at runtime. This new feature is accessed through the Setup toolbar button. We ve added new capability that allows you to select which toolbar buttons are made visible as well as which menu selections are associated with each toolbar button. The default setup screen looks like this. Notice the selections named PCCU Data Collection, Remote Communications, Laptop File Utilities and Archive Utilities. Each of these represents a toolbar button. If the check box is checked, then that button is added to the toolbar. If it is unchecked, that button is removed from the toolbar. WinCCU 6.0 Release Notice page 4 8/10/2005

5 Also notice that under each button definition is a list of names with checkboxes. These represent the menu items that are displayed when their respective toolbar button is selected. Again, if the check box is checked, then that menu item is included and if unchecked then it is not. In this same setup function, there also exist check boxes to select which columns are shown in the Grid View of the Shell s right hand pane. Notice that there are only two toolbar buttons shown below This screen shot depicts a version of the WinCCU Shell for which only the Archive Utilites and the Setup Utilities have been enabled. Whomever is using this version of the WinCCU shell will only have access to these two applications (Archive Utilities and Setup Utilities). WinCCU 6.0 Release Notice page 5 8/10/2005

6 WinCCU 6.0 Invocation of optional plug-ins In addition to the standard plug-ins, such as Archive Utilities, WinCCU now supports optional plug-in capability. At release time there exists one optional plug-in; Plunger GUI. Due to the popularity of our plunger lift application (available on XSeries products), its list of features and options have continued to grow. To better support all the new functionality, we have also implemented a Graphical User Interface (GUI) to the plunger application. This GUI can now be seamlessly integrated with WinCCU 6.0. When installed, the Plunger GUI simply shows up as a menu item associated with the Applications toolbar button. It looks like this. These applications are supplied with the standard WinCCU 6.0 release. Plunger GUI is an optional application that when installed, is added to this menu. Shown here is an example of the Plunger GUI user interface. WinCCU 6.0 Release Notice page 6 8/10/2005

7 Scheduler Redesigned to Fully Utilize the Windows Scheduler First, you will notice that the Scheduler Administration Application is accessed directly from the WinCCU shell; this rather than starting up a separate scheduler program. Scheduler Administration is now accessible through the Setup Toolbar Button. Another significant change is that we have decided to take advantage of the scheduler provided with Windows, rather than our own. Under the hood, it works something like this. You schedule WinCCU applications by accessing the Administration tool through the Setup Toolbar. The Administration tool presents a screen as shown here. Although we won t take time to go through the details here, any of the kinds of scheduling needs you are accustomed to with WinCCU are still available. The result of configuring a WinCCU application for scheduled invocation is that a standard windows batch file is created which describes what WinCCU application to invoke and what options are chosen for that application. The batch file includes a windows command line to start the appropriate process, along with command line options that inform the WinCCU process of what options were chosen during the configuration process. A side benefit of this new scheme is that other systems (other than the Windows Scheduler) can now invoke WinCCU process by using this command line feature. Shown here is an example command line that was constructed and inserted into a batch file during a scheduler configuration. C:\Totalflow\WinCCU60\wccu collect None batch,selectall,group=pod1,setupfile=c:\totalflow\wi nccu60\scheduler\ccunewschedule.ini Admittedly batch files are a bit cryptic for most of us, but it is a powerful feature in the hands of someone who understands Windows batch files and command lines. For the rest of us, we can relax about all these batch file details as the Administration tool constructs the batch files for us when scheduling options are chosen. Neat new feature: WinCCU does not have to be running for scheduled functions to execute. You actually do not even have to be logged in. Migration Note: WinCCU 6.0 does not operate directly on old scheduler files. However it does support an import function to bring in your old schedule files and convert them to the WinCCU 6.0 schema. WinCCU 6.0 Release Notice page 7 8/10/2005

8 Remote Entry Mode for XSeries and microflo With WinCCU 6.0 we now support the ability to remotely interact with XSeries and microflo devices with the same look and feel of PCCU s Entry Mode. In fact, we call it Remote Entry Mode. Remote Entry Mode functionality is defined by ini files, exactly as is PCCU s Entry Mode. In fact, they are the same ini files. Shown here is a Remote Entry Mode screen. Notice the familiar Entry mode tree view and list views. Remote configuration with WinCCU now has the same look and feel as PCCU! The remote entry mode feature can be disabled in the ID Manager if you want WinCCU 6.0 Release Notice page 8 8/10/2005