PTC Acquisition Bolsters Internet of Things Offering

PTC Acquisition Bolsters Internet of Things Offering

Following on to last week’s quick post of PTC’s Internet of Things acquisition of Kepware, I’ve gone a little deeper into the build up to and the strategy of the acquisition.

First off, the Internet of Things is a strategy. It isn’t a “thing.” PTC management seems to “get it.” As you’ll read further down, PTC is not pursuing a simple bolt-on strategy such as what several companies have come to me to help justify. This appears to be a serious attempt to assemble a complete ecosystem / platform going beyond a simple IoT play to offer a business solution to customers.

Warning note. PTC is acquiring software companies and attempting to blend their technologies into a coherent whole. We’ve witnessed many of these seemingly simple processes go south quickly. But PTC has done this before in its core market, then again in the services market. I have confidence the company will show the way in a complete solution.

PTC is paying a large premium for Kepware–Up to $120 million for a company with about $20 million in annual sales. It obviously thinks there is a tremendous upside to its IoT business.

From the press release: PTC announced it has signed a definitive agreement to acquire Kepware, a software development company that provides communications connectivity to industrial automation environments, for approximately $100 million, plus up to an additional $18 million based on achievement of certain strategic initiatives and financial results. The acquisition will enhance PTC’s portfolio of Internet of Things (IoT) technology, and accelerate the company’s entry into the factory setting and Industrial IoT (IIoT).

Founded in 1995 and located in Portland, Maine, Kepware serves customers in more than 120 countries in such industries as manufacturing, oil and gas, building automation, and power and utilities. The company’s flagship product, KEPServerEX, connects disparate devices and control systems, providing users with a single source of industrial data.

Kepware’s KEPServerEX will become a strategic component of the PTC ThingWorx IoT technology platform. Once the companies’ products are integrated, machine data will be able to be aggregated into the PTC ThingWorx platform, integrated with a wide array of internal and external information, and then automatically analyzed using ThingWorx machine learning capabilities. The integration will allow organizations to gain enterprise-wide insight and to proactively optimize mission-critical processes – enabling them to improve operational performance, quality, and time to market.

In its June 2015 research report, entitled The Internet of Things: Mapping the Value Beyond the Hype, the McKinsey Global Institute identified the factory as one of the largest sources of potential value to be realized from the adoption of the Internet of Things. PTC has established a dedicated business segment and has formed a strategic alliance with GE to pursue this brilliant factory opportunity. The acquisition of Kepware is intended to complement the alliance with GE.

Kepware and PTC share many common customers that will be able to realize value from the acquisition. Industrial environments already leveraging Kepware technology will be able to benefit from the added breadth of capabilities available in the PTC ThingWorx IoT technology platform. The acquisition of Kepware will also provide a fast-to-value connectivity option for PTC customers to gain visibility into data from a vast range of industrial controls and production equipment, enabling them to kick-start their smart, connected factory initiatives.

“PTC is committed to helping manufacturers, infrastructure operators, and others realize the enormous value inherent in the Internet of Things,” said Jim Heppelmann, president and CEO, PTC. “With this acquisition, we will gain entry into heterogeneous factory and operating environments with robust technology, an impressive list of customers, and a high-quality, profitable company with incredibly talented employees.”

“Kepware and PTC share a common vision of helping organizations realize the potential of the Industrial Internet of Things,” said, Tony Paine, CEO, Kepware. “We believe this acquisition will benefit our customers, partners, and employees – and ultimately drive software innovation for industrial automation markets. We are excited for the opportunity to become part of PTC.”

Over the past 12 months, privately-held Kepware generated approximately $20 million in revenue. PTC expects to draw on its credit facility to finance this transaction and expects Kepware to be neutral to its FY’16 non-GAAP EPS. The transaction is expected to close in early 2016, subject to customary closing conditions, including regulatory approval. PTC intends to maintain the Kepware partner ecosystem and to continue developing and enhancing the Kepware technology, once acquired.

PTC Internet of Things Acquisitions

2014

Thingworx

The acquisition of ThingWorx positions PTC as a major player in the emerging Internet of Things era.

Axeda

The acquisition of Axeda allows PTC to leverage its core IoT technology to enable companies to establish secure connectivity and remotely monitor and manage a wide range of machines, sensors, and devices.

