SUPER-MEETUP: Boston IoT, Cloud and Devops Communities.
Two panels. Six experts.
1. Billions of New Devices AND Billions of Existing Lines of Code.
Contrary to some popular belief, developing clouds for IoT is not an entirely, or primarily greenfield endeavor. Sure, your teams may start with a 'clean sheet of paper' to initiate strategy and planning discussion, but, eventually, someone will need to account for legacy systems. For the deployers paying the bills for their new IoT clouds, are not being asked by their funding sources to abandon all that came before. There are regulatory, customer and competitive drivers demanding that legacy systems be harvested for any and all intelligence they can provide to enhance IoT-related value creation.
What does all this mean for developers, administrators, you?
2. Historical Baggage AND Future Opportunity
All the rages in IoT standards seems to revolve around technical standards -- AllSeen, OneM2M, Industrial Internet Consortium just to name three of the most popular. There is another side, the policy standards. New data governance rules are emerging in a number of IoT markets. The heavy equipment industry is launching a new telematics standard with data definition, structure and access rules. The Ag industry's largest Association launched a new data governance and transparency policy last that asserted security and farmer's data ownership as the first two policy statements. The groundwater, energy and transportation industries are imagining new intelligence marketplaces. More and more emphasis is being placed on subscription enablement approaches and tools to reflect in digital systems both emerging and age-old carbon relationships among trading partners.
How can your teams be part of these emerging new rules and profit from them?