invensys condition monitoring 2.1 february 2006. 2invensys confidential agenda new features...
Post on 25-Dec-2015
218 Views
Preview:
TRANSCRIPT
Invensys Condition Monitoring 2.1February 2006
2Invensys Confidential
Agenda
New Features– ArchestrA, OPC A&E, Usability
Data Sources – Setup, Troubleshooting
Environment– Entities and Statistics
– Web Services, Email, BizTalk 2004
– Licensing
Demo
3Invensys Confidential
Agenda
New Features– ArchestrA, OPC A&E, Usability
Data Sources – Setup, Troubleshooting
Environment– Entities and Statistics
– Web Services, Email, BizTalk 2004
– Licensing
Demo
4Invensys Confidential
New Features
ArchestrA Industrial Application Server
OPC Alarms and Events
Association Templates & Batch Load
Delta and Absolute values
Dynamic Text in Descriptions
Microsoft BizTalk 2004 Integration
Association Status & Current Values
Search capabilities & Association Lookup
Administration of Configuration files
Integrated Windows Security
XSL Reports
5Invensys Confidential
New Features
ArchestrA Industrial Application Server support– ArchestrA IAS 2.0
– View in CM Configurator displays deployed areas and objects only
– It shows similar icons as found in ArchestrA IDE, less the adornments. It will not show object templates or non-deployed objects.
– Different device types: Simple field devices, OPC, Analog, Discrete and User Defined devices.
– Device objects have numerous attributes, runtime and development time values, and the quality of data indicator. Values are variant data type, usually a string, integer, Boolean or float
value but can also be a XML string or data structure.
– Data structure and array values are not supported by CM. User Defined Attributes.
– The data quality indicator is used to indicate the connection with the LMX server. A quality value of “bad” means CM / LMX lost contact with the server.
6Invensys Confidential
New Features
ArchestrA Industrial Application Server support
7Invensys Confidential
New Features
OPC Alarms and Events– Alarms and Events 1.x
– View in CM Configurator displays the Process Area organization implemented by the OPC Event server.
– If a new OPC Event Server is installed, this instance of the monitor will not include any process area information in the local cached copy. If the IOPCEventAreaBrowserObject interface is supported, the process
area information will be fetched and returned to the Configurator. If IOPCEventAreaBrowserObject interface is not supported, the
Configurator will notify the user and provide an option to allow the user to manually define this hierarchy
– This approach ensures that the OpcAlarmsAndEvents.xml is analyzed first.
8Invensys Confidential
New Features
OPC Alarms and Events
9Invensys Confidential
New Features
Association Templates– Allow rapid specification of similar
monitored elements Template selection via dropdown Drag, Drop, Two Clicks
– Templates are created from existing associations Templates can be defined for all
trigger generation rules, except custom expressions.
Validation and type checking are done on the association.
– Provides a management interface for the templates.
– Allows changes in a template to be selectively reflected in the derived associations.
– Allows enable/disable monitoring for all derived associations
– Can override parameters on specific association definitions
10Invensys Confidential
New Features
Batch Load– Leverages association templates to generate associations
– Import data via XML file with five attributes per association <Template> - Template name <RTP> - RTP path, elements enclosed in square
brackets <Entity> - Entity or Asset Name <Site> - Site for the asset <StatType> - Statistic on the asset
11Invensys Confidential
New Features
Delta and Absolute values– Enables monitoring and triggers based on the rate of change between
readings
– Options for the value to use now include: Real (Default) - Actual reading from the historian or device Absolute - Absolute value of the reading Delta - Positive or negative change since the last
reading Absolute Delta - Absolute value of the change since the last reading
– Can not be changed when editing an association
12Invensys Confidential
New Features
Dynamic Text in Descriptions– Provides the ability to use runtime information within the descriptions of
Work Orders, Work Request, EAR, Statistics and Email
– This context information makes the resulting document much more useful
– The wizard provides the tags which get substituted at runtime
– Extremely useful when using Association templates
– Substitution tags include ‘static’ information such as Entity, Site, Statistic RTP Name, Data Source Generation rule and its specification
– And dynamic runtime information like Result Of Value Rule (ValueRule.Value) All values of the readings Time of Last Reading Time of First Reading Current Standing Work Order/Request Number
13Invensys Confidential
New Features
Dynamic Text in Descriptions
14Invensys Confidential
New Features
BizTalk 2004 Integration– Significant events detected by Invensys Condition Monitoring 2.1 can be
configured to trigger workflows defined in Biztalk.
– Allows Condition Monitoring to leverage enterprise workflows as optional actions
– Flexible implementation Dynamically binds to BizTalk interface
– Condition Monitoring invokes a user specified operation exported by a BizTalk Orchestration.
– Condition Monitoring presents methods that accept an XML document
– The XML document contains context data that can be used to further customize the workflow
15Invensys Confidential
New Features
Association Status– A Configurator instance will reflect the last know evaluation state during an
update cycle If an action (Work order, BizTalk, etc) was triggered during the last
update cycle the association shows “Red” If an action (Work order, BizTalk, etc) was not triggered during the last
update cycle, but there were readings of interest it will show the association as “Yellow”
– A reading of interest occurs when some of the criteria for the generation rule is met
Current Value– Allows the user to view within the Configurator the current value of a
particular RTP point in real time
16Invensys Confidential
New Features
Association Status
17Invensys Confidential
New Features
Search – Find specific nodes within the RTP tree or the entity tree
– Supports previous / next / full word / match case searches
– Keeps history of previous searches
– Supports full regular expression syntax for more complex searches
Association Lookup– Provides a simple tabular interface to sort associations
– Selecting an association then expands both the source RTP point in the tree and the Entity / Statistic side as well
18Invensys Confidential
New Features
Administration of Configuration files– The CMAdmin utility now provides a simple tabular interface to modify the
configuration parameters of the CM Monitor engine and other CM components
– Some items like LoggingLevel will be applied right away, others require the CM Monitor or the specific component to be restarted
Integrated Windows Security– Authorization of a user of the Configurator gets checked against
membership in a CMAdministrators on the server
XSL Report– A simple summary report of the associations on particular monitor
19Invensys Confidential
Agenda
New Features– ArchestrA, OPC A&E, Usability
Data Sources – Setup, Troubleshooting
Environment– Entities and Statistics
– Web Services, Email, BizTalk 2004
– Licensing
Demo
20Invensys Confidential
Data Sources
Filters
AIM* Historian Foxboro
EFS Foxboro
InSQL Wonderware
ArchestrA Wonderware
SmartSignal eCM SmartSignal
OPC OPC Foundation (Standard)
Licensing– Data Sources
– Associations
– Web Services
21Invensys Confidential
Data Sources
Filters– Each Data Source has a unique set of attributes that can be filtered.
– For example, OPC has OPC Server, Item name, Include hosts, Process area and Event source.
– The list of Entities can also be filtered.
– Multiple wildcards can be entered, e.g. AD1*,AD2* would show all computers named AD100 thru AD299.
– More information on the usage of filters can be found in the online help.
– Filtering the list of Entities or Real Time points may display a message that an association is invalid. CMMonitor will continue to collect statistics, however CMConfigurator is not able to validate associations that are filtered from the list.
22Invensys Confidential
Data Sources – AIM* (Foxboro)
AIM* -> Uses AIM* third party libraries.
– CMAIM.dll -> Implementation
– AIMMANAGEDCODEWRAPPER.DLL-> Managed Code Wrapper
– NETAPIDOTNETWRAPPER.DLL -> C++ Wrapper
– APISERV.DLL -> AIM* library
The datasource resolves the historians to display via broadcasting. Once the host is identified, proprietary (AIM*) API's are used to fetch RTP's names and values for the selected historian.
In the case of alarms and events, the user has to update the AlarmCodes.xml that are specific to the implementation
Note that the AIM* machine generally are set to be on GMT (e.g., 5-6 hours ahead)
Several components, individually licensed, needs to be active
Secured, User must be registered with AIM* Historian
23Invensys Confidential
AIM* Setup
an_init.cfg - Specifies the behavior of the AIM* api’s. Location is specified by the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\SIMSCI\AIM\SETTINGS\an_init
The most significant parameter is the values used for [TCPIP]. In this case, AWXPVM specifies and alias for the location (IP Address) of the server hosting the AIM* Historian instance. When running, level of debugging can be adjusted by the tracelevel and Printerr flag.
tracelevel=1 and Printerr=2 generates very detailed logs which can be used to diagnose runtime issues. The ouput will be sent to a file specified by the LogFilePrefix option (e.g., c:\an1.log).
24Invensys Confidential
AIM* Implementation
Display in Configurator
Historian and Tags may be selected for monitoring. Selection of historian specifies Monitoring of System Alarms.
Display of current value for the selected Tag
33Invensys Confidential
Data Sources – EFS (Foxboro) EFS – Extended Frame Service (version 1.1)
– Must be installed and registered properly– Unfortunately, the installer does not provide a means of installing only the
components required for CM. Typically, this is the EFSObject.DLL and a series of XML schemas and templates.
– CMEFS.dll Implementation– EFSMANAGEDCODEWRAPPER.DLL Managed Code Wrapper– EFSWRAPPER.DLL C++ Around efsobject.dll
EFS fetches data from an EFSDB (System) ODBC datasource. The database is either a MS SQLServer or MS Access.
EFS framework monitors devices and persists large and verbose XML documents describing the state of the device into the database.
EFSObject.dll provides the api’s used to fetch the list of configured devices, their parameter and monitored data.
If there are problems fetching data, may have to re-register efsobject.dll
34Invensys Confidential
EFS Implementation
Display in Configurator
Control Processors and Parameters may be selected for monitoring. Selection of Control Processor implies Device Status Monitoring
Display of current value for the selected Tag.
EFS provides minimal data on the current value of the selected RTP Point
35Invensys Confidential
Data Sources - InSQL (Wonderware)
IndustrialSQL Server captures real-time, high volume data and makes it available for business applications.– Based on extensions to SQL Server.
– Database name is Runtime
– Implementation includes a series of views which reduces the runtime data.
– Three types of tags (Discrete, Analog, Event)
CM uses .NET’s ODBC Api to execute queries directly against these views– Trusted connections are used to access Runtime database.
36Invensys Confidential
InSQL - Implementation
Display in Configurator
Only leaf level Tags may be selected for monitoring
Display of current value for the selected Tag
37Invensys Confidential
InSQL – Troubleshooting
Current Value is always blank or quality is always BAD– Confirm that IndustrialSQL Server instance is started
Open InSQL ConsoleStart/Programs/Wonderware/IndustrialSQL Server/InSQL x.x
System is running
Status of System
}
38Invensys Confidential
Data Sources – ArchestrA (Wonderware)
Implemented using Wonderware Smallworld Components– LMX Services
Provides runtime values
– GRAccess Web Service Provides design time settings
LMX Server
CM.Configurator
CM.Monitor
LMX Service
HT
TP
Pro
toco
l
TCP
CMArchestrA.dll
LMX Client
GRAccess WS
IIS
ArchestrA Platform
Design-time Component
Interface
Run-time Component Interface
39Invensys Confidential
ArchestrA Implementation
Displayed in Configurator
Attributes may be selected for monitoring.
Display of current value for the selected Tag
40Invensys Confidential
ArchestrA
LMX Server– Installed on AIS
Platform server only– IIS is required to
provide web services– Has it’s own Windows
EventLog section
LMX Service– Windows service– Can be installed on any
machine including Platform server
– Communicates with Server and caches client subscription values
– Has it’s own Windows EventLog
41Invensys Confidential
ArchestrA
LMX Client component– Installed on the Condition Monitoring Monitor system
– Subscribes to the ACE LMX Service for values
– Caches values locally
GRAccess Web Service– Provides ArchestrA design time information
– Web Service based component
– Installed on the Platform only
– IIS is required for this component
42Invensys Confidential
ArchestrA – Troubleshooting
– Check the EventLogs for errors
– LMX Service has a communication dependency with LMX Server You must restart the Service if the Server is restarted
– Including a reboot
– Verify client setup by selecting current Runtime value
43Invensys Confidential
ArchestrA – Troubleshooting
Installing LMX Server on Windows 2003 SP1– Upgrading to SP1 with
LMX previously installed has no issue
– Post SP1 installation requires the IIS Application Pool be changed to valid user account
44Invensys Confidential
ArchestrA – Troubleshooting
– Set account for IIS AppPool Open IIS and select
Application Pools Open the Properties dialog
and select Identity Set a valid domain account or
use the local AIS account Save and restart IIS
45Invensys Confidential
ArchestrA – Troubleshooting
– Configuration file LMXService.exe.config Windows\system32 directory Client/wellknown section controls the URL to LMXServer <client>
<wellknown type="Invensys.Solutions.Lmx.ILmxServer, ILmxServer" url="http://localhost:8080/LMXServer/LmxServer.rem"/>
</client>
– Configuration file LMXClient.exe.config Windows\system32 directory Client/wellknown section controls the URL to LMXService
<client>
<wellknown type="ILmxService.ILmxService, ILmxService" url="tcp://lmx34:4444/LmxService" />
</client>
46Invensys Confidential
ArchestrA – Troubleshooting
GRAccess– Verify installation by testing
the WS Identity method
– Open the IIS Management snap-in
– Select the Identity method
– Invoking the test will return the name of the connected user name
47Invensys Confidential
ArchestrA – Troubleshooting
– Condition Monitoring Monitor settings for GRAccessWS is in CMarchestra.dll.config
<!-- setting required for integration with GRAccess web services -->
<add key="GRAccessURL" value="http://lmx34:8080/AAGRAccessWS/AAGRAccessWS.asmx" />
<!-- setting needed for WW services -->
<add key="GalaxyServer" value=“LMX34" />
– Common installation error problem GRAccessURL is the URL to the web service GalaxyServer is the Windows name of the server
48Invensys Confidential
Data Sources – SmartSignal (SS)
– Smart Signal is a Avantis Partner which has a comprehensive, high end monitoring solution called Smart Signal eCM.
– For the current implementation, we worked with their architect to define a workflow for monitoring the results of their analysis (in the 3.2 version of their engine).
– Assets are modelled as follows
- Category - Asset - Mode
- Model
- Sensor
– Condition Monitoring scans for events that have been logged against the selected mode.
49Invensys Confidential
SS - Implementation
Display in Configurator Only Mode type nodes may be selected
for monitoring. Model and Sensors are not used in Condition Monitoring, but shown as is done in the eCM tool.
Display of current value for the selected Mode
If no incidents where observed, then a message appears instead of this dialog.
50Invensys Confidential
SS – Troubleshooting
– Condition Monitoring queries the data stored in the SQLServer database. If there are problems retrieving the data Condition Monitoring Uses SQL Server authentication. The values for
the specific database, user id and password to use are stored in the LSA. Ensure that these values are correct.
– To simulate an incident, insert a record into the database Mode records are being monitored Ctrl+N on the selected Mode provides the ID of the mode.
Ctrl+N the parent this this treenode, provides the ID of the asset (machine).
insert into dbo.tblobservation values {1 000 000, {ts '2007-01-01 01:00:00' }, 1, 96, 99}
where 96 and 99 is id of asset and mode. A time in the future is specified
51Invensys Confidential
Data Sources – OPC
– OPC - OLE for Process Control
– CM Supports monitoring of Data Access (1.x, 2.x and 3.x) and Alarms And Events Specification
– Built upon version 1.3 of the OPC Foundations .NET api libraries (OpcComnCtrls.dll, OpcNetApi.Com.dll, OpcNetApi.dll, OpcNetApi.Xml.dll)
– These are GAC'ed so you have to make sure a compatible version is installed.
– When attempting to connect to remote hosts to obtain a list of Data Access (DA) or Alarms and Events (A&E) Servers, OPC uses DCOM to launch a process call opcenum.exe to enumerate the opc servers on the remote host. The current user must have launch and execute permissions for this process on the remote host. In addition, you also need to look at the permissions on the OPC Server you are trying to communicate with.
– www.opcfoundation.org publishes the following document for information about using OPC and DCOM.
“Using OPC via DCOM with Windows XP Service Pack 2”
52Invensys Confidential
OPC Implementation - Data Access
Display in Configurator Only OPC Items with a Green icon may
be selected for monitoring Display of current value for the selected
OPC Item OPC implementation provides
significant detail about the selected point
53Invensys Confidential
OPC Implementation – Alarms And Events
Display in Configurator Only OPC Source nodes may be selected
for monitor OPC Alarms and Events are event driven.
Show current values is not supported for events.
54Invensys Confidential
OPC – Troubleshooting
– OPC Slow displaying list of accessible machines If the network is slow or is very large, a filter should be in place before
expanding the OPC root node. If a machine is physically on a domain but for some reason not registered
with the domain server, the IP of the specific machine may be specified in the Include Host option in OPC Filter.
– Alarms and Events not displaying expected Process Area or source hierarchy Confirm that custom Process Area and Source has not been specified for
the selected OPC A&E Server. If no entries are display but some are expected, determine if the selected
OPC A&E Server supports the OPCEventAreaBrowse interface. If not, user must manually configure the Process Area/Source hierarchy.
Check filtering
55Invensys Confidential
OPC – Troubleshooting
– If no OPC Servers are found for a particular machine and some are expected, it is likely a DCOM security issue Check permissions using DCOMCNFG. See “Using OPC via DCOM with XP SP2.pdf” from the OPC Foundation
web site
– Also confirm that OPC Core components are setup properly e.g., OpcEnum should be running as a service.
56Invensys Confidential
Data Sources – Licensing
Licensing– Same implementation as in Avantis.PRO
– Based on Macrovision FlexLM
– Flexible licensing options Every component is licensable
New Names– All licenses renamed for this release
New licenses are required for CM 2.1
CM Monitor server InvensysCM
57Invensys Confidential
Data Sources – Licensing
Data Sources– Each data source requires a license– Data source licenses are derived from the base license name
InvensysCM.AIM InvensysCM.EFS InvensysCM.ArchestrA InvensysCM.InSQL InvensysCM.SS InvensysCM.OPC
– Association points are separately licensable The value is the total available associations that can be mapped InvensysCM.RTPmap
Avantis Web Services– Licensing changes requires a license update– AvWebService
58Invensys Confidential
Licensing Support
Avantis License Manager– The Avantis FlexLM license service
– The service will detect “back-dating” and other common ploys to circumvent licensing
– CM Monitor is configured in the CMMonitor.exe.config file
<userSettings>
<add key="LicenseServer" value="q13" />
– It is possible to setup failover license servers using similar same syntax found in Avantis.PRO Comma separated list of servers and TCP ports Automatic fall over behaviour built-in to FlexLM
<add key="LicenseServer“ value=“Server=q013,5012@d012,5011@d011” />
59Invensys Confidential
Agenda
New Features– ArchestrA, OPC A&E, Usability
Data Sources – Setup, Troubleshooting
Environment– Entities and Statistics
– Web Services, Email, BizTalk 2004
– Licensing
Demo
60Invensys Confidential
Environment
Environment Setup– Using Templates from Avantis.PRO– Setting up Entities and Statistics– Email Server– BizTalk 2004 Server– Web Services
Security
Association Templates
Association– Trigger Rule / Value Rule / Data Type
Configuration and Administration– Logging levels– Message Queues
Event Log
Console mode
61Invensys Confidential
Environment Setup
Using Templates from Avantis.PRO– To create Work Requests, Work Orders, or Equipment Activity Records
with Condition Monitoring, templates need to be available in Avantis.PRO.
– The title from the template will show up on the final step of the Wizard.
– Only templates from the site chosen during the install will be displayed in the drop down.
– Nothing further needs to be done for Condition Monitoring to see the template.
– A new Work Request / Work Order / Equipment Activity Record will not be created until the Reissue Interval has elapsed.
Troubleshooting– If the list of templates is not what you suspect then ensure the Condition
Monitoring site was set correctly during the install.
– If the title of the Template is not a valid string, then see the troubleshooting section for the web services.
62Invensys Confidential
Environment Setup
Templates
63Invensys Confidential
Environment Setup
Setting up Entities and Statistics– Only statistics that are configured for
real time integration will appear in the Configurator.
– For an Entity to appear in the Configurator, it must have at least one real time integration statistic.
Troubleshooting– If the list of Entities is less than what
you are expecting for this site, then check that a filter is not in effect.
– If the list of entities is not what you suspect then ensure the Condition Monitoring Site was set correctly during the install.
– Check that the Web Services are pointing to the correct environment and are running. (e.g. http://<webserver>/Avantis WebApps/webservices/session.asmx)
64Invensys Confidential
Email Server Notes
Setup Email– CMMonitor.exe.config – Set by the installer
Sets the from email address
<add key="DefaultFromEmailAddress" value="Everybody@Invensys.com" />
– Uses Windows MAPI interface Set the name of the SMTP email server in Avantis Web Services
– Web.config<add key="EmailServer" value="picasso" />
65Invensys Confidential
Email Server Troubleshooting
Error with Mail Server Communications– Check Monitor log file
– Failure to connect to Mail Server will be recorded in the Monitor log file. Additional tracing information will be present in the exception message.
<Method name="SendEmail" context="[2502_dsfsf][CfgRecID:2b2245a1-f489-451c-9148-3fefd9f2421c][Record:968dcf11-de79-4a74-a3a0-35a3f288da1c]">
<Parameter name="Email">
<Object name="Email">
<Message ltext="System.Runtime.InteropServices.COMException (0x80040213): The transport failed to connect to the server.
"
stext="" severity="2" msgid="99999-99" />
</Messages>
</Object>
</Parameter>
</Method>
66Invensys Confidential
BizTalk Notes
Configuration Files– CMMonitor.exe.config file
Sets whether BizTalk is enabled<add key="EnableBizTalk" value="true" />
– CMWSInvoker.xml file Key/Value pair layout
<?xml version="1.0" encoding="utf-8"?>
<CMWebServiceEndPoint>
<Biztalk>
<endpoint key="1" name="Service1 Webservice" description="Service1 Port" biztalkUrl="http://BTServer/BigWebService/Service1.asmx" />
</Biztalk>
</CMWebServiceEndPoint>
67Invensys Confidential
BizTalk Troubleshooting
Configurator must be restarted to pickup any changes to BizTalk (adding new Orchestrations and operations)– Configurator refresh does not clear BiztalkCache
No orchestrations and operations display in Configurator – Ensure CMWSInvoker.xml entries are all valid
The published web service on BizTalk 2004 must be anonymous. – CM invocation of the published methods currently does not pass
credentials.
68Invensys Confidential
Web Services
Setup– Web Services server install is part of Avantis.PRO server components– CM installer only sets up the server name to use
Troubleshooting Failures here are generally
– invalid username / password– License unavailable– Web services server is unavailable
Retries up to 5 times Unsent CM Monitor events are queued – not lost, resent automatically
when service is restored Configurator would be unavailable
Binary data can not be sent without first being text encoded– The SOAP protocol strictly enforces this– Bad data in the database in the form of unprintable characters will
cause web service methods to fail
69Invensys Confidential
Security
CMAdministrators group– As of Condition Monitoring 2.1, when connecting to the Condition Monitoring
service, the current user must be a part of the CMAdministrators group.
Connecting to Other Instances– The Configurator will only connect to Monitors running on the same port
(5444), and at the current level (2.1).
– If running the Monitor Service on Windows 2003 Service Pack 1, then ensure the CMAdministrators group is part of the Performance Monitor Users.
70Invensys Confidential
Association Templates
– Feature introduced to facilitate rapid specification of new similar monitored real time points.
– Templates are created from existing associations
– Checks to determine if template uses a data type that is incompatible with the selected rtp point.
– Changes to a template can be propagated to associations based on that template.
– Templates are used in wizard and in Batch Associate Mode.
– Descriptions should not include RTP specific strings
– Special cases Templates derived from AIM* Alarm monitoring is available only when
similar AIM* rtp points are selected. Templates with User Defined Expressions are not supported.
71Invensys Confidential
Association Templates-Troubleshooting
If an Association Template does not appear in wizard– Selected RTP point may not be compatible with template
– Invoke Manage Template option to determine if Display setting is checked
– Refresh configurator to get the latest information known to the monitor
– Check CMMonitor logs for errors.
– Check CMTemplates.xml (CMTemplatesFileName option) for corruption.
72Invensys Confidential
Trigger and Value Rules
CMMonitoring engine workflow
AccumulateReadings
AccumulateReadings
GenerationRule
ApplyValue Rule
ApplyValue Rule
PerformSelectedAction(s)
PerformSelectedAction(s)
Time To GenerateGeneration Rule Satisfied
XMLplaced in MSMQ
73Invensys Confidential
Trigger and Value Rule Matrix
– The data must be understood to determine the best trigger and value rule to use.
– Available trigger rules depends on the number of RTP point(s) selected for monitoring.
– Available value rules depends on the type of trigger rule selected. Failure to respect these restrictions will result in incorrect behaviour.
– Rule matrix specified in the MonitorMapping.xml loaded by CMConfigurator. This file should not be modified.
– User Defined Expressions have to be coded carefully if you plan to use it in multiple associations.
74Invensys Confidential
Configuration and Administration
Configuration Files– The configuration files can be updated from the Condition Monitoring
Administrator. Click Tools, Settings...
75Invensys Confidential
Configuration and Administration
Troubleshooting– The Condition Monitor service needs to be restarted for most settings to take effect.
One exception is the logging level. This will take effect right away. Logging Level 0 is the default, and has minimum output. Logging Level 3 is the highest and outputs all traffic.
– The output from the Monitor service is sent to the file CMRuntime.log.
76Invensys Confidential
Configuration and Administration
Message Queues– Condition Monitoring uses Microsoft Messaging Services (MSMQ).
– Messages that cannot be sent to the Avantis Web Services are sent to the queue until the Avantis Web Services are available again.
– The queues are created at the time of Installation.
– Failed attempts can be reviewed to see what the problem was. Goto Computer Management->Services and Applications->Message
Queuing->Private Queues->failedeamrequest->Queue Messages to see the current list of failed requests.
77Invensys Confidential
Troubleshooting
Console Mode– The Monitor can be started from the Command Line. To do this:
Stop the service from the Services Control Panel. Navigate to the C:\Program Files\Avantis\Condition Monitoring\bin
directory. Type “cmmonitor /r” The output will now be logged to the screen, and you can stop the
monitor with Ctrl+C.
Event Viewer– Condition Monitoring has it’s own
section in the Event Viewer.
78Invensys Confidential
Agenda
New Features– ArchestrA, OPC A&E, Usability
Data Sources – Setup, Troubleshooting
Environment– Entities and Statistics
– Web Services, Email, BizTalk 2004
– Licensing
Demo
79Invensys Confidential
Questions
80Invensys Confidential
The right information.– Easy access to the information
you want to see, the way you need to see it.
To the right people– Role based configuration.
– Intuitive design delivering unparalleled use-ability.
At the right time.– Real time information
The Approach to Asset Intelligence
top related