2015

ColdLight

The acquisition of ColdLight’s Neuron automated predictive analytics platform will enrich PTC’s technology portfolio and extend PTC’s position as a leader in the Internet of Things (IoT) market.

GE Alliance

GE and PTC announced that the two companies are partnering to deliver an innovative manufacturing solution that will be available within GE’s Brilliant Manufacturing Suite. This new GE-branded manufacturing solution leverages the capabilities of PTC’s ThingWorx Industrial Internet of Things application enablement environment. The result is an industry-hardened solution that features flexible dashboards and powerful data analytics integrated with GE’s software capabilities on the manufacturing plant floor.

 

ThingWorx IoT Platform

  • ThingWorx Composer
    ThingWorx Composer is an end-to-end application modeling environment designed to help you easily build the unique applications of today’s connected world. ThingWorx Composer makes it easy to model the things, business logic, visualization, data storage, collaboration, and security required for a connected application.
  • Codeless Mashup Builder
    ThingWorx “drag and drop” Mashup Builder empowers developers and business users to rapidly create rich, interactive applications, real-time dashboards, collaborative workspaces, and mobile interfaces without the need for coding. This next-generation application builder reduces development time and produces high quality, scalable, smart connected applications which allows companies to accelerate the pace at which they can deliver value-add solutions, resulting in greater market share against new and existing competitors.
  • Actionable, Correlated Data from People, Systems and Things
    ThingWorx is the only platform that can store and correlate data from three dimensions: people, systems, and connected things. This capability allows companies to make business sense of the massive amounts of data from those three dimensions – making the data useful and actionable. The platform supports scale requirements for millions of devices, and provides connectivity, storage, analysis, execution, and collaboration capabilities required for applications in today’s connected world. It also features a data collection engine that provides unified, semantic storage for time-series, structured, and social data at rates 10X faster than traditional relational databases.
  • Search-Based Intelligence
    ThingWorx SQUEAL (Search, Query, and Analysis) brings search to the world of smart connected devices and distributed data. With ThingWorx SQUEAL’s interactive search capabilities, users can now correlate data that delivers answers to key business questions. Pertinent and related collaboration data, line-of-business system records, and equipment data get returned in a single search, speeding problem resolution and enabling innovation.
  • Collaboration
    ThingWorx dynamically and virtually brings together people, systems, and connected equipment, and utilizes live collaboration sessions that help individuals or teams solve problems faster. The ThingWorx data store becomes the basis of context aware collaboration and interaction among the systems users, further enhancing its value. Additionally, the tribal knowledge exposed during the process is automatically captured and indexed for use in future troubleshooting activities.
  • Flexible Connectivity Options
    ThingWorx “inclusive” connectivity strategy maximizes market opportunity and minimizes integration efforts. ThingWorx supports connectivity to devices via several methods, including 3rd party device clouds, direct network connections, Open APIs, and AlwaysOn connectivity.

KEPServerEX Overview

KEPServerEX is a communications platform that provides a single source of industrial automation data to all of applications. The platform design allows users to connect, manage, monitor, and control diverse automation devices and software applications through one intuitive user interface.

KEPServerEX leverages OPC (the automation industry’s standard for interoperability) and IT-centric communication protocols (such as SNMP, ODBC, and web services) to provide users with a single source for industrial data. Designed around the four product pillars of Proven Interoperability, Centralized Communications, On-Demand Scalability, and Industrial Strength, KEPServerEX is developed and tested to meet our customers’ performance, reliability, and ease-of-use requirements.

Product Features

KEPServerEX provides critical technical features that are centralized around accessibility, aggregation, optimization, connectivity, security, and diagnostics.

Accessibility

OPC

OPC is the leading standard for industrial automation connectivity. KEPServerEX supports the OPC Unified Architecture (OPC UA) specification and many of the OPC Classic specifications, including OPC Data Access (OPC DA), OPC Alarms and Events (OPC AE), and OPC Historical Data Access (OPC HDA).

Automation Interfaces

KEPServerEX has preferred access to leading automation software, including iFIX by GE Intelligent Platforms (NIO) and InTouch by Wonderware (SuiteLink/FastDDE). KEPServerEX also supports preferred access to Oracle MES and MOC solutions through their proprietary API.

IT Interfaces

