Proposal For

Technology
Proposed Refreshment
Digi Gov Implementation forof
Existing
National Tsunami System-
Disaster Management Agency
INCOIS

April 2017
Ver 1.0

Deccan Park, Madhapur Road, Cyberabad,

Hyderabad, Telangana 500081
www.tcs.com
Confidential Page 1of 29
 CONFIDENTIALITY STATEMENT
This document contains information that is proprietary and
confidential to TATA Consultancy Services (TCS), which shall not
be disclosed outside, transmitted, or duplicated, used in whole or
in part for any purpose other than as intended. Any use or
disclosure in whole or in part of this information without express
written permission of TATA Consultancy Services is prohibited.
Any other company and product names mentioned are used for
identification purposes only, and may be trademarks of their
respective owners.

Copyright 2008, TATA Consultancy Services (TCS).

TATA Code of Conduct

We, in our dealings, are self-regulated by a code of conduct as enshrined

in the Tata Code of Conduct. We request your support in helping us
adhere to the code in letter and spirit. We request that any violation or
potential violation of the code by any person be promptly brought to the
notice of the Local Ethics Counselor or the Principal Ethics Counselor or
the CEO of Tata Consultancy Services Limited. All communication received
in this regard will be treated and kept as confidential.

Confidential Page 2of 29

PF3020

Document Release Note

Notice No.:

Customer: INCOIS

Project: Proposal For Technology Refreshment of Existing Tsunami-INCOIS

Document details
Name Version no. Description

Proposal For Technology Refreshment of Existing Version 1.0 This document depicts the proposal to
Tsunami-INCOIS migrate TEWS system from IBMs AIX to
X86 architecture .

Confidential Page 3of 29

 CONTENTS

1. EXECUTIVE SUMMARY............................................................................5
2. OUR UNDERSTANDING OF REQUIREMENTS..............................................6
2.1 Scope 6
2.2 Out of Scope 7
2.3 General Assumptions 7
2.4 Technical 8
2.5 Environment and Infrastructure 8
2.6 Overview of Project 8
2.6.1 Existing TEWS Architecture.............................................................................8
2.6.2 TEWS existing Data Centre Architecture Diagram.........................................10
3. PROPOSED SYSTEM ARCHITECTURE......................................................11
3.1 Proposed Servers 11
3.2 Benefits and Advantages of Proposed Solution 12
3.3 Technology/Tools Proposed 13
3.4 Applications/Sub-Systems which needs to be migrated to new hardware
13
3.5 Existing and proposed third party software details 14
3.6 Proposed Hardware Details for Tsunami Website Application Migration.
15
3.7 Disaster Recovery Plan DR setup 15
3.8 Proposed DR Architecture 16
4. MIGRATION & SOFTWARE DEVELOPMENT..............................................17
4.1 Migration 17
4.1.1 Product and Operating System installations.................................................17
4.1.2 System configuration....................................................................................18
4.1.3 TEWS Database & application installation....................................................18
4.1.4 Data migration.............................................................................................. 18
4.1.5 Testing.......................................................................................................... 18
4.2 Software Development 19
5. DELIVERABLES, MILESTONES, ROLES & RESPONSIBILITIES.....................20
5.1 Deliverables and Timeframes 20
5.2 Major Milestones 21
5.3 Roles and Responsibility Matrix 21
5.3.1 Project Organization Structure......................................................................21
5.3.2 Roles and Responsibility matrix....................................................................23
5.3.3 Training of INCOIS Personnel.........................................................................24
6. WARRANTY AND MAINTENANCE SUPPORT.............................................25
6.1 Stabilisation Phase-Warranty Support & Maintance25
6.2 Approach to Maintenance Support 26
6.2.1 Acceptance Criteria.......................................................................................27
7. COMMERCIALS....................................................................................28
7.1 Pricing 28
CONCLUSION...............................................................................................29

Confidential Page 4of 29

 1. Executive Summary
TCS has designed and developed Tsunami Early Warning System (TEWS) with the state-of
the art technology for detecting tsunamis and to disseminate the alerts through emails,
SMS, Fax, Website etc. TCS provided the technical services during warranty &
maintenance phase for last seven years.

INCOIS intended for technology refreshment of tsunami system including integration and
migration of tsunami application software and the task was entrusted to TCS, as TCS, as
an initial implementing agency, has got technical edge over other competitors,

TCS Association with INCOIS

