dt analyst application guide

Wonderware® FactorySuite™DT Analyst™ Application Guide

For Version 2.2

Last Revision: August 5, 2003 2:38 pm

Invensys Systems, Inc.

Administration

All rights reserved. No part of this documentation shall be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of Invensys Systems, Inc. ("Wonderware"). No copyright or patent liability is assumed with respect to the use of the information contained herein. Although every precaution has been taken in the preparation of this documentation, the publisher and the author assume no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained herein.

The information in this documentation is subject to change without notice and does not represent a commitment on the part of Wonderware. The software described in this documentation is furnished under a license. This software may be used or copied only in accordance with the terms of the Wonderware End User License agreement.

© 2003 Invensys Systems, Inc. All Rights Reserved.

26561 Rancho Parkway SouthLake Forest, CA 92630U.S.A.(949) 727-3200http://www.wonderware.com

Trademarks

All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. Wonderware cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affecting the validity of any trademark or service mark.

Wonderware, InTouch and FactorySuite are registered trademarks of Invensys Systems, Inc. All other brands may be trademarks of their respective owners.

WindowMaker, WindowViewer, DBDump, DBLoad, DT Analyst, Wonderware Logger, Alarm Logger, InControl, InTrack, InBatch, IndustrialSQL Server, FactoryOffice, FactoryFocus and SuiteLink are trademarks of Invensys Systems, Inc.

Windows and ActiveX are registered trademarks of Microsoft Corporation in the United States and/or other countries.

5

Contents
Before You Begin.................................................... 9
About This Book............................................................................................ 9

CHAPTER 1: DT AnalystTM Project Scope and Best Practices Methodology ................................ 11

Scoping a DT AnalystTM Implementation................................................... 11Justifying an Implementation with a Pilot ................................................... 14

Discovery Phase ....................................................................................... 14Pilot Implementation Phase...................................................................... 14Pilot Evaluation Phase.............................................................................. 15

CHAPTER 2: Implementing DT AnalystTM based on Best Practices .................................................. 17

Collecting Requirements.............................................................................. 17Planning the Configuration.......................................................................... 18

Conventions for Item Naming.................................................................. 18Item Descriptions ..................................................................................... 18Areas......................................................................................................... 18Systems..................................................................................................... 19Downtime Definitions .............................................................................. 21Triggers .................................................................................................... 22Tags .......................................................................................................... 24Shifts and Schedules................................................................................. 24Read-Only Event Monitors ...................................................................... 25Virtual Tags .............................................................................................. 26OEE .......................................................................................................... 26

Preparing for Implementation...................................................................... 31Materials................................................................................................... 31Resources on Site ..................................................................................... 32

Installing the Software ................................................................................. 33Entering the Configuration .......................................................................... 33

Pre-Configuration..................................................................................... 33Transporting Configuration...................................................................... 33Importing Tags ......................................................................................... 34

Testing the Configuration ............................................................................ 35Testing I/O................................................................................................ 35Testing Logic............................................................................................ 35Testing OEE ............................................................................................. 35

Adjusting Configuration .............................................................................. 36Effects on Previously Captured Data ....................................................... 36Deleting Downtime and OEE Data .......................................................... 36

Preparing for Remote Support ..................................................................... 36

6 Contents

Database Backup...................................................................................... 36Export Configuration ............................................................................... 36Clear Downtime and OEE Data ............................................................... 36Clear the DT AnalystTM Event Log ......................................................... 37Document Deployment ............................................................................ 37Setup Remote Connection and Control Software .................................... 37

Training........................................................................................................ 37Downtime Reports ................................................................................... 37OEE Reports ............................................................................................ 38

CHAPTER 3: Event Monitor and dtWeb Customizations...................................................... 39

Event Monitor.............................................................................................. 39Scripting the Event Monitor ActiveX® Control ...................................... 39

dtWeb........................................................................................................... 63Securing the dtWeb .................................................................................. 63Customizing the dtWeb............................................................................ 63

CHAPTER 4: Troubleshooting............................. 67Setup ............................................................................................................ 67

The Setup will not run due to lack of Administrator rights. .................... 67Setup completes but hangs on reboot, then none of the DT AnalystTM programs run. ........................................................................................... 68The Setup has experienced a problem; examine the setup Log. .............. 68Wonderware Common Components. ....................................................... 68DT AnalystTM installation location.......................................................... 68.................................................................................................................. 69.................................................................................................................. 69Uninstalling SQL ServerTM leaves DTDB database files........................ 69dtWeb will not install because IIS 5.0 or 6.0 is not installed. .................. 69dtWeb install may not create database connection string registry entries.69dtWeb not working due to file permissions on MSVBVM60.DLL. ........ 70Failed database creation. .......................................................................... 70

Database....................................................................................................... 71The dtdbApp Login is not working properly OR a new SQL ServerTM Login is not working properly for the DT AnalystTM components. ........ 71SQL ServerTM uses Windows® Authentication and the DT AnalystTM components are not connecting to the database. ...................................... 71Restoring a backup of the DTDB database to a different SQL ServerTM than the one it was backed up on. ............................................................ 71DT AnalystTM is not able to connect to the database using the dtdbApp Login and Password; using the sa Login and Password works................ 72

Registry........................................................................................................ 73Database connection string registry entries. ............................................ 73

7

Modifying the DT AnalystTM database settings without going through the Configuration or Logic Manager.............................................................. 74Database integrity check. ......................................................................... 74

Logic Manager ............................................................................................ 75Logic Manager will not start due to licensing problems.......................... 75Logic Manager starts but is not recording downtime events. .................. 75Tags are showing up red in the I/O Monitor Window. ............................. 75Tags are showing up yellow in the I/O Monitor Window........................ 75Logic Manager is having problems reading OPC Tags............................ 76Momentary Tag Value changes not being detected by Logic Manager.... 76

Configuration Manager................................................................................ 76Logic Manager is ignoring enabled items in the configuration. .............. 76New license file limits not being recognized in Configuration Manager. 76Configuration changes are not being reflected in the Logic Manager. .... 77The configuration needs to be sent to support for troubleshooting.......... 77Disabling a Shift has no effect. ................................................................ 77Delete Live Data Date .............................................................................. 77

dtWeb ........................................................................................................... 77Problems accessing the dtWeb application site. ....................................... 77Problem locating the dtWeb after installation. ......................................... 77Accessing certain dtWeb pages displays generic web server error. ......... 78

Event Monitor .............................................................................................. 78There is a database connection error in the Event Monitor...................... 78Database connection error on plant floor workstation. ............................ 78Events are not being displayed in the Event Monitor............................... 78

Miscellaneous .............................................................................................. 78System Downtime vs Downtime.............................................................. 78License File. ............................................................................................. 79

8 Contents

Before You Begin 9

Before You Begin

About This BookThis document is a collection of recommendations and tips for successfully implementing the DT Analyst Software. The recommendations in this document are general and should be adapted to the specific project environment.

This document is intended to support an engineer whose job it is to facilitate the installation and configuration of the the DT Analyst software. This information is NOT intended to replace the existing DT Analyst User or Deployment Guides, but rather to supplement it. It is highly recommended that before using this content, the reader have a good working knowledge of the product and has read or understands all of the concepts discussed in the User Guide and Deployment Guides included on the DT Analyst setup CD.

Important! The DT Analyst User Guide contains a chapter called Advanced DT Analyst Concepts. An expert DT Analyst implementer must be thoroughly familiar with these concepts. If you are reading this now and would really like to understand how the DT Analyst software implements some of its more complex features, then stop now and read that section of the User Guide.

10 Before You Begin

DT AnalystTM Project Scope and Best Practices Methodology 11

C H A P T E R 1

DT AnalystTM Project Scope and Best Practices Methodology

The DT Analyst software may be implemented on a limited scale, providing summary information about the operational capabilities of each machine or a particular problematic line. The DT Analyst software may also be implemented on a large scale such that it provides very detailed information about each machine or system in a large plant. This chapter will help you to scope a project and justify an implementation through a successful pilot.

For more information, click on a Help topic.

Contents• Scoping a DT AnalystTM Implementation

• Justifying an Implementation with a Pilot

Scoping a DT AnalystTM ImplementationThe answers to the following questions will help you scope the requirement for a DT Analyst implementation.

1. What are the goals of the Event Tracking application?

• Better understanding of the production process (anomalies, downtimes, maintenance, procedures, etc.)

• Increased efficiencies

• Increased asset utilization (including elimination of under-performing assets)

• Increased capacity without new capital equipment

• Better defined capital investment as necessary

• Reduced cost: labor, cycle time and waste

12 Chapter 1

• Qualified new capital equipment (verified vendor performance specifications)

• Expected improvements (cycle time reduction, reduced waste, reduced overtime, fewer hours worked on weekends, fewer lines used, etc.).

2. What is the scope of the initial DT Analyst application under consideration? (For example, (1) 12 oz. can line and (1) large PET bottle line)

• Pilot?

• OEE with a few downtimes to track Availability?

• Complete DT Analyst software and OEE for the entire department or factory?

3. What level of support is needed? Consulting? Implementation Support? Training?

4. What is the standard PC networking architecture within the plant? Microsoft® 2000-based Network? Microsoft® NT-based Network? Novell Network? Other?

5. Is there an available and appropriate plant Windows® 2000 Server that can host the DT AnalystTM server components? Minimum requirements for an appropriate server are:

• Dedicated Server hosting SQL ServerTM, IIS, and Logic Manager. Dedicated Database and Web servers may also be used, if desired.

• Intel Pentium III 1.0 GHz or higher with at least 256 MB of RAM (512 MB Recommended)

• Windows® 2000 Server OS

• Microsoft® Internet Explorer 5

• At least 5 GB of free hard disk space for application with data. (Application uses about 300 MB of space).

• CPU must not be too heavily loaded with existing applications (depending on the scope of the DT AnalystTM implementation).

6. Is there a Microsoft® SQLServer Software to host the DT Analyst Software? (The SQL Server Software is provided, but it is possible to host the database on an existing server)

7. Do all workstations requiring access to the DT Analyst reports have TCP/IP access to the IIS Server?

8. If the Plant Floor component (Event Monitor) is to be installed, which HMI systems are running in the areas of the plant that will have Event Monitors installed?

9. Are all these PCs on the same network as the DT AnalystTM server? (please note that the PCs will need to be on the same Ethernet network to run the DT Analyst software.)

10. Are there other PCs or Thin Clients that will be hosting the Event Monitor? Please note that Event Monitor supports Microsoft® NT4 and Windows® 2000 Operating Systems, as well as Microsoft®-based thin clients.


11. What PLCs and I/O (SuiteLinkTM or OPC) are you planning to use? (Area,System, PLC Manufacturer, Model, Network Type, Approx. No. of downtimes to be monitored by DT Analyst software, SuiteLinkTM or OPC Server Vendor)

12. Is it necessary to interface to any other types of systems for the purposes of monitoring I/O or Values to Record? For instance, InSQL can be used to monitor values for devices that are being accessed via DDE / NetDDE. In addition, HMI and OIT Systems, such as PanelView, can be used as data sources.

13. The Event Monitor ActiveX® component runs on desired HMI Stations or other PCs and alerts the operator when a downtime within his area exceeds a user configured time limit (for example, 5 minutes). The operator may then provide additional information relating to the reason behind that extended downtime. The Event Monitor is also used by the plant floor personnel to indicate other plant conditions, such as Changeovers, Planned Maintenance, Sanitation, or Planned Non-operation of the equipment. How many Event Monitors will be used? Where will they be located? You may consider putting an Event Monitor in the Maintenance Office as well for monitoring purposes.

14. Are you interested in OEE? How many calculations do you want to monitor?

15. If you are interested in OEE, how are each of the component going to be tracked?

• Performance - What is the Theoretical Run Rate? Are the required PLC counters in place?

• Availability - How are Availability Losses going to be logged? Are they available in the PLC? Can Event Monitors be implemented to log Changeover and Sanitation?

• Quality - Which two of the three Counters are available? Good? Bad? Total?

