Single Mobile Platform

enabling government departments to bring public services closer home to citizens through mobiles
Agenda

 Introduction of Single Mobile Platform (SMP)

 SMP high level technical architecture
 As-Is model of our platform
 To-be model for single mobile platform (SMP)
 Tech Stack
 Cloud Infrastructure Requirement
 SMP Security
 Software Development: Approach & Methodology
 Testing Methodology
 Organization chart
 Project Management Framework
 Risk Management Process
 Change Management Framework
 Performance Management
 Training Methodology & Knowledge Management
 Work Plan
 Mobile App Screens
 Introduction of Single Mobile Platform (SMP)

SMP is the process of accessing government services in very simplified manner and
made "mobile first", which is the most common platform available for most users in
West Bengal to access the internet. Any new digital services by West Bengal state
government departments will automatically be integrated with the application, and the
plan is to eventually enable citizens to access all government services through this
single application. The idea of the application is to allow users to install one single
application to use all the services offered by the government, instead of having to
navigate to multiple websites or install multiple applications. The signup process is
pretty simple….
• Users have to first verify their mobile numbers through an OTP, and then set a pin.
Two security questions have to be set up so the user can recover their account in
case the PIN is forgotten.

• Requirement of having to link the application to your Aadhaar number to use it and Enabling Government departments to bring
of course is must. public Services closer to home for citizens through
mobiles
• Users can also login to the service through their accounts on Facebook, Google and
Twitter but to use in detail registration through Aadhar is must. If users register
first, there is an option to link social media accounts after logging in.
 Introduction of single mobile platform (SMP)

• Peer Performance Pressure: The backend will plug into the different departments under various ministries of the state government. This
approach will encourage competition between the various departments to provide a better service to the end user as a result of "peer
performance pressure".

• Language Option: The application will be available in multiple languages like Hindi, Bengali and English. Initially, users have to pick a language
even before signing in or registering in the application, but users can switch languages later, through the settings any time they want.

• APP for All: The application has been designed to serve a wide variety of users. There are services for the young, the old, and for urban or
rural residents. Traders can access the GST network, university students can check which institutions are accredited by the AICTE, young
children can access educational material and pensioners can calculate their gratuity or lodge a grievance. Support for the application is
available through chat, phone and email. There will be an expansive user manual and FAQ available within the app as well.
 Standard set of API’s that can be
In case department replicate for multiple departments.
don’t have API services, OR
Develop required Developing/customization of
services for department services for departments

SMP high level technical architecture

 SMP high level technical architecture

This diagram provides an architectural information for creating a large scale application. A successful application rely on multiple channels such
as web, mobile and a robust communication system like email/SMS/IVRS/USSD. Centrepiece of this architecture is standard set of API’s to
communicate multiple departments. Citizens can access this application from variety of devices. Traffic manager routes the user to nearest data
centre.
1. Services Used In SMP
These services will be consumed to communicate with many departments at a time. These are standard set of services that will be used in
multiple departments with few customization. There will be some other REST services that will work with the department like VAS Services(bulk
SMS, IVR, USSD and missed call), bulk emailing, transactional services, notification service, app recommendation services and payment
processing service.
2. Multiple Departments
Service On-Boarding - Service Enablement of Government Departments/Agencies who have already mobile application for the services .
3. Load Balancer and Traffic management
Traffic manager routes the user to nearest data centre. Load balancer will improve availability and performance. By using a global server load
balancing solution that takes real-time Internet conditions into account rather than only evaluating whether servers are functional, you ensure
that your end users can access your web content with maximum reliability and minimum latency.
4. Content Distribution Network (CDN)
Content can be return through content distribution network so the unchanged content is cached on edge nodes nearest to the users.
5. SMP Application
Single Mobile platform (SMP) that provides services on mobile devices across State Government departments through a centralized platform.
Once deployed centrally the solution shall support integration and mobile enablement of services with marginal effort for on boarding new
Government applications.
 SMP high level technical architecture

6. Data Layer
There are several services in data tier that support the application in different ways. Mongo DB is used to analyse large amount of customer
data and application logs. All the application specific data such as graphics, user profile is stored in one of the three locations. Blob storage,
MySQL database and cache server. Blob Store is designed for large files like images. Other data is stored in MySQL database. The application can
make direct request to MySQL database for data. But for improvement of performance, system can also make the request from cache server, if
the item is not in cache, cache server can retrieve data in cache from MySQL , temporarily for future request.
7. Logging Framework
Like every other component Logging is an integral part of the system, This enables us in the time of crunch to fix any unwanted situations. Since
our system will be working with different components so tracking them all from a centralized locations is also required and so apart from
individual component logging we will have a central logging data store as well which will enable us getting the various degree of logging from all
the components.
Logging API will log into central logs and persistence data storage also will be responsible for writing the logs for individual components. Central
logs will also be used for checking the health of various components by analyzing the logs.
8. Analytic and reporting server
Reporting Architecture will be responsible for generating reports based on business cases. This will be integrated to the main system to access
all the data for reporting through Rest API.
9. Web Application
Web application will be responsive and be compatible with standard form factors on smart phones. Mobile web will have same features
available on native mobile app(Android/iOS).
e-authentication / e-pramaan framework Integration