TCS Association with INCOIS
TCS is one of the Preferred Partners in realizing INCOIS dream of setting up of a world
class system. It has already designed and operationalized the website and related
applications for Tsunami Early warning System. The same is rated as one of the most
modern and best Tsunami Warning Centres in the world. TCS is also partnering INCOIS in
their endeavour to create and maintain Integrated Seismic & GPS networks and 3D VAS
application.TCS looks forward to develop and maintain long association with INCOIS and
partner INCOIS in realizing its aims and objectives.

TCS Value Proposition

Functional and Technical knowledge of Tsunami early warning system application,

being an incumbent partner.
Working with INCOIS team and organization in various scientific projects of
national repute, for past eight (8) years.
Availability of best skill pool in GIS and related areas. Pioneering applications have
been operationalized by this team.
Availability of right skill sets and resources and over Over 2,30,000 Consultants.
TCSs vast experience in G2C, G2G , G2B B2E, E2E, B2C, B2B solutions.
Alliances with Global leaders in Technology.
Global ReachPresence in 52 Countries, Over 42 Years of Software Consultancy.
Experience.
Worlds First Company to be assessed at Enterprise wide CMMI & PCMM level
5.
TCS Products and Tools enable customers to have a quick to market advantage.

Confidential Page 5of 29

 2. Our Understanding of Requirements
2.1 Scope
The application software that is being used presently at tsunami data centre was
originally got developed and implemented by TCS during the year 2007-2008 where
INCOIS had provided required domain knowledge and TCS had developed the
application software . The applications related to tsunami data centre was actually
hosted in IBM P590 AIX system in high availability mode during that time.
The application had undergone various changes/modifications over the years to
incorporate developments and improvements in the tsunami system including
improvisation of tsunami modelling and development of upgraded version of decision
support system.

Currently few of these modules/subsystems are hosted in HP blade servers and other
Desktop machines.

The current scope of work includes integrating the various sub-systems including
desktop applications and newly developed in-house-DSS and migrate the application
on to the new hardware solution.

As understood from the RFP document from INCOIS, scope of this engagement includes
detailed study and analysis of the existing TEWS to design suitable solution architecture
based on INCOIS requirements, implementation, migration of data and application,
enhancements to the existing system and delivery of the system.

The major activities are mentioned here:

Studying the existing Tsunami data centre setup, existing hardware & network
design.
Studying of existing electrical system, precision air controlling systems, access
control systems, UPS systems.
System analysis & Re-design of the tsunami data centre setup including network,
electrical system, precision air controlling systems, access control systems, UPS
systems based on current INCOIS requirements as a part of technology
refreshment.
Preparation of the tender document with Generic specifications for the proposed
Hardware, Software, Networking Components and any other related components.
Studying the feasibility & integration of existing INCOIS in-house developed
desktop applications.
Undertaking enhancements in the existing TEWS as per INCOIS requirement.

Porting of application to new hardware, migration of existing data and
Commissioning of new TEWS.
Implementation of DR site.
Providing Warranty support for a period of one year, from the date of acceptance.

Confidential Page 6of 29

 2.2 Out of Scope
Additional ongoing production support and maintenance of the system is not included in
the scope of this proposal. Further, procurement of all other Hardware and software
systems from other vendors is excluded from the scope of the project. Content building is
for English only and other Indian languages are not included in the scope. However, TCS
is willing to offer services in these areas at an additional cost mutually agreed by both
INCOIS and TCS.

2.3 General Assumptions

The estimation and schedule in this proposal are based on the information
provided in RFP and further discussions through personal interactions
teleconferencing and responses through email. The estimations would be
validated for differences during the Requirements Analysis phase.
INCOIS would buy licenses for all the required third party tools.
Hardware and Software Platform and their release versions will remain unchanged
during the life cycle of this assignment. In case of any change in the Hardware or
Software platform, an impact analysis of the same will be carried out by TCS and
the appropriate adjustments to the effort, schedule and cost will be made.
.
TCS would be provided access to all relevant systems documentation that would
assist in carrying out the assignment.
Reviews and Signoffs by INCOIS will be provided within mutually agreed
timeframe.
Any change request(s) raised during the project, will directly impact cost, effort
and schedules of the project. Revised estimates for the same will be provided to
INCOIS for sign-off. The changes will be taken up following sign-off from INCOIS.
INCOIS would provide contact points for all external interfaces, if any, to work
with TCS design and development team
INCOIS will ensure that project team(s)/Vendor(s) other than TCS team adhere to
the project schedule.
INCOIS will co-ordinate the interaction between TCS team, other vendor(s) and
business/users for the design and development phase of the project
INCOIS will co-ordinate all the interactions with their administrators for setting up
the onsite environments and deploying the application and for providing support
on the external interfaces to the application
Technical and functional experts on the existing system and related systems
would be available for clarifications, review and acceptance of TCS deliverables.
INCOIS would provide technical and functional experts to work with TCS
design/development team for clarification of any business-related
queries/requirements.
Changes in the design or code after "sign off will follow the change management
procedure.
INCOIS will provide the system test data, System test plan, Acceptance criteria
and acceptance test plan.
Testing the external interfaces will be the responsibility of INCOIS.
Resolution of new bugs/issues raised due to the integration testing that are
attributed outside the scope items will be INCOIS responsibility. Any cost arising
out of idle time will be borne by INCOIS. Notification will be given to the INCOISs
management about the idle time via the Change Management procedure.
INCOIS will be responsible for Acceptance Testing and acceptance of the
deliverable made by the TCS team. INCOIS will adequately staff its review

