Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 44 views

    1 Foreword: Terminology

    Uploaded by

    Manikandan K Krishnankutty
    This standard specifies a general Data Layer Reference Architecture for unified and secure data layers within smart city ICT architectures. It defines system characteristics, a conceptual model, a reference model, and architecture views. Key principles for the data layer include effectively handling big data's variety, volume, and velocity; persisting data in real-time and batch; supporting data models, marts, BI, and dashboards; and analytical modeling capabilities. The goal is to prevent data silos and interpretability issues by modeling data as a shared layer across government departments.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    1 Foreword: Terminology

    Uploaded by

    Manikandan K Krishnankutty
    44 views6 pages
    This standard specifies a general Data Layer Reference Architecture for unified and secure data layers within smart city ICT architectures. It defines system characteristics, a conceptual model, a reference model, and architecture views. Key principles for the data layer include effectively handling big data's variety, volume, and velocity; persisting data in real-time and batch; supporting data models, marts, BI, and dashboards; and analytical modeling capabilities. The goal is to prevent data silos and interpretability issues by modeling data as a shared layer across government departments.

    Original Title

    is template.docx

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This standard specifies a general Data Layer Reference Architecture for unified and secure data layers within smart city ICT architectures. It defines system characteristics, a conceptual model, a reference model, and architecture views. Key principles for the data layer include effectively handling big data's variety, volume, and velocity; persisting data in real-time and batch; supporting data models, marts, BI, and dashboards; and analytical modeling capabilities. The goal is to prevent data silos and interpretability issues by modeling data as a shared layer across government departments.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    44 views6 pages

    1 Foreword: Terminology

    Uploaded by

    Manikandan K Krishnankutty
    This standard specifies a general Data Layer Reference Architecture for unified and secure data layers within smart city ICT architectures. It defines system characteristics, a conceptual model, a reference model, and architecture views. Key principles for the data layer include effectively handling big data's variety, volume, and velocity; persisting data in real-time and batch; supporting data models, marts, BI, and dashboards; and analytical modeling capabilities. The goal is to prevent data silos and interpretability issues by modeling data as a shared layer across government departments.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 6

    1 FOREWORD

    2 SCOPE
    This standarddocument specifies a general Data Layer Reference Architecture in terms of
    defining System Characteristics, a Conceptual Model, a Reference Model and Architecture
    Views for Unified and Secure Data Layer within the Smart Cities ICT Architecture

    3 REFERENCES
    The standards given below contain provisions which, through reference in this text, constitute provisions of this
    standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and
    parties to agreements based on this standard are encouraged to investigate the possibility of applying the most
    recent editions of these standards.’

    ISO/IEC 20924 Information technology -- Internet of Things (IoT) -- Vocabulary

    ISO/IEC 30141 - Internet of Things (IoT) – Reference architecture

    IETF RFC4949 - Internet Security Glossary, Version 2

    4 Terminology and Symbols


    4.1 Terminology
    4.1.1 abb
    For the purpose of this standard, the definitions given in ISO/IEC 20924 shall apply, in
    addition to the following:
    1. Access Control - A process by which use of system resources is regulated  according
    to a security policy and is permitted only by authorized entities (users, programs,
    processes, or other systems) according to that policy
    2. Architecture View - Work product expressing the architecture of a system from the
    perspective of specific system concerns
    3. Architecture Viewpoint - Work product establishing the conventions for the
    construction, interpretation and use of architecture views  to frame specific system
    concerns
    4. 5V’s – Variety, Volume, Velocity, Veracity and Variability
    5. ICT - Information and Communication Technologies
    6. IoT - Internet of Things – Interconnection of computing devices embedded in
    everyday objects using the Internet backbone enabling them to send and receive
    data and thereby participate in generating information.
    7. Conceptual Model (CM) - Describing the key concepts characterizing Smart City data
    layer architecture 

    8. Reference Model (RM) - Providing the overall structure of the elements of the
    architecture
    9. CKAN - Comprehensive Knowledge Archive Network - is a web-based open-source
    management system for the storage and distribution of open data.
    9. OCF - Open Connectivity Foundation - is an industry group whose stated mission is to
    develop specification standards, promote a set of interoperability guidelines, and
    provide a certification program for devices involved in the Internet of Things.
    9. Data Lake – A Large repository composed of polyglot data storage systems like
    NoSQL, BigData, Data Warehouse and Transactional Databases; where data
    generated by IOT Sensors, Enterprise systems and Machine Learning applications are
    stored for future use.
    9. NOSQL DB – A class of database storage systems which are based on data storage
    methods like document storage model, columnar storage & object storage model.
    They do offer data retrieval methods which are not structured query language (SQL)
    and hence the name.

    Symbols and Abbreviations 


    1. API - Application Programming Interface
    2. QoS - Quality of Service
    3. SaaS - Software as a Service
    4. PaaS - Platform as a Service

    5 INTRODUCTION
    The vision of cities in India is to use digital technologies to provide integrated services to its
    citizens through free flow of information, and to usher in an era of good governance.
    Designing smart cities ICT architecture is the essential first step in this direction. 
    Cities are complex ecosystems, where government services pertaining to transportation,
    public safety, utilities, healthcare, education, social services, culture, economic development
    and more are provided by a multitude of government organizations. In most cases, such
    organizations operate in silos. To deal with growing expectations from cities, there is a
    realization to embrace a more holistic integrated perspective of cities. The state of
    urbanization in India is characterized by the following trends and patterns:
     Steady growth of urban population 
     Significant growth to come from Tier 2 and Tier 3 cities 
     Deficient urban infrastructure conditions
     By 2020 India’s cities will contribute about 2/3 of the national economy
    rd

     Urban environmental conditions raising sustainability concerns


    The purpose of creating a Unified Framework for Data semantics and Data models is to
    model data as a shared layer across all government departments and thereby avoiding data
    silos and data interpretability issues. On top of the shared data layer, smart cities can create
    a system to implement an integrated citizen profile to help all departments target the right
    citizens for the right services.
    Smart city data sources offer a variety of data to be processed, observation and
    measurement data are usually aggregated and filtered after collection. The data is then
    transferred often over several systems and transformed according to a semantic data
    representation useful for interoperable & interpretable publication.
    Today most of the cities are unable to use data captured from deployed sensors &
    enterprise systems to generate actionable insights due to data silos and data interpretability
    issues. Smart city data lake is a data repository consisting of data composed of 3V’s –
    Variety, Volume and Velocity. 
    Variety : Smart cities have to deal with variety in data due to the fact that even the
    same type of device generates data in heterogeneous formats or records data in
    different units of measurements.
    Volume : Most of the smart city deployments are focussed on deploying cameras
    across the public spaces to enable use cases like surveillance. Volume of data
    generated through these cameras are huge adding to data storage and processing
    costscost.
    Velocity : Most of the real world control applications need actionable insights in a
    real time basis. Velocity of data generated is the key to delivering real time
    operational alerts and insights.
    While IOT deployments are enabling cities to capture relevant data about the cities,
    environment and citizens it is not enough to think of smart cities as a IOT only solution. 
    Smart city ICT architecture clearly shows that the approach to be taken is a system of
    system’s approach and the diversity & complexity involved cuts across all the layers
    namely:  
     Networking Technologies, 
     Sensors and Physical devices,  
     Communication Technologies,  
     Cyber-physical systems, 
     Information Systems, 
     Data Management,    
     Federation & Distribution, 
     Open Data, Analytics, Visualization, Machine learning 
     And many more components
    Smart Cities ICT Architecture depicting various layers which are part of the system :

    Enablers of Smart Cities : Some of the key vectors enabling transition towards smart cities
    are : 
    1. Ubiquitous Internet
    2. Advancement in Technology  & Reduction in cost of sensors
    3. Advancement in low power communication technologies. 
    4. Availability of Cloud scale deployment and Management frameworks / tools.
    Industry predicts an interconnected world of 50 Billion devices, advancement in technology
    has enabled us to create miniaturized form factor devices which can sense the environment
    by consuming the least amount of power. 
    According to UNDP , 3.5 billion people, half of the world’s population, live in cities. By 2050,
    [1]

    the urban population is expected to reach 6.5 billion. While cCities occupy just 3 percent of
    the Earth’s land but account for 60 to 80 percent of energy consumption and 75 percent of
    carbon emissions. Currently around 828 million live in urban slums and the number is rising. 
    It is imperative for India to work on creating sustainable smart cities as UNDP projects 95%
    of the urban expansion to take place in the developing world. 
    Sustainable Development Goals : Below are the list of sustainable development goals,
    which are a universal call to action by United Nations under the aegis of United Nations
    Development Program (UNDP)
    Goal number 11 – Sustainable cities and communities is a goal that aligns well with the
    smart cities mission of India. 
    This standard document is based on widely used enabling technologies that are defined in
    standards from several organizations such as ISO, IEC, ITU, IETF, IEEE, ETSI, 3GPP, W3C, etc.

    6 DATA LAYER - KEY GUIDING PRINCIPLE

    Data Management
     Technology architecture should be effectively designed (e.g. ingestion, data storage,
    cleansing) to handle the variety, volumes and velocity of big data, allowing it to be
    easily understood and retrieved by different users
     Data Layer should persist data in real time and batch
     Should support Data Models, Data Marts and cross functional BI and Dashboards
     Should support persistence of semi and unstructured data and structured data sets
    beyond 1 year in Big Data infrastructure for advanced analytics

    BI Layer
     Should support Enterprise BI, self service capabilities, low cost footprint, open
    source and have connectivity to data in cold & warm storage.
     Should be able to retrieve Analytics and real time dashboarding for most current
    data and data beyond 1 year seamlessly.

    Analytical Modelling Capabilities


     Should deliver all types of advance analytics modelling capabilities
     Common data models would be deployed to prevent unnecessary data
    transformation and overcome application semantic differences. As such, data
    exchanges would use the schemas that codify canonical data models.

    Extensible and Open Platform 


     Data Layer should favour Open Standard and Technology Independent Solutions
     Open architecture that helps rip and replace components easily from an architecture
    feasibility standpoint
     Solution should be horizontally scalable

    Data Standards

    You might also like