16. Do you need any additional Configuration Component Licenses? Many can manage with a single station running the Configuration Component since the configuration is only changed infrequently.

17. How many FactorySuite CALs are required?

18. Determine if the following items are available:

• Architectural Drawing showing all networks, PLCs, servers, workstations, hubs/switches and other key components of the system as it will be configured after the installation of the DT Analyst software.

• Design and installation of any Ethernet network expansion required.

• Design and installation of any PLC network upgrades required.

• PLC Programming. Depending on the scope of the application, it may be necessary to add some counters and other tags within the PLC logic, if these do not already exist. It may also be desirable to condense tags into smaller areas to reduce polling times for very large applications.

• PLC Logic Investigation. Review PLC Logic and identify the following for each PLC / PanelView / HMI: PLC, PLC Network, System, Downtime Description, Fault Tag(s) and Fault condition(s).

14 Chapter 1

• DT Analyst software Installation plus Server and IIS Configuration.

Justifying an Implementation with a PilotOnce you have determined the goals, you can proceed with creating an effective strategy that will help to clearly define the benefits of the DT Analyst software.

With specific goals in mind, select a line or process that you know well. This helps you better define the needs and shortcomings. Specifically, make sure that the selected line/process is a good candidate for a DT Analyst software pilot. Typically, a high-speed, high-volume, high-value process (for example, high speed filling, canning and packaging lines) would be ideal for a pilot candidate. Also, pick candidates that have a reasonable level of infrastructure already in place (i.e., they have networked PLCs and HMI workstations).

Discovery Phase1. Understand and agree upon the metrics. This means that you know how to

measure, view, and interpret the results. This is a crucial step - do not leave this matter to the end. You must know what would qualify as a successful pilot (e.g., specific reports, operator interactions, ease of use, etc.).

2. Discuss the step after the pilot project. This is important for transitioning from a successful pilot to a production rollout.

3. Define the main components of the project (for example, a line with its main pieces of equipment that will be included in the pilot). For a pilot, avoid very large projects with multiple lines and many pieces of equipment. This would require a good level of planning (consulting, configuration/implementation, training and deployment). The goal here is to have a speedy but effective proof of concept and value.

4. Plan the configuration. This means knowing how to group conditions that result in recorded downtime events. Remember that you are not trying to emulate the HMI Alarm Logger with the DT Analyst software. You do not want to simply trigger downtime events strictly based on status changes of certain PLC bits. This is where optimization experience comes in. In most cases, it is appropriate to combine these status bits to define the reason that would become a Downtime Definition. Also, consider that you may look at the entire line as a system and also configure each of its main components as a system.

5. List the finalized Downtime Definitions. It is helpful to keep the Downtime Definitions to less than 100 for a pilot project.

Pilot Implementation Phase1. Configure the application based on the systems and downtime definitions

planned during the Discovery Phase.

2. Set up the server and make the field network connections.

3. Make sure data collection is working (you can see the DT Analyst software collecting data and can view reports).


Pilot Evaluation Phase1. Allow the data collection to proceed for 2 weeks. In the mean time, verify that

the data collection and reporting process is working by viewing the recorded data and reports.

2. At the end of the 2-week period, review the results. Note the major causes, durations and potential improvement tips. Select the right reports (charts, graphs, etc.) that you will use to demonstrate the proof of concept.

3. Prepare a summary pilot project report of your findings with key points clearly outlined.

4. Set up a formal review meeting to review the report, assess the results and discuss recommendations.

5. Size the proper license for a larger scale rollout.

16 Chapter 1

Implementing DT AnalystTM based on Best Practices 17

C H A P T E R 2

Implementing DT AnalystTM based on Best Practices

A typical DT Analyst implementation involves the phases discussed in this chapter. Included are some tips and recommendations to help you through the process. The next chapter will discuss how to customize the Event Monitor and dtWeb, if required.

Contents• Collecting Requirements

• Planning the Configuration

• Preparing for Implementation

• Installing the Software

• Entering the Configuration

• Testing the Configuration

• Adjusting Configuration

• Preparing for Remote Support

• Training

Collecting RequirementsThe development of a Detailed Design Specification (DDS) is highly recommended. The DDS should capture all the capabilities of the system and all the decisions made relating to a given configuration. The DDS is valuable both for future support as well as for rollout of the configuration to additional lines or other plants.

To assure user acceptance of the system, it is beneficial to involve end users at the design stage to discuss the level of the implementation, and the way the system is being configured. Critical users like Plant Engineers, Maintenance Managers, and Operations Managers should review the structure of the reports based on the configured logic. Collaborative involvement will result in a better configuration that is more rapidly accepted upon deployment.

18 Chapter 2

Planning the Configuration

Conventions for Item NamingSpecial attention should be given to naming DT Analyst Area and System components in the Configuration Manager. These items will be displayed as report headers and drop down pickers in dtWeb. In cases where there are several Systems with the same names in different lines, it is sometimes useful to include a line identifier in the System name (for example "L1 Filler" as the name for a Filler System on Line 1).

Item DescriptionsAll of the configuration items in the DT Analyst software contain a Description field to add additional descriptive text pertaining to the item. It is recommended that the Description fields be used where possible, so that the DT Analyst implementation will be "self-documented".

Areas

Planning AreasWhen planning Areas for a DT Analyst implementation, the most important consideration is reporting. Areas act as folders for combining systems and events. Many of the downtime reports in dtWeb display data for all of the Systems in a selected Area. Area Reports allow for comparing downtime between related Systems.


Sub-AreasBy default, Area reports in dtWeb return event data for Systems which are contained directly under the specified report Area. If the specified report Area contains Sub Areas, event data for any Systems in those sub Areas will not be reported.

The Include Sub Areas in Reports checkbox in the Area property dialog allows for this default behavior to be changed. Checking this option causes Systems in a specified report Area’s Sub Areas to be reported. It should be noted that only direct sub Areas are affected by this setting. Each sub Area’s property setting is used recursively to determine whether Systems in deeper sub Areas are included.

Systems

Splitting Downtimes on Day and Shift EndSpecial attention should be paid to the "Split Downtime on Day End" and "Split Downtime on Shift End" System properties. Setting these properties specifies whether the DT Analyst software automatically splits downtime events that are in progress as Shifts or calendar days (midnight) end.

20 Chapter 2

While splitting downtimes adds to report interpretation when reviewing a single Shift or date, it creates additional "downtime counts" and skewed "average event durations" (a single long event occurring over midnight is split into two smaller events).

Alternative Uses for Capture TagsThe System Capture Tags (Product, Job, Batch and Operator) can be used to capture the value of Tags when a System enters a Downtime state. Downtime reports can be viewed by the values captured by Product, Job, Batch and Operator.

If one or more of these values in not needed, the capture Tag may be used to capture some other value of interest (Container Size instead of Job for example). The dtWeb reports can be customized (discussed later in this document) to display an alternate label ("Container Size" instead of "Job").

Caution! When using these fields for alternate purposes, it is important to understand that there is an inherent parent-child relationship between Job and Batch. dtWeb reports are designed to pull data for a specific Batch number within a specific Job. In other words, there may be a Batch 1-4 for each Job that is run - while the Job number is unique.

Values to Record (VTRs)While VTRs can be used to capture additional Tag values when a System enters a Downtime or ends a Downtime state, it is important to keep in mind that VTRs may only be viewed in detail reports by selecting a specific downtime event. dtWeb reports may not be generated where the data is "grouped by" a VTR.

Summary SystemsIn some cases, it is beneficial to setup "Summary Systems" which combine the logic from several physical pieces of equipment or an entire line (see Referencing System and Downtime Definition State).

This technique can yield a higher level view of the process as well as looking at Downtime from different perspectives. It is common that the downtime for a specific piece of equipment on a line does not have a one-to-one effect on the overall line downtime. In these situations, DT Analyst Systems may be defined to track downtime on the specific machines in the line, as well as an overview or summary System to represent the entire line. The entire line System may have logic defining downtime that combines states of the equipment in line as well as production flow from the end of the line.


Downtime Definitions

System Force New Downtime on Event Start/EndChecking these boxes in the Downtime Definition Properties forces Systems to re-evaluate the primary reason for being down when the Downtime Definition starts or ends. When this re-evaluation occurs, the Downtime Definitions that are currently down are checked and the one with the highest priority (lowest number) will be the new reason for the System downtime.

This feature is useful when configuring Systems where one Downtime Definition should override another Downtime Definition already in progress. Note the following as you use this feature:

• When re-evaluation occurs, the current System downtime is ended and a new one is started. The downtime split occurs even if the same Downtime Definition assumes the fault after the re-evaluation.

• If System downtimes are split and the same reason is still the highest priority, the "average downtime" durations in the reports will be skewed shorter. The "downtime occurrences" will be skewed higher.

PriorityIt is important to note that the Downtime Definition Priority setting is only evaluated when more than one Downtime Definition "starts" within the same Logic Manager scan. It is used to determine the root cause of a particular System Downtime.

22 Chapter 2

If you have an event that should always be a Priority "1" no matter what other events are occurring, the "Force a New System Downtime" Property should be checked and a Priority of "1" attributed to this event. This will end all current events and re-evaluate the System state. Since you have attributed a Priority of "1" to this event, this event will become the new root cause and the other current events will be logged as consequential downtime. This should be used sparingly, otherwise the constant re-evaluation of events will over exaggerate the actual number of events in the reports.

Triggers

Referencing System and Downtime Definition StateIn complex production lines, it may be desirable for Trigger logic to be based on the state of existing DT Analyst Systems or Downtime Definitions, thereby allowing the reuse of already configured logic. Triggers in the DT Analyst software may be directed at the "state" of another DT Analyst System or Downtime Definition. A System or Downtime Definition's "state" is a Boolean value where 1 means the item is "Down" and 0 means the item is "Up".


Down Time DelayFor Triggers that consistently fluctuate between 0 and 1, like a photo-eye, the Down Time Delay property allows you to filter this "noise" by assigning a minimum duration that the trigger has to evaluate to True before the Logic Manager recognizes it as True. Therefore, if an event’s Down Time Delay is 2 seconds, then the trigger has to be equal to 1 (in the example shown below) for more than 2 seconds before it will evaluate as True and start logging the Downtime event.

In some Systems, a Downtime Definition may trigger nearly every time some other Downtime Definition triggers. In cases where this is occurring only due to bad timing of the PLC alarms or logic, the Down Time Delay setting on the Downtime Definition's Triggers can be used to delay the "triggering" of the unwanted Downtime Definition.

Up Time TimeoutIn some Systems, a Downtime Definition may be down for a minute, up for a very short time, and then back down for the conditions again. The Downtime Definition's Trigger properties Up Time Delay can be used to effectively combine these related events by not considering the System fully functional until the Up Time Delay duration has elapsed.

24 Chapter 2

Tags

Tag NamesTag Names should be chosen that are descriptive and relate to the item names of the actual I/O Tags they represent. Since the DT Analyst Tag list is a single level list, Tag Names should be consistently pre-fixed with text that can be used to group them together when the Tag List is sorted alphabetically. For example, Tags for Line 4 may all start with L4. Consistency and attention to detail will help with clarity as the size of the configuration grows.

Shifts and Schedules

Schedule Item Start and EndThe DT Analyst software requires that Schedule Items be defined down to the second, but the Schedule Item properties only allow entry to the minute level. The "seconds" part of the Schedule Item definition is automatically calculated and stored. So for a Line where Shift A goes from 8AM to 3PM and Shift B goes from 3PM to 10PM, do not set the End Time for Shift A to 2:59. This would be stored in the DT Analyst database as 2:58:59 and leave a 60-second gap where no Shift is defined.

Schedule Week Start and EndWhen defining a Schedule in the DT Analyst software, Schedule Items should be created for a single week, starting on Sunday at 12:00:00 AM and going until Saturday 11:59:59 PM. If a Shift must be defined that spans midnight between Saturday and Sunday, then 2 Schedule Items should be defined for the Shift where the first one ends Sunday at 12:00:00 AM (one second will be subtracted and Saturday 11:59:59 PM will be stored) and the next one starts Sunday at 12:00:00 AM.


