We use proprietary and third party´s cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Ask Your Question
0

Smart Cities Help Reuiqred

asked 2017-12-26 16:38:56 +0100

itsumanagaraj gravatar image

Dear Fiware Experts, I'm working on evaluating COTS applications versus oensource solution for Smart Cities. The focus in mainly on usecases related to Integrated Command and Control center focusing on

  1. Smart Traffic Management (Through VMS, Video Analytics, RLVD etc..,)
  2. Safety and Surveillance (With VMS and Video Analytics)
  3. Solid Waste Management (Integration with third party application and view the status of vehicles, garbage collection etc..,)
  4. Integration with Public Information System, Public Address system
  5. Integration with Public transport Passenger information system.

As mentioned above most of the scenarios are direct integration with third party applications. The proposed Integrated command and control center should provide the easy to develop framework and tools to 1. Integrate with Video Management system 2. Libraries and easy to use Video Analytics 3. Powerful user interface screens for city operators to view the situation 4. Context based information processing and correlation 5. System to report different events to ICC 6. Workflow to escalate events and define standard operating procedures 7. Easy to communicate across different stake holders.

I understand Fiware provides different Generic Enablers to start with. In the above context to have an integrated City command and control center I want to know what are the Generic enablers to consider ? We need to do a quick Proof of concept on opensource Fiware to demonstrate the capabilities. In this context please let me know What are the Generic enablers that we should have downloaded Is there any specific enabler/ accelerator that we can consider for this activity ? What is the minimum hardware required for a smart city development with above usecases considered ? Is there any skill set matrix that is available for doing custom development over each of these generic enablers ? Can we have these generic enablers downloaded locally and start using on local setup ? if yes what is the hard ware and software pre requisite ? Is there any cost related details available for reference (Specially hardware requirement, any other software, customization effort etc., ?)

I tried searching some details over fiware resources, but couldn't get much. Any help in this regard will be really useful to push opensource technologies.

Thank you in advance Nagaraj

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2018-01-02 11:02:34 +0100

jmcantera gravatar image

Which are the main logical layers of the architecture and what are their main functionalities?

Infrastructure layer. Provides all the computational resources needed to run a smart city platform instance. It is based on Docker and OpenStack technologies. So, cities can deploy their own infrastructures on premise.

Data acquisition & actuation layer. It allows acquiring and ingesting smart city data from different sources including diverse IoT devices and protocols, existing IT systems, or extra private or public data sources. In addition, it exposes mechanisms to actuate over devices or systems, so that a more efficient and smart behaviour is exhibited by a city.

Context brokering layer. The main component of this layer is a data hub (performing the functional role of a context broker) which integrates all the data coming from different sources. In fact, it offers developers an open API (FIWARE NGSI) intended to publish, consume and subscribe to context information. Context information is modelled using entities and properties which represent what is happening in real (or right) time in a city, integrating and aggregating information from multiple sources as described above. Context information is usually harmonised as per the rules dictated by the FIWARE schemas (FIWARE Data Models). The Context brokering layer enables the creation of multiple and related vertical applications portable at data level and easily replicable in multiple cities. The context brokering layer typically exposes the last value of each data item. However, there is also a short term historical database which allows applications to make use of historical time series for the different properties. This layer also provide plugins which offer the capability to automatically generate long term historical data and populate it to big data stores.

Data processing, Analytics & Visualization layer. It allows processing all the city data so that new information can be derived or useful insights can be obtained. As a result processes can be optimized or better decisions can be taken. Data processing can be performed in real time (using a Complex Event Processing component) or deferred by using long term historical data stored in Big Data systems. Once data has been processed, the platform offers plugins and components for its visualization in a dashboard. Besides, there are graphical tools intended to perform advanced data analyses such as those related to location or business intelligence. Last but not least, some advanced interaction components are offered to deal with 3D representations or augmented reality.

Economy of data layer. This layer incorporates all the components needed to run an economy of data, so that context information from a city is properly published, secured and accounted. It allows data providers to publish, expose and charge for their data, data consumers to acquire data sets and pay for their consumption. As a result a data marketplace is enabled, moving forward from the concept of open data to the economy of data. This layer is powered by the corresponding TM Forum APIs.

How does the reference architecture handle southbound integration? How is integration with legacy systems managed ... (more)

edit flag offensive delete link more

Comments

Thank you for providing the details. This helps me a lot. Hardware requirement is something still not clear from over all solution perspective. I found some details in following links, but it will be great help if there is a standard hardware requirement published by each GE along with some refrence

itsumanagaraj gravatar imageitsumanagaraj ( 2018-01-06 05:06:36 +0100 )edit

Reference like eg: 4 CPU with 8GB RAM and 200GB storage for catering thousand sensors producing metadata of 1KB every 10 minutes, ... I'm giving this as example. Similar might be for visualization where number of portlets and number of concurrent users etc.. for estimating the required HW

itsumanagaraj gravatar imageitsumanagaraj ( 2018-01-06 05:09:59 +0100 )edit

https://ask.fiware.org/question/530/requirements-to-implement-several-enablers/

itsumanagaraj gravatar imageitsumanagaraj ( 2018-01-06 05:10:07 +0100 )edit
Login/Signup to Answer

Question Tools

1 follower

Stats

Asked: 2017-12-26 16:38:56 +0100

Seen: 835 times

Last updated: Jan 02