OAK 0.00% 7.0¢ oakridge international limited

XPE Lounge, page-272

  1. 27,129 Posts.
    lightbulb Created with Sketch. 1756
    Which seems to be the way the IoT market is heading towards and has been noticeable from what XPE has been saying about their "Tap" complete ADRC solution uptake from the market so the market wants something like the ADRC gateway solution???? Which XPE has successfully integrated into Intel's SHDAP????


    1. Tap
    This is based on our ADRC Device Proxy firmware for devices and is focused on device discovery, onboarding, and provisioning in a local area network. While Tap is unique and an elegant user experience, to take full advantage of the Tap experience, a customer is required to accept the ADRC proprietary communication protocol. This requirement is a challenge in the consumer space where the market pressure is to align along industry standards such as Zigbee, Z-wave, WiFi, Bluetooth, etc. As such we have prioritised industrial opportunities with companies such as Vital Xense for the full implementation of the ADRC Device Proxy. We are also starting investigations around what components of Tap can be extended to Zigbee and Bluetooth standards. A future opportunity may eventuate when Tap is demonstrated to the OCF “Easy Onboarding” project group.

    2. Xped APP and RML
    The Xped APP is unique in that we have taken an approach similar to a browser found in your internet search engine today and extended it via RML to the concept of a device browser on your phone, tablet and eventually your TV, PC, or automated virtual assistant. The Xped APP is a single APP that can display multiple different user interfaces and multiple different user experiences for a device simply by changing the RML description file developed for it. Initially many of our customers only pay limited attention to the Xped APP during our discussions, but as we drive deeper into the engagement the true value of the Xped APP becomes more apparent. The Xped APP and RML combined dramatically reduce time to market in launching an APP and then continue to add life to the APP by allowing our customers to add new devices, features, and services to the APP without having to invest significant effort to rewrite the APP. One final point to highlight about the Xped APP is that we are positioning it to be a white-labelled product that our customers can re-brand and customise for their specific needs.

    3. Gateway Software and Cloud Services
    These two components are the most recent addition to our end-to-end platform strategy. The development of our gateway software allows Xped to integrate and support devices that do not use the ADRC Device Proxy and still display them via RML in our APP. This is significant because now we can present ourselves as one, if not the only, solution in the market that has embraced the concept of an open-standards-based platform that allows our customers to maintain ownership of the data being generated by their customers. Our first implementation of our gateway software is targeted to be completed in June and is an integration of Xped software and Intel’s Smart Home Developer Acceleration Platform. The first hardware to support our gateway software is an IoT Gateway developed by Cybertan. By including our gateway software in the cloud and phone using our virtual gateway concept, we also address the needs of ODMs and OEMs who are launching individual devices that they do not want to encumber the cost of a gateway device. This is the approach that we are using with Lenze where a single device will connect with a custom APP specific to that product. Regarding the cloud services portion of the Xped platform, the key differentiators come from the implementation of Xerts (Xped Adverts) which will allow for direct 1:1 engagement between our customer and their users, the creation of our RML repository which stores the RML code for devices that have not implemented our ADRC Device Proxy firmware and our approach to APP to APP integration via our APIs. This APP to APP integration allows our customers to bring in additional devices, services, and features via a cloud to cloud integration vs having to develop the features themselves. An example of this is the integration of the Jemsoft Deep Learning AI components with the Xped Camera Manager and the JCT Nucams solution. From an external perspective, this approach will allow us to integrate with service providers such as Dominos, Uber, and Amazon as well as device manufactures such as Nest, Netatmo, and Philips Hue. Our original MOU with Microsoft was a key driver in the implementation of our cloud services solution hosted in the Microsoft Azure Cloud. The first examples of the Xped cloud services solution will be the Lightsview project and the Lenze Smart Leads device launch.
    Last edited by AlCp: 05/08/17
 
watchlist Created with Sketch. Add OAK (ASX) to my watchlist
(20min delay)
Last
7.0¢
Change
0.000(0.00%)
Mkt cap ! $1.889M
Open High Low Value Volume
0.0¢ 0.0¢ 0.0¢ $0 0

Buyers (Bids)

No. Vol. Price($)
1 19 7.0¢
 

Sellers (Offers)

Price($) Vol. No.
10.5¢ 1524 1
View Market Depth
Last trade - 16.00pm 23/08/2024 (20 minute delay) ?
OAK (ASX) Chart
arrow-down-2 Created with Sketch. arrow-down-2 Created with Sketch.