e-Pramaan based single sign-on e-Pramaan Gateway

Bulk email services integration with SMP

High Level Diagram of bulk email service Internal architecture of email-gateway

Chat Bot Integration with SMP
Chat Bot Integration with SMP (Machine Learning)
AS-IS Model of our platform
To-be Model for SMP Platform
TECH stack

Server Side Technology Client Side Technology Mobile App Technology

Node JS (JavaScript Framework) angular js 2.0 for web Java
Express Js (JavaScript Framework) HTML 5 XML
MySQL as a central database LESS preprocessor Objective C
Mongo DB for data logging Bootstrap Swift
Typescript ECMA Script C#
Cloud infra requirement
SMP Security

Cross Site Scripting(XSS)

• Input Validation on client & server side
• HTML encoding done for special chars
• HTML Safe enabled in web app
• HTML X-XSS protection header
• Enable content security policy

Cross Site Request Forgery(XCRF)

• Date update only in PUT, POST, DELETE REST API’s
• Supported browser has strong single domain policy
• Don’t allow loading in i-frame
• HTTP strict transfer security enabled

API security • Cookie Security

• Transport security – HTTPS, TLS 1.2 • All tokens are encrypted before sending out
• Hash & Salt password storage • Hash Based One time password
• Token based API Authentication • Input data restriction and validation to protect server data
• Client Authentication • Admin control to lock users, invalidate sessions
Software development: Approach & Methodology (Agile Scrum)
Software development: Approach & Methodology

Major Activities
• Team Identification - Formation of Project team and Development team
Key Deliverables
• Formation of Solution and Project Team with definite roles and responsibilities
• Overall Implementation Plan
• Procurement Plan
• Definition of Vision Statement, Business and Technology Objectives
• Formation of Solution and Project Team with definite roles and responsibilities
• Master Project Plan
• Overall Implementation Strategy
Software development: Approach & Methodology

Major Activities
• Create a detailed work plan
• Describe the approach to be used to in terms of deliverable formats, templates, and related documentation strategies.
• Define & communicate the project team, organization structure, operating norms, and specific roles and responsibilities to
support the project through its entire lifecycle.
• Set-up the entire project infrastructures for the team.
• Design and create the technical environment on the development system
Key Deliverable
• Project Plan
• Project Schedule
Software development: Approach & Methodology

Major Activities
• Preparation of As-Is
• Preparation of To-Be
• Gap Analysis based on the best practices

Key Deliverables
• Fit-Gap Analysis Document
• Training Plan
Software development: Approach & Methodology

Major Activities
• Creation of Technical specification Documents
• Building of Unit test cases
• Creation of bi-directional interfaces
Key Deliverables
• Fit Gap Analysis Document
• Project Schedule
• Functional Specifications
• Technical Specifications
• Test cases \ Plans
Software development: Approach & Methodology

Major Activities
• Development of Interfaces and custom reports.
• Creation of Unit Test plans
• The configuration/customization of the requirements
• Provide help in the creation of the configuration/test data
Key Deliverables
• Unit test cases with results
• User Acceptance of the Pilot Upgrade.
• Sign off of UAT
Software development: Approach & Methodology

Major Activities:
• Coordinating with the Technical Team in adhering to Go-Live Plan
• Creating Contingency Plan
• Provide support to technical team in detecting and fixing bugs in the development.
• Coordinate with technical team to ensure stabilization of the new modules
Key Deliverables:
• Developed System with all the customizations.
• User Acceptance of the Tested Production System
Software development: Approach & Methodology

Major Deliverables
• To provide support and maintenance for the Developed System taking into account all SLA parameters for the agreed time
period.
• Implementation of the all the CRs agreed upon.

Key Deliverables
• Seamless service of the Application
• Application with the modifications
Testing Methodology
Organization Chart
Program management framework

PROGRAM MANAGEMENT FRAMEWORK

Risk Management Process

Risk
Risk Identified at
Identification
Proposal Stage
Check List
Identify Project Risks

Brainstorm with
Past Project Data
Stakeholders

Evaluate, Prioritize &

Quantify Risks
Probability of & FMEA Tools
Impact of Risk

Develop Mitigation &

Contingency Plans

Look Ahead
Meetings
Project
Monitoring Continuously Monitor
Review & Reassess Risks
Milestone
Reviews
 Risk Management Process Explained

• Identify Project Risks using • Develop Mitigation Plan - Actions to be taken to minimize occurrence of

Risk Identification checklist risk.

Past project data • Develop Contingency plan - Actions to be taken when risk becomes a

Risk identified at proposal stage reality

Discussions/brainstorming sessions with stakeholders • Mitigation & Contingency plans are mandatory for quantified as 27
(probability * impact).
• Evaluate risk based on the probability and impact such as
cost, Schedule and Technical aspects - Usage of FMEA tool is • Communicate Risks to stakeholders (Customers, affected groups)