Categories and Category GroupsCategories displayed in the Event Monitor are based on the Category Groups that are assigned to the System experiencing the downtime and the Downtime Definition causing it. The Category Groups that are marked Global will also be displayed.

System Specific CategoriesA simple technique for creating and assigning Categories and Category Groups is to create a Category Group for each System in the configuration (naming the Category Group accordingly). Once the Categories and Category Groups are created, assign each Category Groups to its corresponding System.

Read-Only Event MonitorsEvent Monitors can be used in a monitoring only mode. There can be value in placing an Event Monitor running on a PC in the Maintenance Manager's office or in the maintenance shop. This could allow the maintenance team to be aware of all Systems that are currently down and to proactively get involved when a System is down for an extended period.

Events from select Systems and Downtime Definitions can also be configured as Read-Only. So that a single Event Monitor may display a combination of editable and non-editable events.

26 Chapter 2

Virtual Tags

Operator Initiated EventsIn some cases, there are downtime events that must be tracked, but have no relation to any I/O Tag values. In these situations, Virtual Tags may be created and Downtime Definitions may be based on them. Virtual Tag values can be manipulated by operators at plant floor workstations via the Event Monitor Virtual Tag interfaces.

ConstantsVirtual Tags may be used as a place to store constants for downtime evaluation. An example of this would be if several Triggers were configured to "trigger" if a value of a Line Speed Tag was less than a certain set-point. Rather than hard-coding the minimum Line Speed into several Triggers, a Minimum Line Speed Virtual Tag could be created and the Triggers could reference this Tag instead. When a change in the configuration is needed, the Virtual Tag value may be changed via the Configuration Manager.

External DataSince Virtual Tag values are stored in the database, custom code could be written to update values into the appropriate locations from external sources. A DT Analyst System, Downtime Definition, etc… configured to reference the Virtual Tag will use the value in the database, regardless of the source.

OEEOEE is an effective methodology to help improve the efficiency of manufacturing processes. OEE has emerged as a leading approach for accurately measuring the true plant productivity. Although, initially, OEE was regularly associated with Total Productive Maintenance (TPM) programs, it is now being looked at as a powerful means of evaluating the key productivity indicators.

By definition, OEE is the product of Availability, Performance and Quality category percentages:

OEE = Availability * Performance * Quality

Where:

Availability is a measure of Downtime Losses,

Performance is a measure of Speed Losses, and

Quality is measure of Defect Losses.


Defining OEE EventsWithin each OEE category, there are several events that must be identified, and correctly measured and analyzed. There are situations (or events) that may require further thought to decide which category they belong to. For example, Short-lived stops and operator errors could be recorded as either Availability (Downtime) or Performance (Speed) losses. The correct categorization will be made based on the specific manufacturing process and plant. It is important to be consistent and uniform in categorizing events in order to get reliable results.

As stated above, there are many events that affect OEE. However, there are those which are considered the most common causes for efficiency loss in the manufacturing environment. Naturally, by implementing an OEE practice, you must aim to reduce these commonly occurring loss events to increase the overall plant/manufacturing productivity.

Common Events OEE Type CommentEquipment Breakdowns Availability Loss Depending on the specifics

of the production environment, certain variety of breakdowns not requiring maintenance could be categorized as Performance/Speed Losses.

Process Setup and Adjustments

Availability Loss Includes certain operator errors and product changeovers.

Short Stops and Idling Performance Loss Short stops are typically those which do not require maintenance. Generally, problems with consumables could be categorized as Performance/Speed Losses.

Reduced Speed Performance Loss Factors such as equipment age or production anomalies that keep the operation from running at the maximum theoretical speed would be included in this category.

28 Chapter 2

Frequently Asked Questions on OEE1. How universally applied are the key terms that make up the OEE equation?

There are many variants of the OEE equation and definitions, but generally they are using the same approach, which includes Availability, Performance, and Quality components (by whatever name they are called). The most important thing is to set up standard definitions for your company, and then to make sure they are uniformly understood and applied in all plants, so performance (and performance improvement) can be evaluated using the same standards on any line or in any plant.

2. Are terms like Operating Time and Net Operating Time industry standards?

No, for historical reasons, many companies use their own variations of these terms. What one company calls Planned Production Time, another might call Gross Production Hours or Scheduled Production Time. What is important is to document the terms and definitions that your company employs and to make sure that all affected employees understand them.

3. Where is the greatest potential for improvement, with A, P, or Q?

Of course this is highly dependent on the particular industry and process, but in many cases, Availability has not been a focal point for improvement. Many companies have improved performance and quality during the last (20) years, but many of these same companies have not focused on improving the Availability of their lines. Many companies have the potential to reduce their Availability Losses by 30 to 50%. For instance, the stamping industry achieved dramatic reductions in changeover time using an approach pioneered by the Japanese called SMED (Single Minute Exchange of Die).

4. Can OEE be applied to any process?

Startup Rejects Quality Loss Products lost (Rejected) during initial stages (transition) of startup prior to reaching steady state (regularly producing good products).

Production Rejects Quality Loss Products lost (Rejected due to defect) during the normal production stages.

Common Events OEE Type Comment


In the most practical sense, OEE is going to provide the highest value when it is measuring the capability of automated production systems. OEE can be focused on a specific machine or work cell, or applied to entire production line or area.

5. Why is performance measured by counting parts rather than adding up all the line stoppages?

The Performance component of OEE accounts for speed losses, which result from both short stops of the production system (for example jams, running out of materials, machine faults, …) or running the system at a speed less than its Theoretical Capacity. Comparing Actual Parts Produced to the Theoretical Number of Parts that should have been produced during the Operating Time of the line is an ingenious simplification, since this technique captures the losses due to short stops and speed reduction.

In addition, this technique does away with all the complication that would be required to calculate the true duration of many short stops on complex lines, where different systems run at different speeds, and where accumulation may allow parts of the line to keep producing even when some systems are down due to short stop failures.

6. What is the biggest issue that typically drags down the Performance of automated lines?

Once an automated system is installed for measuring OEE, so that accurate data can be collected right from the process network, many manufacturers are really shocked by the large number of short stop failures on their lines. Many automated lines have 1000 or more short stop failures per week with typical durations of 1 to 2 minutes each. Everyone knows about failures that take a line down for several hours, but very few are aware of the losses occurring every day, 1 or 2 minutes at a time!

7. How does OEE data typically compare with the manual downtime data that most manufacturers ask the operators to report on clipboards?

In most cases, the clipboard data is not useful. Since it is not possible for operators to manually capture all the short stops, they tend to only report a few major events per line per shift. Many times they always fill in the same amount of time for a given event, rather than the actual time required.

For example, every changeover will be logged as 90 minutes, or every stop for greasing will be logged as 10 minutes. This makes it impossible to discover and share best practices or to optimize scheduling of changeovers to minimize the lost time.

8. How do OEE performance numbers typically relate to the existing plant efficiency numbers that are already being collected by the plant?

If OEE is properly applied, all of the potential losses are included in OEE, so the OEE figure will be much lower. Most plants have developed ways of measuring their "efficiency" where the key detractors are excluded from the equation, i.e. efficiency is often measured only when the line is running. Consequently, a plant that has been reporting efficiency of 85-90%, may find that their OEE is actually in the 40-60% range.

9. What type of Return on Investment should we expect from an OEE program?

30 Chapter 2

Many manufacturers who implement a serious OEE improvement effort achieve a 4 to 10% OEE improvement in the first year. Depending on the output of the line and the value of the product, this often produces a seven figure return in the first year.

10. Who needs to be involved in an OEE improvement effort?

First, top management must be involved to set the overall objectives and establish the importance of the effort to the business. It is also vital to have the support of the operations team, because operators and supervisors have a big impact on the process.

In addition, engineering, maintenance, quality, and scheduling are all important groups to have on the improvement team. Oftentimes, manufacturers already have TPM or Continuous Improvement Teams in place that involve representatives from the key departments.

11. Who is achieving World Class OEE?

The World Class OEE figure of 85% needs to be tempered based on the industry and process under consideration. Continuous processes will be more likely to approach the 85% World Class level than discrete processes. The key is to develop an accurate measurement of the current OEE of your process and then to set targets for specific improvements in A, P, and Q.

12. What is the biggest "gap" in setting up an automated OEE system?

Most highly automated lines, even those including SCADA (Supervisory Control And Data Acquisition) systems, do not have a provision for tracking Availability related losses. Therefore, it is important that the automated solution incorporate an ability to allow operator or equipment triggered Availability related downtimes. These include events such as Sanitation / Cleanup, Changeover, Preventative Maintenance, Lunch / Breaks, Meetings, and No Personnel.

13. What events are normally NOT included in OEE?

