Kepware is a privately held company established in 1995 that is located in Portland, Maine. It is the largest OPC server company in the world, delivering 100,000 units annually with over 50 employees. Kepware's SNMP OPC Server software allows automation engineers to easily integrate and monitor Ethernet network devices from their OPC client programs. It supports features like auto discovery, MIB importing, and generating tags to monitor both managed and unmanaged devices. The document provides information on the server's configuration process and contact details for Transcend Automation to address any questions.
2. Kepware Overview
Why Kepware
Where and When
Terminology
Kepware’s SNMP OPC Server
Features
Configuration
Contact
3. Established in 1995
Privately Held
50+ Employees and Growing
Located in Portland, Maine
Delivering 100,000 units annually
Largest OPC Server company in the world
4. Fact:
Today, Kepware is the most widely OEM’d software product in the
Automation Marketplace…
(Other than Microsoft)
Why?
Quality, Driver Quantity, Product Architecture, Pricing, and Business
Model
Opportunity:
Kepware can deliver SNMP to a vast array of OEMs, Sales Channels and
End Customers. Proven Connectivity between your products and all
major software vendors can be taken for granted…
5.
6. OPC = OPen Connectivity through Open Standards
SNMP = Simple Network Management Protocol
NMS = Network Management System
Agent = Software module residing on a managed device.
MIB = Management Information Base
Public MIB = Conforms to IETF Standards
Private MIB = Unique to Device Manufacturer
OID = Object Identifiers
Managed & Unmanaged = Device with or without support
for SNMP
IETF - Internet Engineering Task Force
9. Using the Kepware SNMP
OPC Server software product,
automation engineers can
easily integrate the
monitoring and management
of their Ethernet network
devices into their OPC client-
enabled HMI, Historian, or
Alarm package.
10. Not all Ethernet network devices
are SNMP managed. The Ping
driver works along side the SNMP
driver to help monitor those
unmanaged devices. The Ping
driver automatically generates
OPC tags for each Unmanaged
device defined. These quot;heartbeatquot;
and quot;response timequot; tags provide a
standardized and reliable way to
monitor all devices in the Ethernet
network.
11. Auto Discovery – Save time by using the Auto-Discovery
tool to search your Ethernet network for managed network
devices
MIB Import – Import MIB files from manageable devices and
easily map network device MIB addresses to iSNMP tag
names
Network Analyst – Network Analyst gathers raw SNMP data
from network devices and continually performs calculations
to generate data that can be used, such as bandwidth
utilization and network error rate statistics
12. SNMP Traps Support - Many SNMP-manageable devices
can be configured to send unsolicited data to network
management software systems such as SNMP. By
configuring an SNMP device to send data without being
quot;polledquot; such as when a critical system tag goes into an
unfavorable state, you can reduce the need for quot;pollingquot; the
network device. SNMP supports receiving SNMP Trap data
via Events tags as well as through defined Trap OIDs.
Historical Data Attributes –Historical values are generated
by the SNMP driver (not the remote Agent/device) when an
OID has valid historical modifiers appended to it.
13. Events Tags – A FIFO-based queue to receive
Traps/Notifications from previously configured Agents.
Table Offsets – Table access is accomplished by enumerating
columns of a table. The SNMP Device driver uses an array-
like notation for Table access.
Scan Floor property – SNMP devices are typically scanned
at much slower rates than other controls equipment.
Scanning an SNMP device too quickly may result in
degraded device performance. The Scan Rate Floor has been
added to prevent users from inadvertently overloading
Agent/devices with read requests in the order of
milliseconds.
21. Once the MIBs
have been
imported, any
supported Client
application can
begin monitoring
the Network.
22. If you have questions regarding Kepware’s SNMP
OPC Server please contact Transcend Automation
Baiju.P.S Transcend Automation
Business Manager #776,1st Floor, 7th ‘A’ Main, HRBR Layout
Transcend Automation 1st Block, Kalyan Nagar,
Email: baiju.ps@transcenda.in Bangalore – 560 043
Mobile: +919986182625 www.transcenda.in
Notas do Editor
OPC – In its latest form is referred to as OPen Connectivity through Open Standards. Past definition was Ole for Process Control.SNMP - An application layer protocol that facilitates the exchange of management information between network devices.NMS - is a combination of hardware and software used to monitor and administer a network.Agent – are software modules that reside in managed devices connected to a network that collect and store management information MIB – is a collection of objects in a (virtual) database used to manage devices (such as routers and switches) in a network. MIBs describe the structure of the management data of a device subsystem Public - data conforms to IETF standards per device type Private – data set in a file from manufacturer (OID data unique to this device)OID - identifies a variable that can be read or set via SNMPKepwares SNMP Suite offers connectivity for both Managed and Unmanaged. Unmanaged is done with our Ping driver, included with the SNMP Suite. Unmanaged devices do NOT support SNMP but can respond to HeartBeat polls like communication Status & response Time
How does the automation professionalverify the plant network is OK? (with current practices) They either call the IT department or walk around and look for blinking lights and traffic indicators on networked devices.Because Automation controllers are dependant on the performance and reliability of the underlying Ethernet network and components there was a need for a better solution.SNMP OPC Server Gives Automation & Control users access to the entire control system.
This section covers some basic configuration steps when using the configuration wizard. Not all steps are included, for a more detailed step by step process please reference the SNMP user manual. 1st Step is to Create a “channel” which is where you will determine which communication driver you would like to use. In this case you will select the SNMP driver.2nd Step is to Create a “device”. This is where you define the Ethernet device you would like to communicate with.
1st Step is to Create a “channel” which is where you will determine which communication driver you would like to use. In this case you will select the SNMP driver.2nd Step is to Create a “device”. This is where you define the Ethernet device you would like to communicate with.
SNMP Objects are collections of information with shared traits. A managedObject consists of one or more identifiers.A MIB in a managed device typically consists of many public and private Objects (and resulting object identifiers).OIDS – Object Identifiers - Think of OIDs as items,tags or memory addresses
Supported Client technologies include: OPC Data Access: 1.0a, 2.0, 2.05a, 3.0OPC UA:Coming soon to publicDDE Formats:CF_Text, AdvancedDDEOther Formats:FastDDE & Suitelink for Wonderware NIO Interface for iFIX
