Cinntra’s Response

To
National Health Mission, Madhya Pradesh

Request for Proposal

For
Upgradation/Customization, Development
Operation and Maintenance
Of
MP ANMOL Portal

Submitted by:

Disclaimer & Confidentiality

The information in this document shall not be disclosed outside International SOS and shall not be duplicated, used or disclosed, in l

Technology • Outsourcing • Confidential• Implementation •Support 1

 Table of Contents

Contents
1. Executive Summary ..............................................................................................................................4
2. Company Profile ……………………………………………………………………………………………………………………………………5
2.1 Web and Mobility Capabilities & Strengths ......................................................................................... 8

3.KEY DIFFERENTIATORS AND VALUE ADDITIONS ......................................................................................9

4. MASTER PROJECT AND IMPLEMENTATION PLANS ................................................................................ 11
4.1 Implementation Plan ...................................................................................................................... 11

5 CHANGE MANAGEMENT STRATEGY AND EXECUTION ........................................................................... 12

5.1 Project Change Management Methodology ...................................................................................... 13

6. Scope of Project ................................................................................................................................. 16

6.1 Upgradation, Development and Migration ........................................................................................ 18
6.2 Application Support ........................................................................................................................ 19
6.3 Pre-requisites for Deliveries ............................................................................................................ 20

7. DATA MIGRATION ............................................................................................................................... 21

8. TESTING STRATEGY ............................................................................................................................. 22
8.1 Purpose ......................................................................................................................................... 22
8.2 Testing Objectives .......................................................................................................................... 22
8.3 Testing Scope ................................................................................................................................ 22
8.4 Overall Test Approach .................................................................................................................... 23

9. DELIVERABLES MANAGEMENT ............................................................................................................ 28

10. TEAM STRENGTHS ............................................................................................................................ 33
11. BEST PRACTICES LIST......................................................................................................................... 34
11.1 Design and Architecture Best practices .......................................................................................... 34
11.2 Application Development Best Practices ......................................................................................... 35

12. APPLICATION SUPPORT AND MAINTENANCE METHODOLOGY (ASM) ................................................. 38

12.1 Incident Management ................................................................................................................... 41

Technology • Outsourcing • Confidential• Implementation •Support 2

13. KNOWLEDGE TRANSFER (KT) ............................................................................................................ 42
14. ROLES AND RESPONSIBILITIES MATRIX .............................................................................................. 44

Technology • Outsourcing • Confidential• Implementation •Support 3

1. Executive Summary
Cinntra, a niche Technology organization focused on transformational solutions and services would like to
thank National Health Mission, Madhya Pradesh (NHM-MP) for giving us this opportunity to submit a
proposal for upgradation/customization, development, testing, maintenance and support of ANMOL web
and Android mobile application. As a part of assignment, Cinntra needs to manage application source code
and provide the implementation, and deployment of applications on stores.
The National Health Mission was launched by the Hon’ble Prime Minister on 12th April 2005, to provide
accessible, affordable and quality health care to the rural population, especially the vulnerable groups. The
Union Cabinet by its decision dated 1st May 2013, has approved the launch of National Urban Health Mission
(“NUHM”) as a sub-mission of an over-arching National Health Mission, with National Rural Health Mission
(“NRHM”) being the other sub-mission of National Health Mission. NRHM /NHM seeks to provide equitable,
affordable and quality health care to the rural section, especially the vulnerable groups.
The MP ANMOL Portal is designed for early identification and tracking of the individual beneficiary
throughout the reproductive lifecycle of women and promote, monitor and support the reproductive,
maternal, new-born and child health (“RMNCH”) schemes/ programme delivery and reporting. To meet all
customized needs of the state, especially with respect to the RMNCH program, the state has also made its
own application of ANMOL RCH.
This proposal is based on our high-level understanding and key expectations of the National Health Mission,
Madhya Pradesh (NHM-MP). The best practices which are adopted in the Technology Sphere by many of
the leading entities in the world, are followed by our team of experts to deliver the services of highest
quality. All developments & enhancements will be done at par with best industry standards and in
compliance with the regulatory requirements framework.

Technology • Outsourcing • Confidential• Implementation •Support 4

2. COMPANY PROFILE
Cinntra is a globally focused software and services company delivering comprehensive services in mission-
critical applications, enterprise applications, e-business and BPO. Cinntra is based out of Noida, India and
spread across 4 countries around the world; with sales & operations presence across India, US, UAE and
Kenya. The figure below represents Cinntra’s locations worldwide.

Figure 1 – Cinntra’s Business Organization

Cinntra has built and consolidated a comprehensive portfolio of services in IT and BPO towards supporting
our customers in meeting their business goals. This portfolio offers a sliding range of benefits along the value
chain, from cost to value arbitrage, from efficiency gains to lasting business impact, from the tactical to the
strategic level.

Technology • Outsourcing • Confidential• Implementation •Support 5

 Figure 2 – Cinntra’s Service Portfolio

Cinntra delivers these services through a strong sales & operations presence across markets including India,
US, UAE and Kenya. All support functions are decentralised at respective locations with reporting to Head
office (Noida, India) Support function units. This helps to quickly set up and operate customer specific
delivery centres.

Cinntra - Key Highlights

 SAP Asia Pacific Innovation Winners
 Times Group Awarded Best ERP Solution Provider
 Featured in Global Innovation Playbook
 100+ Customers and 200+ Software Experts

Cinntra - Primary Contact for this RFP

Full Name: Nipun Dixit
Job Title: Director
Phone Number: +91-8882144982
Email Address: [email protected]
Table 1: Contact Person Details

Some of our Customers

Technology • Outsourcing • Confidential• Implementation •Support 6

Technology • Outsourcing • Confidential• Implementation •Support 7
2.1 Web and Mobility Capabilities & Strengths
Cinntra is a one-stop-shop for Web and Mobile Solutions Development, right from initial study and due
diligence for Roadmap creation, UI/UX expertise, Development, Deployment and all the way to ongoing Web
and Mobile Device Management (MDM).

Figure 3- Cinntra Capabilities

Cinntra exercises expertise in development of web applications, portals and web services that enable
configuration across platforms and flexible integration to cater for the changes in business processes. This
approach of developing Service Oriented Architecture (SOA) applications provides C’s customers with faster
time-to-market and significant cost savings. This approach ensures that platform dependency is done away
with; hence, once a solution has been designed as a service, it may be deployed across various platforms.

Cinntra - Key Highlights

 Cinntra’s web application are being used by various customers in India, Middle East in Health Care
Industry, Pharmaceuticals.
 Cinntra’s has been working with various customers in Health care Industry like: Soothe, Vision
