Jump to content

Cesar A Gonzalez

  • Posts

  • Joined

  • Last visited

Everything posted by Cesar A Gonzalez

  1. Here is an Open Group webinar explaining their interoperability standard for IoT with some basic uses cases. It is interesting how the Internet of Things is becoming more isolated solutions depending on the cloud platform and closed communication protocols. O-MI and O-DF suggest an easy way to implement interoperability based on schemas. Would be interesting to know, how many other standards are out there. Also, interoperability would raise another architecture concern: security.
  2. The news about the possibility for Engineers to be registered to provide engineering services made me think about IoT domain. I encourage reading the consultation paper here The proposed eligibility requirements are the likes of the Queensland Board (BPEQ). Qualifications Experience Make sense: A Degree should tell that someone is capable. The experience should be backed by a degree. This is Status Quo, Steve Jobs would have a different opinion Ok,, back to the subject, the schemes also proposes to register engineers against Industry verticals or Field of Engineering or (maybe both?). The proposed industry sectors are: · Mining · Utilities · Construction · Transport · Consulting and professional services. The industry vertical scheme proposal got me thinking, IoT is about open platforms, open standard that will enable connectivity of Things that weren’t connected before. What should be the Industry sector for an IoT engineer? Maybe it is too early to say or the industry has not been created. Today an IoT engineer is comprised of various specialities engineers in enabling technologies (access, networks, security, DevOps, etc) and industry domain engineers; Civil, Mining engineers and others. So, should an IoT Design for Agriculture be performed by an Agriculture engineer with major in IoT? It is clearer the Internet of Things is a field demanding new skills. Is the registration consultation developed based on scalability of the field of engineering? The Internet of Things promises an Industryless architecture comprising several technologies enabling different systems to talk each other and provide data or insight like never before. I am positive of the registration, I support it and also I think will lift the standards of the engineering practice for Victoria and Australia (Queensland is way ahead). But we need to think if the scheme proposed is suitable for today scene. I encourage reading section 5. Definition of regulated engineering work based on QLD's Professional Engineers Act 2002. Does this definition needs to be updated or is suit for purpose? Do we need to think about an evolution of the field as inter-domain engineering? All the information provided is my personal opinion only, the links, information and data is provided on as-is basis. I can be reached by using the Message feature provided by the community platform or by writing to cesar . iec @ gmail
  3. Anybody here, would know the toolbox for spectrum modelling in Matlab/Simulink? I suspect one of the following: RF Toolbox or Phased Array Systems? any ideas?
  4. Yes agree with you, I think the promise of the Open Group with its O-MI standard is promising in the long run, at the very end IoT is exactly the connection of things so they will a common protocol to speak. And amongst these disparate of standards bodies the adopted ones will be the successful ones.
  5. @Geoff Sizer The 3GPP I wound't call it emerging proprietary standards, this group have a rich history in the cellular domain coming from the development of GSM with ETSI, which all know who won the battle of CDMA vs GSM. They developed the UMTS, which is 3G and developed the LTE, 4G or LTE-A. However, you're right saying the body standard are lagging behind but this is history repeating itself with disrupting technologies. Something to note, will be the new standard working group from 3GPP developing 5G which will cover narrowband, 15 years power device expectancy. Other standard group is the Open Group with its (O-MI) Open Messaging Interface, they called it the HTML of the IoT.
  6. @Andrew at MEA thanks for replying. So basally, Plexus is a turn-key solution. I though there was some RF Design/Planning prior the deployment, so was trust the radio coverage of 1km with LoS (Line of Sight) and assumed a 2 metres height to have access to the radio signals. Always good to have some desktop analysis prior deployment to ensure good quality signals/coverage. LoS/nLoS: Line of Sight or Non Line of sight, this are some characteristics to be taken into account when designing RF solutions. Thanks Cesar.
  7. @Tim Kannegieter do you have rough number to see how will look like. Perhaps validate at least the overall metric i.e community engagement for the next core meeting. Furthermore, looking at the post Value Measurement-IoT Practice Community @Ankur Barua there are here some interesting topics and I will use some of the timeframes for the first version of the roadmap and we'll see how it goes. Map Needs for Roadmap.xlsx
  8. @Andrew at MEA great post, amazing effort from you and your team. it is a true entrepreurship endevour from engineering. I would like to ask about this bit: "All this before we even let customers near the data that was being produced" Is this means that you were designing a product without knowing the data you needed ? What design approach did your team used? A more technical one, what software was used for RF coverage, LoS/nLoS and QoS? Thanks again for sharing this. Cesar.
  9. Hey IoTers Following up the last core members meeting and based on the different topics listed here: I’ve created what I call a “table needs”, from this table needs we can have the main themes for the roadmap, you’ll see goals, outcomes and possible way to measure them. The table is on google sheets, which I though is the best possible tool so everyone can have access on and comment. I propose after the Goals have been agreed, then we can start develop the roadmap and the subset of plan to achieve each goal, for example, develop the Wiki. Have a go and let me know if there’s an issue with accessibility of the document. Table needs for roadmap: https://docs.google.com/spreadsheets/d/1LUKQoYE90BP5UUfx_heby6kJQnI4MWBnRUb6lSpczxM/edit?usp=sharing
  10. until

    I will not be able to attend this webinar. I do hope will be available in MyCPD.
  • Create New...