Confidential Page 7of 29

 2.4 Technical
The Integration services other than those mentioned in this proposal under the
functional requirements section are out of scope for the proposed solution.
The basic application framework, common components code will remain same for
both the DR and Primary models of hosting. Also as much as possible the
application code will be reused in both the models. But there will be some
differences in the design and code depending on the requirements and will be
evaluated by TCS in the requirements study and design phase. The DR site will be
treated as a scaled down version of the production site without the model
analysis software from the primary site.
The existing database will be modified to suit the requirements coming out of the
requirements phase.

2.5 Environment and Infrastructure

The Development/System Test/Production/Training environment setup at Onsite
will be done by INCOIS
Server/Network Administration support will be given to the onsite team by INCOIS
The staging and production environment will be ready before testing and
implementation
Licenses for software to be used both onsite and offshore will be provided by
INCOIS. For offshore development, TCS will utilize its own licenses for certain
software that is available with it for this project and will inform INCOIS of the
available software at the beginning of the Design phase.
INCOIS will make available access to all the necessary mainline applications.
INCOIS will provide facilities to the onsite TCS staff to enable them to carry out
their responsibilities by providing adequate computer and office resources. This
should include telephone, email, fax, office stationary etc if there is any need for
the usage of the same after due verification by INCOIS project manager.

2.6 Overview of Project

2.6.1 Existing TEWS Architecture

TEWS is equipped with a data centre housing 2 nos. of P590 server racks and one no of
IBM DS4700 storage. The existing P590 compute racks has Application server, Web
server, FTP Server, Central DB & Staging DB configured in HACMP cluster, Sea level
Acquisition server, File server, back server, modelling server, DNS server, STB COMM
server & STB data server.
The schematic diagram of P590 servers at TEWS and software details is as follows.

Confidential Page 8of 29

2.6.2 TEWS existing Data Centre Architecture Diagram

Confidential Page 9of 29

 3. Proposed System Architecture
TCS has carried out detailed analysis of the current system of INCOIS & considering
performance & scalability proposes the solution based on x86 architecture, which has an
technical advantage of ease in configuration, handling and economical in maintaining
the system. The proposed solution is as given below:

3.1 Proposed Servers

Database Servers Intel x86 based Blade servers
Core Application & Web Servers Virtual Machine running on Intel x86 servers

The overall deployment architecture proposed by TCS is as below

Proposed solution has been designed considering following

Resilience The proposed architecture is resilient means there are no single point of
failure for any of the solution. The solution is designed to ensure that the redundancy is
built at all the level including power supply, network adapter, HBA etc. In case of virtual
servers, it is ensured that two virtual server part of one solution are hosted on different
physical servers.

Confidential Page 10of 29

Availability - High availability is been provided for all Database servers installed on two
physically x86 Server by using Red Hat HA-Add On. Web server & application servers are
install in virtualization so its provide additional high availability to web server &
application server in addition to there inbuilt high availability functions.

Scalability- Virtualization provide scalability in terms of memory, CPU & virtual machine
can be move between physical servers if required without any downtime.

Performance The TCS solution is designed, keeping performance as key objective.

Each server is planned in terms of CPU and memory utilization. The latest highest
available clock CPU with multiple cores to enhance throughput has been considered

Security - Security has been considered for the deployment of the central infrastructure
keeping in mind the application and Data security based on the access required.

Standardized Processes and Methodologies Maintenance and administration of IT

Infrastructure should follow standardized processes as agreed between the TCS and
INCOIS.

3.2 Benefits and Advantages of Proposed Solution

1) High Availability: Virtualization technology provide additional high

