Tools / Products Evaluation Framework By Jitender
The document is prepared to assist the team members for creating RFP for ABC Company.
Technical Evaluation Framework
The technical aspects of the RFP response will be evaluated and will be given marks on the
following areas: -
Architecture Framework
Application Architecture -
Integration
Data Architecture -
Infrastructure Architecture -
Validation Criteria Weight
Overall Solution
Architecture
- Modularity and Ability
to customize
- Performance
- Tools (Check if the
software is not obsolete)
- Quality of documents
and supporting facts
- Ease of Integration
- Modules
- Third party integration
- Quality of documents
and supporting facts
- Data Model
- Data Migration
- Quality of documents
and supporting facts
Hardware sizing to be
adequate from the
perspective of
- transactional
performance
- Scalability (Vertical or
Horizontal) - sized for at
least 5 years growth
- Backup and DR recovery
process
- Ease of Maintaining
- Compatibility with ABC
Company
- Deployment strategy
and planning
- Documentation should

Security Architecture -
Support and Maintenance
be exhaustive with details
application-wise, system-
wise, providing for the
entire range of hardware
required, substantiated
with the product
literature, benchmark
reports and duly relating
with the information
provided for hardware
sizing
Encryption (Data at Rest
or Motion)
- Virus protection/ Patch
update
- Quality of documents
and supporting facts
- Upgrade cycles
- SLA
- Quality of documents
and supporting facts

Tools / Products Evaluation Framework By Jitender

The tools and products proposed by the bidder/vendor can be evaluated objectively with the
help of the below framework tables: -

Evaluation Criteria Marks Weigh

Criteria t
Type of Open Source with Support
Tools/Products
Proprietary and open source based with support
Proprietary with support
Open Source or Proprietary without support
Open Source with Support
Type of License Perpetual - Server based 10
Perpetual – Node based
Perpetual - User based (concurrent user)
Perpetual - User based (named user)
Non- Perpetual - Server based
Non- Perpetual - Node based
Non- Perpetual - User based - (concurrent user)
Non- Perpetual - User based - (named user)
 Any other - Will be decided based on details
Level of On site
support on
software/tool
Off-site: on-line ticketing system, Telephone and e-mail
Off-site: Telephone and e-mail
Market Share Above 30
10 – 30 %
5-10%
<5%
Experience of More than 3 years 10
Implementatio
n 10%
Between 2 to 3 years
Between 1 to 2 years
Less than 1 year
Debugging & Easy
Exception
handling 10%
Medium
Difficult
Source Control Built in
Not built in
Last version Less than 1 years
Release date
Between 1 to 3 years
Between 3 to 5 years
Ease of Easy
Installation
Medium
Complex
Application Easy
Integration &
Integration
with other
Systems
Medium
Complex
Unique feature Will be decided based on details
of the
software / tool
Security Excellent
 Features 10%
Good
Fair
Maintainability Easy
Medium
Complex
Uptime Uptime percentage 10%
99.9% and above
99% to 99.89%
Below 99%
Scalability Vertical
Horizontal
Backup and Easy
recovery
process
Medium
Complex

Coverage of Requirement Evaluation Criteria By Jitender

The tools and products proposed by the bidder/vendor can be evaluated on the Coverage of
Functional Requirements by one of the below 2 methods: -

Method 1 – MoSCoW prioritisation: -

Must Have Must have are critical features.

Should Have Should have are important but not necessary for implementation.
Could Have Could have are desirable but not necessary features.
Won't Have (Other Features) Won't Have features are the least-critical, lowest-payback items,
or not appropriate for current implementation

Based on the response provided by the vendor or discussion with the Vendors and further
hands-on experience on product/tool demo, each of features/functionality can be marked as
Available/ Workaround/ Customization or Not Available for each of tools.

The score key can be prepared for Evaluation

Method 2 – Mostly for unique new tools

Categorize the feature of the tool/product in the below types: -

Critical functionality
Important functionality
Nice-to-have functionality
Productivity features
Cost-saving features
Others