Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Technology
Proposed Refreshment
Digi Gov Implementation forof
Existing
National Tsunami System-
Disaster Management Agency
INCOIS
April 2017
Ver 1.0
Customer: 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 .
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
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,
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.
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.
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.
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.
Scalability- Virtualization provide scalability in terms of memory, CPU & virtual machine
can be move between physical servers if required without any downtime.
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.
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.
The following are the existing and proposed third party software needed for new setup.
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.
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
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
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.
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:
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
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.
7 Implementation of CRs
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
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
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
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
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.
Conclusion
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
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.