availability layer to the system
2) Highly Flexible: The offered solution includes virtualization technology for
maximum flexibility of resources.
3) After successfully migration, INCOIS can decommission existing IBM P590
& save AMS cost or they can use free resources or other application or
projects
4) Maintenance & operational cost will reduce.
5) Save footprint All new x86 server can be mount in single rack will save
space.
6) Uninterrupted Operation Using virtualization functionality, all
maintenance & upgrade operation can be done without downtime.
7) High Flexible The offered solution includes virtualization technology for
maximum flexibility of using resources.
8) Resource Planning New system design considering all available resource
with proper planning.
9) Updated Application New system install with current & updated version
of application
10) Automatic Patching All Red Hat servers register with RHN for
automatic updating of OS & security patch (additional Red Hat satellite
server required).

Confidential Page 11of 29

 3.3 Technology/Tools Proposed
From our understanding of the requirements, TCS feels that the following service areas
needed to be refreshed with state of the art technological systems for smooth
functioning of INCOIS TEWS :

Extraction, Transformation and Loading of Data acquired from primary

subsystems as well as the international TG& BPR data received through internet.
Data warehousing of the data acquired in step 1.
Staging area for this data in step 2 along with graphical analysis and alert
mechanisms required for any abnormalities in the data.
GIS for staging area.
Interface to modelling data
Decision support system (DSS).
Portal for TEWS .
WebGIS
Integration of SMS, FAX, GTS,CAP,EBC services with redundancy & load
balancing
Video wall and Video conferencing Data to be integrated and displayed from all
subsystems, individual terminals and FTP sites.
Data Dissemination - through various communication channels after relevant
approvals.

The Present-day Tsunami Early Warning System consists of the following Sub-Systems.

1. Seismic Sub-System
2. Sea-Level Sub-System
a. Tsunami BPR Sub-System
b. Tide Guage Sub-System
3. Tsunami Modelling Sub-System
4. Decision Support System
5. Dissemination Sub-System.

3.4 Applications/Sub-Systems which needs to be

migrated to new hardware
The following are the Applications/Syb-Sytems planned for migration.

S.No Application /Sub System Presently Hosted at

NAQ Server
Seismic National data (172.16.3.240,172.16.3.241)
1 acquisition
Seismic International data
2 acquisition
Seiscomp3 (172.16.3.15 &
172.16.3.44)
Hydra(172.16.3.243 &
3 Seiscomp3 , Hydra Systems 172.16.3.244)
3 Tsunami BPR National data 172.16.4.32

Confidential Page 12of 29

 acquisition Systems
Tsunami BPR International
4 data acquisition 172.16.4.32,NSS,NSS1,NSS2
TideGuage-National(Via 172.30.2.187,172.16.1.112,NSS1,N
5 INSAT and GPS) SS2
6 TideGuage International 172.16.4.32,NSS1,NSS2
Decision Support System
Application(in-house 172.16.3.6(Primary),172.16.3.34(St
7 developed) and-by)
Dissemination Sub-System
Applications (SMS Regpoint
application, FAX 172.16.3.38,172.16.3.29, SMS
8 applications) Regpoint - 172.16.3.31
Tsunami Website
9 application AIX P590
Tsunami Central & Staging
10 Database AIX P590
Tsunami Modelling sub-
11 System INCOIS-HPC,FT Server
12 Spatial Database AIX P590
ArcIMS & Arc GIS
13 Applications AIX P590
14 WebDSS AIXP590
SIMS and RIMS Model
Server , GIS central data
15 server with version control 172.16.3.10
Systems Health Monitoring
Servers and Hourly
16 monitoring servers 172.16.3.20

3.5 Existing and proposed third party software

details

The following are the existing and proposed third party software needed for new setup.

Server Existing software Recommended

Web Server IBM Http Server for AIX IBM HTTP Server for RHEL
or any open source
webserver like Apache
Webserver
Application Server IBM Websphere ND version for IBM WebSphere ND version
6.1 AIX 6.1 for RHEL or any open
source Application Server
software like JBOSS, etc
GIS Server ArcIMS 9.2 ArcGIS Server 10 or above
Database Server IBM DB2 Version 7.2 IBM DB2 Version 9.2 or
above should support for
RHEL/UNIX
AIX HACMP RHELC OS cluster software

Confidential Page 13of 29

Clustering Software
Backup Software TSM HP Data protector
Operating System AIX RHEL 7/HP-Unix &
Windows 2012
Virtualization IBM LPAR VM ware/ RHEL VM