Diagnostics, Abaris Healthcare, Hi-Tech Medics etc.
 Cinntra’s CRM, POS mobile applications have been globally recognized and have been published in
SAP Global Innovation Playbook.
 Cinntra’s mobile products are being used by various customers across India, Middle East.
 Cinntra’s expertise in all kinds of mobile application, Native, PWA, Hybrid etc.
 Cinntra in-house products have been successfully published over the last 3 years in Global
Innovation book.

Technology • Outsourcing • Confidential• Implementation •Support 8

3.KEY DIFFERENTIATORS AND VALUE ADDITIONS
The uniqueness of Cinntra’s offerings for the engagement is based on our Organizational Values, Capabilities
and Experience of successfully delivering similar engagements to our customers. In the sub-sections below
we have listed some of our key differentiators and value additions that will differentiate us from the
competition.

Key Differentiators
A. Uniqueness of our offerings
Executive Management Commitment
 Cinntra values NHM-MP as one of its strategic customer and this would mean that the account would
periodically be reviewed by the Cinntra Executive Management. As a Strategic customer, NHM-MP will
benefit from proactive investment into the account, including a dedicated senior account management
team, availability of in-house developed IPs and knowledgebase.

End-to-end Service Capability

 Being a full scope service integrator, Cinntra brings to the table the unique combination of Consulting,
Domain, Technology, Infrastructure Management and Support Services expertise. We are equipped to
take over any IT and Business Process related challenge of NHM-MP and deliver value to the
engagement.

Reduced Time-to-Market
 Our Tools, Templates and Framework based approach helps us to jumpstart an engagement. We are
prepared on Day 0 to start an engagement and thus optimize the overall delivery timelines without
compromising on schedule, quality and cost.

Business Agility
 Our Customer-focused engagement models helps to align our engagement with our customers based on
their business plans and priorities.
 Shared services model for intermittent needs to help our customers to utilise our capacity and
capabilities without any upfront investment or long-term business commitments.
 Planned and duly skilled resource pool to meet any ad-hoc business needs.

Outcome focussed and Process driven Delivery Capability

 Proven and mature global delivery model and processes following global standards like ISO & SEI CMMI
 Extensive experience in implementing complex projects in different technologies.
 Emphasis on industry certified professionals

Technology • Outsourcing • Confidential• Implementation •Support 9

Integrated User Experience capabilities
 Certified Human Factors & design consultants
 Extensive experience in designing usable applications
 Team comprising of seasoned professionals with skills in Information architecture, Usability Analysis,
Usability Testing & visual design
 Sound understanding of usability best practices

Value Additions
Best Practices
Cinntra based on its global experience of delivering IT projects has an organizational knowledgebase
repository which provides Best Practices for every aspect of the Software Development and Implementation
Lifecycle. The Process and Standards Organization which is a core functional unit of the organization owns
the repository and updates the knowledgebase as a Quality process based on learning from the delivered
projects and other industry standards. The Best Practices are audited and benchmarked independently by
third party auditors.
Keeping the NHM-MP project objectives in view and based on our past lessons learnt recommends the
following Best Practices:
 Cinntra’s Agile Project Management approach
 Cinntra’s Design and Architecture Best Practice
 Testing Best Practices

Enterprise Mobility Reusable Components

We have developed a rich set of reusable components which can be readily used in the NHM-MP project.
The following reusable components which we intend to use have already been deployed in number of
projects and are guaranteed for reliability.
 Authentication
 Secure Data transfer
 Notifications
 Device detection
 Offline/Online Capability
 Persistent Connection

Technology • Outsourcing • Confidential• Implementation •Support 10

4. MASTER PROJECT AND IMPLEMENTATION PLANS
The master project plan and implementation plan for the NHM-MP Project depicting the high-level activity
details is presented below. Each project activity has been assigned a specific duration based on the estimated
efforts. For the purpose of planning we have assumed the project start date as 3th of April, 2023 which is
subjected to change based on the actual engagement. The Gantt chart provided illustrates the timeline of
execution of each of the activity, also elucidating the activities that will be executed simultaneously and
overlaps between the key activities. The project will be managed by a Project Manager from Cinntra and the
efforts have been blended in the tasks. A detailed Project Plan will be prepared in consultation with NHM-
MP team before the initiation of the project.

Figure 4 - Master Project and Implementation Plan (Best viewed in 150% zoom)

Cinntra proposes to optimize the User Experience, Expected Features release as mentioned above.

4.1 Implementation Plan

Provided below is the implementation plan for each of the project phases, including the activities to be
performed under each phase and task milestones.

Activity/Task Duration in Man

Days
Requirements Gathering and 30 days
Current System Understanding
Development 45 days
Integrations and Dashboard 30 days
Testing 15 days
UAT 10 days
Go-Live 10 days

Technology • Outsourcing • Confidential• Implementation •Support 11

5 CHANGE MANAGEMENT STRATEGY AND EXECUTION
Cinntra understands that the NHM-MP Mobile Application project is an important engagement that will
impact multiple stakeholders of the organization. Hence it is imperative to have an effective Change
Management Strategy and Execution plan for the expected Value Realization from the initiative.
Cinntra’s Change management strategy is a systematic approach that is focused on the outcomes and
closely aligned with the project management methodology. The method focuses on the strategic execution,
people change and value realization of the transformation initiatives.
The picture below illustrates the change enablers, all linked to value realization and comprises of step-by-
step guidance to accelerate the project towards the expected value realization.

Figure 5 - Change Enablers for Value Realization

Our experienced team of consultants and SMEs get involved in the project right at the initiation and work
with the customer executive management and stakeholders to formulate the Change Management Plan.
To substantiate our experience in delivering Transformation Engagements where we have effectively utilized
our Change Management methodology and industry best practices we have included several case studies
separately.

Technology • Outsourcing • Confidential• Implementation •Support 12

Cinntra also believes that for a seamless execution of the project aligned with schedule and delivery of the
project deliverables it is important that a Project level Change Management process is effectively followed
and adhered. To ensure this, Cinntra follows a proven Project Change Management methodology which has
been detailed below.

5.1 Project Change Management Methodology

Cinntra’s change management methodology is based on the concept of baselines. The baselines are
documents that define the intended scope, timeline and standards of the project against which all changes
are measured. We develop the baselines along with NHM-MP to ensure its buy-in and a common
understanding of project scope. Cinntra defines baselines in two categories:

Project Baselines
These documents will define the base expectations of the project management, duration and life cycle. The
baseline will be composed of:
 The Proposal and Scope of Work; and
 The Project plan, resourcing plan and billing milestones
 Implementation Project Plan.
 Implementation documentation.
 Any other document influencing the financial /relationship management aspects of the engagement