Items classified as Planned Shutdown, which do not count against the OEE, typically include Not Scheduled to Run (i.e. the line could be available but there are no production requirements), Weekend (for plants that don't run on weekends) and Holiday. If you don't measure it, you probably won't be focused on improving it, so a proper OEE focus should include items such as Lunch, Meetings, Breaks, Training, etc. against the Availability.

14. Besides the actual OEE, A, P, and Q numbers, what other data is it important to get out of an OEE program?

To fully understand the performance of the system / area / line being measured, it is important to be able to overlay the OEE, A, P, and Q data against:

• Date, Time, and Shift

• Product being manufactured

• Job or Workorder

• Batch (if applicable)

• Quantity produced during any time period

• Total Produced


• Total Rejected

• Total Good (1st pass yield)

• Other production factors which provide context to the data, for example package size, case count, operator name, etc.

15. What is the significance of being able to monitor the OEE of production systems in real-time through a Web-browser?

Oftentimes operators will struggle with an emerging problem far too long without asking for help. As an example, let's assume that a manufacturer received a shipment of cartons that were not scored properly. This will cause many more jams than normal on the case packer and a significant loss of performance.

In a traditional plant, it would probably take several shifts before the discrepant materials problem is recognized and responded to. The availability of near-real time OEE data, and the supporting detailed event data underneath it, will allow the management team to recognize and respond to the problem more rapidly.

The fast recognition and response to problems is a major advantage of implementing a real-time system for tracking OEE and detailed Downtime information.

16. Is it a good idea to involve operators in all Performance related short stops?

No, since many lines have 100 or more failures per day, it is important that the tool that provides interaction with the operators provide a lot of configurability related to when operators get involved.

For instance, a routine label jam that occurs and is resolved within 3 minutes does not require any operator involvement in the data collection. On the other hand, if that label jam was still on-going after 10 minutes, then something exceptional has happened and it would be important to get some insight from the operator related to the cause of the fault.

Preparing for ImplementationIt is important that before an implementation, the proper materials and resources are available. Preparation can make a dramatic difference in the efficiency and success of the installation effort.

MaterialsThe following materials should be collected and made available before an implementation begins.

• DT Analyst software Setup CD

• DT Analyst software Licenses

In addition to the DT Analyst software licenses, a demo license is useful for installing DT Analyst components on additional PCs for temporary demo and troubleshooting purposes.

• Microsoft® SQL ServerTM Software

32 Chapter 2

The DT Analyst software Setup CD contains the installation for SQL ServerTM 7 Standard Edition. Depending on the custom requirements, then following versions of SQL ServerTM should be available:

• SQL ServerTM 2000 Standard Edition

• SQL ServerTM 2000 Developer Edition (for Windows® 2000 Pro)

• SQL ServerTM 7 Developer Edition (for Windows® 2000 Pro)

• Operating Systems

Often operating system components need to be installed/re-installed during implementation. The following Windows® OS CDs should be available:

• Windows® 2000 Professional

• Windows® 2000 Server

• Windows® XP Professional

• Windows® NT 4

• Service Packs

The latest service packs for Windows®, SQL ServerTM and the DT Analyst software should be available. They should all be available for download online. If internet access is limited on-site, it is recommended that they be downloaded before implementation.

• Spare PC

During implementation it is recommended that a PC be available for testing and troubleshooting. This PC should be capable of running all of the DT Analyst components (including IISTM and SQL ServerTM).

Resources on SiteIt is very important to have the right resources on-site during the implementation. Personnel resources should be available that can provide the following types of information/assistance:

Network Support• User Names and Passwords for adding new DT Analyst PCs to the network

(servers and/or Event Monitor workstations).

• User Names and Passwords for accessing existing PCs on the network (server and/or Event Monitor PCs).

• Desired PC Names for adding new DT Analyst PCs to the network.

• IP Addresses for adding new DT Analyst PCs to the network.

• Authority for modifying DCOM settings on DT Analyst PCs (for OPC server installations).

I/O Access• Tag Addresses for relevant I/O points.


• IP Address, Node Name, Application and Topic Names for all relevant SuiteLinkTM I/O Servers.

• IP Address, Node Name, OPC Server Name and Access Path for all relevant OPC Servers.

Equipment Control Programming• Identify meaning of I/O point values (Tags) for relevant equipment.

• Interpreting equipment behavior from the program standpoint.

• Ability and authority to make minor modifications in equipment programming.

Equipment Operations• Starting and stopping relevant equipment.

• Manually triggering equipment faults for testing the DT Analyst software.

• Interpreting equipment behavior from the operational standpoint.

Installing the SoftwareThis is discussed in detail in the DT Analyst Deployment Guide.

Entering the Configuration

Pre-ConfigurationWhen possible, it is recommended that as much of the configuration be input in the office environment. This allows much of the event data entry to be done before implementation and more time on-site to focus on the testing and adjusting.

Transporting ConfigurationThe entire DT Analyst configuration may be transported by transferring the entire DT Analyst database (DTDB by default). This can be done by a SQL ServerTM backup and restore. Remember that a SQL ServerTM 7 database can be restored to a SQL ServerTM 2000, but a SQL ServerTM 2000 database may NOT be restored to a SQL ServerTM 7.

After restoring a database from a different server, the DT Analyst logins and users must be repaired using the following script:

/**************************************************** * DTDB Login Repair Script (8/9/2002) ****************************************************

34 Chapter 2

* IMPORTANT!!! Login as "sa" before running this * script, otherwise it will most likely fail. * ****************************************************/DECLARE @sDB VARCHAR(128)/****************************************************/--NOTE: Change these if using a different DB name!SET @sDB = N'DTDB'USE DTDB/****************************************************/EXEC sp_dropuser N'dtdbApp'EXEC sp_dropuser N'dtdbAdmin'EXEC sp_dropuser N'dtdbUser'

EXEC sp_droplogin N'dtdbApp'EXEC sp_droplogin N'dtdbAdmin'EXEC sp_droplogin N'dtdbUser'

EXEC sp_addlogin N'dtdbApp', N'dtdbApp', @sDBEXEC sp_addlogin N'dtdbAdmin', N'dtdbAdmin', @sDBEXEC sp_addlogin N'dtdbUser', N'dtdbUser', @sDB

EXEC sp_grantdbaccess N'dtdbApp', N'dtdbApp'EXEC sp_grantdbaccess N'dtdbAdmin', N'dtdbAdmin'EXEC sp_grantdbaccess N'dtdbUser', N'dtdbUser'

EXEC sp_addrolemember N'db_datareader', N'dtdbApp'EXEC sp_addrolemember N'db_datawriter', N'dtdbApp'EXEC sp_addrolemember N'dtdb_spuser', N'dtdbApp'

EXEC sp_addrolemember N'db_owner', N'dtdbAdmin'

EXEC sp_addrolemember N'db_datareader', N'dtdbUser'/****************************************************/

Importing TagsTags may be imported into the DT Analyst Configuration Manager using the Tag Import options in the Tools menu. However, unless there are a large number of Tags needed for the DT Analyst software, and they are all known early in the process, it can be a distraction to collect and import them. Sometimes it is easier to just enter them in as needed.

Note The DT Analyst software typically utilizes only a small percentage of Tags from all of the Tags typically present in a plant floor environment. It is not usually a good idea to "batch import" large numbers of Tags indiscriminately.


Testing the Configuration

Testing I/OAfter setting up the configuration on-site, it is a good idea to verify that the Logic Manager is communicating with all of the Tags that are configured. To check the I/O connections, start the Logic Manager and open the I/O Monitor Window. All of rows in the I/O Monitor Window should contain black text. If there are any errors communicating with the configured I/O, the problem Tags will be displayed in red text. Common I/O communication problems are:

• Incorrect Access Name settings

• Incorrect Item Name setting

• SuiteLinkTM or OPC Server not running

• SuiteLinkTM or OPC Server not configured to monitor the proper Tags

• InTouch HMI not running (when accessing InTouch memory Tags).

Testing LogicThe Logic Manager's Logic Monitor Window lists each Downtime Definition in the configuration and its Up/Down state. Testing configured Downtime Definitions logic can be done by simulating equipment downtime and observing the following:

• Verify that the expected Tags change values using the I/O Monitor Window.

• Verify that the Downtime Definition state changes in the Logic Monitor Window.

Make sure to take into account configured Trigger Down Time Delay and Up Time Delay values when looking for Downtime Definition state changes.

Testing OEEDuring on-site implementation, it is recommended that the OEE Record Interval be set to a lower value (5 to 15 minutes). Using a lower value for the Record Interval will allow more frequent feedback on the OEE data collection to verify correct configuration.

Note It is very important to set the Record Interval to the desired value before leaving the implementation to run in production mode, because a short Record Interval may cause unnecessary data to be stored in the database and waste storage space. In general, a 30-minute Record Interval is recommended

36 Chapter 2

Adjusting Configuration

Effects on Previously Captured DataWhile setting up, testing and adjusting a DT Analyst configuration, it is common for downtime and efficiency data to be collected before the configuration is finalized. This data, while correct based on the configuration when it was collected, may not be compatible with data collected once the configuration is finalized and deployed.

Deleting Downtime and OEE DataTo avoid confusing data in reports, the following data cleansing recommendations should be considered.

• When major configuration changes are made, clear all old data using the Archive/Delete tool.

• When significant configuration changes are made to a specific System, consider creating a new System for the new configuration and deleting the old System. Deleting a System removes all of the data collecting for that System only.

• When the on-site implementation is over, it is recommended that the data collected while on-site be cleared using the Archive/Delete tool to remove any unusual data that may have been collected due to the unorthodox operation of the software necessary during startup.

Preparing for Remote SupportThe following should be performed before leaving the on-site stage of an implementation. These suggestions will aid in remote DT Analyst support.

Database BackupThe DT Analyst database should be backed up. The database backup can be restored to aid in remote troubleshooting.

Export ConfigurationExport the DT Analyst configuration using the File | Export Configuration menu option from the Configuration Manager. The XML dump can be used as a quick reference of the configuration.

Clear Downtime and OEE DataDelete all data using the Archive/Delete tool to remove any unusual data that may have been collected due to the unorthodox operation of the software necessary during startup.


Clear the DT AnalystTM Event LogClear the DT Analyst event log. Navigate to the Event Log Viewer page in the Utilities section of dtWeb and click the "Clear Event Log" link.

Document DeploymentDocument the physical deployment of all the DT Analyst software components. This includes the following:

• Domain Names

• PC Names

• IP Addresses

• User Names

• Passwords

Setup Remote Connection and Control SoftwareIf needed, setup a way to remotely connect to and control the DT Analyst software server. VPN to the network and PC Anywhere would be an example of this type of access. Test the connection to ensure functionality.

TrainingOnce the DT Analyst software is installed and configured, the end users should be familiarized with the using the software. The following are important points to convey during DT Analyst training.

Downtime Reports

Grand Totals on Area ReportsThe grand total downtime at the bottom of Area reports is a sum of all downtime events for all Systems in the selected Area. It is important to understand that this number may exceed the total amount of time specified in the report definition parameters. For Areas that represent the Systems in a Production Line, the grand total should not be used to determine the total amount of time the Production Line was down during the report duration - as several of the Systems may be down at the same time. For configurations such as this, the grand total is best used as a relative measure of downtime for the Line from period to period.

Downtime Events that Overlap Report BoundariesAll downtime reports include only portions of downtime events that fall within the date and time range specified in the report definition parameters. This means that for a report from 4/7/2003 12:00:00 AM to 4/7/2003 11:59:59 PM would only include 1 hour of downtime from an event that started at 4/7/2003 11:00:00 PM and ended at 4/8/2003 2:00:00 AM.

38 Chapter 2

Downtime events that span the report boundaries are marked with an asterisk in detail reports.

OEE Reports

Record Interval SplittingReal-time OEE is calculated and stored in small periods called Record Intervals. These Record Intervals are combined to create OEE numbers for Days or Shifts in the OEE reports. Normally, the Logic Manager creates new Record Intervals based on the configured value in the Configuration Manager's OEE Calculation Property Window. However, there are certain circumstances that force the creation of a new Record Interval. When any of the following values change, the Logic Manager will stop an OEE Calculation's current Record Interval, make a recording and then start a new Record Interval:

• The Product value for the OEE Calculation's parent System.

• The Batch value for the OEE Calculation's parent System.

• The Job value for the OEE Calculation's parent System.

• The Operator value for the OEE Calculation's parent System.

• The Shift for the OEE Calculation's parent System.

• The OEE Calculation's Theoretical Rate.

This will cause a variety of Record Interval lengths. The Record Interval's length should be considered when interpreting data captured for the period. The Record Intervals length is taken into account when they are averaged to calculate OEE for a Day or a Shift report.

Removing Anomaly OEE Record IntervalsOccasionally, unusual circumstances with OEE counters and other conditions in the process may create OEE Record Intervals with extremely large or extremely low OEE numbers. These anomaly points can be hidden from the graph and removed from the averaging by clicking the point in the graph, and then clicking the red arrow icon next to the point in the data table.

Record Intervals that have been excluded can be viewed by clicking the Show Excluded Points link at the top of the OEE report.

Record Intervals that have been excluded can be re-included permanently by clicking the green arrow icon next to the point in the data table.

Event Monitor and dtWeb Customizations 39

C H A P T E R 3

Event Monitor and dtWeb Customizations

The Event Monitor ActiveX® Control and the dtWeb components of the DT Analyst software can be customized to meet your requirements. The Event Monitor in the DT Analyst software exposes a number of methods, properties, and events that allow you to customize the control. This chapter describes these methods, properties, and events. There are also tips for securing and customizing the dtWeb, if required.


Contents• Event Monitor

• dtWeb

Event Monitor

Scripting the Event Monitor ActiveX® ControlThe following sections describe the Properties, Methods and Events of the Event Monitor ActiveX® Control.

Event Monitor Properties

ActiveEventCountThe ActiveEventCount Property is the number of downtime events in the Event Monitor, excluding those that have not exceeded their configured Display Delay.

Data Type LongDesign Time N/ARun Time Read Only

40 Chapter 3

AllEventCountThe AllEventCount Property is the total number of events in the Event Monitor, including those that have not exceeded their configured Display Delay.

BeforeEventAcknowledgeCancelThe BeforeEventAcknowledgeCancel Property should be set to True from within the BeforeEventAcknowledge ActiveX Event to notify the Event Monitor to abort the downtime event acknowledgement. This is a workaround for programing in InTouch which does not support ByRef parameters in ActiveX events. Setting this Property to True will cancel the downtime event acknoledgement and keep the Event Property page displayed.

BeforeEventAutoPostedCancelThe BeforeEventAutoPostedCancel Property should be set to True from within the BeforeEventPosted ActiveX Event to notify the Event Monitor to abort the downtime event auto posting. This is a workaround for programing in InTouch which does not support ByRef parameters in ActiveX events. Setting this Property to True will cancel the downtime event auto posting. Note that the next Event Monitor Poll will attempt to Auto Post the downtime event again.

CategoryTreeviewThe CategoryTreeview Property controls the user interface presented to Operators for selecting Downtime Categories. When this Property is set to False, the Downtime Categories are presented in a flat list. When this Property is set to True, the Downtime Categories are presented in a popup Treeview dialog. The Downtime Categories are gouped in the Treeview by Downtime Category Groups (as defined in the Configuration Manager).

Data Type LongDesign Time N/ARun Time Read Only

Data Type BooleanDesign Time Read/WriteRun Time Read/Write




ComputerNameThe ComputerName Property is the name of the PC that the Event Monitor resides on. If the ComputerNameType Property is set to 0 - Computer Name, then this value is matched to the Computer Name specified for the Event Monitor in the Configuration Manager for event routing from the Logic Manager.

ComputerNameTypeThe ComputerNameType Property specifies how messages are looked up from the Logic Manager. This Property must match the way the Event Monitor is configured in the Configuration Manager. The possible values for this Property are:

• 0 - Computer Name - The Event Monitor retrieves messages from the Logic Manager sent to the Name of the computer that the Event Monitor is running on.

• 1 - IP Address - The Event Monitor retrieves messages from the Logic Manager sent to the IP Address of the computer that the Event Monitor is running on.

DBConnectType

The DBConnectType Property specifies whether SQL ServerTM Authentication or Windows® NT Authentication is used to connect to the DT Analyst software SQL ServerTM database. The possible values for this Property are:

• 0 - SQL ServerTM Authentication

• 1 - Windows® NT Authentication

DBNameThe DBName Property specifies the name of the DT Analyst database to connect to. This Property's default value is "DTDB".

Data Type StringDesign Time N/ARun Time Read Only

Data Type LongDesign Time Read/WriteRun Time Read/Write


Data Type StringDesign Time Read/WriteRun Time Read/Write

42 Chapter 3

DBPasswordThe DBPassword Property specifies the password for access to the DT Analyst database. This Property's default value is "dtdbApp".

DBServerThe DBServer Property specifies the name of the computer hosting the SQL ServerTM that contains the DT Analyst database.

DBUserThe DBUser Property specifies the password for access to the DT Analyst database. This Property's default value is "dtdbApp".

EventDialogDisplayedThe EventDialogDisplayed Property indicates whether the event acknowledgement form is currently displayed.

FontSizeNormalThe FontSizeNormal Property controls the Font Size for the downtime event and Virtual Tag Listviews when the Event Monitor is in non-Touchscreen mode.




Data Type BooleanDesign Time N/ARun Time Read Only



FontSizeTouchScreenThe FontSizeTouchScreen Property controls the Font Size for the downtime event and Virtual Tag Listviews when the Event Monitor is in Touchscreen mode.

IsPollingThe IsPolling Property indicates the polling status of the Event Monitor control. It is also writable and may be used to start and stop the polling of the Event Monitor as an alternative to the StartPolling and StopPolling Methods.

OnEventClickCancelThe OnEventClickCancel Property should be set to True from within the OnEventClick ActiveX Event to notify the Event Monitor to abort the downtime event click. This is a workaround for programing in InTouch which does not support ByRef parameters in ActiveX events. Setting this Property to True will cancel the click Event preventing the Event Property window from being displayed when the Event Monitor is in Touchscreen Mode.

OnEventDoubleClickCancelThe OnEventDoubleClickCancel Property should be set to True from within the OnEventDoubleClick ActiveX Event to notify the Event Monitor to abort the downtime event click. This is a workaround for programing in InTouch which does not support ByRef parameters in ActiveX events. Setting this Property to True will cancel the double-click Event preventing the Event Property window from being displayed when the Event Monitor is in non-Touchscreen Mode.





44 Chapter 3

PollIntervalThe PollInterval property specifies the polling rate (in seconds) of the Event Monitor. This is the interval which the Event Monitor will check the DT Analyst database for event updates.

ReadOnlyThe ReadOnly Property specifies weather the event acknowledgement form is displayed when users click events in the Event Monitor List View.

RepopMinutesThe RepopMinutes Property specifies the interval which the Event Monitor will raise the ActiveX Repop Event. The Repop Event is only raised when there are events that have been sent to the Event Monitor that have exceeded their configured Display Delay

SelectedDowntimeIDThe SelectedDowntimeID Property returns the Downtime ID of the currently selected event in the Event Monitor List View.

TouchscreenModeThe TouchscreenMode Property specifies the visual mode for the Event Monitor user interfaces.

Setting this Property to True or 1 enables Touchscreen Mode where all controls and text are larger and more suitable for use with a touch screen interface. Touchscreen Mode also exposes a touch screen keyboard for data entry into text fields.






Setting this Property to False or 0 enables a smaller text and control mode more suitable for mouse and traditional keyboard interaction.

VersionThe Version Property returns the Version of the Event Monitor ActiveX control.

Event Monitor Methods

About BoxThe AboutBox Method displays the Event Monitor About box dialog.

DTCategoriesLoadThe DTCategoriesLoad Method returns a delimited list of all Downtime Categories and their IDs, delimited by the character specified by the Separator parameter.

The LoadType parameter can be one of the following:

• DTDef - uses the ID parameter as a DTDef ID. The Method returns all Downtime Categories assigned to the DTDef, its parent System, and all Global Downtime Categories.

• DTDefOnly - uses the ID parameter as a DTDef ID. The Method returns only the Downtime Categories specifically assigned to the indicated DTDef.

• System - uses the ID parameter as a System ID. The Method returns all Downtime Categories for the System and all Global Downtime Categories.

• SystemOnly - uses the ID parameter as a System ID. The Method returns only the Downtime Categories specifically assigned to the indicated System.

Data Type BooleanDesign Time Read/WriteRun Time Read Only

Data Type StringDesign Time Read OnlyRun Time Read Only

Parameter Data TypeNo ParametersReturns Nothing

Parameter Data TypeID Long (Optional) (-1)LoadType String (Optional) ("DTDef")Separator String (Optional) (",")Returns String

46 Chapter 3

DTCategoriesLoadXMLThe DTCategoriesLoadXML Method behaves the same as the DTCategoriesLoad Method, but returns XML instead of a delimited list.

DTCategoriesLoadGlobalThe DTCategoriesLoadGlobal Method returns a list of Global Downtime Categories and their IDs, delimited by the character specified by the Separator parameter.

DTCategoriesLoadGlobalXMLThe DTCategoriesLoadGlobalXML Method behaves the same as the DTCategoriesLoadGlobal Method, but returns XML instead of a delimited list.

EventAcknowledgeThe EventAcknowledge Method saves the event specified by the DowntimeID parameter and removes it from the Event Monitor List View (if it was visible). The AcknowledgeState parameter indicates how the event will be saved. The options are:

• 0 - Never Shown

• 1 - User Confirmed

• 2 - Auto Posted

• 3 - In Process

The Method returns an error string if the action fails.

Parameter Data TypeID Long (Optional) (-1)LoadType String (Optional) ("DTDef")Returns String

Parameter Data TypeSeparator String (Optional) (",")Returns String

Parameter Data TypeNo ParametersReturns String

Parameter Data TypeDowntimeID Long (Optional) (-1)AcknowledgeState Long (Optional) (1)Returns String


EventGetXMLThe EventGetXML Method returns an XML string representation of the downtime event specified by the DowntimeID parameter.

EventLockThe EventLock Method locks the event specified by the DowntimeID parameter. The EventLock Method should be called to lock an event while a user is interacting with and editing data for an event. An event lock expires after 5 minutes and must be relocked periodically using the EventRelock Method.


EventPropertyGetThe EventPropertyGet Method returns the value of the downtime event property specified by the PropertyName parameter for the event specified by the DowntimeID parameter.

The valid values for the PropertyName parameter are:

• SystemDowntimeID

• EventType

• StartDateTime

• ISOStartDateTime

• StartShiftID

• StartShiftName

• EndDateTime

• ISOEndDateTime

• EndShiftID

• EndShiftName

• IsDown

• AreaID

• AreaName

• SystemID

• SystemName

• DTDefID

• DTDefName

Parameter Data TypeDowntimeID Long (Optional) (-1)Returns String

Parameter Data TypeDowntimeID Long (Optional) (-1)Returns String

48 Chapter 3

• DTCategoryID

• DTCategoryName

• DTCodeID

• DTCode

• DTCodeName

• ProductName

• Job

• Batch

• Operator

• A

• B

• C

• D

• E

• F

• G

• H

• I

• J

• UserNotes

• TimeoutSeconds

• AckDurationSeconds

• AckWhileDown

• Visible

• LockedBy

EventPropertyListThe EventPropertyList Method returns a list of the possible values for the PropertyName parameter of the EventPropertyGet Method. The list is delimited by the character specified by the Separator parameter.

Parameter Data TypePropertyName String (Optional) ("")DowntimeID Long (Optional) (-1)Returns String

Parameter Data TypeDowntimeID String (Optional) (",")Returns String


EventPropertySetThe EventPropertySet Method sets a property associated with a downtime event. The downtime event is specified by the DowntimeID property. The property of the downtime event that is to be modified is specified by the PropertyName parameter. The value to update the property to is specified by the PropertyValue parameter.

The valid values for the PropertyName parameter are:

• DTCategoryID

• DTCodeID

• DTCode

• Product

• Job

• Batch

• Operator

• A

• B

• C

• D

• E

• F

• G

• H

• I

• J

• UserNotes

If the downtime event is locked by another Event Monitor, then property update will fail.


Parameter Data TypePropertyName String (Optional) ("")DowntimeID Long (Optional) (-1)PropertyValue String (Optional) ("")Returns String

50 Chapter 3

EventRelockThe EventRelock Method resets the lock on an event (specified by the DowntimeID parameter) after the EventLock Method has been called. If the EventRelock Method is not called regularly while the event needs to be locked, the event lock will expire and another Event Monitor may acquire a lock on the event.


EventShowThe EventShow Method displays the dialog form for acknowledging the downtime event specified by the DowntimeID parameter. The form automatically handles all downtime event locking and saving.


EventUnlockThe EventUnlock Method unlocks a downtime event locked by the EventLock Method specified by the DowntimeID parameter. Only an Event Monitor on the same computer an event was locked from, can unlock an event.


GetFactoryTime

The GetFactoryTime Method returns the date/time from the SQL ServerTM

computer hosting the DT Analyst database. The date and time is only as current as the last Event Monitor poll.

Parameter Data TypeDowntimeID String (Optional) (-1)Returns String





ListEventsIDListThe ListEventsIDList Method returns a list of Downtime IDs of events in the Event Monitor delimited by the character specified by the Separator parameter. Passing a value of False or 0 for the VisibleOnly parameter will return not only the visible events, but also the events that have been broadcast to the Event Monitor but not yet displayed due to Event Monitor Display Delay settings (System or Downtime Definitions settings).

ListEventsIDXMLThe ListEventsIDXML Method behaves the same as the ListEventsIDList Method, but returns the results as an XML string.

ShowVirtualTagsThe ShowVirtualTags Method displays a dialog for viewing and modifying DT Analyst Virtual Tags. The Virtual Tags that are displayed are those in use by all of the Systems that are configured to report to the Event Monitor.

The dialog is displayed in the screen coordinates specified by the Top and Left parameters.

ShowVirtualTagsForSystemThe ShowVirtualTagsForSystem Method displays a dialog for viewing and modifying DT Analyst Virtual Tags. The Virtual Tags that are displayed are those in use by the System specified by the SystemID parameter.


Parameter Data TypeVisibleOnly Boolean (Optional) (True or 1)Separator String (Optional) (",")Returns String

Parameter Data TypeVisibleOnly Boolean (Optional) (True or 1)Returns String

Parameter Data TypeTop Float (Optional) (0)Left Float (Optional) (0)Returns Nothing

Parameter Data TypeTop Float (Optional) (0)Left Float (Optional) (0)SystemID Long (Optional) (-1)Returns Nothing

52 Chapter 3

ShowVirtualTagsGroupedThe ShowVirtualTagsGrouped Method displays a dialog for viewing and modifying DT Analyst Virtual Tags. The Virtual Tags that are displayed are those in use by all of the Systems that are configured to report to the Event Monitor. This Method displays the Tags in a Tree View grouped by System. The System nodes in the Tree View are expanded by default. To show the dialog with the nodes collapsed, pass False or 0 for the ExpandAll parameter.


ShowVirtualTagsGroupedForSystemThe ShowVirtualTagsGroupedForSystem Method behaves the same as the ShowVirtualTagsGrouped, but the Tree View is collapsed except for the System specified by the SystemID parameter.

StartPollingThe StartPolling Method must be called in order for Event Monitor to begin running. It initiates the database polls which are the basis for the messaging from the Logic Manager. This Method should be called when showing a window or form that contains an Event Monitor control.

StopPollingThe StopPolling Method must be called in order for Event Monitor to stop running. It stops the database polls which are the basis for the messaging from the Logic Manager. This Method should be called when unloading a window or form that contains an Event Monitor control.

Parameter Data TypeTop Float (Optional) (0)Left Float (Optional) (0)ExpandAll Boolean (Optional) (True or 1)Returns Nothing

Parameter Data TypeTop Float (Optional) (0)Left Float (Optional) (0)SystemID Long (Optional) (-1)Returns Nothing




SystemsAssignedListThe SystemsAssignedList Method returns a list of System IDs and Names for all of the Systems that are configured to report to the Event Monitor. This list is delimited by the character specified by the Separator parameter.

SystemsAssignedXMLThe SystemsAssignedXML Method behaves like the SystemsAssignedList Method except it returns a XML formatted string.

VirtualTagGetValueByIDThe VirtualTagGetValueByID Method returns the current value of the Virtual Tag specified by the TagID parameter.

VirtualTagGetValueByNameThe VirtualTagGetValueByName Method returns the current value of the Virtual Tag specified by the TagIName parameter. The TagName parameter refers to the Tag's Name property as specified in the DT Analyst Configuration Manager.

VirtualTagListLoadThe VirtualTagListLoad Method returns a list of Virtual Tag Names for the System ID specified by the TagListID parameter. If -1 is specified as the System ID then Virtual Tag Names for all Systems configured to report to the Event Monitor will be returned. The list is delimited by the character specified by the Separator parameter.

Parameter Data TypeSeparator String (Optional) (",")Returns String


Parameter Data TypeTagID Long (Optional) (-1)Returns String

Parameter Data TypeTagName String (Optional) ("")Returns String

Parameter Data TypeTagListID Long (Optional) (-1)Separator String (Optional) ("")Returns String

54 Chapter 3

VirtualTagListLoadXMLThe VirtualTagListLoadXML Method behaves the same as the VirtualTagListLoad Method but returns an XML formatted string.

VirtualTagSetValueByIDThe VirtualTagSetValueByID Method allows the update of a Virtual Tag's value. The Virtual Tag to update is specified by the TagID parameter and the new value is specified by the VirtualValue parameter.

New values should be validated before an update is attempted using one of the Event Monitor Methods:

• VirtualTagValidate

• VirtualTagValidateDiscrete

• VirtualTagValidateFloat

• VirtualTagValidateInteger

• VirtualTagValidateString


VirtualTagSetValueByNameThe VirtualTagSetValueByName Method behaves the same as the VirtualTagSetValueByID Method except the Virtual Tag is specified by the TagName parameter.

VirtualTagValidateThe VirtualTagValidate Method validates the value specified by the Value parameter. The value is validated against the data type of the Virtual Tag specified by the TagID parameter.

Parameter Data TypeTagListID Long (Optional) (-1)Returns String

Parameter Data TypeTagID Long (Optional) (-1)VirtualValue String (Optional) ("")Returns String

Parameter Data TypeTagName String (Optional) ("")VirtualValue String (Optional) ("")Returns String


This Method returns an empty string if the validation is successful. The appropriate error message is returned if the validation fails.

VirtualTagValidateDiscreteThe VirtualTagValidateDiscrete Method validates the value specified by the Value parameter. The value is validated as a Discrete data type.


VirtualTagValidateFloatThe VirtualTagValidateFloat Method validates the value specified by the Value parameter. The value is validated as a Float data type.


VirtualTagValidateIntegerThe VirtualTagValidateInteger Method validates the value specified by the Value parameter. The value is validated as an Integer data type.


VirtualTagValidateStringThe VirtualTagValidateString Method validates the value specified by the Value parameter. The value is validated as a String data type.


Parameter Data TypeTagID Long (Optional) (-1)Value String (Optional) ("")Returns String

Parameter Data TypeValue String (Optional) ("")Returns String



Parameter Data Type

56 Chapter 3

VTRDeleteThe VTRDelete Method deletes a VTR entry for the downtime event specified by the DowntimeID parameter. The VTR that is deleted is specified by the TagID and OnDown parameters. An OnDown value of True or 1 will delete the VTR that was captured when the System went down and an OnDown value of False or 0 will delete the VTR that was captured when the System came back up.


VTRGetValueThe VTRGetValue Method returns the value of the VTR entry for the event specified by the DowntimeID parameter. The VTR that is retrieved is specified by the TagID and OnDown parameters. An OnDown value of True or 1 will retrieve the VTR that was captured when the System went down and an OnDown value of False or 0 will retrieve the value that was captured when the System came back up.

VTRInsertThe VTRInsert Method creates a VTR entry for the downtime event specified by the DowntimeID parameter. The VTR that is inserted is specified by the TagID and OnDown parameters and the VTR value is specified by the TagValue parameter. An OnDown value of True or 1 will insert the VTR that as one captured when the System went down and an OnDown value of False or 0 will insert the VTR as one captured when the System came back up.


Value String (Optional) ("")Returns String

Parameter Data TypeDowntimeID Long (Optional) (-1)TagID Long (Optional) (-1)OnDown Boolean (Optional) (True or 1)Returns String

Parameter Data TypeDowntimeID Long (Optional) (-1)TagID Long (Optional) (-1)OnDown Boolean (Optional) (True or 1)Returns String

Parameter Data TypeDowntimeID Long (Optional) (-1)TagID Long (Optional) (-1)TagValue String (Optional) ("")OnDown Boolean (Optional) (True or 1)Returns String


VTRUpdateThe VTRUpdate Method updates the value of an existing VTR entry for the downtime event specified by the DowntimeID parameter. The VTR that is updated is specified by the TagID and OnDown parameters and the VTR new value is specified by the TagValue parameter. An OnDown vdalue of True or 1 will update the VTR that was captured when the System went down and an OnDown value of False or 0 will update the VTR that was captured when the System came back up.


Event Monitor Events

AfterEventAcknowledgedThe AfterEventAcknowledged Event fires after the downtime event data is saved back to the DT Analyst database following an acknowledgement by a user (Event Monitor dialog) or by Method (EventAcknowledge Method). The Event passes out the new property values of the event as they were saved to the database.

Parameter Data TypeDowntimeID Long (Optional) (-1)TagID Long (Optional) (-1)TagValue String (Optional) ("")OnDown Boolean (Optional) (True or 1)Returns String

Parameter Data TypeDowntimeID LongSystemDowntimeID LongEventType LongStartDateTime StringStartShiftID LongStartShiftName StringEndDateTime StringEndShiftID LongEndShiftName StringAreaID LongAreaName StringSystemID LongSystemName StringDTDefID LongDTDefName StringDTCategoryID LongDTCategoryName StringProduct String

58 Chapter 3

AfterEventAutoPostedThe AfterEventAutoPosted Event fires after the downtime event data is saved back to the DT Analyst database following an auto acknowledgement by the Event Monitor or by the EventAcknowledge Method. The Event passes out the new property values of the event as they were saved to the database.

BeforeEventAcknowledgedThe BeforeEventAcknowledged Event fires before the downtime event data is saved back to the DT Analyst database following an acknowledgement by a user (Event Monitor dialog) or by Method (EventAcknowledge Method). The Event passes out the property values of the event as they are about to be saved to the database.

The property values may be changed before they are saved by assigning new values to the arguments passed into the Event. The acknowledge action can be canceled by assigning True or 1 to the Cancel argument.

UserNotes StringTimeOutSeconds LongAckDurationSeconds LongAckWhileDown Boolean

Parameter Data TypeDowntimeID LongSystemDowntimeID LongEventType LongStartDateTime StringStartShiftID LongStartShiftName StringEndDateTime StringEndShiftID LongEndShiftName StringAreaID LongAreaName StringSystemID LongSystemName StringDTDefID LongDTDefName StringDTCategoryID LongDTCategoryName StringProduct StringUserNotes StringTimeOutSeconds LongAckDurationSeconds LongAckWhileDown Boolean


Note Assigning new values to the Event arguments and canceling the acknowledge action by setting Cancel to True does NOT work in InTouch 7.X (not tested in InTouch 8.X at this time). InTouch 7.X does not allow values to be passed back to the calling control through ActiveX® Events.

BeforeEventAutoPostedThe BeforeEventAutoPosted Event fires before the downtime event data is saved back to the DT Analyst database following an auto acknowledgement by the Event Monitor or by the EventAcknowledge Method. The Event passes out the property values of the event as they are about to be saved to the database.

The property values may be changed before they are saved by assigning new values to the arguments passed into the Event. The acknowledge action can be canceled by assigning True or 1 to the Cancel argument.

Parameter Data TypeCancel BooleanDowntimeID LongSystemDowntimeID LongEventType LongStartDateTime StringStartShiftID LongStartShiftName StringEndDateTime StringEndShiftID LongEndShiftName StringAreaID LongAreaName StringSystemID LongSystemName StringDTDefID LongDTDefName StringDTCategoryID LongDTCategoryName StringProduct StringUserNotes StringTimeOutSeconds LongAckDurationSeconds LongAckWhileDown Boolean

60 Chapter 3

Note Assigning new values to the Event arguments and canceling the acknowledge action by setting Cancel to True does NOT work in InTouch 7.X (not tested in InTouch 8.X at this time). InTouch 7.X does not allow values to be passed back to the calling control through ActiveX® Events.

EndDowntimeThe EndDowntime Event fires when a downtime event that has been sent to the Event Monitor ends. The EndDowntime Event will not fire for a downtime event whose duration has not yet exceeded its Display Delay (per the Display Delay setting at the events source System).

The Event passes out the property values of the event as they were at the time the event ended.

Parameter Data TypeCancel BooleanDowntimeID LongSystemDowntimeID LongEventType LongStartDateTime StringStartShiftID LongStartShiftName StringEndDateTime StringEndShiftID LongEndShiftName StringAreaID LongAreaName StringSystemID LongSystemName StringDTDefID LongDTDefName StringDTCategoryID LongDTCategoryName StringProduct StringUserNotes StringTimeOutSeconds LongAckDurationSeconds LongAckWhileDown Boolean

Parameter Data TypeDowntimeID LongSystemDowntimeID Long


EventRemovedThe EventRemoved Event fires anytime a visible event (one that has exceeded its Display Delay setting) is removed from the Event Monitor for any reason.

The Event passes out the DowntimeID for the downtime event that was removed.

OnEventChangedThe OnEventChanged Event fires when a downtime event in the Event Monitor's List View gets the focus.

The Event passes out the DowntimeID for the downtime event that received the focus.

OnEventClickThe OnEventClick Event fires when a downtime event in the Event Monitor's List View is single clicked.

EventType LongStartDateTime StringStartShiftID LongStartShiftName StringEndDateTime StringEndShiftID LongEndShiftName StringAreaID LongAreaName StringSystemID LongSystemName StringDTDefID LongDTDefName StringDTCategoryID LongDTCategoryName StringProduct StringUserNotes StringTimeOutSeconds LongAckDurationSeconds LongAckWhileDown Boolean

Parameter Data TypeDowntimeID Long


62 Chapter 3


OnEventDblClickThe OnEventDblClick Event fires when a downtime event in the Event Monitor's List View is double clicked.


RepopThe Repop Event fires on a regular interval specified by the Event Monitor RepopMinutes property. The Repop Event only fires if there are downtime events in the Event Monitor that have exceeded their configured Display Delay.

StartDowntimeThe StartDowntime Event fires when a downtime event that has been sent to the Event Monitor ends. The StartDowntime Event will not fire for a downtime event whose duration has not yet exceeded its Display Delay (per the Display Delay setting at the events source System).

The Event passes out the property values of the event as they were at the time the event ended.



Parameter Data TypeNo Event Arguments

Parameter Data TypeDowntimeID LongSystemDowntimeID LongEventType LongStartDateTime StringStartShiftID LongStartShiftName StringEndDateTime StringEndShiftID LongEndShiftName StringAreaID LongAreaName StringSystemID LongSystemName String


TimerThe Timer Event fires on a regular interval specified by the Event Monitor PollInterval property.

dtWeb

Securing the dtWebIIS may be configured to allow authorized users access to specific areas of the dtWeb site. In order to do this, the various files and folders in the dtWeb (by default at C:\Program Files\Wonderware\DT Analyst\dtWeb) must be set with the desired Windows® Domain Group and User permissions (the "read and execute" right being the key). Once the permissions are set, the dtWeb virtual directory must be configured in the Windows® Internet Information Services Administrative Tool.

1. Right click on the dtWeb virtual directory and select Properties.

2. On the Directory Security Tab select the Edit button under "Anonymous Access and Authentication Control.

3. Uncheck the "Anonymous Access" checkbox.

4. Check the "Integrated Windows® Authentication" checkbox.

It is important to understand that the flexibility of this technique is dependent on the underlying Windows® Domain Groups and User infrastructure.

Customizing the dtWebWARNING! The customizations to the dtWeb described below require knowledge of ASP (Active Server Pages) web development. Problems encountered while modifying dtWeb may not be supported by Wonderware technical support.

DTDefID LongDTDefName StringDTCategoryID LongDTCategoryName StringProduct StringUserNotes StringTimeOutSeconds LongAckDurationSeconds LongAckWhileDown Boolean

Parameter Data TypeNo Event Arguments

64 Chapter 3

Hiding Report By TypesSome of the downtime report types can be deactivated if not viewed by the user. Hiding these report types not used can help to simplify the report interface. Use the following constants in the util_extend.asp file in the root of the dtWeb.

' Custom Use Constants...CONST gbCUST_USE_SCHEDULED_TYPE = TrueCONST gbCUST_USE_PRODUCT = TrueCONST gbCUST_USE_JOB = TrueCONST gbCUST_USE_BATCH = TrueCONST gbCUST_USE_OPERATOR = TrueCONST gbCUST_USE_CODE = True

Customizing Report By LabelsThe labels for some of the downtime reports can be customized to reflect your specific terms. By default, the constants are looked up in the translation XML files. They can be changed to any hard coded value desired. The following constants can be edited to modify certain labels in the util_extend.asp file in the root of the dtWeb.

' Custom Label Constants...DIM gsCUST_LABEL_PRODUCT : gsCUST_LABEL_PRODUCT = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_PRODUCT")DIM gsCUST_LABEL_PRODUCT_PLURAL : gsCUST_LABEL_PRODUCT_PLURAL = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_PRODUCT_PLURAL")DIM gsCUST_LABEL_PRODUCT_POSSESIVE : gsCUST_LABEL_PRODUCT_POSSESIVE = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_PRODUCT_POSSESIVE")

DIM gsCUST_LABEL_JOB : gsCUST_LABEL_JOB = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_JOB")DIM gsCUST_LABEL_JOB_PLURAL : gsCUST_LABEL_JOB_PLURAL = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_JOB_PLURAL")DIM gsCUST_LABEL_JOB_POSSESIVE : gsCUST_LABEL_JOB_POSSESIVE = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_JOB_POSSESIVE")