KEPServerEX supports multiple interfaces for integration with IT applications, including ODBC for logging information to a database and SNMP for providing information to a Network Management System (NMS). With the advent of IoT and Big Data applications, KEPServerEX now includes the ability to communicate with Splunk software and cloud services via the Industrial Data Forwarder for Splunk.

Cloud Interfaces

With the IoT Gateway, KEPServerEX can seamlessly stream real-time industrial control data directly into Big Data and analytic software for Business Intelligence and Operational Excellence. Its customizable data format supports most MQTT and REST applications—enabling users to choose the vendors and communication methodologies right for their system.

Exporters

Some applications require information to be made available from a file or database. This information is typically exported at a predefined rate and includes both current and historical data. KEPServerEX has the ability to export historical Electronic Flow Measurement (EFM) data (via the EFM Exporter plug-in) or historical trend data (via supported drivers) to files and/or databases.

Aggregation

Centralized Platform

KEPServerEX is a communications platform that can support connections to thousands of data sources and provide information to hundreds of applications. The platform design simplifies the configuration of the connected applications by providing a single point of entry to all information. KEPServerEX also enables troubleshooting and issue diagnosis, provides control to the access of information based on user roles, and the ability to restrict the frequency of communications over bandwidth-limited telemetry-based environments.

Unified Configuration

KEPServerEX provides a unified configuration for managing connectivity to any data source. Anything can be added, configured, or deleted while the server is on-line and operational. Users can configure projects manually using a step-by-step wizard or programmatically through the export and import of XML and CSV files.

Data Storage and Retention

KEPServerEX is capable of archiving the real-time data it collects to local storage. By leveraging the Local Historian plug-in, applications can access this historical data (via OPC HDA) for future analysis. KEPServerEX can also store information in any ODBC-compliant database using the DataLogger plug-in, which has a store-and-forward capability for when a database is unreachable or unable to process the information fast enough.

Optimization

Data Conditioning and Reduction

In addition to providing raw values to connected applications, KEPServerEX can perform linear or square root scaling, perform basic arithmetic expressions, or apply deadband calculations on raw data and provide its aggregate. This provides minimal bandwidth and resource utilization by providing only the most critical updates.

Redundancy

KEPServerEX is used in critical applications where highly-reliable systems are required for maximum uptime. It includes the ability to define redundant network paths, primary and secondary data sources, and applicable failover criteria.

Load Balancing

In large networks that have many devices and applications requiring information, flexible control is necessary to allow for customized load-balancing of data collection and information flow. KEPServerEX provides tools to schedule the frequency of communications and throttle the demand across the network.

Communications

KEPServerEX optimizes communications with devices by aggregating identical requests from different applications whenever possible. Multiple demands on data can be batched together into the fewest requests possible. These optimizations are unique to each protocol, and are designed to reduce network overhead and device processing.

Machine-to-Machine Linking

In a typical industrial automation network, devices and controllers must communicate with one another even if they are not from the same manufacturer or do not support the same protocol. KEPServerEX provides the ability to establish links between data values in different data sources, allowing Machine-to- Machine (M2M) communications as close to the device as possible.

Connectivity

Driver-Based Access

KEPServerEX offers the broadest range of drivers available, supporting devices across various verticals within the Industrial Automation Industry. While most drivers act as masters that initiate requests, there are many drivers that can emulate a device where communications are driven by a controller. KEPServerEX drivers also support a variety of wired and wireless network mediums for Ethernet, serial, and proprietary networks. Although most drivers connect directly with hardware devices, some are designed to connect with other applications—such as databases, custom software applications, or other OPC servers.

Telemetry Environments

Industrial automation equipment can be deployed in a dry and heated factory, but it can also be installed inside a vehicle, on a remote pipeline, or in a well or pump station. In these remote environments, there are often a variety of telemetry solutions in use like cellular, radio, or satellite modems. KEPServerEX supports these telemetry configurations and provides additional ways to optimize communications through virtual networks, timing parameters, device demotion, and by scheduling communications across devices.

Rapid Deployment

As automation networks have grown from ten controllers to thousands of controllers, tools that aid and accelerate deployment are critical to a solution’s success. KEPServerEX provides many tools that speed the deployment of new devices, including Automatic Tag Generation (ATG) and Device Discovery (when supported by the device and communication protocols). Users can also export, manipulate, and import an XML project file to programmatically define the configuration.