Development Baselines
These documents will define the technical and functional scope of the work conducted by Cinntra.
Components of the development baselines will be:
 coding standards;
 system requirements specifications ;
 design specifications
 Documentation Standards
 Detailed Functional Specifications ; and
 any other documents which will influence the development work conducted by Cinntra developers
Once the baseline definition is put in place, the process of managing change is a process of managing
compliance to baselines and their controlled change.

Change Requests
Baselines are not necessarily static throughout the project. We incorporate all changes by way of a change
request. We process the change requests as described below.
 The projects documentation is base lined at various phases of the project and the change control process
is initiated for any change to the baseline. Formal change requests are initiated for any change in the
scope of work or any other deliverable defined for the project. This formal request for change is based
on inputs/request from NHM-MP.
 The Cinntra project team analyzes the impact of the change on the schedule, the quality as well as the

Technology • Outsourcing • Confidential• Implementation •Support 13

 effort. The findings of the impact analysis are discussed and shared with NHM-MP along with an
implementation plan.
 Once approved by NHM-MP, the project baselines are updated to incorporate the impact of the change
requests and the change requests are taken up for implementation. In case of multiple change requests,
the NHM-MP team should be able to prioritize the requests.
 Depending on the impact of change on the delivery schedule, the change request implementation can be
initiated at various levels like Project Manager Level, Team Leader level, etc.

Figure 6 - Change Management Process Flow

Technology • Outsourcing • Confidential• Implementation •Support 14

Accepted change requests are incorporated back into the baseline to reflect the new scope of the project.
Once the baseline definition is put in place, the process of managing change is a process of managing
compliance to baselines and their ongoing update. The steps in managing the change request are as follows:

Sr.
Step Owner Description
No
A documented definition of the change in scope,
1 Define Change NHM-MP
documenting urgency and business impact.
Determine cost, time and risk implications of the
2 Document Impact Cinntra PM requested change and identify possible low-
impact alternatives
Evaluate and assess risk and determine if change
NHM-MP PM/
3 Schedule change is justified in the project critical path. Document
Cinntra PM
potential delay consideration
Update Development Update Functional Requirement Specifications
4 Cinntra Team
Baselines and Technical Design Documents (if required)
Update project Update master project plan, cost estimates,
5 Cinntra Team
baselines deliverable lists
Table 2: Change Request Management

Technology • Outsourcing • Confidential• Implementation •Support 15

6. Scope of Project
The MP ANMOL portal/ application are instrumental in ensuring timely identification of high-risk cases,
tracking their timely management, ensuring proper and timely referrals to higher level of health facilities
and ensuring proper delivery outcomes.
MP ANMOL is an innovative application for increasing the coverage of Reproductive Child Health, maternal
health interventions by improving performance of public health functionaries through better data
management and developing technology-based job aid. MP ANMOL application was released on two
platforms community (Mobile app) and facility (web-based). Mobile application was released at community
level for ANM users and web application was released at facility level for CHO and doctors to track the
patient movement using a two-way communication between the community-based android application and
the facility-based web applications to ensure that the high risk has been managed timely. The application is
being used by ANMs, and web application is being used at facilities by health officers at block/district/state
level.
The portal/ app has facilitated improvement in monitoring of High-risk pregnant women coming both from
facility or during Village Health and Nutrition Day (“VHND”) level. In future, the system will be extended for
users of SNCU as well and will also cater to HBNC at community level to track children developing high risk
symptoms whilst in community. MP ANMOL digitizes ANMs’ multiple register including RCH Register. The
system is also being used to disburse the payments to the beneficiaries MP ANMOL portal/ application is
aimed at improving the quality, effectiveness and timeliness of the delivery of quality services, specifically to
rural populations, to ensure better healthcare for women and children.
MP ANMOL portal/ application are aimed to improve data driven monitoring and tracking of Women and
Children, that will ensure the accountability of healthcare service provider to ensure better health care for
women and children through following features:
 Easy to understand User Interface (“UI”)
 Data entry tools are designed per requirement
 Decision taking logics are applied - Multilingual Support
 Reports (count and line list) are generated
 MP ANMOL app allows ANMs to enter and update data for beneficiaries of their jurisdiction
 MP ANMOL app works in the offline mode also when no internet connectivity is available and as
soon as internet connectivity is available, offline data is synchronized with the central server

Technology • Outsourcing • Confidential• Implementation •Support 16

There are 2 aspects of the Project Scope:
 Web Application: This was released at facility level for CHO and doctors to track the patient
movement using a two-way communication between the community-based android application and
the facility-based web applications to ensure that the high risk has been managed timely.
 Mobile Application: Mobile application was released at community level for ANM users

Technology • Outsourcing • Confidential• Implementation •Support 17

6.1 Upgradation, Development and Migration
MP ANMOL is a mobile and web application used by ANMs, CHOs, PHC staff, and health officers at
block/district/state level and Medical Colleges. NHM-MP is desirous to enhance the utility of the current MP
ANMOL portal/ app to address the identified challenges related to:
 Mobile based login and access, (e.g., ANM able to login in multiple devices, ID not found issues),
 Validation (e.g., validation mismatch at server and mobile application),
 De-duplication (same beneficiary available with multiple RCH-ID),
 Authorization (e.g., related to payment), Synchronization (data failed, data loss),
 Mechanism for registration of any migrated beneficiary from the facility level (i.e. any facility of any
district should be able to register a PW irrespective of the district in which she is resident)
 Mechanism for registration of beneficiary from any stage (e.g. if beneficiary come to facility for ANC
checkup without registration in portal, then there should be provision to register beneficiary from
PW module, no need to register from EC module)
 Divisional mapping is not available
 Two-way communication across community module and facility module is not available
 Provision for customization by state (difficult to add any additional requirement from the state)

The proposed logic framework for MP ANMOL Application and elements of integrated solution

Technology • Outsourcing • Confidential• Implementation •Support 18

Proposed Log frame of MP ANMOL Portal; payment system

6.2 Application Support

Cinntra shall upgrade/ customize, develop, manage, and maintain the portal/ application for the entire
Contract Period. The portal/ application shall be accessible to the users for all the desired services as
specified in the Scope of Work. Cinntra shall undertake to provide:
 Customization/ modification of portal/ application as per requirement
 Visual changes in the portal/ application
 User access management
 Providing training to the NHM-MP officials as per the finalized training schedule
 Doing change request as per the requirement of NHM-MP
 Monitoring regular systems logs and user load

Cinntra will be deploying the manpower as per the RFP which will be taking care of Application Support.