DIM gsCUST_LABEL_BATCH : gsCUST_LABEL_BATCH = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_BATCH")DIM gsCUST_LABEL_BATCH_PLURAL : gsCUST_LABEL_BATCH_PLURAL = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_BATCH_PLURAL")DIM gsCUST_LABEL_BATCH_POSSESIVE : gsCUST_LABEL_BATCH_POSSESIVE =


goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_BATCH_POSSESIVE")

DIM gsCUST_LABEL_JOB_BATCH : gsCUST_LABEL_JOB_BATCH = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_JOB_BATCH")

DIM gsCUST_LABEL_OPERATOR : gsCUST_LABEL_OPERATOR = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_OPERATOR")DIM gsCUST_LABEL_OPERATOR_PLURAL : gsCUST_LABEL_OPERATOR_PLURAL = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_OPERATOR_PLURAL")DIM gsCUST_LABEL_OPERATOR_POSSESIVE : gsCUST_LABEL_OPERATOR_POSSESIVE = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_OPERATOR_POSSESIVE")

DIM gsCUST_LABEL_CODE : gsCUST_LABEL_CODE = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_CODE")DIM gsCUST_LABEL_CODE_PLURAL : gsCUST_LABEL_CODE_PLURAL = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_CODE_PLURAL")DIM gsCUST_LABEL_CODE_POSSESIVE : gsCUST_LABEL_CODE_POSSESIVE = goLookup.GetText(Session.LCID, "ROOT_UTIL_EXTEND", "CONST_LABEL_CODE_POSSESIVE")