Simulation

As systems are configured, components must be implemented and tested before the entire system becomes available. KEPServerEX allows any data source to be placed into simulation mode prior to deployment. In addition, the Memory Based driver can be configured to create a range of static and dynamic data points. The Advanced Simulator driver can leverage a database and its contents to drive application-specific simulation data into connected applications.

Security

Configuration

Access to the KEPServerEX configuration can be restricted through the User Manager. This tool allows the administrator to define user groups and users with restricted access to certain project configuration tasks, and also provides the ability to disconnect client applications.

Runtime

There are various tools available within KEPServerEX to control user access to the server, data source, or data values. The Security Policies plug-in limits access based on OPC UA user credentials while supporting default handling for anonymous users (both OPC UA and other client interfaces). The ability to dynamically address information can be disabled, limiting user access to tags defined within the project. KEPServerEX supports a number of secure client standards including SNMP (v3 security), OPC UA, and OPC DA (DCOM security) to further restrict access to the server, as well as a number of secure device protocols to meet the requirements of DNP3, SNMP, and OPC UA data sources. Secure data tunnels can be configured by leveraging multiple KEPServerEX instances at remote endpoints to pass data through firewalls and meet authentication and encryption requirements across the Internet.

Diagnostics

OPC Diagnostics

OPC Diagnostics provide a real-time and historical view of OPC events between any OPC client and the server, including method calls made by the client or callbacks made by the server. The ability to view actual communications and responses is invaluable when troubleshooting client accessibility. The diagnostics tools within KEPServerEX greatly speed deployment and reduce downtime.

Communications Diagnostics

Communication Diagnostics provide real-time capturing of the protocol frames transferred between the server and any device, as well as indications on the driver’s performance. All read and write operations can be viewed or tracked directly in an OPC client application using built-in diagnostics tags. This is useful when modifying key communication parameter settings (such as baud rate, parity, or Device IDs), because corrections are immediately visible.

Third-Party Diagnostics Integration

Diagnostics information can be viewed within KEPServerEX and by third-party applications. Diagnostics information is provided through system-defined tags and accessible to the same clients connecting to the data sources. KEPServerEX logs event information, which is accessible within the configuration tool or to any application that supports the OPC Alarms and Events specification.

PTC Acquisition Bolsters Internet of Things Offering

IBM Delivers Engineering Software for ‘Internet of Things’

During NI Week last week in Austin, Texas, IBM representatives discussed some news with me about a new engineering software tool the company has released – called Product Line Engineering (PLE) — designed to help manufacturers deal with the complexity of building smart, connected devices. Users of Internet of Things (IoT) products worldwide have geographic-specific needs, leading to slight variations in design across different markets. The IBM software is designed to help engineers manage the cost and effort of customizing product designs.

You may think, as I did, about IBM as an enterprise software company specializing in large, complex databases along with the Watson analytic engine. IBM is also home to Rational Software—an engineering tool used by many developers in the embedded software space. I had forgotten about the many engineering tools existing under the IBM umbrella.

They described the reason for the new release. Manufacturers traditionally manage customization needs by grouping similar designs into product lines. Products within a specific line may have up to 85% of their design in common, with the rest being variable, depending on market requirements and consumer demand and expectation. For example, a car might have a common body and suspension system, while consumers have the option of choosing interior, engine and transmission.

Product Line Engineering from IBM helps engineers specify what’s common and what’s variable within a product line, reducing data duplication and the potential for design errors. The technology supports critical engineering tasks including software development, model-based design, systems engineering, and test and quality management—helping them design complex IoT products faster, and with fewer defects. Additional highlights include:

  • Helps manufacturers manage market-specific requirements: Delivered as a web-based product or managed service, the IBM software can help manufacturers become more competitive across worldwide markets by helping them manage versions of requirements across multiple domains including mechanical, electronics and software;
  • Leverages the Open Services for Lifecycle Collaboration (OSLC) specification: this helps define configuration management capabilities that span tools and disciplines, including requirements management, systems engineering, modeling, and test and quality.

Organizations including Bosch, Datamato Technologies and Project CRYSTAL are leveraging new IBM PLE capabilities to transform business processes. Project CRYSTAL aims to specify product configurations that include data from multiple engineering disciplines, eliminating the need to search multiple places for the right data, and reducing the risk associated with developing complex products.

