Jump to content
WEC2019 Call for Abstracts Read more... ×

Leaderboard


Popular Content

Showing content with the highest reputation since 06/01/2016 in Posts

  1. 2 points
    Contact information for WPLAN systems and operators in Australia: Ingenu http://www.ingenu.com/ http://www.iotoz.com.au/ LoRa https://www.lora-alliance.org/ http://meshed.com.au/ https://www.thethingsnetwork.org/ http://www.nnnco.com.au/ NB-IoT http://www.3gpp.org/http://www.3gpp.org/news-events/3gpp-news/1785-nb_iot_complete SIGFOX https://www.sigfox.com/ http://www.thinxtra.com/ Taggle http://www.taggle.com.au/
  2. 2 points
    IMHO... IOT is a user of technologies rather than a being a technology itself so there is no single set of standards governing IOT. Device developers choose technologies based on the constraints they operate under. There are two broad categories of standards in which to make choices: network access (comprising the physical and data-link layers) and application protocol. A lot of standards that have been mentioned previously have to do with network access (Bluetooth, Zigbee, wifi, etc). These standards can be used by IOT but were not designed specifically for IOT. At the application layer, there are some protocols that could come to dominate the field - whether that will be MQTT, REST API, or something else is yet to be seen. I don't see that any standards org is going to come out and dictate that IOT must use this or that particular access method. A comparable analogy would be that no one dictates to you how you access the Internet - you may have ADSL, cable, mobile broadband, or some other means. However, once you are connected, if you want to browse the web, you must have a client that speaks HTTP at the application layer. Standardisation of the application layer would make IOT devices more inter-operable, and should enable a company that runs an IOT network to move from one service provider to another.
  3. 2 points
    Please contribute to this thread by adding information about government and other support and collaboration opportunities available to startups and other developers in the IoT space. Below is a start on this. Australian Govt Support R&D tax incentive https://www.business.gov.au/assistance/research-and-development-tax-incentive Commercialisation support https://www.business.gov.au/assistance The Industry Growth Centres http://www.industry.gov.au/industry/Industry-Growth-Centres/Pages/default.aspx IoT Alliance - Collaboration http://www.commsalliance.com.au/Documents/Publications-by-Topic/IoT http://www.iot.org.au/ http://www.iot.org.au/workstreams/ Workstream 6 is on IoT Innovation
  4. 2 points
    Following are some Ideas for community outputs gleaned from our initial survey and research. The text in brackets are my interpretation of what the output could look like. Please comment below on what other things you might like. Explanatory guides/webinars An overview of the basic framework. e.g. What happens after the front end data is collected. [An overall framework of IOT, spelled out in basic technical detail, i.e. the Body of Knowledge Framework] Reference guide to common acronyms. [Glossary with simply English explanations, part of wiki?] IOT for other engineers [A plain English version assuming no ICT knowledge whatsoever] Commercial guidance - what are current models and why aren't they suitable for the new technologies. + How others justify investment towards IOT technologies and what is happening in Australia [1)How to build a business case, and 2) How to select the right technology set] Guide to IoT standards and protocols Examples/Case studies of applications [1) to spark imagination of what is possible, and 2) Demystifies IOT] Expert forums where i can get in touch with people involved in IOT rollouts [Links to more specialist forums?] Industry/discipline specific application guides (electrical dist x2, power generation x2, asset mgt, mining,civil, geotechnical, mechanical [What would this look like? What is different between industries?] Guide to relevant grants supporting innovation using IOT Advanced tools Risk assessment methodologies needed when complex technologies are integrated. [Risk engineering guide for IOT] How IOT can be secure and be accessible for public development [Guide to security issues] Rasperry Pi or Arduino interfacing to environmental monitoring sensors and ("conventional") control systems, and expanding from there. [??] IOT Testing Lab for engineers to play and test solutions Product technology selection “IoT is so varied it can be daunting finding the right thing (product or service).” + “Access to high level but also detailed information about current technologies, products and challenges. Low priced self data analytics [Guides to specific segments of the IOT framework] Guides on wireless/satellite communications and power consumption. A directory of product / service providers. [Integrated guide, showing how providers focus on different parts of the IOT framework and different industries] new product/innovation newsletter Other STEM outreach guides i.e. IOT for high school students IOT challenge for engineering students Please comment below with additional suggestions.
  5. 2 points
    Hi Geoff Three of us at MEA listened to your inaugural talk this morning on the IoT and thoroughly enjoyed it. You handled question time with panache and told us a few things we didn't know (SigFox - whatever that is - heading the list...) You also mentioned that folks likely to field a 'top-to-bottom' solution for an IoT application were still in the future, and likely to need a team of about 20 good folks to pull it off. Even counting our sales, marketing and administration folk - plus external industrial design and manufacturing support - brings us no-where near that number of staff. Yet we have built and are operating over a thousand on-farm IoT nodes across Australia, moving soil moisture and climate data to the cloud (our 'Green Brain' web app) with data available 'any time, anywhere' on an irrigator's mobile. But your point is valid - the IoT is a multi-disciplinary field requiring a very broad approach to engineering, product development and customer support. To end on a lighter note, one of our engineers found this IoT quote somewhere on-line: - “IoT is like teenage sex: Everyone talks about it, nobody really knows how to do it. Everyone thinks everyone else is doing it, so everyone claims they are doing it too.” Andrew (at MEA in Adelaide)
  6. 2 points
    Hi Andrew, the topic you raise is spot on, and is a core item I will address in my webinar on 5th July. The IoT when considered top-to-bottom - ie from the Cloud down to deloyed Things - encompasses just about every facet of ICT, software engineering and and electronics engineering. There are at least a dozen technology elements, each of which has a steep learing curve. And add to that the required knowledge of the system where IoT is to be applied. That said, many aspects of IoT technology are not new - just used in and integrated manner, often by engineers who are expert in the field where they wish to use IoT, but not in the actual IoT technologies themselves. One of the primary drivers for forming this community was the need to provide a means for those involved in IoT - both technology providers and technology adopters - to come together to help build critical mass.
  7. 2 points
    New community site is online!
  8. 1 point
    When all is said and done, there has usually been more said than done! This is surely true of the IoT. I agree with IoT’s promise, but see few of its practitioners. Much of the IoT hype talks about connecting the fridge to the stove, although why, I can’t imagine. Business cannot thrive without customers, and who are they in IoT land, once the Early Adopters have tired of its promise? I can claim some small expertise in this area, having successfully launched an On-Farm Internet-of Sensors system called Plexus three years ago, moving soil moisture and climate data using solar-powered mesh networks across the farm and up to a web-application in the cloud that allows farmers to access their irrigation data from anywhere, at any time. To break into this field required a huge investment of funds over three years, a multi-disciplinary approach that hauled together electronic, mechanical, communications and software engineers, plus external industrial design skills, a manufacturing link into China, all sorts of technical skills to set up the production line, and some thirty years of previous environmental measurements in the bush merely to battle-harden the troops. Then you have to sell it and keep it working until you’ve crossed the ‘valley of death’ between early adopters and the early majority. So the hard reality is that breaking into the whole IoT technological arena is non-trivial; it’s no place for the faint-of-heart or the weak-of-purse or the inexperienced-yet-hopeful. But it is fun, and at last, slightly lucrative. Dr Andrew Skinner FIEAust CPEng NER South Australian Professional Engineer of the Year, 2015
  9. 1 point
    Hi Adam, Thanks for joining and commenting. It's always great to see people getting in to this space. We host year 10 students for work experience, and they are all over it. Bodes well for the future, but also a bit of a kick for more experienced guys to stay current. Re you questions. "In the short term, what would be a good place to start to learn how to get data from a Thing to a cloud?" Yes - and vice-versa. I would suggest AWS as the simplest entry to the cloud space, and then initially getting a feel for comms transport via some basic PC or mobile device app. There are many options for comms and transport. Choose one that has library support for your mobile device and AWS and use it. Better to know one REALLY well than 10 superficially. Don't forget the downlink - you'll want to be able to actuate you mobile device app from the cloud (presumably via a web GUI). You could make your own thing, or buy a thing, but a mobile device is a highly capable and transparent dev tool for things. That said, you may want to branch out to more things, say BLE-connected to your app, and then sub-squently available on the IoT. Again, at the local wireless network level, there are many options. Choose the ones that are best supported and learn them from end to end. BLE and WiFi are easy entry points. WiFi is possibly the simplest but is power hungry(er). Re Image gathering, and AR, certainly it is a hugely cool topic. It's not my particular area although we do do image recognition stuff & triggering of abstracted logic based on that. Yes the video is also more data and processing hungry. If you had a good data plan to play with you could upload to the cloud and process there if you thing was not up to the task. Check out https://artoolkit.org/. Cheers! Jon
  10. 1 point
    There are a few new market reports out on the state of the global IOT industry. 360 Market Updates is forecasting the IOT market to "grow at a CAGR of 35.97% during the period 2016-2020". I didn't purchase the report but the exec summary has an interesting list of the key vendors. More at: http://www.360marketupdates.com/global-internet-of-things-market-2016-2020-10290207 IDTechEx has an interesting discussion on the market. It says: "We do not repeat the mantra about tens of billions of nodes being deployed in only a few years. The many analysts sticking to such euphoria ignore the fact that, contrary to their expectation, very little IoT was deployed in 2016. They are "bubble pushing" with their forecasts, predicting ever steeper takeoff, now a physical impossibility. However, our ongoing global travel, interviews, conferences and research by our multi-lingual PhD level analysts located across the world does lead us to believe that a large market will eventually emerge." In particular, it argues that IOT "nodes" (being the devices themselves) are being rapidly comoditised and that "the money will lie in the systems, software and support." Read more at: http://www.idtechex.com/research/reports/internet-of-things-iot-2017-2027-000499.asp
  11. 1 point
    This is indeed the general approach we are working on. However, I have to wait for EEA to deliver the capability sorry. They have had a bit of staff turnover recently that I think is hampering finalization.
  12. 1 point
    This post describes the core processes of the community, as illustrated in the following flow chart. The core functions of each role are as follows: a. Community Leader: i. Hosts core member meetings and sends meeting invites ii. Takes minutes and copies to Community Agenda Forum iii. Approves all webinars and other events iv. Champions any special community projects and obtains any resources required to deliver them v. Ensures good variety of activities and coordination of all other roles vi. Backs up the other roles as required vii. Recruits and appoints new core members to roles as required. viii. Approves major changes to the wiki b. Body of Knowledge Manager: i. Responsible for Wiki structure ii. Evolves wiki page templates to best capture useful knowledge iii. Identifies gaps and requests the Webinars Program coordinator to find speakers on these topics iv. Works with volunteers to get webinar transcriptions into a good format for the wiki. v. Uploads final content into the wiki. vi. Identifies opportunities for practice notes and other special projects. c. Webinar Program Coordinator: i. Works with other core members to identify potential speakers ii. Makes initial contact and organises/confirms date, iiii. Updates webinar management list and ensures there is a speaker every week. iii. Sends speakers guidelines and assigns/confirms a volunteer host for each webinar iv. Updates the event calendar d. Community volunteers (x6) i. Works with assigned speakers to get webinars description and bio min two week prior to meeting ii. Hosts meetings (one per month) iii. Edits transcriptions ready for upload to wiki. iv. Leads Practice Note projects as required e. Forums facilitator i. Monitors Google Alerts and adds appropriate news items to Industry News Forum ii. Stimulates discussion threads on Engineering Forum (methods to be determined) iii. Ensures all posts are responded to by appropriate community members f. EA Liasion– EA staff member(s) i. Recruit/approve the community leader ii. Creates webinars in webinar system iii. Reminds Community volunteers of upcoming content deadlines for promotion of webinars. iv. Organises input of webinar descriptions into EA’s Event Alert system v. Organises transcriptions of webinars vi. Uploads webinar recordings to MyCPD vii. Manages email inbox (iotengineering@engineersaustralia.org.au) and resolves member issues. viii. Develops and delivers support and training materials (process maps and instructions for new core members) ix. Develops and maintains community platform x. Coordinates promotion of community to the public xi. Identifies and pursues sponsorship opportunities.
  13. 1 point
    Hi All, A colleague and I have produced a paper for an International Conference next year. We work in the power engineering domain and the control thereof and see the IoT as a key to the future of this practice. Regards Ian Boake Boake Rijgersberg A proposal for real-time monitoring and control of the reticulation grid with photo-voltaics electrical vehicles and batteries em_fin.pdf
  14. 1 point
    The Chasm between Australian Industry and Science Much public hand-wringing has occurred in the past few years about Australia’s poor international rating when it comes to collaboration between our industry and our scientific bodies. During our IoT webinars, this curious snake-in-the-grass has reared its head in the same old way, suggesting that there remains a fundamental misunderstanding between the two camps. What really gets my goat are steamy statements from academia about how the growth of the IoT is dependent upon industry driving the cost of sensors and hardware down to just a few dollars each. I’ve watched in dismay over the last decade as CSIRO, NICTA and Sense-T have all promulgated a message that their clever research will make this happen, bypassing the clunky technology of existing industrialists and heading straight for grateful farmers. This inanity reached a peak some years back with statements that these new ultra-cheap IoT devices would be ‘scattered like confetti from helicopters, link up automatically and feed data back’ to the Big Data folks, seemingly forever. That the helicopters never took off is just a self-evident footnote to my grumblings. The reality on the ground is that the deployment of technology and the building of profitable markets that can feed further development is a long hard grind. That’s why technology doesn’t just skip merrily ahead like a spring lamb once the research funding is used up. It will cost money to sell service and support IoT gear – just like everything else. So my gut feeling is that the disconnect between Australian industry and academia is somehow fuelled by this hype and a general failing to understand each other’s very different currencies. More on that later… Perhaps this webinar series will tentatively open some doors between us all and lift our collaboration ratings?
  15. 1 point
    Here is an interesting low cost low energy LPWAN technology competing with SigFox, which is being rolled out by Dutch Telco KPM. An interesting aspect is it has a location function, which could be used to track transported item.
  16. 1 point
    The standards activity under way within ISO/IEC JTC1 WS10 is focussing on defining reference architectures, standardising nomenclature etc. The objective is not to restrain what is done in the IoT space - but rather to provide a platfrom to foster interoperablity between devices and systems. Indeed, there is a desire to encompass open source and public domain standards. The regulatory compliance aspect of IoT devices is addressed by existing regilatory standards - EMC, radiocommunications, electrical safety etc.
  17. 1 point
    Question from 5-Jul Webinar: Can you please briefly outline the pros and cons of the competing wireless protocols for IoT application. Answer: This topic is the subject of a webinar on 9-Aug-16 "The future of narrowband communication technologies enabling the IOT" The webinar will address technologies for Wide Area Networking (3G/4G/5G/NB-IOT, Sigfox, LoRa, Ingenu), local area networking (WiFi, 6LoWPAN, Zigbee) and personal Area Networking (Bluetooth, BLE).
  18. 1 point
    Question from 5-Jul Webinar: Do you feel it's more likely that enterprise will look to develop IoT development capabilities in house or rely on external consultancy? Answer: The technologies and engineering skills require to implement IoT system top-to-bottom are extensive, and it is unlikely that typical engineering teams using IoT in their systems or developing IoT-capable products will have the full range of required capabilities. Additionally, these skills are different from the core skills required to design and develop the primary functions of the system or product. It is likely that most organisations will require the services of external consultancies, or full service providers such as the large industrial automation and building management system providers.
  19. 1 point
    Hello all, Here is a starting point for ways to measure value addition by the community. Please comment and offer suggestions so we can finalise and turn it into a matrix. Value Measurement-IoT Practice Community (Draft).docx
  20. 1 point
    IOT data management company Buddy Platform will add to its Australian presence by acquiring device management provider Zentri, which has an office in Sydney. Buddy already has an office in Adelaide, the home of one of the company's founders. Buddy said: "The addition of Zentri brings together Buddy’s powerful IoT Data Graph to manage, process, and visualize IoT data coming from embedded chipset solutions managed and powered by ZentriOS and Device Management Service." See more at https://buddy.com/blog/buddy-announces-intent-acquire-zentri-inc/
  21. 1 point
    In order to be cost competitive in the medium to long term, Australian innovators must be cunning and target niche markets where we have a natural competitive advantage. Any IoT product which takes off in the consumer space risks being overwhelmed by a flood of cheap competing products from overseas - including wearables, home automation and other fads and "flavour of the month" applications. The first mover advantage in these spaces is likely to be short lived. Areas to focus on include e-health, agriculture, transportation, mining and smart cities.
  22. 1 point
    Folks - I've lifted this 'sidebar' about our Plexus IoT development story from an application note I'm writing about powering IoT devices using solar energy. We named the product (in the photos above) - after the 'Solar Plexus' in the human body - two puns intended - is a mesh network delivering data from across the farm (where cellular access is not always present or reliable) via 2.4 GHz ZigBee radio. Hope you enjoy the story Andrew (at MEA) ‘Plexus’ - an On-farm Internet of Things Designing and operating an ‘Internet of Things’ on-farm requires a multi-disciplinary approach to product development involving electronics, firmware, software, mechanical engineering and industrial design, web design, communications engineering, manufacturing skills, good field people and a deep understanding of just how tough an environment it really is when trying to keep measurement technology running year-round for a decade despite the hazards of weather, farm machinery and the occasional rogue human. That we came into this business with thirty years of data-logging experience and environmental measurements helped, but we needed to learn new skills on all fronts to pull this off, innovating our business model as we switched from a custom engineering base to that of a manufacturer. Driving this development was a sense that the old days of storing data in data loggers - then unloading it the farm computer - were at an end, and that modern farmers needed access to their sensor data at any time and from anywhere. This required the power of the Internet to move, store and present this data on PCs, tablets and smart phones without any proprietary software in the mix. It was a new world. Data needed to be collected using energy gathered on-site, ‘hopped’ by cooperative radios across the property to some master controller then automatically fed via a modem to an Internet server that would store data and serve it up to the farmer whenever he logged in. Temporary data storage was needed all along the chain to patch over the usual in-field outages, automatically playing catch-up when network elements were restored. The IEEE 804.15.4 ‘ZigBee’ standard was the obvious starting place to develop such technology because of the deep underpinning developed by the standards people and implemented by big IC manufacturers who made radio systems-on-chip, including the internal software ‘stacks’ that operate the various layers of networked radios. This created an immediate problem for the development team, as each node on the Plexus on-farm network needed to be a ‘router’ under the design brief, forwarding data across a self-healing mesh network with the minimum of set up fuss. However, ZigBee routers are typically ‘always on’, and the solar-powered energy budget simply did not allow for this. The eventual compromise was to re-fashion the whole network for a solid minute every fifteen minutes, then go into complete power-down mode for the remaining 14 minutes to conserve energy. Plexus systems guarantee a maximum 1000 m spacing between any field station in flat country. Given a 5-deep parent-child router arrangement, this allows coverage of most on-farm applications up to 1000 hectares. Radios, solar panels and batteries have to be light-weight and streamlined to live safely about two metres above the top of the crop for clean solar and radio access. Over-row machinery in permanent row crops such as grapes means that the whole Plexus field station pod needs to be ‘knock-down-spring-back’ so that on-farm operations are unaffected by the presence of the radio system. All this geometrical confinement forces a limit on the energy budget that is physical; it only becomes possible if the solar panel is small and light enough to fit inside a tough polycarbonate streamlined enclosure. 5V 400mW solar panels measuring 50m x 50mm fitted the bill but limit field station average operating current to a maximum of 8 mA, distributed between radio, sensor and system elements. Plexus product development took over three years of intensive effort, including seemingly endless returns to the field to be beaten up and humiliated yet again as we tried to understand what was going on – or was not. All this before we even let customers near the data that was being produced. The usual engineering compromises were reached in an effort to meet the deadlines imposed on us by the need to get to market and get a return on investment. Needless to say, we are still unwinding some of these ‘frozen-in-stone’ decisions in an effort to build a more flexible system capable of handling sensors and systems we’ve not even heard of yet. Yet the original concepts proved robust, and more than two years of field data from hundreds of sites across a broad range of crops and climates has vindicated the design decisions made. Like all new game-changing technologies, the Internet of Things is in danger of being over-hyped. Yet it can be made to work by a highly disciplined and experienced engineering team, given sufficient focus and across-company support. But it’s not a game for the faint-hearted or the weak-of-purse.
  23. 1 point
    Hi, After today's webinar by Geoff Sizer "How the Internet of Things will affect every engineer", one of the questions by an attendee prompted me to look into what is happening around the world with regards to the rollout of networks and the support for the 50 billions of IoT devices to be connected by 2020. ref: http://www.statista.com/statistics/471264/iot-number-of-connected-devices-worldwide/ So I've started this thread to provide a central spot for this community to share or add links to news about the rollout of IoT networks around the world. So please feel free to add and grow the following list: South Korean telco SK Telecom recently claimed it was rolling out the world's first nationwide Internet of Things (IoT) network, but it looks like the Netherlands has beaten it to the punch. http://www.gizmag.com/netherlands-nationwide-iot-network/44134/ http://www.gizmag.com/samsung-south-korea-nationwide-iot-network/43518/ Exclusive SigFox network operator for A/NZ, Thinxtra, has started the deployment of the live SigFox public network, with installations of antennas on top of the tallest buildings in Australia – Sydney Tower Eye and Melbourne Eureka Tower. http://www.arnnet.com.au/article/598439/thinxtra-starts-iot-deployments-australia/ http://www.mobileworldlive.com/featured-content/home-banner/sigfox-iot-network-heads-to-australia-new-zealand/ Arqiva plans mobile rollout to underpin IoT project in 10 major cities, including London, Manchester, Glasgow and Birmingham http://www.v3.co.uk/v3-uk/news/2345068/uk-internet-of-things-network-rollout-to-make-nation-smarter Ingenu has announced the initial rollout of its Machine Network that will rise in Phoenix and cover 30 US cities by the end of 2016. http://telecoms.com/452612/ingenu-to-roll-out-iot-connectivity-to-30-us-cities-by-2017/
  24. 1 point
    Welcome to the Applied IOT Engineering community. The community does not officially start operating till after our first webinar on 5 July. However feel free to initiate conversations or introduce yourself in the comments below. DO please take the time to optimise your profile.
  25. 1 point
    Hi Andrew, You and Geoff raise important points about successful IoT enterprises. Because this is an engineering and not a IOT business forum, my response is brief. I agree it is necessary: to understand the application and the underlying IoT technology have access to multidisciplinary skills, including engineering and design to focus on sales and marketing have a route to manufacture have a route to market involve capital partners if necessary The following may also be needed: a great business plan supported by a network of business advisers strategic intellectual property planning, including freedom to operate patent filing strategies (which may be to file nothing) I've started a blog on this site about IoT intellectual property strategy. Justin
×