Hiding dtWeb PartsElements of the dtWeb interface may be hidden by manipulating the following constants in the util_extend.asp file in the root of the dtWeb (for example, hiding the menu options to limit access to the Downtime Editor).

' Show Custom Constants...CONST gbCUST_SHOW_HOME_IMAGEMAP = TrueCONST gbCUST_SHOW_HEADER = TrueCONST gbCUST_SHOW_HEADER_MENU = TrueCONST gbCUST_SHOW_HEADER_MENU_NONE = TrueCONST gbCUST_SHOW_HEADER_MENU_DT_REPORTS = TrueCONST gbCUST_SHOW_HEADER_MENU_EF_REPORTS = TrueCONST gbCUST_SHOW_HEADER_MENU_DT_EDITOR = TrueCONST gbCUST_SHOW_HEADER_MENU_UTILITIES = TrueCONST gbCUST_SHOW_SIDE_DT_REPORTS = TrueCONST gbCUST_SHOW_SIDE_EF_REPORTS = TrueCONST gbCUST_SHOW_SIDE_DT_EDITOR = TrueCONST gbCUST_SHOW_SIDE_UTILITIES = TrueCONST gbCUST_SHOW_FOOTER_MENU = TrueCONST gbCUST_SHOW_FOOTER = True

66 Chapter 3