Application support includes, but not limited to monitoring, troubleshooting and addressing the
functionality, availability and performance issues, implementing the system change requests etc. The
Cinntra shall keep the portal/ application in good working condition in order to handle the user loads and
perform changes as and when requested by NHM-MP. Key activities to be performed by the Cinntra in the
application shall include but not limited to:
 MIS report changes as per request
 Providing comprehensive support to the entire portal/ application throughout the Contract Period
or any extension thereof
 Visual changes in portal/ application
 User Access Management
 Data point changes in portal/ application
 Any other changes as per the requirement of NHM-MP

Technology • Outsourcing • Confidential• Implementation •Support 19

Software Maintenance and Support
 The Cinntra shall address all the errors/ gaps/ bugs in the functionality in the solution implemented
in line with the FRS/ SRS as per RFP
 The Cinntra shall provide regular updates patches to the system during the Contract Period
 Any changes, updates to the software performed during the support phase shall meet the specific
requirement and should not impact any other functions of the system
 Issue logs for the errors and bugs identified in the solution and any changes done to the solution
shall be periodically submitted to the concerned department

6.3 Pre-requisites for Deliveries

 NHM-MP would provide access to all the source code and if any version control software being used as
repository.
 NHM-MP would provide all required Cloud Servers, Licenses e.g. SQL Server database, version control
etc., and would ensure that pre-requisites and instance(s) for the implementation are available to the
project team before the start of the project
 Access to various existing inbound and outbound systems w.r.t application will be made available to
Cinntra
 NHM-MP will provide access to the version control system, if any, for the Cinntra team will be provided
 Android and Apple iOS Enterprise Program account for development and distribution of the Android and
iOS application
 Account required for Google, SMS, Email integration will be provided by NHM-MP
 NHM-MP will retain the responsibility of system and network administration of the servers
 Any changes to the system design, project scope, or project schedule will be handled through change
control procedure
 There will be clearly identified and separate environments available for development and for testing
 English, Hindi will be the primary language of communication throughout the engagement duration
 Any delays in performing UAT from NHM-MP end will result in time and cost over run
 NHM-MP will provide connectivity from offshore to perform some of the implementation phases

Technology • Outsourcing • Confidential• Implementation •Support 20

7. DATA MIGRATION
Cinntra proposes to have a parallel Due Diligence phase during the requirement analysis phase. During this
phase Cinntra’s Database Architects will work with the NHM-MP Database Management and Administration
team to analyse the complete database structure of the current application. The data model prepared as a
part of this activity will be used as a baseline for the new database model and planning for the data
migration activities. The Data Migration activity will be completed before the Go-Live/Rollout phase of the
project.

Cinntra’s proposes a comprehensive Data migration approach.

 Migrate existing data from the existing database to the staging database
 Check Results, validate understanding and refine migration approach
 Check specific cleansing requirement
 Migrate application data from the staging database to the new database

Technology • Outsourcing • Confidential• Implementation •Support 21

8. TESTING STRATEGY
This section provides a high level overview of the proposed testing strategy for NHM-MP ANMOL Web and
Mobile Application project which aims to improve user experience, develop next generation solution to
support the ANMOL Web and users. The expectation is that solutions should meet the need as set forth by
the business.

8.1 Purpose
The purpose of the strategy is to provide a guide as to the proposed testing process and planning to be used
in testing ANMOL Web and Mobile Application, and enhancement of solution. The core activities of
proposed test strategy is to:
 Define the scope of testing
 Identify the phases of testing to be undertaken to meet the objectives
 Identify the data setup approach to accomplish the testing
 Define the roles and responsibilities for testing team
 Identify the environment / s required for testing
 Define deliverables within the scope of testing
 Identify the Assumptions, Risks and Mitigations associated with the Test Strategy

8.2 Testing Objectives

Project’s testing objectives are to validate the new and upgraded applications to work as per the business
requirements with respect to following:
 UI and features enhancements
 Application performance meets the expected and defined benchmarks
 Identify the vulnerabilities in the application and meet its specified security objective
 Application meets the usability standards
 Compatibility with all mentioned OS / browser combinations

8.3 Testing Scope

In scope
The following functionalities are in-scope of testing ANMOL Web and Application project:
 Push and pull notifications to end user who can operate with the application
 Feedback management
 Search Engine Optimization
 Security Auditing

Technology • Outsourcing • Confidential• Implementation •Support 22

Out of Scope
Following aspects / areas are considered out of scope for testing ANMOL Web and Application project:
 Compatibility testing with the OS-Browser combinations not explicitly mentioned

8.4 Overall Test Approach

Levels and Types of Tests
Considering the program goal and testing objectives, the following types and levels of testing are proposed
for ANMOL Web and Mobile Application project.

Level of Test
Types of Test Description Responsibility
Test Environment
Development owned testing of Cinntra Dev
1.1. Unit Testing
application modules. Team
1. Unit
1.2. Component Development owned testing of Local – DEV
Testing Cinntra Dev
Integration integration between application
Team
Testing modules.
The testing conducted on a complete,
integrated system to evaluate the Cinntra QA
2.1. System Testing
system's compliance with its specified Team
requirements
To ensure rich user experience and
2.2. Usability Cinntra QA
easy navigation to assist users in
2. System Testing Team
performing key tasks. Local – QA
Testing
To ensure consistent visual experience
irrespective of computer configuration
2.3. Compatibility (OS/Browser combination) at the Cinntra QA
Testing users’ end, and no impact on Team
application functionality (across the
recognized OS/Browser combinations).
The testing process that exercises a
software system's coexistence with
3.1. System
multiple integrated systems, assuming Cinntra QA
Integration
that each have already passed system Team
Testing
testing, SIT proceeds to test their
3. SIT required interactions. QA
To verify consistency among data from
3.2. Data
a source to a target data storage and Cinntra QA
Synchronizatio
vice versa and the continuous Team
n Testing
harmonization of the data over time.
3.3. Regression Validation of the overall functionality Cinntra QA

Technology • Outsourcing • Confidential• Implementation •Support 23

 Testing after defect fixing. Team
The process of testing transactions or
business processes as they pass right
4.1. End to End through all the integrated systems. Cinntra QA
Testing This ensures that all aspects of the Team
business requirements are supported
by the systems under test.
Security testing aims at ensuring that
new system and interfaces are not
vulnerable to attacks and data and
confidentiality is not at stake. Security
4. E2E Cinntra QA Stage - QA
4.2. Security Testing of the systems through penetration
Team
testing, vulnerability assessment,
threat modelling and cross site
scripting assesses how secure the
application is.
Peak, Stress and Soak testing at system
4.3. Performance Cinntra QA
and component levels based on Non-
Testing Team
Functional Requirements (NFR’s).
4.4. Regression Validation of the overall functionality Cinntra QA
Testing after defect fixing. Team
Acceptance Testing is the formal
testing conducted to determine
5.1. User NHM-MP Biz
whether a software system satisfies its
Acceptance Team / Cinntra
acceptance criteria and to enable
Testing QA Team
business owner to determine whether
to accept the system or not.
Operations Acceptance Testing is
5. UAT carried out to ensure that application
Cinntra QA Stage - QA
5.2. OAT can operate on a production
Team
environment without any problems
before going live.