3.6 Proposed Hardware Details for Tsunami

Website Application Migration.
Qty For
S.No Description DC
1 50 TB Usaable Storage 1
2 SAN Switches 2
Tap Library & backup
3 software 1
4 X 86 DB Servers 4
X 86 application Servers
5 (VM Box) 2
6 DATA migration tools
7 Router with min 8 GE ports 2
Network Switch with min 48
8 ports 2
9 Application Load balancer 2
Firewall min 500 concurrent
10 users 2
11 Fiber cables & cables 1 lot

The detailed Hardware BOM needed for migration of existing in-house desktop
applications & DSS will be submitted during solution design phase after detail discussion
with INCOIS.

3.7 Disaster Recovery Plan DR setup

The goal of any disaster protection planning is to protect the most business-critical
processes and minimize unplanned downtime of operational system. Keep in mind that
all planning for any type of a disaster-tolerant solution is always subject to balancing the
solution versus the downtime versus the cost.
For achieving Business Continuity, there is a need of setting up of Disaster Recovery Site,
which will be the replica of critical components of the above topology without
redundancy. It is now widely recognized that Business continuity planning and disaster
recovery planning under INCOIS are vital activities. However, the creation of (and
maintenance of) a sound business continuity and disaster recovery plan is a complex
undertaking, involving a series of steps.
Some principles have been kept in mind while preparing a comprehensive disaster
recovery plan for the proposed INCOIS system is given below:
Design of Preventive Measures, with the following in view:
Quick restore of normal operations
Isolation of strategic resources
Interconnection technology, so that operations can be quickly and painlessly be
transferred to an alternate site
Cost factors
Redundancy

Confidential Page 14of 29

 Availability of an alternate site
Availability of appropriate hardware spares
Availability of system software recovery mechanisms
Availability of system and applications data backups
Availability of Uninterrupted Power Supplies and Generators at sites
Redundancy in communication lines
With an understanding that INCOIS plans to host the Disaster Recovery site at one of
their own Data centres in Pune or at any other MoES locations, the architecture is
proposed. However, as an alternative, INCOIS also may consider hosting DR on a private
cloud to reduce CAPEX and to minimise on OPEX. Based on the interest expressed by
INCOIS, a detailed Cloud based Solution for hosting DR on cloud shall be provided by
TCS.

3.8 Proposed DR Architecture

Following responses have been considered:

Scenario 1
The DR site of INCOIS is typically situated in a different geographical location, located at
a considerable distance from the main production site. Consider a scenario when a
disaster happens on the primary site, in that case we can connect the DR site to work as
the production site, and can restore the primary site in that time. The data backup will

Confidential Page 15of 29

not be a problem as we are proposing to keep the asynchronised data replication at the
DR site.

Scenario 2
Consider a scenario when the disaster happens on the DR site, in this case we have the
Primary site already available and working, we can take a fresh backup of all the primary
site data and can set a DR site afresh without loosing the services.

WAN Connectivity

Application Server Incremental Application Server

change

Database Server Data Replication Database Server

Confidential Page 16of 29

 4. Migration & Software Development

4.1 Migration
The application software that is being used presently at tsunami data centre was
originally got developed and implemented by TCS during the year 2007-2008 where
INCOIS had provided required domain knowledge and TCS had developed the application
software . The applications related to tsunami data centre was actually hosted in IBM
P590 AIX system in high availability mode during that time.

The application had undergone various changes/modifications over the years to

incorporate developments and improvements in the tsunami system including
improvisation of tsunami modelling and development of upgraded version of decision
support system.

Currently few of these modules/subsystems are hosted in HP blade servers and other
Desktop machines.

The current scope of work includes migrating the AIX servers to LINUX clusters
,integrating the various sub-systems including desktop applications and newly developed
in-house-DSS and migrate the application on to the new hardware solution.

The Applications functionality features and usage will remain mostly unchanged. The
proposed migration to Linux servers is expected to result in:

Optimizing the application performance.

Reducing the maintenance cost.
Reducing the maintenance effort.
Removing dependency on specific hardware platform
Leveraging existing linux expertise available within the organization

The following tasks are under the scope for the proposed migration:

Hardware readiness
Configuration of target server to match with AIX(source) servers
Backup of the source data & file systems
Restoration of the data & file systems
Software installation
Parameter tuning to meet the application's requirements with respect to Linux
server
System testing
User acceptance testing
Go-live
Post live support for the migrated system
Execution of AMC after post live support

The scope of work broadly will cater to the below tasks:

Confidential Page 17of 29

 4.1.1 Product and Operating System installations
Installation and configuration of target hardware.
Installation of Operating system under cluster and kernel tuning.

4.1.2 System configuration

Target Linux server to be configured to match the source (AIX) server in terms of kernel
parameters, OS patch level, security compliance ..etc to ensure that the application
works fine as earlier without any issue. To achieve this, both the AIX and linux OS,
Parameters, patches, packages, built-in tools ..etc will be compared and values will be
tuned accordingly.

4.1.3 TEWS Database & application installation

After installation of OS and application binaries, Application team will deploy INCOIS
customized code / application on newly configured linux server.
In the similar way, newly configured database server(linux) will be installed and
configured with IBMs DB2 database in line with source (AIX) DB2. Values for all the
parameters of the database will be reviewed and tuned to match with source.

4.1.4 Data migration

After installing, configuring and tuning the application software, the data migration
activity will be carried out to ensure that data from source-AIX server will be ported to
proposed linux server. As a part of data migration, user data, application data will be
migrated from old system to new system using techniques like backup/restoration,
export/import..etc.

4.1.5 Testing
Testing include following activities
System testing
Application testing
Performance testing
UNIX team & client will test new system (hardware / OS) & end to end connectivity with
all components. .
Testing team will test end to end application functionality & data integrity. After the new
system is set to operational in production, data will be captured for validation from
performance perspective.

Confidential Page 18of 29

 4.2 Software Development
TCS proposes to use its time-tested onsite-offsite model for the development of
application enhancements identified by INCOIS. This model is best described in the
following diagram

Confidential Page 19of 29

 5. Deliverables, Milestones, Roles &
Responsibilities
5.1 Deliverables and Timeframes
TCS will make available to INCOIS the following deliverables within the time frame
defined in the tentative Project Plan:

S. No. Deliverables Timeline

1 System Architecture T+1 months

Hardware Plan
CR Development Plan
Communication Plan
Technical Support Facilities Plan
Migration & Integration Plan
Project Plan
Warranty& Operational maintenance Plan
2 Tender Documents T+2 months

3 Revised System Requirement Specification (SRS)T+3 Months

Document
4 Revised High level design document (HLD)/ Low level
design document (LLD)/
5 Final System Integration Document T+5 Months
ATP Document

6 Migration of TSUNAMI website and other applications to

proposed Hardware

7 Implementation of CRs

8 Test Plans & Test Reports

Acceptance Document
9 Unit/System/Integration Test Plans & Test Reports
Application code Final Version
Final Design Documents
User Acceptance Document
10 Integration Report T+6 months
11 Acceptance Documents
User Manuals
User Training
12 Completion of one year support post migration T+18 Months

Confidential Page 20of 29

 5.2 Major Milestones
The following are the milestones:

Arriving at System Architecture

Tender document with generic technical specifications
Project plan submission and approval
Revised System Requirement Specification(SRS) preparation, QA and approval
Revised High-level Design (HLD/Preliminary) and Low Level Design
(LLD/Elaborated) documents preparation, QA and approval
Data Migration
Porting of applications to new hardware
System Integration
Development of CR Application software Beta version
Preparation of Test plans and test reports
Development of CR Application software Final version
Completion of User Training
Completion of User Acceptance

5.3 Roles and Responsibility Matrix

5.3.1 Project Organization Structure

TCS proposes the project teams organization structure as below.

INCOIS Team:
TCS proposes that INCOIS should formulate a project team as under:
INCOIS Sponsor for the Project
Project Manager
Project Champions - one from each participating department
Change Management Champion
Design Lead
Release Lead
Technical Lead
In addition to the above, INCOIS can identify suitable representatives for the following
teams to ensure that required information and details are made available to TCS team as
and when required.
Project Management Office (PMO)
Business functional / technical / testing /logistics team from participating
departments
TCS Team:
TCS team will have the following associates working in the team:
Project Manager
Module Leaders
Testers
System Administrator
System Architect
Database Administrator

Confidential Page 21of 29

 Network and Infrastructure Administration and Experts
Web designer / Implementation / Deployment team

S. No TCS Team INCOIS Team

Role Responsibilities Role Responsibilities

