Understand the Smart City solution architecture and solutions from field sensing to the cloud compute, currently implemented use cases and additional use cases could be built, on the existing system / extending the system.
Understanding available data means such as what APIs are available in the city solutions? Are these good enough for getting the available data? How often is data available? What are the problems with the data .streams (repetitions etc.)? What are the various available fields and meaning of these fields? What Data structure formats (JSON, dates, geoJSON etc.) closely working with city officials, system integrators, solution providers and other data providers?
Solution architecture, Application architecture, Develop adaptors to ingest data into IUDX< which include writing modules to ingest data, push data to IUDX (using REST APIs, streaming protocols (AMQP, MQTT etc.), Containerization of adapters, Develop data-models and applications following the best practices for software development in Agile development methodology.
Test architecture, test design and automation framework for the data ingestion modules, data streams, applications and operations and guide the development and validation teams to implement them.
Deployment of the cloud-based IUDX platform for the city, operations, enables and supports the application development eco-system to create applications to benefit the city management and citizens.

Solution Architect