NHM-MP
5.3. Regression Validation of the overall functionality Business Team
Testing after defect fixing. / Cinntra QA
Team
Table 3: Levels and Types of Tests

Technology • Outsourcing • Confidential• Implementation •Support 24

Entry & Exit Criteria
The diagram below depicts the Entry & Exit criteria Cinntra proposes to follow for the different Testing
Phases of the ANMOL Web and Mobile Application project.

Figure 7 - Entry Exit Criteria for Testing

System Testing:
Entry Criteria Exit Criteria
 Unit test is complete and the exit criteria have  All planned test scripts have been successfully
been met. executed with agreed pass rate percentage, 1
 Smoke test scenarios are tested and passed or 2 Test Priority defects are closed and
without any major blocking issues. Priority 3 issues have been agreed as excluded
or failed test coverage.
 Prioritised defects in Unit Testing have been fixed
and successfully tested  Defect retests (on fixes made) have been
successfully executed.
 Test cases / scripts have been agreed for coverage
with the Business Analyst and Technical teams.  Temporary workarounds are identified for any
known open issues, which will help inform the
 Test environment readiness.
Integration Test phase.
 Test data readiness.
 Daily execution plan is in place.
Table 4: Entry and Exit Criteria for System Testing
System Integration Testing:
Entry Criteria Exit Criteria
 System test is complete and the exit criteria have  All planned test cases / scripts have been
been met. successfully executed with agreed pass rate
 Prioritised defects in System testing have been percentage, 1 or 2 Test Priority defects are
fixed and successfully tested. closed, and Priority 3 issues have been agreed
as excluded or failed test coverage.
 Test cases / scripts including suitable test data are
created.  All Critical, High and Medium Business Impact

Technology • Outsourcing • Confidential• Implementation •Support 25

 Test environments readiness. defects are closed or have been agreed with
 Test data readiness. the business teams and appropriate
workarounds or fixes agreed.
 Defect retests (on fixes made) have been
successfully executed
 All test Cases have been successfully executed
with only Low priority defects that remain
Opening.
Table 5: Entry Exit Criteria System Integration Testing
End-to-End Testing:
Entry Criteria Exit Criteria
 System Integration testing phase has been  All planned test cases have been successfully
completed. executed with agreed pass rate percentage, 1
 Prioritised defects have been fixed and or 2 Test Priority defects are closed, and
successfully System integration tested Priority 3 issues have been agreed as excluded
or failed test coverage.
 Test cases / scripts including suitable test data are
created.  All Critical, High and Medium Business Impact
defects are closed or have been agreed with
 Test environments readiness.
the business teams and appropriate
 Test data readiness. workarounds or fixes agreed. Low issues have
been agreed with fix priority or
rejected/deferred to a future release.
 Defect retests (on fixes made) have been
successfully executed
 All Test Cases have been successfully executed
with only Low priority defects that remain
Open
 A test completion report is available detailing
passed, failed, not run, excluded results
Table 6: Entry Exit Criteria for End-to-End Testing
User Acceptance Testing:
Entry Criteria Exit Criteria
 End-to-End testing has been completed  No open critical issues in User Acceptance
 All the reported defects have been fixed and Testing.
tested  All Business functionalities are working
 Test cases / scripts including suitable test data is satisfactorily.
created  Signed-off from business users after UAT.
 Test environments readiness.
 Test data readiness.
Table 7: Entry Exit Criteria for User Acceptance Testing

Technology • Outsourcing • Confidential• Implementation •Support 26

Test Environment
The environment details for each Level of Test in ANMOL Web and Mobile application project are illustrated
below:

Test Environment Level of Test Environment Details

Local – DEV Unit Testing On NHM-MP Servers
Local – QA System Testing On NHM-MP Servers
QA System Integration Testing On NHM-MP Servers
Stage - QA End-to-End Testing On NHM-MP Servers production access controls
UAT
Table 8: Environment v/s Level of Testing

Technology • Outsourcing • Confidential• Implementation •Support 27

 9. DELIVERABLES MANAGEMENT
Following is the list of the key deliverables to be made during Implementation and Cinntra Project Manager will plan the reviews with relevant
NHM-MP stakeholders.

Project Phase Milestone Procedure Deliverables Acceptance Criteria Dependency

Requirements Requirements Signoff Requirements  Project  Requirements gathered Availability of NHM-

Gathering & walkthrough with NHM- Management during requirements MP stakeholders
Analysis MP Team Plan gathering & analysis during requirements
 Activity list phase are mutually gathering & analysis
agreed by NHM-MP phase
 Risk register
and Cinntra Team
 Issue log
 NHM-MP Team has
 Requirement reviewed the
documents specifications and
other related
documents to ensure
its sufficiency for
beginning application
design

Architecture &  Technical Design Design walkthrough  Application  Review and signoff of Completion of
Design signoff with NHM-MP Team and Architecture design documents for Requirements
 Wireframes sharing the wireframes Document correctness, Gathering & Analysis
signoff with NHM-MP Team for  High-Level Technical completeness, and phase
review and obtaining Design consistency with
the signoff respect to the
 Low level design
prioritized

Technology • Outsourcing • Confidential• Implementation •Support 28

 Project Phase Milestone Procedure Deliverables Acceptance Criteria Dependency
 Wireframes (Visual requirements
Design) established in the
 HTML & CSS System Requirements
Specification
 Database Design
 NHM-MP Team has
 Data Backup/ Archival
reviewed the
Process
specifications to
 Requirement
ensure that all
Traceability Matrix
requirements are fully
represented in the
design

Development Completion of Sharing the Unit test  Source code  Completion of Completion of Design
development and Unit results with NHM-MP  Unit Test Scripts & development and phase
Test case signoff Team and obtaining the Results execution of unit test
signoff scripts
 No critical defects

System Testing System Testing signoff Sharing the System test  Testing Strategy  Execution of system Completion of
results with NHM-MP  System Test Results test cases Development phase
Team and obtaining the  No critical defects
signoff
 Signoff from NHM-MP
Team on System Test
results
System Integration Sharing the System  Integration Test  Execution of system Completion of
Testing Integration test results Results integration test cases System Testing phase
with NHM-MP Team and

Technology • Outsourcing • Confidential• Implementation •Support 29

 Project Phase Milestone Procedure Deliverables Acceptance Criteria Dependency
