IoT-Connector As-a-Service (Aka PDaaS)
Table of Contents
- What is PDaaS Connector?
- Claim of Ownership
- Device Owner
What is PDaaS Connector?
Connector As-a-Service is a compatible
Murano IoT-Connector with additional capabilities.
It means any existing or future Murano Applications can consume data from PDaaS Connector transparently potentially with a mix of Standard IoT-Connectors.
The main capability of a PDaaS Connector is to support multi-tenancy.
While with a standard IoT-Connector, each connected application share access to all devices, with Connector As-a-Service, only the owner of devices can see and interact with them.
As a noticeable value, multi-tenancy enables a single point of management for the Device Maker to manage the fleet a device along with firmware management and OTA.
Marketplace of Ready-to-Use Devices
Every IoT Connector created with Product as a Service technology can be listed in the Exosite IoT Marketplace (Exchange) as an “Off the Shelf” product.
This immediately provides two things to the OEM/VAR:
- Visual listing in the Marketplace: a card, along with detailed “where to buy” and documentation information, can be created, and tags applied, so that the Product will be visible to all customers visiting Exosite’s IoT Marketplace.
- Application-specific listings: if the product is usable in a specific industry, and a case study created showing its use with Exosite software, Exosite support can apply a tag for that industry so that customers filtering results by application will see the product as part of their search results
For products that are useful in a target market that Exosite also publishes an Off-the-Shelf IIoT Bundle, the product is eligible for consideration to be included as part of the native bundle. This means that customers who purchase the bundle, or who investigate what is included in the bundle, will be able to use the device with zero additional configuration or setup.
Learn more on the publisher page.
Each PDaaS Connectors provides a micro-site for customers to discover, claim and interact with acquired devices of the expose product line. This micro site is externally visible and search engines will index the site, providing an excellent landing page for the OEM/VAR’s technical product marketing person to expand on the product’s connected capabilities. In addition to the marketing messaging on the micro-site, the site is also a functional portal customers can use to claim their device and connect it to the cloud of their choice.
The micro-site can be fully Branded with zero-coding making a transparent experience for the Users within minutes while a full customization is also possible.
Learn more about branding on the publisher page and about the IoT-Connector Portal features on the Device-Owner page.
As multi-tenants service The IoT-Connector Portal enables each user to setup its own application (s) for data analysis, dashboarding and reporting.
Application can be either Murano hosted, such as ExoSense, or external trough a backed Rest API. Read more on the Device Owner application integration guide.
Claim of Ownership
This is done with a
Claim Code, provided along with the device purchase, granting a user the digital ownership. Once the Claim code is provided to the IoT-Connector Portal or integrated App, related devices are made visible for the user. For ease of use the claim code can be also provided as a QR code which can be scanned from a mobile device.
Find out how:
The device Owner (Typically the End-User) is the persona having physical access to the device and benefit from its operation, but however has no mean to change the device firmware and connectivity settings, which is handled by the Publisher.
Through PDaaS, the Device Owner has following capabilities:
- Find ready to use hardware devices on the Exchange IoT-Marketplace
- Claim ownership of a device
- See device status & data
- Define & Connect applications
- Associate Devices to applications
In the case of multi-tenant Application pre-configured by the Publisher the Device Owner can manage device ownership through the App and might not need to access the
The Publisher is the personal connecting the Devices to Murano (Typically the manufacturer), and usually not involved in its operation.