Thanks for doing this, it has helped me to feel like I'm getting a grip on this. A few comments:
[B1] Vision for Transformation. I would suggest that the point you make here is true for any collaborative situation, and therefore any TGF programme and the more heterogenous the types of organisations the more diverse the aims and agendas will be. This leads me to two questions:
- Should we be drawing this out in the main document? (Possible change for v3?)
- Is the problem different for IoT, or exacerbated to the extent that it needs specific treatment?
[B7] Supplier Partnership. I think the key point here is that relationships could become more complex around IoT - the same organisation may be custodian, supplier and consumer in a single area, and may even have multiple "instances" of these roles. However, I think this needs to be addressed in [B5], not [B7] which is about transforming procurement thinking. (Although there may be knock-on effects here as well.)
[S3] Does something need to be said about what is "private"? Interesting article on the BBC today here
[T1]/[T2] Given how easy it is for organisations to lose track of traditional IT assets, what happens
if when they lose track (or lose interest) in IoT assets? If the asset is still live and connected, but no longer being maintained, does this become a security risk? Does something need to be said about this?
This is a very good start Nig ;-)
I feel the win-win and service oriented approach with competing vendors from different technology platforms and different networked products are crucial for the service and citizen centric approach of the TGF work.
Being working with process control in different markets(ship & offshore, energy/utility,paper industry, home automation, healthcare etc etc) the interoperability layer has been solved through open APIs and open BUS-protocols many years ago.
The new approach is the globalization requirement of merging "open" services on a functional XML level dealing with open information exchange in real time. ( Going from Local Automation to Global Automation ) This require an understanding of a hybrid information exchange structure.
The lowest control level is the process control of interacting networked devices of one or several interoperable BUS-protocols.( BUS interoperability) This is handled by different BUS-standards(technology standards) and their trade organizations. I recommend that this technology level should not be the the topic of the TGF approach. Never the less some of the functionalety in these systems needs to be exposed(mirrored) to a service level to be part of wanted interaction of different services(both public and private).
We do call this service level:
- Scenario composing on an individual user defined level.
This is the level of service templating we are dealing with in OASIS CAM and BCM.
Nig, I have earlier sent some slides of eDevice templating descriptions. Will it be useful trying to explain these OASIS CAM eDevice templates dictionaries in a more easier way for non technical people ?
Siterer Greenaway Nigel <Nig.Greenaway@uk.fujitsu.com
As discussed on our call on 24/7, here is a note containing bullet points for each of the patterns identified in section 3.
As stated in the note I think the next actions are for everyone to look at the issues raised under 'IoT Delta' headings and
1) agree that they are indeed issues
2) agree that they are in the right place
3) Identify any further issues that we should address in the CN.
Then, we need to look at the recommendations, comment upon them and identify any further ones.
I did originally offer to attempt to draft the full patterns for review by our meeting on 21st August. I don't think that will be possible given the need for the TC to comment on this note and my other commitments. Thus, I suggest that we aim to have this note (including a full set of recommendations) agreed by the end of that meeting. I hope that is acceptable.
In either case, I would appreciate comments as requested above ASAP and, wherever possible, I will incorporate them into a further issue of this note.
Lovelace Road, Bracknell, Berkshire, RG12 8SN
Tel: +44 (0) 843 354 5637 Internal: 7444 5637
Mob : +44 (0) 7867 833147 Internal: 7383 3147
Unless otherwise stated, this email has been sent from Fujitsu Services Limited, from Fujitsu (FTS) Limited, or from Fujitsu Telecommunications Europe Limited, together "Fujitsu".
This email is only for the use of its intended recipient. Its contents are subject to a duty of confidence and may be privileged. Fujitsu does not guarantee that this email has not been intercepted and amended or that it is virus-free.
Fujitsu Services Limited, registered in England No 96056, registered office 22 Baker Street, London W1U 3BW.
Fujitsu (FTS) Limited, registered in England No 03808613, registered office 22 Baker Street, London W1U 3BW.
PFU Imaging Solutions Europe Limited, registered in England No 1578652, registered office Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE.
Fujitsu Telecommunications Europe Limited, registered in England No 2548187, registered office Solihull Parkway, Birmingham Business Park, Birmingham, B37 7YU.
To unsubscribe from this mail list, you must leave the OASIS TC thatgenerates this mail. Follow this link to all your TCs in OASIS at:https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php