obtaining the signoff  No critical defects
 Signoff from NHM-MP
Team on Integration
Test results

Final Delivery, Setup Implementation Sharing Implementation  All source code and  No critical defects Completion of
and Pre-test signoff and approval Plan with NHM-MP executables found in System & Integration Testing
for implementing the Team and obtaining the  Details on the Integration testing phase
code to UAT signoff usability of the phases
environment existing IT  Signoff from NHM-MP
infrastructure Team on System &
 User Manual / SOP Integration Test results

 Technical Manual,  Signoff from NHM-MP

Help Manual Team on
Implementation Plan
 Physical Database
Design
 Production Database
DDL
 Signing key of mobile
app development on
all platforms

User Acceptance UAT Signoff Execution of UAT Test  UAT Sign off by NHM-  Severity 1: Show  UAT Test case
Testing cases by NHM-MP MP based upon Stopper and Critical preparation by
Business users and UAT Agreed Acceptance functionality not NHM-MP Team
support from Cinntra Criteria working – Zero  Availability of

Technology • Outsourcing • Confidential• Implementation •Support 30

 Project Phase Milestone Procedure Deliverables Acceptance Criteria Dependency
Team  Severity 2: Issue with NHM-MP
work around available - Business Users to
Less than 5% perform UAT
 Severity 3: Low priority
issue like cosmetic,
incorrect
message...etc. – Less
than 10%

Go Live Implementation code Implementing the steps  Deployment of No critical defects Completion of UAT
to Production specified in application on phase
environment Implementation Plan Production
Environment
 Conducting Sanity
tests in Production
environment

Project Periodic reviews Sharing the project  Master Project Plan All the deliverables are
Management management  Project Change updated as agreed and are
Deliverables and deliverables with NHM- Request Form complete and consistent
Forms MP Team on periodic
 Project Completion
basis like Project Status
Checklist
Report etc. and others
as and when it is  Project Evaluation
updated and obtaining Document
the signoff  Project Issue Form
 Project Status Report

Technology • Outsourcing • Confidential• Implementation •Support 31

Project Phase Milestone Procedure Deliverables Acceptance Criteria Dependency
 Project Work plan
 Risk Information
Sheet
Table 9: Phase wise Key Deliverables

During these phases, Cinntra expects following inputs from NHM-MP Team:
 Any documentation related to business process, wireframes, branding and visual design, standard style guide, test cases etc. available for
the earlier Mobile application
 Availability of stakeholders for Phase signoffs
 Access to test environments

Technology • Outsourcing • Confidential• Implementation •Support 32

10. TEAM STRENGTHS
Cinntra proposes to deploy a team of experienced resources headed by seasoned Project Manager. Every
member of the team will have excellent communication skills and cultural alignment with NHM-MP. The core
strength of the team is the motivation and commitment to deliver a value beyond expectations to NHM-MP.
Listed below are some of the professional strengths each team brings to this engagement.

Project Manager  The Project Management team is supported by strong methodologies, process
frameworks and industry wide certifications (viz., PMP, Prince2, ITIL)
 Pro-actively manage the scope, assumptions, complexity, risks to resolve them
before they happen and contingency plans.
 Continuous project tracking, monitoring, reviews with all stakeholders, CPI,
reporting.
Business Analyst  Experienced Analysts in helping organisations with improvements in business
processes and project outcomes, while managing changes and scope creeps.
 Experience in working with core team through a collaborative and iterative
design process (stakeholder engagement) towards exploring and evaluation
options.
 Systematic approach to analysing, questioning techniques, root cause of
business & technical problems using tools.
 Expertise in Prioritizing, Organizing, Verifying and validating requirements.
Architect & UI Design  Well versed with various software architectures like n layer, SOA etc.
 Well Acquainted with industry best practices
 Backed by Architecture Review team in Cinntra
Development Team  Experienced team members in Java/.net technology
 Experienced team members in MIS
 Experienced team members in Android
 Android Developer skilled in Java/Kotlin
 Database: MYSQL
 Expertise in delivering solutions across verticals and geographies
Testing Team  Resources with CSTE, CSTM, CSQA, ISTQB certifications
 Strong track record for providing independent testing solutions to a number of
global clients
 Technology and vertical specific processes and frameworks
 Reusable assets and home grown tools

Technology • Outsourcing • Confidential• Implementation •Support 33

11. BEST PRACTICES LIST
To make every customer engagement successful at global level, we believe in constantly evolving ourselves.
We keep a track on the pulse of the online trends and globally followed practices by participating in industry
forums, seminars, events and conferences. Our access to exclusive reports and forecast papers found in IT
research firms like Gartner keeps us abreast on global trends & practices.
Our development processes and strategies are based on the best practices followed in the industry which
helps us in creating innovative solutions.
The Tables below highlight some of the best practices we follow in the area of design and architecture, and
development

11.1 Design and Architecture Best practices

Best Practice Description/Consideration Benefit
Identify Constraints and Identify any constraints and Re-work is avoided
Assumptions Early assumptions early in the design phase
to avoid surprises in later phases
Use of Layered Design A layered design is one that factors in A multi-layered approach
presentation, business, and data with separate presentation,
access logic. A good layered design business, and data access
exhibits high degrees of cohesion by logic helps to build a more
keeping frequently interacting scalable and more
components within a single layer, maintainable application.
close to each other
Service Oriented Architecture Each core business process should be Allows the business
exposed as Web Services. functionality to be re-used
in other applications.
Minimize round trips by Minimize round trips to reduce call Improved Performance and
batching work. latency. For example, batch calls less bandwidth
together and design coarse-grained consumption
services that allow you to perform a
single logical operation by using a
single round trip.
Security Consideration Authentication and Authorization To prevent unauthorized
Input Data Validation access and ensure data
security
Cross Site Scripting
SQL Injection
Etc.

Technology • Outsourcing • Confidential• Implementation •Support 34

 Re-usability Identify the common attributes It minimizes component
between various components to build duplication, and
small re-usable components. Also, development and
identify and use proven patterns, implementation time.
application blocks, libraries and
frameworks viz. Enterprise Library,
and Entity Framework.
Table 10: Design and Architecture Best Practices
Also the focus on various qualities attributes like availability, performance, maintainability, reliability, etc. are
also major aspects of the design and architecture best practices.

11.2 Application Development Best Practices