1 Project Manager Overall project Project Approval of
planning, project Manager project
monitoring, Status Scientist in deliverables
reporting, Delivery, charge (s)
Configuration
Management ,
Billing
2 Module Leaders Change Project Leader Clarification of
Requirements Point of changes in
Analysis, Design, Contact for requirements,
Allocation of day to day Providing data
module wise tasks issues formats, real-
to team members, time data,
support for UAT, providing
Application metadata for
deployment , seismic, tide
updation of user gauge & BPR
manuals stations
verification of
individual
functionalities,
UAT
3 Testers Preparation of test
cases and carrying
out Integration
Testing &
Regression Testing,
Preparation of test
reports.

4 System Admin OS Migration,

Cluster Build,
Application
installation, INCOIS
custom code
deployment
5 System Architect System architecture
and design
6 Network and Design and trouble
Infrastructure shoot network,
Administration and hardware issues
Experts

Confidential Page 22of 29

 5.3.2 Roles and Responsibility matrix

Activity Responsibility
TCS INCOIS
Project Startup
System Architecture
Hardware Plan
Software Development Plan
Communication Plan
Technical Support Facilities Plan
Integration Plan
Warranty and Operational
Maintenance Plan
Approval of compiled plans above
Supporting INCOIS in Tender
Documents preparation
JAD meetings for Requirement
analysis
Application software development
Preparation of SRS document
SRS Approval
Application software development
Preparation of HLDs Design Review
documents, Preliminary design
documents
Preliminary Design Approval (HLD)
Application software development
Preparation of LLDs Design Review
documents, Detailed design
documents
Detailed Design Approval
System Integration
Application software deployment
Beta version Preparation of Test
plans, reports and Acceptance
document
Tsunami scenario generation
Application software development
Deployment of final version
Total system integration
Acceptance testing and operation of
entire system

6. Warranty and Maintenance Support

6.1 Stabilisation Phase-Warranty Support &
Maintance
TCS proposes to support the new systems for a period of 12 months from the
date of acceptance of the migrated application.TCS will use all its best practices
to provide excellent service during this phase. TCS Support team will be the

Confidential Page 23of 29

second level support to the INCOIS systems. First level support will be given by
respective teams of INCOIS who will be trained to operate the systems.
TCS Support team comprising of two consultants will provide support to the
portal team. The responsibilities of this team are confined to:
Defect fixing
Consultancy on how the application to be used
Support and handhold INCOIS administrators in managing the help-desk, setting
up the process for logging defects, maintaining and analysis of metrics,
containing SLAs, etc.
This team will not be responsible for any new features or development towards
enhancements of features would not form part of this phase. However TCS
would be glad to provide a team to assist INCOIS develop and enhance the
solution for futuristic requirements, under a separate assignment with mutually
agreed terms and conditions.
TCS will follow a structured methodology for defect reporting and closure
mechanism and will adhere to SLA targets pre-determined and approved by the
INCOIS team. All the changes or defects will be impact tested before release.
The INCOIS Project Managers/Heads approval will be the closure criteria of a
defect or Change Request. All the impacted documents will also be updated and
reviewed before releasing the change or defect resolution. Defect data will be
stored and a causal analysis will be performed. The findings and
corrective/preventive actions will be documented in the CA report. This report
will be published to INCOIS.
TCS will ensure that the INCOISs new systems will meet the entire target
Performance Requirements described in the RFP. Before going live, TCS will
deliver a complete operational document about INCOISs new databases to the
INCOISs support staff. This document comprises of database exporting,
importing, maintaining, archiving, tuning, replicating and training procedures.
Also escalation procedures will be discussed and finalized with INCOIS and in
case of any deviation, the INCOIS can follow the escalation mechanism to report
the instance of deviation.

Confidential Page 24of 29

 6.2 Approach to Maintenance Support
TCS proposed the following Support Models to provide System Maintenance
Support.

The terminology used in these models is described below:

First Level Support: Consultants providing this support will handle requests
that require on-line solutions. The First level support consultants will have
adequate knowledge on the systems to provide such solutions.
Second Level Support: This support provides solutions for the requests
received from the first level. The second level support requests can be of two
types:
System Enhancement Request: Changes to the current application
Adhoc Requests: One-time additional requirements

All the second level support requests will be prioritized before they are taken up
for execution.
High Priority: All Second Level Support request that is critical for the business
functions or is of highest priority or that will require a high level of client
involvement.
Low Priority: All Second Level Support requests that needs to be accomplished
but is lying low in the priority list.
Business Critical: All Second Level Support Requests that are critical to the
business.
Given below are the brief details of each model and the model selection drivers. TCS has
been able to support all its clients within the framework of these models.

Model Definition
Type
I First and Second Level Support from
ONSITE (Client Location: INCOIS)
TCS Helpdesk located at Onsite
Preferred model for business critical
applications