recommended Increased efficiency in pay bill generation. • Continuously monitor & re-assess risks

• Probability of risk is quantified as High (9), Medium (3) and Project Monitoring Reviews

Low (1). Impact is quantified as High (9), Medium (3) and Milestone reviews
Low(1). Look Ahead Meetings
Change Management framework
Performance Management

Strategic MIS Plan

Target Setting Monitor
Refine Corporate
Determine Key
Determine Key Vision &
Measures of
Value Drivers Strategic
Success
Objectives

Department Value
Develop Action Plans
Assessment Enablers

Top Management Standardized

support Processes
Set Targets for Review Performance
Key Measures of Integrated IT with Executive
Accountability Architecture Management

App based tracking Data Structures &

and data collection Controls
Approach to Cascade
Monitor Key Measures
Targets to Lower Level
of Business Performance
Metrics/ Organization
Operate
Allocate
Review, Challenge
Develop Plans to Resources (all
& Finalize Plans &
Achieve Targets categories) to
Forecasts
Achieve Plans
A meaningful drill-down structure and reporting dimensionality is key to
performance monitoring

• Dimensional design provides Level I dimensions Level II dimensions Level III dimensions
consistency of information at Stage of Application
each level of the organization
Certificate
“gets everyone on the same Form Filling
page” Regions S Curve
Government approvals
• It allows flexible starting Mobile App City
points depending on how you PM Compliance
want to view performance App download
Status
• Ideally primary dimensions
should default to Payment Transactions Insurance
organizational accountability

• Dimensions can be toggled for

different slices of the same
level of data
Training Methodology and knowledge management

Key User Training:

 The Application overview and Key concepts
 Details of the modules being implemented in terms of functional coverage and integration with other modules
 Master Data
 Key business transactions
 Integration with other modules
End User Training:
 Familiarity with input screens and output reports
 Use of Applications in relation to work practices
Senior Management Training:
This training would encompass all major modules to be implemented which would be of use / interest to Senior Management
Key Resource Pool Training:
 Interested Department Official would be trained to look after the Application, Database and Network as a part of sustenance of the
Project when the contract with the Vendor ends
 Key Resources identified may be trained in Vendors Facility to have a feel of LIVE project development
 Training Methodology and knowledge management

 Role based training to the officers of the Office

 Training and capacity building shall be an on-going exercise.
 We shall prepare a training plan based on the list of officers during SRS and MSA sign off stage.
 On the basis of the requirements, detailed training plan shall be submitted at least 30 days prior to the start of the
training schedule.
 Detailed training plan is subject to approval from The Client.
 Detailed Training plan shall contain the schedule , training period , content outline.
 Training shall be conducted in batches with similar roles.
 Infrastructure required for the training shall be arranged by The Client. Infrastructure requirements shall be done by
selected bidder in the detailed training plan.
 Around 500 officers may be trained during the tenure of the contract.
 For each service enablement , training to be provided to selected officers of the government department / other service
provider onboarding with the single mobile platform
 Upon changes in the platform, solution or changes in the officers.
 Periodical trainings shall be conducted by the selected bidder as and when required.
 Unsatisfied participants shall be provided trainings again till they are satisfied.
Work plan (In Months)

Project Implementation Plan

# Work Work Breakdown M1 M2 M3 M4 M5 M6 M7 M8 Y1 Y2 Y3

Communication Management Plan

Resource Procurement and Management Plan
Application Development
1 Scope Development
Project Management
Scheduling
Document Change Control Processes
Evaluate Existing Document All Existing Users and User Roles
Reporting(End User/Management/System Administrative/Technical)
3rd Party interconnects
Evaluate Legacy Application(3rd Party Interconnects/Evaluate
2 Business Requirements Legacy Data)
Define Workflow
Define Specific UI Requirements
Define Specific Technology Requirements
Requirements Documentation
Functional Specifications (Process Models/User Interface/Database
Model)
3 Application Architecture Technical Specifications (Platform Specifications/Development
Language Specifications)
Client Signoff on requirement after demo on UI
 Project timeline

A Project Implementation Plan

A# Work Work Breakdown M1 M2 M3 M4 M5 M6 M7 M8 Y1 Y2 Y3
Create Code Design Document(Define Features
a Web
Included in Each Release)
Implement Code Control System
Application
4 Setup Development Environment
and Backend
UI Designing
Development
UX Development
Code Development (Release Testing/Bug Fixes)
Application Development
Create Code Design Document(Define Features
Included in Each Release)
Android /iOS Implement Code Control System
Application Setup Development Environment
Development UI Designing
UX Development
Code Development (Release Testing/Bug Fixes)
Test Environment Setup
Test Plan
Unit Testing
5 Application Testing
System Performance Testing
UAT
Results Reporting
6 Application Deployment Production Data Migration
Pilot of services &
7 Audit/Certification API Integration of TWO Pilot service
8 Training & Go Live Training & Go-Live
9 O&M Operation and Maintenance