Image

Unlock Your IIoT Today

Connect machines, Collect data, Combine manufacturing data and operational information. Compute previously unavailable information sets. Convey discovered information and make business decisions with confidence.

Achieve 5C

KepConnect is a unique service that shims multiple Kepware™ communications servers and your enterprise systems. Data exchange between the two environments is accomplished through Kepware’s IoT Gateway agents. With KepConnect, you choose what to connect, collect, combine, compute, and convey. index

Interop With Enterprise Systems

Leverage the Microsoft.NET framework and transform industrial data into information and knowledge through C# scripts.

Script Missing PLC Logic

Create custom representations of data from multiple PLC sources.

Generate Knowledge With Splunk

Combine manufacturing and operational data and convey it into Splunk with a single line of code.

Open Source

Approach IIOT with a pragmatic lens and a community driven framework.

Web Application / HTTP API

Created using the latest version of Microsoft ASP.NET MVC and Web API.

Connecting Machines

Kepware Technologies is the only player that satisfies our requirements of communicating with industrial programmable logic controllers on-premise. We have researched platforms from larger and smaller companies and arrived at the conclusion that only KEPServerEX™ fits into our IIOT strategy as a data broker.

  • Industrial Grade

    The focus of their communications platform remains on connecting machinery and industrial equipment.

  • Forward Thinking

    The IoT Gateway enables communication with industrial equipment out of the box using standards such as HTTP and MQTT.

  • Customer Oriented

    They strive to improve their product by listening to their customers’ needs. This is evident through new feature releases.

Scripting Engines

KepConnect has four scripting engines:

  • feature scripting engine
  • action scripting engine
  • stream scripting engine
  • database seeding script engine

All scripting engines utilize the Managed Extensibility Framework to load script libraries during engine initialization. This approach allows you to add, replace, and remove script libraries on the fly.

The feature scripting engine is triggered by an HTTP POST to the /api/feature endpoint from any HTTP client. The inbound payload must be JSON and in the correct format. Based on the requested thing’s identifier value and requested environment, the correct IoT Gateway HTTP server agent URI is retrieved from the service endpoints list. Then, a user script is located by matching the thing’s kind (or category type) and requested unlisted feature name. An instance of the matching script is created and invoked with the received external features and any defined lookups. Any reading and writing of internal features defined in the script occurs against the previously retrieved service endpoint URI.

Terminology

Internal Feature

Device I/O point.

An internal feature is an OPC tag which identifies a specific I/O point on the connected device. Tags become available to Kepware Proxy once they are added to an IoT Gateway agent. An internal feature can have a virtual entity.

External Feature

Client supplied parameter.

An external feature is a key-value pair supplied by a KepConnect client. It can also be the active key-value pair within KepConnect's lookup data set.

Unlisted Feature

The missing PLC feature.

An unlisted feature is a combination of internal and external features to form a previously non-existing feature.

Lookup Data Set

A keyed value.

A lookup is a collection of key-value pairs of the same key. Only one of these key-value pairs is the active one.

Thing

A physical, connected entity with a virtual representation.

A thing is a representation of a KEPServerEX channel with a physical and connected device. A thing can also have internal and unlisted features, and a virtual entity. It also belongs to a particular type or kind of things.

Aggregated Thing

Combination of multiple things to form a larger system.

An aggregated thing is a combination of multiple things. Aggregated things are the primary way of constructing unlisted features that require data from multiple PLCs. Each part plays a specific role within the larger system.

Virtual Entity

The enterprise context of a thing or its internal features.

A virtual entity is a cross-reference between a thing or its internal features and the thing's representation in an enterprise context, such as a database.

Service Endpoint

IoT Gateway HTTP server agent locator.

A service endpoint contains the URI of an IoT Gateway HTTP server agent, along with an environment name and geographical location.

Feature Script

C# script of an unlisted feature triggered by external clients.

A feature script is a user created C# script to read and write the IoT Gateway on demand. A feature script also accepts external features and returns values that represent an unlisted feature.

Action Script

C# script triggered by ingestion of data from the IoT Gateway.

An action script is a user created C# script that is invoked when ingested IoT Gateway data matches specified regular expressions.

Stream Script

C# script triggered by ingestion of data from non-OPC clients.

A stream script is a user created C# script that is invoked when ingested non-OPC data matches the stream name.