Configure and connect industrial devices and systems in any environment.
Challenges For medical device manufacturers, unplanned equipment downtime negatively impacts patient outcomes. That's why medical device manufacturers are adopting a remote service approach.
Solution A Medical device manufacturer used ThingWorx to easily connect to medical devices in the field for remote monitoring of status and performance. The ThingWorx Edge Microserver provides secure, bi-directional connection to send data that is displayed on the web application created using ThingWorx Mashup Builder. Different machine types are modeled using purpose built features of ThingWorx Composer that anticipate this exact use case. ThingWorx seamlessly integrates with other enterprise systems to create a comprehensive, enterprise-wide solution and provides flexibility to meet the necessary security and auditing requirements.
Results Service employees detect, diagnose, and resolve problems faster, minimizing or even preventing equipment downtime. They can also more effectively collaborate with field service technicians to provide contextual guidance, improving first-time fix rates.
Data collected from connected devices is easily integrated into other existing business processes—such as parts planning and allocation or compliance reporting—which further enhances outcomes and reduces costs. Many manufacturers are also leveraging data to develop and deliver differentiated, value-add services, like automatic consumables replenishment and usage-based billing.
The C SDK is the basis for ThingWorx Edge SDKs and the Edge MicroServer (EMS). You can compile C SDK applications on any platform and even run it without an operating system. Using the C SDK for your application means least amount of RAM, processing power, and disk space, frequently requiring less than 200 kilobytes. The C SDK is also the only SDK that is distributed as source code.
The Java SDK is especially useful if you are integrating with an application that uses a Java-based API. While applications based on the Java SDK tend to use more RAM, processing power, and disk space than a C SDK equivalent application, they typically take less time to develop. To use it, you will need a platform with a supported Java Virtual Machine.
Use the Microsoft .NET SDK when integrating with a .net based application or if your team typically works with Microsoft technologies. It may only be used on Windows based machines.
The iOS SDK integrates with Apple's iOS based devices like the iPhone, iPad, and iPod Touch. It can be used as a bridge where the iOS based device collects data from a source, be it Bluetooth or Wi-Fi, processes it, and communicates with the ThingWorx Platform.
Check out our Meet ThingWorx guide to understand the basics of ThingWorx and quickly experience how easy it is to develop an IIoT application.
Use the REST API to Connect Low-Capability Devices to ThingWorx
Using the ThingWorx REST API is an easy way for low-capability devices to connect with the ThingWorx platform and push data to the platform. Any edge device that can make an HTTP POST can read and update properties or execute services on the ThingWorx platform.
Connect natively to ThingWorx using an AlwaysOn protocol SDK
SDKs are available for Java, C, .net, Android, and iOS and allow you to connect your devices to ThingWorx with the AlwaysOn protocol. Using the Edge SDKs will give you all the flexibility you need to meet your application's requirements and build robust, secure, full-featured edge integrations and gateways for any platform.
Secure, embeddable, and easily deployable communications designed for connecting sensors, devices and equipment across any network topology and any communication scenario.