Best Practice Description/Consideration Benefit
Globalization Use Unicode as your character encoding to represent text Application can be
and User Interface elements should be isolated from source code easily extended to
Localization and kept in resource files, message file, private database multiple locales.
Avoid text in Bitmaps and Icons
Leave non-localized strings as string constants in the source
code
Exception Programmatically check for a condition that is likely to occur Makes a program
Handling without using exception handling as too much exception more robust and less
handling can also lead to less maintainable code. In other prone to crashing
situations, using exception handling to catch an error condition because the
is appropriate. application handles
such errors
Coding Adhering to agreed coding standards and conventions Improves code
Conventions maintainability and
readability
Caching Implement cache at identified layers of application. Add Performance benefit,
caching support to layers provides performance benefit low bandwidth
consumption
Code Review Perform manual as well as automated code reviews and Improved code
and Code analysis using tools like FxCop and StyleCop quality
Analysis
Code and A good code versioning scheme ties each deliverable back to Better traceability
build all the coding changes that comprise and impact the
versioning deliverable.
Continuous Frequent check-ins, use of dedicated integration build Early visibility of

Technology • Outsourcing • Confidential• Implementation •Support 35

 Best Practice Description/Consideration Benefit
integration machines, integration issue
Table 11 - Application Development Best Practices

We employ practices that not only helps organizations improve internal operations & reduce cost but also
strategize on leveraging the internet to increase sales among existing and new customers.

User Experience Management

For a mobile application to succeed, it has to be accepted by its users. Usability is the engine that drives user
acceptance and stickiness. We have a team of usability analysts, information architects, visual & graphic
designers who ensure that each solution meets the defined usability goals. Right from user research & task
analysis to heuristic evaluations, usability testing and W3C coding standards for development, our processes
are based on the internationally followed usability standards & guidelines.
 Internationalization & Localization: Different countries, varied users, multiple cultures. Any strategy that
we formalize is toned to be scalable and fit seamlessly into the local culture & sensitivity.
 Accessibility: As a practice, we adhere to local accessibility laws & ensure that defined disabled users
are able to access the website/application through various tools. Our developers follow the W3C defined
coding standards.
 Brand Guidelines: With organizations having footprint across the globe, creation of brand guidelines &
online development style guides becomes critical. We assist organizations is creating these guidelines
and style guide assets. These assets capture the organization’s online brand strategy and define the tone
of communication for all online initiatives of the organization.

Risk Management
We follow the best practices to remove the surprise factor during any development process. Our years of
experience in software development field has helped us in creating major software risk categories and
software risk items that typically threaten any development project and strategies for neutralizing the same.

Change Management
For organizations whose geographically distributed teams handle high volumes of online content and
multiple stakeholders, managing change can be an enormous task. Our change management solutions based
on global best practices allow organizations to control, manage and implement change effectively.

Engagement & Relationship Management

Each and every engagement of ours follows a defined client relationship process. Communication
mechanisms & reporting structures are defined, governance model is setup, key SLAs – where required are
defined along with metrics based management model with periodic checkups.

Technology • Outsourcing • Confidential• Implementation •Support 36

Development & Maintenance
For customer engagements that involve maintenance of applications, we create a maintenance blueprint
that extensively covers content matrix, update schedules, key contact people details, infrastructure & load
management details and overall roadmap of keeping the application up and running 24x7.

Technology • Outsourcing • Confidential• Implementation •Support 37

12. APPLICATION SUPPORT AND MAINTENANCE METHODOLOGY
(ASM)
As part of the Contract, Cinntra need to maintain the Application for 5 years and provide the Support of the
newly implemented features of the Application.
Cinntra will implement proven application support & maintenance model to maintain newly developed
application into Support & maintenance mode for NHM-MP. Post go live of enhanced features of the
application, in consultation with NHM-MP below methodology will be mapped as applicable to the project.
Complete Support will be managed by the Cinntra.
L1, L2 support engineer will try to understand problem and find the root cause. Most of the issues that get
resolved at this level would not involve code changes. If ticket does not get resolved, it is escalated to higher
levels.
Some typical activities L2 support does are given below:
• Handle escalations from L1 (Advanced application support)
• Workarounds
• Data fixes
• Root cause Analysis (Initial level of Problem Management) and Change Management (Impact Analysis)
• Manage deployments and related outages
• Knowledge base update
• Escalation to next level
Our model is based on a strong underlying Knowledge Management. Cinntra will proactively baseline the
systems key performance thresholds and implement necessary actions to track health of the application
performance based on laid processes and metrics.

Key Highlights of our proven Application Support & Maintenance Methodology:

 Bring Cinntra’s Industry best practices, knowledge repositories, solution frameworks

 Leverage Cinntra’s past experience for other customers to make the engagement better
 Conduct periodic innovation sessions for resources to identify areas of value creation
 Improve process maturity to higher levels of CMM as appropriate and practical

 Application Portfolio Management as an optional service to improve maintainability of the customer’s

applications.

Technology • Outsourcing • Confidential• Implementation •Support 38

To Support the Application Cinntra will be deploying following manpower listed below as asked in the RFP,
the Manpower deployed will be responsible to provide the support to following activities:
Cinntra shall upgrade/ customize, develop, manage, and maintain the portal/ application for the entire
Contract Period. The portal/ application shall be accessible to the users for all the desired services as
specified in the Scope of Work. The Cinntra shall undertake to provide:
 Customization/ modification of portal/ application as per requirement
 Visual changes in the portal/ application
 User access management
 Providing training to the NHM-MP officials as per the finalized training schedule
 Doing change request as per the requirement of NHM-MP
 Monitoring regular systems logs and user load

Technology • Outsourcing • Confidential• Implementation •Support 39

 S.
Title Nos. Min. Educational Qualification Working Hours Deployment
No.
B. Tech / B.E./MCA with minimum
Should be available for all
07 (seven) years of relevant
1. 01 the meetings and discussion
Project experience in managing operations
at NHM-MP, Bhopal office
Manager of similar nature
or as per requirement by
NHM-MP
B. Tech / B.E./MCA with minimum
05 (five) years of experience in the
2. 01 field of managing/ implementing IT
Project As per NHM-MP Office At NHM-MP, Bhopal
coordinator projects timings office
B. Tech / B.E./MCA with minimum 03
As per NHM-MP Office At NHM-MP, Bhopal
(three) years of experience in the
timings office
3. MIS Expert 02 field of handling of IT projects

01 resource at NHM-
B. Tech / B.E./MCA with minimum MP, Bhopal office
DBA (MySql, 05 (five) years of experience in
Oracle, MS 01 resource should be
databases such as My SQL, Oracle, As per NHM-MP Office
4. Sql etc.) 02 available remotely
MS Sql as a Data base Administrator timings
(full time)
Master of Science in information
As per
technology (MS-CIT) or equivalent
5. Helpdesk team req
with minimum 01 (one) year of As per Office timings At NHM-MP, Bhopal
experience in the field of IT projects (post go-live) office
Should be available
B. Tech / B.E./MCA with minimum
remotely (full time
6. 03 05 (five) years of experience as a
.Net As per NHM-MP Office for the entire
.net developer
Developer timings contract period)