Adding Content to dtWebASP scripting can be added to the functions in the util_extend.asp file in the root of the dtWeb. Code and content added to these functions will show up and be executed in the location specified by the function name. For example, to add a new menu item to the main menu, the following code could be added:

Function gaspHeaderMenuAfter(ByVal psArgs)%><a href="/new_section">Link to New Section</a><%End Function

The psArgs string contains some information about the context of the calling page. The contents of the psArgs argument are not documented at this time but they can be observed by outputting the string using "Response.Write psArgs".

Saving CustomizationsAny changes to the dtWeb should be backed up outside of the FactorySuite/DT Analyst directory structure. The entire dtWeb directory structure can be saved and restored. This is recommended because a re-install or service pack updates could overwrite customizations to the dtWeb. Some customizations may need to be re-done after a service pack update.

Troubleshooting 67

C H A P T E R 4

Troubleshooting


Contents• Setup

• Database

• Registry

• Logic Manager

• Configuration Manager

• dtWeb

• Event MonitorSetup

• Miscellaneous

Setup

The Setup will not run due to lack of Administrator rights.

The DT Analyst software setup program must be run with local Administrative rights. If the setup asks for a re-boot, the login when the computer is re-booted must also have local Administrative rights.

68 Chapter 4

Setup completes but hangs on reboot, then none of the DT AnalystTM programs run.

Problem

The PC hangs on reboot because some of the InstallShield files needed to complete the installation after reboot are missing. The result is that many of the DT Analyst files are not registered. This causes the Configuration and Logic Managers to immediately error and quit when started (the cursor will change to the hourglass quickly and nothing will happen). Repair and Remove functionality from the Windows® Add Remove Programs dialog will fail as well.

This is usually caused when a previous installation of the DT Analyst software has been removed and the suggestion for a reboot has been ignored.

Solution

Run the Setup.exe from the DT Analyst software disk again and select the Repair option.

The Setup has experienced a problem; examine the setup Log.

The setup process is logged in a file called DTAnalyst.log in the root of the drive that the program is being installed into.

Wonderware Common Components.Wonderware Common Components are installed whenever the Logic Manager or Configuration Manager are installed. The Configuration Manager uses the licensing subsystem of the Common Components and the Logic Manager uses the licensing and SuiteLinkTM subsystems.

DT AnalystTM installation location.The DT Analyst software is installed in the same directory structure as other FactorySuite software. If the DT Analyst software is being installed and other FactorySuite software is already on the PC, then the DT Analyst software will automatically install in the existing location. If no existing FactorySuite software is on the target PC, the user will be prompted for the installation location, but only if neither Configuration nor Logic Manager will be installed.

Troubleshooting 69

Uninstalling SQL ServerTM leaves DTDB database files.

Problem

Uninstalling MS SQL ServerTM from a PC leaves the database files intact (*.mdf and *.ldf files) including the DTDB database files. If MS SQL ServerTM is re-installed on the same PC in the same location, the DTDB database remains in the MSSQL\Data folder but the new installation of SQL ServerTM has no knowledge of it. If the DT Analyst software is re-installed and the Configuration Manager attempts to create the DTDB database, it will fail because the database files it is trying to create (DTDB_Data.mdf and DTDB_Log.ldf) already exist.

Solution

The solution is to delete or move the existing DTDB_Data.mdf and DTDB_Log.ldf files and then re-attempt the database creation wizard. The DTDB_Data.mdf and DTDB_Log.ldf contain any configuration and downtime data collected in the past so use caution in recommending that they be deleted.

dtWeb will not install because IIS 5.0 or 6.0 is not installed.

Problem

The dtWeb application will not install properly. The Windows® 2000 Server that will host dtWeb must be running Internet Information Server (IIS). IIS is installed by default with a typical Windows® Server installation but it is possible to not install it.

Solution

Install IIS on the Windows® Server. Use Add/Remove Programs in the Control Panel and select Add/Remove Windows® components. Re-attempt to install dtWeb.

dtWeb install may not create database connection string registry entries.

Problem

If dtWeb is installed on a server without any of the other components, it may not be able to connect to the database. This is because the dtWeb runs under the IWAM_<SERVERNAME> and IUSR_<SERVERNAME> accounts and these accounts do not have rights to add registry keys. The other DT Analyst applications create the registry keys if they do not find them there, dtWeb cannot.

70 Chapter 4

Solution

Use the DT Analyst Database Settings Utility to manually set the connection string information into the registry. The default settings should be:

Database User: dtdbApp

Database Password: dtdbApp

Security Type: SQL ServerTM Authentication

Database Server: <enter the database server name or IP address>

Database Name: DTDB

dtWeb not working due to file permissions on MSVBVM60.DLL.

Problem

The dtWeb may not display properly if the file permissions on the file MSVBVM60.DLL are not set properly. The error messages on the web page will vary depending on how the web-server is configured to report errors but the error should have some text like the following:

The call to Server.CreateObject failed while checking permissions. Access is denied to this object.

The DT Analyst setup program may replace the MSVBVM60.DLL file with a newer version. The setup program sets the appropriate permissions to the file immediately or after reboot depending on if the file is in use during the setup. In situations where the setup is not completed properly due to cancellation at critical points, system crash, or complication during reboot, the MSVBVM60.DLL may be left with too few permissions for the DLLs in the dtWeb to be able to use it properly.

Solution

Check the permissions on the MSVBVM60.DLL file. The file should be located in the WINNT\SYSTEM32 directory. Make sure the file allows the EVERYONE group at least Read & Execute rights.

Failed database creation.Problem

