[Fiware-wpa] FW: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2//

[Juan Bareño Guerenabarrena]

Dear WPLs

 

Please find below the detailed plan for complete the standardization deliverable for M15, end of this month

 

Please react to what NEC, task leader, ask from you:

-       Identify a responsible partner per WP

-       Provide the inputs required in the wiki

-       Review content and format requirements

 

For any doubt please contact Lindsay/Ernoe, in cc

 

Thanks for your contribution

 

Juan

 

From: Lindsay Frost [mailto:Lindsay.Frost at neclab.eu] 
Sent: jueves, 05 de julio de 2012 15:12
To: Juan Bareño Guerenabarrena; Miguel Carrillo; Nuria De-Lama Sanchez; Carmen Perea Escribano; lorant.farkas at nsn.com; thierry.nagellen at orange.com
Cc: Ernoe Kovacs
Subject: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2//
Importance: High

 

Dear FI-WARE management team,

 

Please distribute this email on PCC; fiware-wpl at lists.fi-ware.eu; and  fiware-wpa at lists.fi-ware.eu 

 

We refer to information provided to NEC in a teleconference on 02.07 by FI-WARE management regarding

providing in the next 3 weeks a new Standardization Plan.

 

NEC protests at the way the management decision was reached and communicated. The decision took 

no account of NEC proposals which were sent 23.05.2012 and for which responses were 

twice requested. The decision now requires NEC to make a burst of effort in the next 3 weeks 

to immediately create a new Standardization Plan, without considering NEC staff availability. 

Furthermore, the needed strategic inputs are not in the hands of NEC to create.

 

Nevertheless, NEC has created a new fast-track plan with some chance of success, assuming continuous 
and strong input from partners. Endorsement, help and support from FI-Ware management and PCC

is strongly requested. Depending on the inputs from FI-WARE partners and the later review of the EC, 

NEC will reconsider its' future participation in this part of WP11. 

 

Outline of Plan (detailed plan below):

·         FI-WARE WPLs identify which Generic Enabler interfaces are important and therefore crucial for standardization. 
It is essential that a FI-WARE software architect complete such a list/diagram immediately to focus the work.

·         FI-WARE WPLs nominate responsible partners and _persons_ who will input the plan and status for standardization 
at _specific_ SDOs, for _each_ of those important interfaces (a subset of all interfaces)

·         The nominated responsible persons input their plan into the private Wiki as described below, and update
the Wiki FI-WARE Standardization v2 (private wiki) <https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2>  with (their) past contributions as well as planned future ones.  
FI-WARE management team has promised weekly oversight of this activity.

·         NEC summarizes results in last week of July, creating D11.4b pdf from the Wiki

 

NEC requests confirmation of this plan, which is detailed below.

 

Yours sincerely,

Dr. Lindsay Frost,  Dr. Ernoe Kovacs

 

ATTACHMENTs

(1)    Old, still valid Action Plan to react to EC comments (file 2012-05-23-ActionPlan.txt)

(2)    Detailed Plan for D11.4.b by End July (see below)

 

 

Attachment 2:

The following is the step-by-step plan:

 

(D) NEC Conclusions for Standardization Plan content and format

6.       General content required (to be generated by FI-WARE partners)

a.       identify what standardization makes sense for FI-WARE (targets), 
taking account of specific gaps which the EC requested fixed

b.      identify where to do it (selected SDOs) /note: should reference "Section 2 CONTRIBUTE" actions in D11.4a/

c.       explain (if it is planned) where IP generated in FI-WARE is inserted into SDOs specifications

d.      for each selected SDO and FI-WARE target, show the timeline of how to achieve the target, with "concrete steps" and partners, starting work "even before usable results" as requested by EC

e.      show how ongoing actual contributions to SDOs fulfill the "concrete steps" (i.e. ongoing status)

7.       Step by step Format

a.       WPLs create a webpage mapping important FI-WARE interfaces/protocols to the Target SDO which could be responsible. It should also indicate any IPR which FI-WARE may bring in. This webpage would satisfy (D)6.a and (D)6.b and (D)6.c above.
In the opinion of NEC, standardization is most valuable for the exposed interfaces, and in a secondary way to efficiently design the internal interfaces. Therefore all exposed interfaces are important, and some internal ones. As an example of some important interfaces, the (old) picture https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/Snapshot_2012.06.01_of_Deliverable_Page_for_D2.3_Architecture_Specifications could be used. 

b.      WPLs create a webpage showing which partner is responsible for each important interface and their responsible person to make it standardized. The format can be a table ("Target SDO / Responsible Persons") with entries <SDO><Exposed Interface><responsible partner><responsible person><comment>.

c.       Responsible persons add to FI-WARE Standardization v2 (private wiki) <https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2>  page, for each Target SDO,  a timeline based on the SDO meeting schedules and methods, which is designed to get the exposed interface standardized. A partial example is given for ETSI M2M. This satisfies (D)6.d. This can only be created by the responsible persons who also ensure that that Target SDO work happens. It should indicate the phases as e.g. (1) feasibility-study (2) architecture (3) datamodels and protocols.
The format can be a table ("Target SDO / Contributions Table ") ordered by date, so later it is easier for the information to be integrated into a complete project plan, e.g. <dates> <SDO or Event><contribution title and SDO ID><Exposed Interface><responsible partner><responsible person><phase/IPR/comment/status>

d.      The responsible person updates the Target SDO / Contributions Table every week, with new planned inputs and new results. Care should be taken to note any IPR. This satisfies (D)6.e.

e.      NEC creates an integrated timetable showing the aggregated copies of all tables from step (c) above, which is the overview for the EC. NEC will combine it with (a) and (b) - assuming all partners have strongly contributed - so as to resolve all EC requests.

f.        Optionally partners can extend the information in (c) above, to include highly relevant non-FI-WARE results which are monitored (M). Also partners can include relevant work they do which however is not part of the agreed important interface work. Monitoring standards is also part of the standardization plan and this work should be reported to the EC, as long as it is shown as supporting a significant amount of active contributions work.

 

NEC rejects proposals to use Googledocs because NEC was required to change from doc to Wiki during the previous phase of the project and the good reasons for doing that still hold.

 

 

 

------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended 
solely for the addressee; it may also be privileged. If you receive 
this e-mail in error, please notify the sender immediately and destroy it. 
As its integrity cannot be secured on the Internet, the Atos 
group liability cannot be triggered for the message content. Although 
the sender endeavours to maintain a computer virus-free network, 
the sender does not warrant that this transmission is virus-free and 
will not be liable for any damages resulting from any virus transmitted. 

Este mensaje y los ficheros adjuntos pueden contener informacion confidencial 
destinada solamente a la(s) persona(s) mencionadas anteriormente 
pueden estar protegidos por secreto profesional. 
Si usted recibe este correo electronico por error, gracias por informar 
inmediatamente al remitente y destruir el mensaje. 
Al no estar asegurada la integridad de este mensaje sobre la red, Atos 
no se hace responsable por su contenido. Su contenido no constituye ningun 
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. 
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor 
no puede garantizar nada al respecto y no sera responsable de cualesquiera 
danos que puedan resultar de una transmision de virus. 
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120705/23620f73/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 2012-05-23-ActionPlan.txt
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120705/23620f73/attachment.txt>