Presentation by Juanjo Hierro CTO, FIWARE Foundation FIWARE Global Summit 21-22 May 2019 - Genoa, Italy

1. Front-runner Smart Cities
A collaboration between TMForum and FIWARE Communities

2. Background
1

3. Front-runner Smart Cities initiative
§ Goal: to support a digital single market of interoperable and replicable solutions for smart cities
and the transformation of cities into platforms through the adoption of:
• A reference architecture relying on:
□ FIWARE NGSI API for breaking information silos and describing context of the city in right-time
□ TM Forum Business Ecosystem Open APIs to bring support to data monetization
• Compatible public and royalty-free common data models validated through projects implemented in
cities where a platform aligned with the defined architecture has been deployed
§ Launched at the SCEWC’18 in Barcelona, joined by The cities of Vienna (Austria), Nice, Saint
Quentin (France), Genoa (Italy), Utrecht (Netherlands), Porto (Portugal) Santander, Valencia
(Spain), Gothenburg (Sweden), La Plata (Argentina), Montevideo (Uruguay), with an open
invitation to other cities to join (Eindhoven joined soon afterwards)
§ Specifications will be considered stable as soon as enough cities have validated them in
practice (driven-by-implementation process).
§ Stable specifications will become TM Forum formal deliverables following TM Forum’s defined
processes
2

4. Specification processes
3

5. Main principles
§ Keep an open and agile spirit, implementation-driven
• Technical work done mainly offline. Calls only for admin/marketing purposes. Kick-off, major events.
• Using the facilities offered by open source collaborative tools, ensuring maximum transparency
• Using a common Github organization: https://github.com/front-runner-smart-cities
§ Have a lightweight process that
• enables fast track adoption of proposed specifications
• Empowers actors (cities, SDOs, techn. providers) to propose new specifications that can be quickly adopted
• Adopt specifications which demonstrate applicability in real world scenarios
§ Open-closed. Do not make breaking changes to already approved specs. New versions shall
• Deprecate attributes. Add new attributes. Extend enumerations, etc.
• Create a completely new entity type if someone proposes something totally different for the same city asset!
§ Recognizing previous work done by the FIWARE and TMForum communities
• i.e credits shall be given to contributors when publishing the work
4

6. General program framework
§ Data Model Licensing mode proposal.
• Creative Commons by Attribution 4.0 https://creativecommons.org/licenses/by/4.0/
• Still under discussion. Pending TMForum’s legal department feedback.
§ Mechanism to track participant’s comments:
• Jira and Confluence tools provided by TM Forum, to support collaboration (meetings, planning).
• Github for the management of specification lifecycle
§ Contributions open to anybody (not only members), while final decision making corresponds to
TM Forum and FIWARE Foundation members
5

7. Specification Adoption workflow
§ Specifications are grouped by themes or verticals (parking, waste management, etc.)
§ Specifications could be in the following states:
• Curated (v1.0). Comments from cities might be received through RFC.
□ A mechanism to raise comments will be put in place (Github, ).
• Approved (vx.y) (explicitly endorsed by at least 10 cities)
§ RFC duration is 6 months
6
Curated
Version
(v 1.0)
RFC open Approved
(v x+1.y+1)
New version cycle
with RFC period open
RFC
Period open
Comments
Addressed

8. New specification proposal workflow
§ (It refers to the case when an existing FIWARE or TM Forum Data Model does not cover a need)
§ At least 2 cities or technology providers propose new specifications for a given Smart City
challenge to be addressed
§ FF and TM Forum launch an RFP (duration 4 months on average)
• RFP is responded and proposals analysed
• If more than one submitted proposal, FF, TM Forum and interested cities (with their partners) align and create a
single v1.0 draft
□ 2 months period
• Afterwards an RFC is issued and the proposal workflow (described by the previous slide) is put in place
7
RFP
Issued
Submissions
Analysis
First
Curated
Version
(1.0)
RFP responses
Responses
alignment

9. Next steps
8

10. Starting the process with existing specs
§ The process will start with curated specifications already available in the FIWARE Data Models Project
• (aligned with TM Forum as already agreed with TMForum’s chief architect)
§ The initial RFC phase will have a duration of 6 months to allow cities to react properly
§ 8th of May 2019: TM Forum and FF will communicate to stakeholders through a kick-off call
• Process
• Publication mechanisms
• Way of working
§ Week starting 10th June: first RFC will be launched about curated specifications (v1.0)
• See next slide for contents
• Initial internal PoC will be validated with TM Forum Architect.
9

11. V1.0 Curated Data Models
10
First RFC Launch: Week of 10/06/2019.
RFC Duration: 6 months
Vertical
Waste
Management
Environment
Weather
Parking
Point of Interest
Transportation
Street Lighting
Device
Alert
V1.0 of curated Data Models will be released on 10th Jun 2019

12. First f2f working meeting in Genoa, May 22
§ During the FIWARE Summit on May 21-22 in Genoa, we will be running a first f2f working
meeting of the initiative. This will take place on May 22 from 09:00am-10:30am
§ Agenda of the meeting:
• Intro and status of roll-out process
• Publication and testing of first set of Data Models (relying on initial FIWARE Data Models)
□ Calendar for publication of Data Models on GitHub and corresponding RFCs
□ Call for participation/contribution to showcases relying on first set of Data Models:
– Visibility under umbrella of collaboration with World Economic Forum – Global Smart City Coalition
– Exhibition (FIWARE Booth) and announcement at SCEWC in Barcelona
• Preparation work for first series of New Data Model RFPs:
□ Identification of Smart City challenges (interactive session)
□ Definition of Working Groups in charge of RFP drafting around identified challenges
□ Definition of target calendar
• Next meetings
11

13. Project Responsibilities
12

14. Responsibilities
§ Global Coordination : Co-leaded
• Call for RFPs, RFCs, transition of specifications, etc. version control.
• Project monitoring
§ Collaboration activities: Lead: TM Forum.
• Communication to stakeholders (jointly signed) and TM Forum members (TM forum signed)
• Call for teleconferences, etc. Call discussion facilitation, etc.
• First level help desk
• Publication as TM Forum Recs, etc.
§ Technical activities: Lead: FF. TM Forum to revise Pull Requests to Core assets.
• Implement change requests. Analyse feedback. Level 2/3.
• Implement support tools ex. Validators, etc. ensure alignment with TMF architects.
• Technical support to publication activities
• Revise new RFP answers, consolidate, develop.
13

15. Annex: Repository Organization (Github)
14

16. Repository organization
15
One Data Model publication Repository per vertical
Individual Versioning
https://github.com/front-runner-smart-cities
Umbrella Repository.
Common assets
Git submodules
CI: Schema validation

17. Publication Repository Structure
16
One Folder per Entity Type
Adoption Status
Technical issues reporting

18. Data Model Structure
17
JSON Specification file
(Machine-readable)
Examples
spec doc (human-readable).

19. Documentation Structure
18
Data Model
Specification

20. Specification Structure (Markdown)
19
Will include examples of
use with both NGSIv2
and NGSI-LD
Acknowledgments to the
FIWARE Community
members that created the
spec shall be given

21. Thank you!