If there is a failure during the "Create New Database" wizard for any reason (out of disk space, etc…), successive attempts to create the database (of the same name) may fail.

Solution

Troubleshooting 71

The database creation process assumes that there is no database that exists with the name that is attempting to be created. If a database creation process fails, the problem should be solved (free up disk space, etc…) and the remnants of the database that was partially created should be dropped via SQL Enterprise Manager. The "Create New Database" wizard can be run by starting Configuration Manager and selecting "Create New Database" from the first dialog that is displayed.

Database

The dtdbApp Login is not working properly OR a new SQL ServerTM Login is not working properly for the DT AnalystTM components.

The DT Analyst applications use the dtdbApp login. The dtdbApp Login and User belong to the dtdb_spuser Role. Any Login/User that is going to be used by the applications must be able to execute all of the stored procedures as well as be able to read and write from all tables.

SQL ServerTM uses Windows® Authentication and the DT AnalystTM components are not connecting to the database.

If the SQL ServerTM is set for Windows® Authentication Only, then make sure that all of the PCs that are running DT Analyst applications have their database settings set to Windows® Authentication. The Configuration Manager, Logic Manager and Event Monitor access the database through the currently logged in user. The dtWeb accesses the database via the IWAM_<SERVERNAME> account.

Restoring a backup of the DTDB database to a different SQL ServerTM than the one it was backed up on.

Problem

If a backup of the DTDB database is restored to a different SQL ServerTM than the one it was backed up on, the DTDB Users may not map properly to the DTDB Database Logins. Deleting the Logins and Users and running the Database Repair from the Configuration Manager will not fix the problem either.

72 Chapter 4

Solution

Using SQL ServerTM Enterprise Manager, delete the DTDB Logins and Users. Run the following SQL script on the DTDB database.

/**************************************************** * DTDB Login Repair Script (8/9/2002) **************************************************** * IMPORTANT!!! Login as "sa" before running this * script, otherwise it will most likely fail. * ****************************************************/DECLARE @sDB VARCHAR(128)/****************************************************/--NOTE: Change these if using a different DB name!SET @sDB = N'DTDB'USE DTDB/****************************************************/EXEC sp_dropuser N'dtdbApp'EXEC sp_dropuser N'dtdbAdmin'EXEC sp_dropuser N'dtdbUser'

EXEC sp_droplogin N'dtdbApp'EXEC sp_droplogin N'dtdbAdmin'EXEC sp_droplogin N'dtdbUser'

EXEC sp_addlogin N'dtdbApp', N'dtdbApp', @sDBEXEC sp_addlogin N'dtdbAdmin', N'dtdbAdmin', @sDBEXEC sp_addlogin N'dtdbUser', N'dtdbUser', @sDB

EXEC sp_grantdbaccess N'dtdbApp', N'dtdbApp'EXEC sp_grantdbaccess N'dtdbAdmin', N'dtdbAdmin'EXEC sp_grantdbaccess N'dtdbUser', N'dtdbUser'

EXEC sp_addrolemember N'db_datareader', N'dtdbApp'EXEC sp_addrolemember N'db_datawriter', N'dtdbApp'EXEC sp_addrolemember N'dtdb_spuser', N'dtdbApp'

EXEC sp_addrolemember N'db_owner', N'dtdbAdmin'

EXEC sp_addrolemember N'db_datareader', N'dtdbUser'/****************************************************/

Run the Database Repair from the Configuration Manager to rebuild the Logins and Users.

DT AnalystTM is not able to connect to the database using the dtdbApp Login and Password; using the sa Login and Password works.

Problem

Troubleshooting 73

The dtdbApp (and other DT Analyst Logins) Login and Password is not allowing the DT Analyst applications to connect to the database, but the sa Login and Password is allowing the applications to connect. The DTDB database has been installed successfully and the dtdbApp Login exists and has not been tampered with. The SQL ServerTM is using SQL ServerTM Authentication.

The exact cause of this problem is unknown at this point and is being investigated.

Solution

In some cases, adding public access to the Master database to the dtdbApp Login will allow the applications to access the DTDB database and fix the problem.

Registry

Database connection string registry entries.All of the DT Analyst software (except the Event Monitors) connect to the database using connection string information stored in the DT Analyst portion of the registry. These registry entries are described below:

Registry Location

HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\DTAnalyst

DBConnectType

This describes the SQL ServerTM security method used to connect to the database. A value of 0 is SQL ServerTM Authentication (SQL ServerTM Login and Password) and 1 is Windows® Authentication (currently logged on NT User Name and Password).

DBLoc

This is the server name of the SQL ServerTM PC.

DBName

This is the name of the DTDB database. It should always be DTDB.

DBUser

IfSQL ServerTM Authentication is being used, this is the SQL ServerTM Login used to connect. It should be dtdbApp or a Login with equivilent rights.

DBPwd

If SQL ServerTM Authentication is being used, this is the password for the SQL ServerTM Login used to connect.

DBInstall

A value of 1 indicates that if the Configuration Manager cannot connect to the database, it shows the Database Create/Repair wizard. This is set to one when the DT Analyst software is first installed to guide the user through the database creation process.

74 Chapter 4

Modifying the DT AnalystTM database settings without going through the Configuration or Logic Manager.

The DT Analyst Database Settings Utility program (under the Wonderware FactorySuite | DT Analyst Start Menu folder) allows the changing of the database connect string settings in the registry.

Database integrity check.The Configuration Manager performs a Database Integrity Check when every time the application starts to make sure that the DTDB database is in relatively normal condition. The following items are checked during the integrity check:

• All DTA tables exist.

• All DTA fields exist.

• All DTA indexes exist.

• All DTA foreign key relationships exist.

• The proper number of stored procedures exist (each individual stored procedure is not checked in order to save time).

Depending on the severity of the problem, a Warning or an Error will be displayed. Any Errors will force the repair process to be run. If there are only Warnings, the Configuration Manager will attempt to run and the repair process may be run through the Tools menu.

The repair process will attempt to fix some of the conditions detected above as follows:

• Recreate any missing DTA tables.

• Recreate any missing DTA indexes.

• Recreate any missing DTA foreign key relationships.

• Delete and recreate all of the DTA stored procedures.

Note Missing fields are not re-created and that all stored procedures are dropped and recreated during this process.

Troubleshooting 75

Logic Manager

Logic Manager will not start due to licensing problems.

The license file on the Logic Manager PC must contain a valid "DT Analyst Server" feature line. If the feature line is valid and not expired, then make sure the number of enabled Downtime Definitions and Event Monitors in the DTDB database does not exceed the licensed amount.

Logic Manager starts but is not recording downtime events.

Open the Logic Manager monitor windows and make sure that the Logic Manager has loaded the appropriate configuration items to monitor the desired Downtime Definitions. Make sure that the Tags are "black" in the I/O Monitor and that they are reporting current values. If the correct configuration appears to be loaded and the Tags are being monitored, then double-check the logic in the Groups and Triggers.

Tags are showing up red in the I/O Monitor Window.A red line means that the Logic Manager is unable to communicate with the Tag or Access Name. Check the Access Name and Tag configuration. The Logic Manager will re-attempt to connect to Access Names where previous communication has failed. The Logic Manager will also attempt to re-connect with any Tags that have failed in an otherwise successful Access Name connection.

Tags are showing up yellow in the I/O Monitor Window

Tags appearing in Yellow indicate that performance is suffering and that Logic Manager may be missing data changes. Only SuiteLinkTM connections will indicate this state.

If any other applications are running that may be competing for processor time or network bandwidth, they should be closed. If nothing else is running on the computer and the tags consistently remain yellow, then the machine is simply not powerful enough to handle all of the tag changes that are occurring. If reducing the number of tags that frequently change is not an option, then the hardware must be upgraded or the configuration must be distributed across different Logic Managers running on separate computers.

76 Chapter 4

Logic Manager is having problems reading OPC Tags.

For any problems with accessing OPC servers, refer to the OPC Troubleshooting Guide included in the DT Analyst User Guide.

Momentary Tag Value changes not being detected by Logic Manager.

The Logic Manager has a minimum poll rate of 1000ms (1 second). This means that a Tag that holds a value for less than 1 second may not be detected. For example, A Trigger that is based on a Boolean Tag holding a value of 0 for longer than 10 seconds may evaluate to True after 10 seconds, even if the Tag value changed to 1 momentarily during that 10 second span.

This is a limitation of the Logic Manager and may be addressed in future versions.

Configuration Manager

Logic Manager is ignoring enabled items in the configuration.

If an item is disabled, all of its children items are treated as disabled, even though they don't show up disabled in the Tree-View. For example, disabling a System will cause all of its DTDefs, Groups, Triggers, etc… from being considered by a Logic Manager.

New license file limits not being recognized in Configuration Manager.

Problem

If a new DT Analyst feature line is imported into the wwsuite.lic file, they may not be reflected in the Configuration Manager immediately. The Logic Manager reads the Downtime Definition and Event Monitor limitations in the license file on startup. The Logic Manager writes the new limits to the database, and the Configuration Manager reads the license limits from the database.

Solution

After updating the DT Analyst licensing, run the Logic Manager. After the Logic Manager starts, restart the Configuration Manager and the new license limits will be in effect.

Troubleshooting 77

Configuration changes are not being reflected in the Logic Manager.

Configuration changes do not take place until the Logic Manager is restarted.

The configuration needs to be sent to support for troubleshooting.

File | Export Configuration creates an XML export of the entire configuration. This file can be emailed to tech support for identifying problems. An import utility may be available in the future for support purposes only.

Disabling a Shift has no effect.The Enabled check box in the Shift properties (Configuration Manager) dialog has no effect on the system functionality. The Enabled property of the Shift is not being used. It is for possible future use.

Delete Live Data DateThe default "delete before" date that is displayed in the Delete Live Data Wizard (part of the Archive/Delete Tool) comes up as the current date minus 1 year.

When the goal of the delete process is to delete all of the live data in the database, this is somewhat confusing, as most users assume it is the current date and proceed without looking closer. This is by design to protect against accidentally deleting current data.

dtWeb

Problems accessing the dtWeb application site.Problem

The dtWeb application should be available from the host webserver at the address http://<servername>/dtWeb. Depending on the specific network environment/proxy server settings on the target network, accessing webs on the webserver by the server's name may not work properly.

Solution

Access the dtWeb application using the webserver's IP address instead (http://<serveripaddress>/dtWeb).

Problem locating the dtWeb after installation.The dtWeb is at http://<SERVER NAME OR IP ADDRESS>/dtWeb.

78 Chapter 4

Accessing certain dtWeb pages displays generic web server error.

The dtWeb uses the DLLs listed in the Utilities | Versions section of the site. These DLLs must be accessible to and executable by the local IWAM_<SERVERNAME> account.

Event Monitor

There is a database connection error in the Event Monitor.

Double-check the connect string properties and verify that the computer has access to see the database server properly. Try database server name and IP address changes.

Database connection error on plant floor workstation.

The Event Monitor may not be able to connect to the database on a workstation that has limited security rights. By default, the Event Monitor connects to the database using the Named Pipes protocol. The Windows® 2000 security right, "Access this computer from the network," is required for the client to establish a connection to the database server. Changing the network protocol in which the client connects to the database server to TCP/IP will solve this problem. This can be done using the SQL ServerTM Client Utilities.

Events are not being displayed in the Event Monitor.

Systems must be assigned to report to Event Monitors. Events do not show up in the Event Monitor unless configured to do so.

Miscellaneous

System Downtime vs Downtime.Refer to the first topic of the Advanced DT Analyst Concepts section of the DT Analyst User Guide for more information.

Troubleshooting 79

License File.DT Analyst license files are required to run the Configuration or Logic Managers. After installation there are no license files present. License files must be purchased or 30 day demo license files can be obtained from a Wonderware distributor or possibly the Wonderware website.

80 Chapter 4

dt analyst application guide

Documents

wonderware logger

dt analysttm implementation

pilot implementation

dt analysttm project

pilot evaluation phase

discovery phase

best practices methodology

alarm logger