What is iDigi?
The iDigi Device Cloud is the (M2M) industry's first ready-to-use public cloud platform for device network management. It provides secure application messaging, data storage and device management for networks comprised of wired, cellular and satellite-connected devices.
iDigi is based upon a cloud computing model that provides on-demand scalability so you can rest assured that when you need additional computing and storage iDigi will scale to meet your needs. The iDigi Device Cloud is designed using a high-availability architecture, with redundancy and failover characteristics in mind.
Infinitely scalable, fully redundant and with commercial-grade availability, the iDigi Device Cloud addresses the complexities of device network management, without the need for costly infrastructure planning.
Using iDigi, customers can now easily develop cloud connected devices and applications that quickly scale from dozens to hundreds, thousands or even millions of endpoints.
The iDigi Device Cloud provides four core capabilities:
What is a device network?
Sometimes referred to as Machine-to-Machine (M2M), device networks enable both wired and wireless systems to communicate with other devices and applications across different network types. As an example, a device (such as a sensor or meter) captures an event (such as temperature, tank level, etc.) which is relayed through a network aggregation layer (wired, wireless or both) and infrastructure to an application (software program) that translates the captured event into meaningful information (for example, tanks need to be emptied or refilled).
What is cloud computing?
Cloud computing offers a flexible new approach to delivering IT services. In the most basic sense, "The Cloud" encompasses resources (hardware, software, infrastructure and services) that can be accessed through the Internet. The benefits of cloud computing are similar to a public utility model: only buy what you need, when you need it, with the ability to quickly scale resources on-demand as resource utilization grows.
Cloud computing is often packaged and delivered in three distinct tiers of service:
Software as a Service (SaaS):
SaaS delivers software as a service over the Internet, eliminating the need to install and run applications on the customer's own computers and simplifying maintenance and support. SaaS applications are often delivered using a web browser interface.
The iDigi Manager Pro™ application is an example SaaS for managing remote devices connected to the iDigi Device Cloud. SaaS services, like all software, must run on a platform.
Platform as a Service (PaaS):
PaaS delivers a computing platform and/or solution stack (such as an operating system and database) as a service over the Internet. The PaaS includes device interfaces, Application Programming Interfaces (API"S), and systems, operating, monitoring and security systems.
The iDigi Device Cloud is an example a PaaS. iDigi customers often develop their own SaaS applications that use the iDigi PaaS via web service calls to communicate with end devices.
PaaS, like all operating systems and databases, must run on hardware infrastructure.
Infrastructure as a Service (IaaS):
IaaS delivers hardware and software infrastructure as a service. Rather than purchasing servers, data center space or network equipment, clients instead buy those items as a fully outsourced service. Suppliers typically bill such services on a utility computing basis and amount of resources consumed (and therefore the cost) will typically reflect the level of activity.
Why use a third party cloud service like iDigi?
The iDigi Device Cloud provides the most scalable, reliable, secure and cost-effective device application platform available. Digi International has invested well over 100 man-years of development into the platform to date, and that investment continues to accelerate as customer adoption and requests for new features continue to grow.
Each user of the iDigi Device Cloud benefits from Digi's engineering investment:
See www.idigi.com/why-idigi for more information on the features and benefits of iDigi.
What can I do with the iDigi platform?
The iDigi platform is the Platform as a Service (PaaS) component of the iDigi Device Cloud. It includes all aspects of the system except the iDigi Manager Pro application for device management.
The iDigi platform offers the following features and functions:
Device Connectivity
Application Connectivity
Integration
Scalability
Availability
What can I do with the iDigi Manager Pro web application?
The iDigi Manager Pro is the Software as a Service (SaaS) component of the iDigi Device Cloud. It is a web-based graphical user-interface for management and control of remote devices.
Gateway Device Management
XBee® Sensor Device Management
Cloud Storage Management
User Management
Subscription Management
Web Services Console
What application partners use iDigi today?
Multiple solutions are presently under development. The Smart Energy market was an early adopter of iDigi because of its potential for massive scalability. Additional solutions are now emerging in other verticals, such as fleet management, tank management, asset tracking, mining and manufacturing, precision agriculture and renewable energy – just to name a few.
Please refer to the Partners section of iDigi.com for more information.
What example mobile applications use iDigi today?
The iDigi Device Cloud is ideally suited for mobile application solutions. Several mobile applications have shipped to date, with more continually being planned and developed.
Smartlee™ (available free on both the iPhone and Android platforms) is an excellent example of what is possible. With this application, a user can monitor home energy consumption of gas, water and electric meters, set programmable thermostats and receive important messages from their utility providers. You can download a trial version that includes a demo mode to simulate smart energy sensors and control devices.
How scalable is iDigi?
The iDigi platform is infinitely scalable. We’ve conducted thorough testing with up to 1 million connected devices and bursts of up to 2,000 transactions per second. Our Systems Assurance function is continually testing existing and new features to ensure an ever-growing capacity and optimal performance. Our horizontally scalable computer architecture scales transparently by adding new blades.
Why not build it myself?
You could perhaps build your own platform, but only with significant investments in development, man hours and money in order to achieve the full range of features and functionality that are available from iDigi today. Keep in mind that during this development time the iDigi Device Cloud will continue to advance. The primary benefit of the iDigi Device Cloud is cost; Digi continually invests significant R&D resources to deliver world-class scalability, reliability and security at the lowest cost possible.
Only a prebuilt, cloud-based solution can offer full-feature, production-class capabilities to an initial pilot and proof-of-concept. The iDigi Developer Cloud allows application developers to test with full capabilities during evaluation, while only funding the small incremental cost to add their device or application to an existing production-ready system. The iDigi Device Cloud enables application developers to bring their solutions to market quicker than ever before.
(Please also see the question titled "Why use a 3rd-party cloud service like iDigi?")
We've already run a limited proof-of-concept with a spare server; why use iDigi for production deployment?
When your proof-of-concept transitions to the iDigi Device Cloud, the operating costs will be comparable or less for most pilot scenarios, with all of the versatility and technical benefits offered by iDigi. And best of all, reliability, scalability and performance are baked into the iDigi solution.
Is iDigi secure?
Yes. The iDigi Device Cloud has been built to secure all transactions and data. Connections between remote devices and the iDigi service are encrypted and validated with certificates, as are connections between client applications and the iDigi service.
iDigi's security and privacy office has created the iDigi security policy using 164 controls that are based upon the CSA, ISO27002, NERC CIP, PCI and HIPAA standards. The controls are enforced with active monitoring tools and verified with independent, third-party policy compliance audits.
What does iDigi cost and how is it billed?
iDigi Manager Pro is priced on a pay-as-you-go model, starting at $1.59 per registered device, per month. Sending data to and from the iDigi Device Cloud is billed on a transactional basis. The transactional fees are available at different usage levels, but are on the order of micro-cents per transaction (~ $ 0.0000x per transaction).
For detailed information on pricing and billing methods, please see the iDigi Billing Whitepaper.
Why is iDigi sold as a subscription-based cloud service?
For a number of reasons: to keep support prices as low as possible; to enable rapid scalability; to enable a pay-as-you-grow usage model; to leverage economies of scale; to maintain a low cost of entry for new solutions.
Is the iDigi platform available as a stand-alone application?
No. This was contemplated in the early days of iDigi. The question has been asked far less frequently as customers gain practical knowledge using the cloud model and gain experience with the technical, business and security benefits that the cloud model delivers.
When cellular and satellite data links are used, how are costs of these services contained?
Originally, devices were expected to keep a persistent network connection open to iDigi. An occasional heartbeat/keep-alive was sent in the absence of application data to confirm the link.
iDigi now includes Short Messaging System (SMS) for deployment scenarios where bandwidth costs are premium. Some actions, like reboot, may actually be initiated over SMS. For more complicated transactions, iDigi can send an SMS request connect "shoulder tap" which will cause the device to initiate a traditional connection back to the server. Once connected, web services requests and UI actions can be made to the device.
Can Digi help me build a specific iDigi solution?
Yes. Design help is available from many sources. The free iDigi Dia framework includes reusable software modules and open source code. The free integrated development environment (based on Eclipse) includes meaningful examples and tutorials. Digi also hosts a developer Wiki and a discussion forum for the development community to share cooperative solutions.
Professional design services are also available from Spectrum Design Solutions, a wholly owned subsidiary of Digi International. Spectrum's focus is wireless design. As an innovative wireless design company, Spectrum also carries deep expertise in embedded design services, software services and printed circuit board design.
Where can I get more detailed technical information?
Use the "drop-down" filter selector at the top of this page to view more detailed technical questions.
Which Digi devices are compatible with the iDigi Device Cloud?
iDigi is a feature of all Digi devices out-of-the-box. Digi devices are configured to automatically "phone home" to iDigi and register with a Technical Support account when they are booted up for the first time. For cellular devices, this process involves sending a one-time SMS, which will be taken from your SMS data plan or may incur a charge from your carrier. With Technical Support account registration, our Technical Support team are able to provide enhanced torubleshooting and technical support services.
What kits are available to gain hands-on experience using the iDigi Device Cloud?
The iDigi Gateway Development Kit is a great resource. It is designed to make it easy to setup a ZigBee network, upload a custom iDigi Dia application, and provide seamless connectivity to the iDigi Device Cloud for web services integration to standard business applications over the Internet.
More information is available at www.digi.com/gatewaydevelopmentkit.
Are 3rd-party devices compatible with the iDigi Device Cloud?
Yes. The free iDigi Connector™ software download allows any M2M device to integrate with the iDigi Device Cloud. To access the iDigi Connector, login to iDigi or create your free Developer account and go to the Resources page.
What Integrated Development Environments (IDEs) are available for Digi devices?
Digi ESP is an integrated IDE based on Eclipse that includes Python scripts, sample code and tools which have been designed to facilitate the development of applications for Digi devices. Digi ESP provides an ideal development environment for beginners and experts.
Digi ESP is available for both Microsoft Windows and Apple Mac OSX platforms at www.digi.com/esp.
What is the iDigi DIA?
iDigi Dia (Device Integration Application) is software that simplifies connecting devices (sensors, PLCs, etc.) to communication gateways. It includes a comprehensive library of plug-ins that work out-of-the-box with common device types and can also be extended to include new devices.
iDigi Dia provides the core functions of remote device data acquisition, control and presentation between devices and information platforms. It collects data from any device that can communicate with a Digi gateway, and is supported over any gateway physical interface. iDigi Dia presents this data to upstream applications in fully customizable formats, significantly reducing a customer's time-to-market.
Detailed information is available in the iDigi Dia Online Documentation, available on the Resources page of the iDigi Manager Pro web application.
How do I connect my supported device to iDigi?
Devices must be registered under a valid user account with either the iDigi Device Cloud or the iDigi Developer Cloud to receive service. Create a free developer user account at developer.idigi.com.
Some configuration is required on both the device and on iDigi. The device must be configured with the fully-qualified domain name of the iDigi Device Cloud or Developer Cloud. Please consult the Configuration Guide for your specific device to configure "Remote Management." The iDigi Device Cloud must be configured with the "Device ID" of the new device that is to be registered. If you’re new to the device cloud, use the "Add Device" wizard in the iDigi Manager Pro web application. Advanced users could use a web service call to register new devices.
New users would be well-served to follow the Getting Started Guide for the iDigi Gateway Development Kit available at www.digi.com/gatewaydevelopmentkit.
What connectivity is possible?
Digi offers a number of devices that are compatible with the iDigi Device Cloud. Many devices support Ethernet or Wi-Fi network connectivity, while other devices include cellular and satellite support. Digi sales engineers can work with you to help identify the best network connectivity for your application and the most cost-effective application protocols to communicate between devices, the iDigi Device Cloud and ultimately your end-users' client applications.
Can devices that are restricted to a private network connect to iDigi?
(Without leaving the private network; without traversing the public Internet directly?)
Yes. With the iDigi Virtual Private Networking (VPN) service, data can travel between devices, iDigi and client applications using end-to-end private IP addressing.
Can devices connect from behind a firewall?
Yes. iDigi-enabled devices initiate a client-side IP connection to the iDigi Device Cloud. This mechanism is the most compatible with common firewall configurations, including the Network Address Translation (NAT) services delivered on most home internet routers.
How can I control the amount of cellular data used by remote gateways?
Working with an iDigi Solutions Architect, we can recommend multiple approaches to control the size and frequency of cellular data traffic. The requirements of the overall solution will be key: how much information is needed from the device and how frequently?
iDigi includes support for the Short Messaging System (SMS) protocol. This technology allows cellular devices to drop their client-initiated connection when it is not required to reduce data usage. iDigi has the capability to send a short "shoulder tap" SMS message to the cellular device to request that it reinitiate the management connection if necessary.
Does iDigi maintain a persistent management connection to the end devices?
By default, yes, however this is configurable. iDigi executes a variety of operating functions in the background to provide the customer with the status of devices in the network, including pushing a ping to the device to determine if it is still connected. The default for this ping is every 15 minutes, but can be adjusted by the customer if necessary. For example: battery powered devices. Even though the ping requires very little resources it can accelerate the consumption of the fixed power resource from the battery. In this event the customer may choose to decrease the frequency of the ping dramatically. This type of "are you still there" transaction is not counted towards the customer's chargeable transaction count from iDigi (although cellular carrier data usage may still apply.) It is considered platform administration.
Short Messaging System (SMS) functionality allows a cellular device to drop the persistent management connection indefinitely. iDigi can send an SMS "shoulder tap" notification at any time that requests the device to re-initiate the client-side connection to iDigi when it is needed.
What cellular networks do the Digi devices operate on?
Multiple, including GSM GPRS/ GSM HSUPA/UMTS /EDGE/HSPA/CDMA EV-DO
Please consult the latest product documentation for your specific device, or contact a Digi sales engineer for a device recommendation based on your applications requirements.
Where can I get the latest firmware for my devices?
On the www.digi.com website. Please click on "Firmware Updates" under the "Support" banner.
Can we use iDigi for reporting device signal strength?
Yes. Assuming signal strength or other data points are available from the device, web-services can be used to create a web application or widget that displays signal strength or other attributes.
Is a Digi device required to have a public or static IP address to make use of iDigi?
No. Neither a public IP address nor a static IP address is required to make use of iDigi. Devices initiate a client-side IP connection to the iDigi Device Cloud, which is compatible with private and dynamically-assigned device IP addresses.
How can I use iDigi if my machines/devices have no connection to the internet?
Multiple options are available to connect machines/devices to iDigi that originally lack a network connection. Analog and Digital outputs from the machine or device may be collected by a Digi gateway. That gateway, in turn, can make the connection to iDigi via wired, Wi-Fi, cellular or even satellite connections.
When multiple machines or devices co-exist in a physical location, it is possible to place an inexpensive XBee wireless module on each of the machine to collect the analog or digital data. Then a single Digi gateway collects the sensor readings from each of the wireless XBee modules on all of the machines and reports the data up to iDigi using a single network connection.
Digi devices equipped with the Iridium Satellite module are able to use the Iridium Satellite network, where traditional Internet connectivity is not available.
Digi Solutions Architects and Sales Engineers will be able to provide greater detail on this.
How do I setup/configure device authentication on iDigi Manager Pro?
The hierarchy of remote device configuration settings is dynamically learned from each remote device by iDigi Manager Pro; it is not hard-coded into the iDigi Manager Pro application. Double-click on any device in the "Devices" tab of iDigi Manager Pro to populate the web GUI with the configuration hierarchy of your device. In the ConnectPortX4, for example, the configuration setting is available under "Advanced Configuration" and "iDigi Device Security".
The exact location of the configuration setting for iDigi device authentication may vary slightly between device families and firmware versions. Please consult the documentation for your specific remote device.
Where can I get more detailed technical information about iDigi-supported devices?
Please see the "Resources" section of the iDigi Manager Pro web application (available with a free developer account at developer.idigi.com.) In addition to documentation, the Resources section includes links to the iDigi Platform Wiki, the iDigi Dia Wiki, the Python Wiki and the Customer Support Forum.
Digi sales representatives and sales engineers are also available to help answer questions. Please refer to the "Contact Us" section on the footer of the iDigi.com website.
Contact a Digi sales representative or sales engineer for more information.
How long is sensor/application data stored in the iDigi platform?
Data is retained for seven trailing days.
What commands can I send to a remote device over the iDigi infrastructure?
The possibilities are wide open. Standard web service calls are available to manage traditional device settings. An optional Server Command Interface / Remote Command Interface (SCI/RCI) mechanism is in place to any custom device or application commands a developer requires.
What is SCI/RCI?
SCI (Server Command Interface) is one of the web services interfaces that allows users to perform commands and access information that relate to their device. Many of those commands utilize RCI (Remote Command Interface), a protocol that defines settings and capabilities specific to each device type and version. Examples of these requests include retrieving and setting configuration parameters, updating firmware, retrieving and updating files, working with XBee devices, and others.
More information on SCI is available at www.digi.com/wiki/developer/index.php/SCI.
What is the iDigi Dia web services API and how is it used?
Digi allows customers to build custom remote sampling solutions that report data through iDigi Dia. The data will be stored in the database on the iDigi Device Cloud using Dia tables (instead of the original method of being stored as files). This will allow iDigi client applications to query Dia tables directly with web service calls rather than downloading and parsing XML files. You can enable this feature using the Dia data service subscription.
More information on the Dia API is available on the "Resources" section of the iDigi Manager Pro web application.
What is the iDigi Smart Energy API and how is it used?
Remote devices that conform to the ZigBee Smart Energy profile will report data to iDigi. The data is stored in the database on the iDigi Device Cloud using Smart Energy tables. This allows iDigi client applications to query tables directly with web service calls.
Please refer to the documents listed under "Smart Energy Resources" on the "Resources" section of the iDigi Manager Pro web application.
Where is the iDigi platform hosted?
Just as customers contract with iDigi for best-of-breed device cloud services, Digi International has contracted with best-of-breed Infrastructure as a Service providers to host the platform. Today we have instances in the US and in Europe.
Where can I get more detailed technical information about the iDigi Device Cloud?
Please consider the "Resources" section of the iDigi Manager Pro web application (available with a free developer account at developer.idigi.com). In addition to documentation, the Resources section includes links to the iDigi Platform Wiki, the iDigi Dia Wiki, the Python Wiki and the Customer Support Forum.
Contact a Digi sales representative or sales engineer for more information.
How is sensor/application data retrieved from the iDigi platform?
A client application may poll a remote device directly through the iDigi Device Cloud. Alternatively, the remote devices may be configured to push data up to the iDigi Device Cloud at a controlled rate (i.e., transmit once per minute) or under certain conditions (i.e., transmit immediately when value >50).
Advanced querying of data is possible when devices push data up to short-term storage on the iDigi Device Cloud. Client applications can then build more sophisticated queries such as "list all sensors that have a temperature over 100 degrees" or "list all devices that have not uploaded data in the last 24 hours".
For both designs, the client application will use web services to retrieve the data using iDigi. A client application may poll iDigi for new data or register to monitor various data elements and have iDigi push them to the client application when those elements change.
More information on the iDigi web service calls is available in the "iDigi Web Services Programming Guide" available on the "Resources" section of the iDigi Manager Pro web application.
What are RESTful web services and how do they work?
A web service is a method of communication between two electronic devices over a network. Representational state transfer (REST) attempts to describe web service architectures that use HTTP or similar web protocols by constraining the message interface to a set of well-known, standard operations (like GET, POST, PUT, DELETE for HTTP).
The iDigi Web Services API exposes a number of functions via web services that allow devices and client applications to send data, retrieve data, change settings, update firmware, etc.
More information on the iDigi web service calls is available in the "iDigi Web Services Programming Guide" available on the "Resources" section of the iDigi Manager Pro web application.
Where can I see example web service calls to iDigi?
The iDigi Manager Pro web application includes a Web Services Console that allows developers to select example web service calls from easy-to-navigate drop down menus. The equivalent, detailed HTTP methods are displayed for review. Users may click to transmit any web service call to live, target devices, and the response from the remote device is displayed for review.
Where can I see example applications built to demonstrate data retrieval from iDigi?
The iDigi Gateway Development Kit includes an example application that is used to communicate with iDigi, display sensor values on a web page, and pass commands down to a device. The web application source code for the Google App Engine is also included on the documentation tab for the kit on digi.com.
Please see the documentation at www.digi.com/gatewaydevelopmentkit.
Can Digi recommend an application/dashboard developer?
Yes. Digi has worked with a number of client application developers. Some are focused on specific industry verticals, while others build custom applications across many industries. In addition, Digi’s application development service, iDigi Applications, builds custom M2M applications tailored to your specific solution.
We want to use iDigi for our application but no existing solution partner has what we need. What can Digi do to help?
Solution partners often get started by building specialized solutions that are focused for specific industry verticals (e.g. manufacturing or health care). However, many are willing to branch-out to build solutions for other adjacent industries as needs evolve.
Please contact us to discuss Digi solution partners that have done relevant work in a similar vertical.
Where can I get more detailed technical information about integrating end client applications to the iDigi Device Cloud?
Please consider the "Resources" section of the iDigi Manager Pro web application (available with a free developer account at developer.idigi.com). In addition to documentation, the Resources section includes links to the iDigi Platform Wiki, the iDigi Dia Wiki, the Python Wiki and the Customer Support Forum.
Contact a Digi sales representative or sales engineer for additional information.
What is the difference between device management and device monitoring capabilities?
Device management includes those functions required to operate and maintain a device. This includes turning it on and off, deactivating a device, changing configurations, software/firmware updates, scheduled operations and controlling groups of devices.
Monitoring is a function of polling or querying a device on a pre-defined frequency for health status. The health status is usually displayed in a graphical user interface (GUI) that represents the network in a relevant way to the user. Alerting is made available with monitoring capabilities.
How will the device settings of my 3rd party device appear in iDigi?
Won't iDigi have to be coded with knowledge of my device?
The hierarchy of remote device configuration settings is dynamically learned from each remote device by iDigi Manager Pro; it is not hard-coded into the iDigi Manager Pro application. The configuration elements of your device are passed up to iDigi using a UI Descriptor model.
Please see www.digi.com/wiki/developer/index.php/UI_Descriptor.
How can I generate SMTP or SNMP alerts or alarms out of iDigi?
iDigi Manager Pro features Device Monitoring and Alerts functionality. More information on the monitoring is available in the "iDigi Web Services Programming Guide" available in the "Resources" section of the iDigi Manager Pro web application.
Can iDigi host my own web services application?
No, not within the iDigi Device Cloud itself. The decision was intentionally made to focus iDigi engineering, time and resources on building the most reliable, scalable and affordable Device Cloud possible, and investments have remained diligently focused on achieving and maintaining that goal.
Where can I get more detailed technical information about iDigi Manager Pro?
Please consider the "Resources" section of the iDigi Manager Pro web application (available with a free developer account at http://developer.idigi.com). In addition to documentation, the Resources section includes links to the iDigi Platform Wiki, the iDigi Dia Wiki, the Python Wiki and the Customer Support Forum.
Contact a Digi sales representative or sales engineer for additional information.
What does iDigi cost and how is it billed?
The two tiers of service, iDigi Manager Pro (SaaS) and the iDigi Device Cloud (PaaS), are billed separately.
iDigi Manager Pro Software as a Service
iDigi Manager Pro is billed monthly on a pay-as-you-go basis, per registered device. Prices start at $1.59 per registered device, per month.
iDigi Device Cloud Platform as a Service
Billed on a transactional model. A typical transaction of less than 100 MB is 15 micro-cents ($0.00015) each (Spring 2011 pricing.) Please contact a Digi sales representative for a price quote.
For detailed information on pricing and billing methods, please see the iDigi Billing Whitepaper.
What constitutes a transaction for billing in the iDigi Device Cloud, and how can I calculate my expected transactions?
A device or client application performing a web service call into the iDigi Device Cloud will consume one transaction for the ACTION/RESPONSE pair. Consider the following examples:
A remote device performing one web service call to POST data up to the data cache of the iDigi Device Cloud will consume one transaction:
A client application performing one synchronous web service call to get cached data from the data cache of the iDigi Device Cloud will consume one transaction:
A client application performing one synchronous web service call to get non-cached data directly from one end device via iDigi will consume two transactions:
A client application performing asynchronous web service calls to get non-cached data directly from one end device via iDigi will consume three transactions:
A client application performing asynchronous web service calls to get non-cached data directly from three end devices via iDigi will consume five transactions:
For detailed information on pricing and billing methods, please see the iDigi Billing Whitepaper.
What is an overhead transaction versus a query transaction?
Overhead transactions are infrastructure messages passed between the iDigi Device Cloud and end devices, such as persistent keep-alive messages. Overhead transactions are not billed to end customers by iDigi.
For detailed information on pricing and billing methods, please see the iDigi Billing Whitepaper.
How is a transaction billed that is fragmented across multiple IP packets?
Transactions that are fragmented during transport into multiple IP packets are billed as a single transaction. For example, a web service call to move a file onto a remote device will be billed as a single transaction, even if the web service call is fragmented into ten 1500-byte IP packets as a result of the file size.
For detailed information on pricing and billing methods, please see the iDigi Billing Whitepaper.
Where can I get more detailed information about iDigi Device Cloud transactions and billing?
Please see the iDigi Billing Whitepaper or contact a Digi sales representative for more information.
The CSA is a member-driven organization, chartered with promoting the use of best practices for providing security assurance within Cloud Computing.
