[Fiware-oasc-etsi] Proposal to create a short CIM ISG "outreach" presentation

Lindsay Frost Lindsay.Frost at neclab.eu
Fri Sep 9 14:22:29 CEST 2016


Dear Cathy, Juanjo, Franck and all,

I propose a powerpoint of about 10 pages, covering the points below, and I ask your
feedback about how to jointly create it and use it.

We need a convincing "launch" presentation if the Board recommends the ISG, to send
a "outreach" (positive presentation) towards ETSI, oneM2M, SmartM2M members
to engage their interest and to avoid that they assume we are trampling on their topics.
If the Board should _not_ recommend the ISG, then we even more need a positive
presentation to convince them.

Therefore, what do you think of this outline?

_______Contents of CIM ISG Launch Presentation_________
) key message

-         smart cities and applicatiions with IoT need to be developed/trialed/evolved asap ... urgent!

-         (a) no re-inventing the wheel! (b) interoperability with oneM2M is targeted (c) open and public

-         a few organisations see the need for immediate action, and have the commitment
) importance of the topic (CIM for Smart Cities)

-         smart cities are key ROI for IoT, cities are centres of living and production

-         traffic, pollution, parking, water, power (efficiency), crime ... all cry out for efficient IoT solutions

-         eGov and IoT can release many resources/data for synergy with new business and quality of life

-         IoT is the fundamental requirement, BUT most of the synergies between systems rely on Context Info

-         there is no common agreement for how to exchange context information
) desired outputs

-         survey of "who has done what, where is development ongoing, where can liaisons be effective"

-         data models: common vocabulary and/or agreed mappings between many verticals
and also between many spoken languages with different words for same "entities"

-         API to allow _exchange_ of context information

-         promote external open-source implementations and proof-of-principle
) who should contribute?

-         in a world with hundreds of IoT fora, many organisations are already overworked,
so need to make a short-term and focused approach .... "open ended" will not be attractive!

-         who?

o   smart cities are the "users" for the initial use cases, so need to gather together their inputs!

§  OASC are first target

o   application developers and system integrators with strong need for results

§  FIWARE Community are first target
) why is an ISG the right approach

-         low threshold to entry for smart cities

-         initial ideas do not face barrier of huge "learning curve" for existing SDO documents

-         provides a consolidated input, from many sources, towards other SDOs

-         outputs are specifications NOT standards: allows "try and see" without promising
that the results will be adopted by a European Standards Organisation or a global SDO.

-         An ISG can be focused more on the European viewpoint, without promising to cover
also all Americas or Asian viewpoints for smart cities. This is a limitation which might also
help get some success in a restricted context before expanding globally.
) next steps, (your) participation, collaborations/liaisons

-         open to any ETSI member and non-ETSI participants

-         outputs will be public, liaisons as frequently as results are available

-         most urgent: provide tips and info for the initial survey of organisations/specifications

o   initial obvious list (org and WG): ITU-T SG20, oneM2M WG5, ....

Thanks for your feedback
Lindsay


________________________________________
Dr. Lindsay Frost, Chief Standardization Eng.
frost at neclab.eu<mailto:frost at neclab.eu>     Mobile +49.163.275.1734
NEC Laboratories Europe, Kurfürsten-Anlage 36,
D-69115 Heidelberg, Germany.

Reg. Headoffice: NEC Europe Ltd, VAT DE161569151
Athene, Odyssey Business Park, West End Road,
London HA4 6QE, Reg. in England 2832014


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-oasc-etsi/attachments/20160909/f3b852a4/attachment.html>


More information about the Fiware-oasc-etsi mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy