Solution Architecture Models — IOT

IoT Architecture

There is not such a unique or standard consensus on the Internet of Things (IoT) architecture which is universally defined. The IoT architecture differs from their functional area and their solutions. However, the IoT architecture technology mainly consists of four major components:

Components of IoT Architecture

• Sensors/Devices
• Gateways and Networks
• Cloud/Management Service Layer
• Application Layer

Stages of IoT Solutions Architecture

There are several layers of IoT built upon the capability and performance of IoT elements that provides the optimal solution to the business enterprises and end-users. The IoT architecture is a fundamental way to design the various elements of IoT, so that it can deliver services over the networks and serve the needs for the future.

Following are the primary stages (layers) of IoT that provides the solution for IoT architecture.

1. Sensors/Actuators: Sensors or Actuators are the devices that are able to emit, accept and process data over the network. These sensors or actuators may be connected either through wired or wireless. This contains GPS, Electrochemical, Gyroscope, RFID, etc. Most of the sensors need connectivity through sensors gateways. The connection of sensors or actuators can be through a Local Area Network (LAN) or Personal Area Network.
2. Gateways and Data Acquisition: As the large numbers of data are produced by this sensors and actuators need the high-speed Gateways and Networks to transfer the data. This network can be of type Local Area Network (LAN such as WiFi, Ethernet, etc.), Wide Area Network (WAN such as GSM, 5G, etc.).
3. Edge IT: Edge in the IoT Architecture is the hardware and software gateways that analyze and pre-process the data before transferring it to the cloud. If the data read from the sensors and gateways are not changed from its previous reading value then it does not transfer over the cloud, this saves the data used.
4. Data center/ Cloud: The Data Center or Cloud comes under the Management Services which process the information through analytics, management of device and security controls. Beside this security controls and device management the cloud transfer the data to the end users application such as Retail, Healthcare, Emergency, Environment, and Energy, etc.

Conceptual solution architecture model

Solution Overview

The proposed conceptual solution architecture is based on a simplified yet holistic approach towards a filing solution that can scale with online filing as well as supporting paper-based processes.

The solution architecture is based on following key guiding principles:

• Promote automation and self-service via Web as the key guiding principle.
• Align with the Business Architecture.
• Receive, Augment, Fulfill, Record
• Create common services that can be leveraged across different business units within the Corporations and Charities Division.
• Allow flexibility and scalability towards future changes as much as possible.
• Integrate with SOS partners in a flexible and open fashion.
• Create a streamlined and lean flow for internal and external filers while allowing for exceptions.
• Integrate with the SOS Revenue system in a loosely coupled fashion.
• Create a robust system of record for filing information and data.
• Allow existing and future partners to integrate with SOS in a flexible fashion.

Solution Objectives

The objectives of the solution are to:

• Improve the overall processing time and quality of services provided by different business units within the Corporations and Charities Division.
• Increase the rate of online filing and customer self-service to reduce overall cost.
• Develop the system in a flexible and scalable fashion to allow long-term viability.
• Provide a consistent and improved processing flow for staff to handle paper filings and exceptions.
• Provide better integration with partners and affiliates by creating an open and standards-based programming interface.
• Provide a system that can be aligned to Lean principles and improve quality of service.
• Reduce staff involvement in application workflows Minimize requests backlog and number of queues
• Expand online capabilities to all feasible services Make documents available online for public consumption
• Reduce amounts of clicks and data reentry required by professional (power/super) users
• Reduce number of delinquencies, administrative dissolutions and reinstatements by delivering a more intuitive entity lifecycle workflow via the UI
• Reduce number of calls to customer support involving generic legal and filing questions

Strategic Alignment

The conceptual architecture creates a system structure based on business services and service orientation. The architecture aligns with the overall customer experience for both paper filing and the online environment. The project is aligned with the overall vision of transitioning to having the online user experience be the primary focus, while providing an integrated and robust filing system. The conceptual architecture is also aligned with providing an auditable and dependable filing system as the foundation. The overall architecture will support REST-based services that align with OCIO standards and vision for a statewide integrated portal.