The sequential steps in providing the support to INCOIS users is as below:

ING users can dial / reports problem to INCOIS service / help desk.
ING service desk identifies it to be an application-related problem and routes it to
INCOIS Support team.
ING Support team identifies the problem to be one of the 3 types: security and
administration, technical support (database, network etc.), INCOIS application
system functionality.
If its a security and authorisation or technical infrastructure problem, it will be
routed to respective teams.
If its an application system functionality problem, the problem will be transferred
to TCS onsite coordinator / project leader

Confidential Page 25of 29

 TCS on-site coordinator will log the problem in a problem register and will assign a
unique PR number. This number will be communicated back to INCOIS.
TCS onsite coordinator will decide if the problem is to be attended at on-site or
needs to be transferred offshore.
If the problem is a bug / error, TCS will rectify as per service level agreements.
If the problem is an enhancement to existing functionality, TCS will raise a change
request. The change request will have the impact details with schedule and cost.
These requests with the details of schedule and cost will be forwarded to INCOIS
for approval. Once the approval is received TCS will enhance the system as per
the requirements.
Deliveries by TCS will be sent through TCS onsite coordinator. PR number in the
problem register will be closed on the acceptance of the delivery by INCOIS.

6.2.1 Acceptance Criteria

The following will form the basis for the acceptance of every deliverable or the support
service provided by TCS.

Deliverable meets the defined Service Level set by INCOIS and agreed upon by
TCS.
Deliverable meets the Quality Targets set by INCOIS, agreed upon by TCS. In the
absence of Quantitative Quality targets, TCS will use its own Quality Targets after
approval from INCOIS.
Deliverable conforms to the requested requirements.
Deliverable conforms to the coding standard set by INCOIS. In the absence of
such standards, TCS coding standard will be used during system development

TCS has well defined in-process measurement system. Tools developed in-house will be
used for the measurement. TCS will be willing to share any documentation of such tools
with INCOIS on request.

TCS expects INCOIS to provide a letter of acceptance for every deliverable made. Any
deviations from the finalized requirements will be corrected by TCS within mutually
agreed upon time frame at no extra cost to INCOIS. If no errors are reported for two
weeks after delivery, the deliverable is deemed to be accepted.

Confidential Page 26of 29

 7. Commercials
7.1 Pricing
The proposed price for the services and scope provided Section Rs. 31,708,881 . All the
applicable taxes would be extra and at actual.

Item Name of the Service Cost

No.
1 Solution Architecture 4,227,851
Design(Hardware, Software,
Networking )
2 AIX to LINUX Migration, undertaking 23,253,179
enhancements/improvements in the
application software & 1 Year
Application Support
3 DR implementation excluding 4,227,851
hardware
Total 31,708,881

7.2 Payment milestones

S. No Milestone % of Total
1 Project plan submission and submission
Solution Architecture along with generic 100 % of Item no 1.
hardware specification for proposed solution
2 Revised SRS,HLD document submission
3 Data Migration & Porting of applications to 15% of Item 2
new hardware
4 Deployment of CR Application software 15% of Item 2
Beta version
5 System Integration Testing & Deployment of 10% of Item 2
final version of CR application software -
DC site Go-Live
6 DR Site Go-live . 100% of Item 3
7 Start of Maintance Phase
1st Quarter AMC 15% of Item 2
2nd Quater AMC 15% of Item 2
3rd Quarter AMC 15% of Item 2
4th Quarter AMC 15% of Item 2

Conclusion

Confidential Page 27of 29

TCS is uniquely qualified for this technology refreshment of Tsunami Warning System
project as TCS understands working with Government Functions worldwide, has delivered
many such time bound mission critical projects, and also brings the following best things
to this engagement:

TCS Portal Centre of Excellence will help leverage its best practices

TCS experience in G2C, G2G, G2B, B2E, E2E, B2C and B2B solutions
Alliances with Global leaders in Technology
Offerings in Content Management
Preferred Partner for INCOIS for software Development

Confidential Page 28of 29

 Flexible Delivery Model
TCS experience in Usability Design and GIS experience
Global Reach Presence in 34 Countries
Over 38 Years of Experience in Software Consultancy
Research & Development which enables quick turnarounds and reduces time to
Market

TCS understands and conforms to all the qualification criteria for technical qualification.
TCS would like to emphasize the point that its track record for delivering solutions to
INCOIS is proven and also with its technical capabilities TCS is capable of delivering
solutions to INCOIS in this prestigious endeavour.

Confidential Page 29of 29