Should be available
B. Tech / B.E./MCA with minimum
remotely (full time
7. 01 05 (five) years of experience as a
Android As per NHM-MP Office for the entire
Android Developer
Developer timings contract period)

Should be available
B. Tech / B.E./MCA with minimum
remotely (full time
8. 01 03 (three) years of experience in the
Software As per NHM-MP Office for the entire
field of IT projects as software
Tester timings contract period)
tester
B. Tech / B.E./MCA with minimum Should be available
Business As per NHM-MP Office
03 (three) years of experience in the remotely as and
analyst timings
9. 01 field of IT projects as business when required
analyst

Technology • Outsourcing • Confidential• Implementation •Support 40

SLA for the Maintenance of the Application
Support Window: 9*5 Time: 9:30 AM to 6:30 PM
*Support on need-basis during non-support window/hours.
*Support for addressing security and regulatory compliance requirement during non-support
window/hours.

12.1 Incident Management

Outlined below is the expected SLA in case of any incidents:

Technology • Outsourcing • Confidential• Implementation •Support 41

13. KNOWLEDGE TRANSFER (KT)
To ensure that the enhanced ANMOL Web and Mobile Application solution delivers maximum benefit to the
end-users and the NHM-MP team can effectively and efficiently maintain and run the deployed solution on
an ongoing basis, it will be necessary to have a clearly understood and agreed method of knowledge transfer.

Cinntra recognises that there is the non-formal knowledge transfer that takes place as part of being involved
within the Project itself and the more formal process of training. While we promote an active collaboration
with NHM-MP IT team all through the project, we also propose for a ‘train the trainer’ approach for the
NHM-MP Operational staff, but it is envisaged that some of the NHM-MP’s IT staff or Super Users will require
direct training. In the interests of cost efficiencies and to minimize impact on resources, Cinntra will expect
training to be local to the Project area where possible.

Cinntra envisages the following activities and their estimated duration for the Knowledge Transfer:

Planned Activities during Knowledge Transfer Duration (In days)

Training Need Analysis & Training Plan Development 5
Code Review and Training 7
Train the trainer (User Experience) 5
Train the trainer (Enhancements) 2
System Administration Training (Super Users) 1
Table 12 - Planned Activities During Knowledge Transfer

Also as a part of the Knowledge Transfer to Production Support, Cinntra plans to carry out the following
activities:
Post Go Live activities
 Hand over application to the support organization, as per contract
 Hand over the following documentation to the Support organization
o Requirement analysis
o Design document (technical architecture, database schemas, systems documentation)
o Functional document
o Test plans and test cases
o Issues resolved /Logs

The formal handover to Production support also includes the following items:
 Applications Maintenance Manual. This manual contains :
o Libraries and locations
o Job schedules

Technology • Outsourcing • Confidential• Implementation •Support 42

 o Interface Points between Mobile Application and other Applications
 Known errors and outstanding support items.

o List of known errors

 Evolution list (enhancements):
o List of known CRs/enhancements requested by the client post GO Live
 List of stakeholder contacts:
o A list of people and roles as they relate to the ANMOL Web and Mobile application

Technology • Outsourcing • Confidential• Implementation •Support 43

14. ROLES AND RESPONSIBILITIES MATRIX
The table below provides the roles and responsibilities envisaged from both Cinntra and NHM-MP’s
perspective with respect to each project phase, highlighting the responsibilities which would need to be
followed by each role to ensure successful project execution.
Ser Phase /
Staff Designation/ Role Vendor International SOS
ial Activity
1. Project Cinntra Project Project Plan Project Plan Approval
Initiation Manager, NHM-MP Finalization
Project Manager
2. Requirements Cinntra Project Team Management, Facilitate Requirements Phase
Analysis Manager, NHM-MP Client Interactions,
Project Manager
Cinntra Business Capture and elicit the Provide the requirements,
Analyst, NHM-MP Requirements from Review and Sign off the
Subject Matter Expert Business Stakeholders Functional Requirement
and prepare the Specifications document
Functional
Requirement
Specifications
document, Prepare
Functional Test
Scenarios
Cinntra Senior Understand the Provide the source code, any
Technical Consultant, existing NHM-MP documents for existing ANMOL
NHM-MP IT Manager application landscape Web and application
3. Analysis & Cinntra Project Team Management, Facilitate Analysis and Design
Design Manager, NHM-MP Client Interactions Phase
Project Manager
Cinntra Technical Work on the High Level Review and Approve HLD
Architect, NHM-MP IT Design and Technical
Manager Architecture
Senior Technical Work on the High Level Review and Approve HLD
Consultant, NHM-MP IT Design
Manager
Cinntra Usability Prepare Wireframes, UI Approve UI Design
Expert, NHM-MP Design, Prepare UI User
Subject Matter Expert Test Scenarios

Technology • Outsourcing • Confidential• Implementation •Support 44

4. Development Cinntra Project Team Management Facilitate the Development
Manager, NHM-MP and Client Interactions, Phase by making licenses,
Project Manager Facilitate the source code, configuration
Development by management and any other
making licenses, source tools available. Make relevant
code, configuration Business and IT stakeholder
management and any available for queries if any
other tools available.
Cinntra Technical Mentors and guides
Architect the developers in line
Cinntra Senior with the technical
Technical Consultant solution. Segregate and
delegate the technical
work to right
developers. Review the
source code, coding
standards and quality
assurance.

Cinntra Business Query Resolution Query Resolution(if any)

Analyst, NHM-MP
Subject Matter Expert
Cinntra Developers Coding and Unit
Testing
Test Engineer/ Testers Understand the
requirements, design.
Prepare the test plans
and test cases.
5. Testing Cinntra Project Team Management, Facilitate Testing Phase,
including UAT Manager, NHM-MP Facilitate Test Facilitate UAT, UAT Signoff
Project Manager environment setup
Cinntra Test Engineer/ Perform Test Cycles
Testers
Cinntra Senior Defect Analysis &
Technical Consultant Resolution
Cinntra Developers Code Debugging & Bug
Fixing
6. Warranty Cinntra Senior Defect Analysis and Support Signoff
Support Technical Consultant, Application
NHM-MP Project Monitoring, Knowledge
Manager Transfer
Cinntra Developers Code Debugging & Bug
Fixing

Technology • Outsourcing • Confidential• Implementation •Support 45

 Cinntra Business Training and
Analyst Knowledge Transfer
7. Maintenance Cinntra Support Support Management
Support Technical Engineer

Technology • Outsourcing • Confidential• Implementation •Support 46

Technology • Outsourcing • Confidential• Implementation •Support 47