Dr. Christian El Salloum, AVL List GmbH Graz Austria, the global project coordinator for the ARTEMIS CRYSTAL project, said, “Project CRYSTAL aims to drive tool interoperability widely across four industry segments for advanced systems engineering. Version handling, configuration management and product line engineering are all extremely important capabilities for development of smart, connected products. Working with IBM and others, we are investigating the OSLC Configuration Management draft specification for addressing interoperability needs associated with mission-critical design across multi-disciplinary teams and partners.”

Rob Ekkel, manager at Philips Healthcare R&D and project leader in the EU Crystal project, noted, “Together with IBM and other partners, we are looking in the Crystal project for innovation of our high tech, safety critical medical systems. Given the pace of the market and the technology, we have to manage multiple concurrent versions and configurations of our engineering work products, not just software, but also specifications, and e.g. simulation, test and field data. Interoperability of software and systems engineering tools is essential for us, and we consider IBM as a valuable partner when it comes to OSLC based integrations of engineering tools. We are interested to explore in Crystal the Product Engineering capabilities that IBM is working on, and to extend our current Crystal experiments with e.g. Safety Risk Management with OSLC based product engineering.”

Nico Maldener, Senior Project Manager, Bosch, added, “Tool-based product line engineering helps Bosch to faster tailor its products to meet the needs of world-wide markets.”

Sachin Londhe, Managing Director, Datamato Technologies, said, “To meet its objective of delivering high-quality products and services, Datamato depends on leading tools. We expect that product line engineering and software development capabilities from IBM will help us provide our clients with a competitive advantage.”

PTC Acquisition Bolsters Internet of Things Offering

Standards and Roadblocks to Manufacturing Software Development

Looks like there is a debate in the software development community again. This time around node.js

Dave Winer is a pioneer in software development. I used his first blogging platform, Radio Userland, from 2003 until about 2009 when it closed and I moved first to SquareSpace and then to WordPress. Below I point to a discussion about whether the node.js community needs a foundation.

His points work out for manufacturing software development, too. Groups of engineers gather to solve a problem. The problem usually involves opening up to some level of interoperability.

This is a double-edged sword for major suppliers. They’d prefer customers buy all their solutions from them. And, yes, if you control all the technology, you can make communications solider, faster. However, no supplier supplies all the components a customer wants. Then some form of interoperability is required.

Therefore, technologies such as OPC, HART, CIP, and the like. These all solved a problem and advanced the industry.

There are today still more efforts by engineers to write interoperability standards. If these worked, then owner/operators would be able to move data seamlessly, or almost seamlessly, from application to application solving many business problems.

Doing this, however, threatens the lucrative market of high-end consultants whose lock-in of custom code writing and maintenance is a billion-dollar business. Therefore, their efforts to prevent adoption of standards.

Winer nails all this.

I am new to Node but I also have a lot of experience with the dynamics [Eran] Hammer is talking about, in my work with RSS, XML-RPC and SOAP. What he says is right. When you get big companies in the loop, the motives change from what they were when it was just a bunch of ambitious engineers trying to build an open underpinning for the software they’re working on. All of a sudden their strategies start determining which way the standard goes. That often means obfuscating simple technology, because if it’s really simple, they won’t be able to sell expensive consulting contracts.

He was right to single out IBM. That’s their main business. RSS hurt their publishing business because it turned something incomprehensible into something trivial to understand. Who needs to pay $500K per year for a consulting contract to advise them on such transparent technology? They lost business.

IBM, Sun and Microsoft, through the W3C, made SOAP utterly incomprehensible. Why? I assume because they wanted to be able to claim standards-compliance without having to deal with all that messy interop.

As I see it Node was born out of a very simple idea. Here’s this great JavaScript interpreter. Wouldn’t it be great to write server apps in it, in addition to code that runs in the browser? After that, a few libraries came along, that factored out things everyone had to do, almost like device drivers in a way. The filesystem, sending and receiving HTTP requests. Parsing various standard content types. Somehow there didn’t end up being eight different versions of the core functionality. That’s where the greatness of Node comes from. We may look back on this having been the golden age of Node.

Follow this blog

Get a weekly email of all new posts.