RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid) [Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 1 of 140 Request for Proposal (RFP) Document for Implementation of Integrated Health Management System (iHMS) with Telemedicine for the State of Rajasthan NIB Reference No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017 UBN:- RISL/17/OCB/231 Mode of Bid Submission Online though eProcurement/ e-Tendering system at http://eproc.rajasthan.gov.in Tendering Authority/ Purchaser Managing Director, RajCOMP Info Services Limited (RISL), First Floor, C- Block, Yojana Bhawan, Tilak Marg, C-Scheme, Jaipur (Rajasthan) Date, Time & Place of Pre-bid meeting 18-April-2017 at 11:30 AM Board Room, First Floor, C-Block, Yojana Bhawan, Tilak Marg, C-Scheme, Jaipur, Rajasthan Last Date & Time of Submission of eBid 12-May-2017 at 2:00 PM Date & Time of Opening of Technical e-Bid 12-May-2017 at 5:00 PM Cost of Tender Document: Rs. 5,000/- Only (Rupees Five Thousand Only) Name of the Bidding Company/ Firm: Contact Person (Authorised Bid Signatory): Correspondence Address: Mobile No. Telephone & Fax Nos.: Website & E-Mail: RajCOMP Info Services Limited (RISL) 1st Floor, Yojana Bhawan, Tilak Marg, C-Scheme, Jaipur (Rajasthan) Phone: 91 (141) 2229394, 5103902 Fax: 91 (141) 2228701 Website: http://risl.rajasthan.gov.in Email: [email protected]
140
Embed
Request for Proposal (RFP) Document for Implementation of ...
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 1 of 140
Request for Proposal (RFP) Document for Implementation
of Integrated Health Management System (iHMS) with
Selected Bidder is expected to carry out all ground work for implementation
including documentation, coordination with RISL and other stakeholders of the
project, site survey, etc. These reports or deliverables are to be submitted timely
by Selected Bidder to RISL to ensure timely and smooth execution of the project.
Certain key deliverables are identified for each of the parts/stages, which are
mentioned hereunder. However, Selected Bidder has to prepare and submit any
required information in form of Reports / excel sheet / document desired by RISL
related to Integrated HMS other than defined hereunder in the table.
The milestones and deliverables for the implementation of Integrated HMS will be
as follows:-
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 32 of 140
Component Group Activity Deliverables
Timelines (days) (T0- Date of Signing of
Agreement)
Payment Terms
Phase-1 (Group-1 to
Group-3)
Modules under Group-1 as
defined in section 4.2 of RFP
Preparation of SRS for Group-1 of Phase-1 of Integrated HMS Solution.
Design, Development, Beta version Testing, Deployment & UAT of Group-1 Modules
Integration with necessary applications, Development of Mobile application (Registration-OPD, Lab. Tests and MIS)
SRS and Design document
Test Cases document
UAT Signoff report of Group-1
T1= T0+ 100 days
11% of the Cost of Design and Development of Integrated HMS solution as per agreed cost of Serial No. 1 of Financial Bid.
Modules under Group-2 as
defined in section 4.2 of RFP
Preparation of SRS for Group-2 of Phase-1 of Integrated HMS Solution.
Design, Development, Beta version Testing, Deployment & UAT of Group-2 Modules
Integration with necessary applications
SRS and Design document
Test Cases document
UAT signoff report of Group-2
T2= T0+ 150 days
11% of the Cost of Design and Development of Integrated HMS solution as per agreed cost of Serial No. 1 of Financial Bid.
Modules under Group-3 as
defined in section 4.2 of RFP
Preparation of SRS for Group-3 of Phase-1 of Integrated HMS Solution.
Design, Development, Beta version Testing, Deployment & UAT of Group-3 Modules
Integration with necessary applications
SRS and Design document
Test Cases document
UAT signoff report of Group-3
T3= T0+ 180 days
11% of the Cost of Design and Development of Integrated HMS solution as per agreed cost of Serial No. 1 of Financial Bid.
ToT for Modules under Group-1 to
Group-3 of phase-1 as
defined in section 4.2 of RFP
Training of Trainers (ToT) for Group-1, Group-2 and Group-3 (Phase-1) of Integrated HMS
Attendance Record of various sessions of training conducted
T4= T0+ 190 days
As per actuals based on agreed cost of Serial No. 7 of Financial Bid.
Modules under Group-1 to
Group-3 of as defined in section
4.2 of RFP
Go-Live of all modules under all groups of Phase-1 of Integrated HMS solution on Internet/ Intranet
Go-Live Report
Safe to Host Certificate of Group-1 to Group-3
T5= T0+ 200 days
13% of the Cost of Design and Development of Integrated HMS solution as per agreed cost of Serial No. 1 of Financial Bid.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 33 of 140
Component Group Activity Deliverables
Timelines (days) (T0- Date of Signing of
Agreement)
Payment Terms
Phase-2 (Group-4 to Group-6)
Modules under Group-4 as
defined in section 4.2 of RFP
Preparation of SRS for Group-4 of Phase-1 of Integrated HMS Solution.
Design, Development, Beta version Testing, Deployment & UAT of Group-4 Modules
Integration with necessary applications
SRS and Design document
Test Cases document
UAT sign off report of Group-4
T6= T0+ 250 days
7% of the Cost of Design and Development of Integrated HMS solution as per agreed cost of Serial No. 1 of Financial Bid.
Modules under Group-5 as
defined in section 4.2 of RFP
Preparation of SRS for Group-5 of Phase-1 of Integrated HMS Solution.
Design, Development, Beta version Testing, Deployment & UAT of Group-5 Modules
Integration with necessary applications
SRS and Design document
Test Cases document
UAT signoff report of Group-5
T7= T0+ 300 days
7% of the Cost of Design and Development of Integrated HMS solution as per agreed cost of Serial No. 1 of Financial Bid.
Modules under Group-6 as
defined in section 4.2 of RFP
Preparation of SRS for Group-6 of Phase-1 of Integrated HMS Solution.
Design, Development, Beta version Testing, Deployment & UAT of Group-6 Modules
Integration with necessary applications
SRS and Design document
Test Cases document
UAT signoff report of Group-6 with Safe to Host Certificate
T8= T0+ 340 days
7% of the Cost of Design and Development of Integrated HMS solution as per agreed cost of Serial No. 1 of Financial Bid.
ToT for Modules under Group-4 to
6 of phase-2 as defined in section
4.2 of RFP
Training of Trainers (ToT) for Group-4, Group-5 and Group-6 (Phase-2) of Integrated HMS
Attendance Record of various sessions of training conducted
T9= T0+ 355 days
As per actuals based on agreed cost of Serial No. 7 of Financial Bid.
Modules under Group-4 to
Group-6 (Phase-2) as defined in
section 4.2 of RFP
Go-Live of all modules under all groups of Phase-2 of
Integrated HMS solution on Internet/ Intranet
Go-Live Report
Safe to host certificate of Group-1 to Group-3
T10= T0+ 365 days
13% of the Cost of Design and Development of Integrated HMS solution as per agreed cost of Serial No. 1 of Financial Bid.
Support & Maintenan
ce
Support & Maintenance of Integrated HMS Solution as per section 4.2.3
Integrated HMS Application Support and Maintenance (FMS)
Quarterly Support and Maintenance reports and Quarterly SLA attainment reports as per
T11= T10+ 90 days
T12= T10+ 180 days
T13= T10+ 270 days
T14= T10+ 365 days
1/4 of agreed support & maintenance cost as per Serial No. 2, 3, 4, 5 or 6 (for 1st, 2nd, 3rd, 4th or 5th
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 34 of 140
SLAs mentioned in section 7.2
+
T30= T10+ 1825 days
year respectively) of Financial Bid to be paid quarterly along with 1% of the Cost of Design, Development and Deployment of Integrated HMS solution as per agreed cost of Serial No. 1 of Financial Bid.
Data Migration
As Applicable Data Migration MIS Report indicating amount of data migrated
As described in Section 4.2.4
As per actuals per MB data migrated as per Serial No. 6 of Financial Bid.
Change Request
As Applicable Additional design and development / integration work as per change request.
As applicable
Based on actuals as per man-month rates as per Serial No. 5 of Financial Bid.
It may also be noted that the time schedule for each milestone shown in the table
above would be enforced independently. Any delay in the approval of the
deliverable(s) submitted by the Selected Bidder to RISL/ M&H Dept / ME Dept
shall not account for the delay on Selected Bidder’s part.
Selected Bidder has to design and implement a very detailed plan of
implementation that seeks to execute several activities in parallel, adopts Critical
Path Method so as to keep up with the overall deadline of implementation as
mentioned above. The time specified for delivery and other activities as
mentioned in the table above shall be deemed to be the essence of the contract
and the Selected Bidder shall arrange supplies and provide the required services
within the specified period
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 35 of 140
5. INSTRUCTION TO BIDDERS (ITB) & BIDDING PROCESS-
1. Sale of Bidding/ Tender Documents: The sale of bidding documents shall be
commenced from the date given in NIT. The complete bidding document shall also
be placed on the RISL and e-Procurement portal. The prospective bidders shall be
permitted to download the bidding document from the websites and pay its price
while submitting the Bid to the procuring entity.
2. Pre-bid Meeting/ Clarifications-
a) Any prospective bidder may, in writing, seek clarifications from the procuring
entity in respect of the bidding documents.
b) A pre-bid conference is also scheduled by the procuring entity as per the details
mentioned in the NIB and to clarify doubts of potential bidders in respect of the
procurement and the records of such conference shall be intimated to all bidders
and where applicable, shall be published on the respective websites.
c) The minutes and response, if any, shall be provided promptly to all bidders to
which the procuring entity provided the bidding documents, so as to enable those
bidders to take minutes into account in preparing their bids, and shall be
published on the respective websites.
3. Changes in the Bidding Document-
a) At any time, prior to the deadline for submission of Bids, the procuring entity may
for any reason, whether on its own initiative or as a result of a request for
clarification by a bidder, modify the bidding documents by issuing an addendum
in accordance with the provisions below.
b) In case, any modification is made to the bidding document or any clarification is
issued which materially affects the terms contained in the bidding document, the
procuring entity shall publish such modification or clarification in the same
manner as the publication of the initial bidding document.
c) In case, a clarification or modification is issued to the bidding document, the
procuring entity may, prior to the last date for submission of Bids, extend such
time limit in order to allow the bidders sufficient time to take into account the
clarification or modification, as the case may be, while submitting their Bids.
d) Any bidder, who has submitted his Bid in response to the original invitation, shall
have the opportunity to modify or re-submit it, as the case may be, within the
period of time originally allotted or such extended time as may be allowed for
submission of Bids, when changes are made to the bidding document by the
procuring entity:
Provided that the Bid last submitted or the Bid as modified by the bidder shall be
considered for evaluation.
4. Period of Validity of Bids-
a) Bids submitted by the bidders shall remain valid during the period specified in the
NIB/ bidding document. A Bid valid for a shorter period may be rejected by the
procuring entity as non-responsive Bid.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 36 of 140
b) Prior to the expiry of the period of validity of Bids, the procuring entity, in
exceptional circumstances, may request the bidders to extend the bid validity
period for an additional specified period of time. A bidder may refuse the request
and such refusal shall be treated as withdrawal of Bid and in such circumstances
bid security shall not be forfeited.
c) Bidders that agree to an extension of the period of validity of their Bids shall
extend or get extended the period of validity of bid securities submitted by them
or submit new bid securities to cover the extended period of validity of their bids.
A bidder whose bid security is not extended, or that has not submitted a new bid
security, is considered to have refused the request to extend the period of validity
of its Bid.
5. Format and Signing of Bids-
a) Bidders must submit their bids online at eProcurement portal i.e.
http://eproc.rajasthan.gov.in.
b) All the documents uploaded should be digitally signed with the DSC of authorized
signatory.
c) A Single Stage Two part/ cover system shall be followed for the Bid: -
i. Technical Bid, including fee details, eligibility & technical documents
ii. Financial Bid
d) The technical bid shall consist of the following documents: -
SNo. Documents Type Document Format
Fee Details
1. Bidding document Fee (Tender Fee) Proof of submission (PDF)
2. RISL Processing Fee (eProc) Instrument/ Proof of submission (PDF)
3. Bid Security (EMD) Instrument/ Proof of submission (PDF)
Eligibility Documents
4. Bidder’s Authorization Certificate As per Annexure-5 (PDF)
5. All the documents mentioned in the “Eligibility Criteria”, in support of the eligibility
As per the format mentioned against the respective eligibility criteria clause (PDF)
Technical Documents
6. Covering letter of the bid Annexure -2
7. Tender form Annexure-4
8. Certificate of Conformity/No deviation Annexure-7
9. Project references for pre-qualification and Technical Qualification Criteria
Annexure-11
10. CVs for evaluation in prescribed format Annexure-13
11. Technical Proposal including Understanding of Scope, Approach and Methodology and Work Plan
cases, etc. and maintaining records of Certificates issued by hospital
Facility to extract EMR of patient using his / her credentials / identity details
Facility to modify patient details after authorization of competent authority
Facility to track records related to and generate reports linked to System
usage report, Inward/Outward report, Stamp information report, Court case
report, MLC cases, National / State Human Rights Commission cases,
Vidhan Sabha / Lok Sabha Questions, RTI Cases, etc.
Facility to generate dynamic MIS Reports as per need
8.1.27 Real Time Management Information System (MIS)
An interactive module to meet the requirements of users according to their
roles
Overall performance of hospital
Outpatient Statistics – number, age and gender distribution, geographical
area of residence, speciality
Inpatient Statistics – number, age and gender distribution, geographical area
of residence, speciality
Facility to generate reports for Ward-wise day and night status of patients
Bed Occupancy Rate – overall and by speciality
Average Length of Stay – overall and by speciality
Turnover Interval – overall and by speciality
Operation statistics
Major, minor and total operations – overall and by speciality
Number of Medico-Legal Cases
Referrals – overall and by specialty
Death Rate of Patients – overall and by specialty / unit / ward
Cause of death – overall and by specialty
Net Death Rate of Hospital – overall and by specialty
Performance of RMRS
Revenue generation through User Charges
Expenditure incurred by RMRS
Expenditure incurred on patients exempt from User Charges
8.1.28 Telemedicine and PACS Module
Specialist End – Equipments integrated with this module for capturing
investigation data, for receiving investigations from Patient End and for
transmitting directions / orders
Patient End – Equipments integrated with this module for capturing
investigation data, for forwarding investigations to Specialist End including
PACS and for receiving directions / orders
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 102 of 140
Facility for Scheduling time for Telemedicine Consultation
Compliance with global standards like HL-7, ICD, MDDS and SNOMED CT,
LOINC, DICOM-3, NDC, DRG and HIPAA as and when applicable. The
telemedicine software should have the facility of processing of medical
images as per DICOM 3.0 standard. Interface to import and export to existing
HIS database in hospitals using appropriate file-based HL7 messages.
The GUI of the system should adhere to industry-accepted practice, which is
to be followed by the underlying platform. GUI with customizable forms to
enter patient demographic data, patient visits, etc. as a part of patient history
information.
Telemedicine solution should be of client-server architecture and should be
browser based, with access only after authorization using login process.
The telemedicine software shall be layered and module based. The
telemedicine solution should be based on Object-oriented, modular and
scalable architecture, designed as platform independent.
All screens of the system should have a consistent look. Every screen should
have date, time and station name, application name etc.
Option of customization of menus and format as per user requirement.
The product shall have an open API for integration and customization of
further modules with reference to the client requirements.
Should provide well defined and easy-to-use tools for operation and
maintenance activities like backup and restoration.
Should provide facilities for detailed logs, audit trails and other major user
activities.
Should have management information system feature of providing on-line and
off-line statistical information for monitoring the overall performance of the
system.
All such functions/data parameters, which may undergo changes from time to
time during the life of the software, should be kept in ‘User Table’ so that the
user can modify these.
Software threat concerns (virus attack, unauthorized login, hacked user name
and password, unauthorized network access, unauthorized access to data,
loss of data integrity, unauthorized tampering with network resources) need to
be addressed.
Video conferencing facility between patient end and doctor end.
The software architecture should be scalable so that any expansion in terms
of number of clients is easier and cost-effective. In case of server failure, the
patient-end software should be able to handle major tasks and store the
patient information in the local disk, which can be transferred to server end
upon link restoration. The software should be able to take care of the
redundancy in servers.
Support the normal network protocol stack, consisting of publicly available
and non-proprietary communication and database protocols.
Server applications to generate usage reports based on parameters.
The software shall have capability to work in a PKI environment for issuing
digitally signed including e-Sign medical prescription by doctor to the patients at
other remote location.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 103 of 140
System shall be database independent.
Database has to be on RDBMS structure.
Database capability / Support for storing multiple specialty hospitals
information with unique identification.
Database capability / Support for multiple specialty doctors under each
hospital with unique identification.
Database capability / Support for multiple remote hospitals with unique
identification.
Database capability / Support for multiple patients for each remote hospital
with a unique identification.
Server should have provision for data backup.
The solution should be interoperable with all existing medical systems of
Government of Rajasthan viz Arogya Online, Bhamashah Swasthya Bima
Yojana, Bhamashah Scheme
The solution should be interoperable with other vendor systems including the
transfer of complete patient information to other vendor system. Vendor should
supply list of interoperable systems from other vendors.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 104 of 140
Functional Requirements of Telemedicine software
Module Name Functionality Required
EMR/ e-health card
building capability
Provision for choosing a doctor from the available list of doctors
at the patient end hospital for Tele-consultation.
Functionality supporting the level 1 doctor to view the level 2
doctor’s recommendation upon login (from Patient End to
Specialist End and from all entrepreneur level to super speciality
end in case of emergency as depicted in the diagram above)
Identification of patient information / medical history at the level 2
with referred hospital with unique id for each patient.
Provision for patient’s multiple visits and previous medical
records should be accessible during follow-up.
Provision for follow up information of level 1 doctor and level 2
doctor of a patient for each visit.
Provision to import and export complete patient information from
client hospital to specialist hospital and vice versa.
The system should have capability to register a new patient with
the detailed information of the patient.
Multiple modalities such as X-RAY, MRI, Ultrasound, Blood
Reports, ECG, etc. should be supported.
Capability to add Inferences and Opinions of specialists.
For Web based software, it should be possible to upload and
download data by user.
Provision to include and view various image file formats (BMP,
JPG, etc.)
Provision to include and view various document file formats
(TXT, DOC, HTML etc.)
Provision to include Audio and Video files (AVI, MPEG, WAV,
etc.)
Provision to include unrecognized file formats
Electronic Medical Record shall allow import of text files,
physician notes and audio files.
Offline Data Transfer The system should have capability to send patient’s medical data
offline from one location to another.
The system should have capability to route data to other
specialist within and outside the site.
The system should have capability to send data at scheduled
times.
For Web based software/components, it should be possible to
send data to intended user for viewing.
System shall allow the specialist end to view/review the data
collected and forward their Inference/Opinion to patient-end
location by offline mechanism or during telemedicine interaction
itself.
Online Collaboration The system should have facilities in it such that a user should be
able to collaborate over same data over the communication
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 105 of 140
Module Name Functionality Required
network through the software.
It should be possible for a user to act over data and such action
shall be displayed to the other user.
It should provide features to distinguish between the action taken
by local and remote user.
System shall allow text-chat, desktop audio-video conference,
sharing of data, collaboration on shared data (like, white-board,
annotation, image operations, etc
Diagnostic Support Provide integrated data viewer of all supported formats (Images,
documents, DICOM-3, etc.)
Provide basic imaging operations and annotation on images.
Patient queuing feature should be available.
Centralized Data and
Services
The system should be able to centralize data on one system for
easier data handling and maintenance.
The system should be multi-user capable i.e. the user should not
be tied down to one system for usage. The end user should be
able to login from any location in the network where the software
is installed and access the centralized data. Also, more than one
user shall be able to use the system.
Proper security measures like user authentication, data edit and
delete privileges, administration privileges should be
incorporated into the system.
Capability to select different communication media for
connectivity to different sites or users must be present.
Interoperability with
other systems
The system should support the following standards for data
exchange using file or network based transfer mechanism:
o DICOM-3 (Part-10 file export & import, network
communication)
o HL7
The system should have the capability to integrate with
standards based systems, such as
o PACS
o HIS
o EMR / EHR Solution to build patient e-health card
o ICD-10
The Tele-Consultation Models that need to be supported by the
system are:
o Offline Data storage
o Store & Forward ability
o Integrated Real-Time collaboration over data
o Web-based data upload/download/view
System shall allow patient-end location to interact with specialist
end and vice versa by means of SecLAN Connectivity/
Broadband/ Lease Line link PSTN, ISDN, DSL, VSAT and
Ethernet (wired/wire-less) or any such suitable medium. The
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 106 of 140
Module Name Functionality Required
patient’s medical data will be forwarded by offline mechanism or
during telemedicine interaction.
MIS/Reports Personalized MIS Provision for doctor(s) to view list all patients
referred to him/her upon login and their status.
System should be able to provide predefined reports for
availability, space management, workload and operations.
The functions required are Patient file/ data/ image management,
using international standards (HL7), details on Diagnostic data,
reports generation & images.
Patient data: A readymade format to enter the required and
sufficient data on patient demography and medical history.
Support for report generation for all data entered by client (doctor
and patient ends) and prescription generation. (Report
generation printouts)
Patient file/data/image management, using relevant events of
CDA & ADT subsets of international standards (HL7)
Authentication of doctors at patient end and specialist end for the
data entry/retrieval/viewing.
Data protection and backup facility for super specialty hospital
and each client hospital attached connected to it should be
ensured.
Other Features: Standard operations supported by applications like printing
reports, help, and window operations, etc. should be provided.
Provide utilities to manage the application like configuration,
administration, backup/restore and reporting tool, etc.
Should support integration with Video conferencing facility
between patient end and doctor end.
All diagnostic equipments should have interface with
Telemedicine system and diagnostic result should automatically
enter in the Telemedicine system
Should support integration with medical equipments
Log of all-important activities be stored and monitored regularly.
Modification/ Alteration/ Deletion of patient data, clinical data and
images once authenticated should not be allowed.
Provision for server system administrator to enter and manage
doctor’s information including specialization and time of Tele-
consultation and as defined in HL7 to be entered at specialist
level.
Support for the following Industry and Medical Standards for data
acquisition, data viewing, data transfer and data transformation.
o Direct capture from devices, which are TWAIN compliant.
o Direct capture from video devices such as camera, which
are DirectX compliant.
o Capability to acquire a DICOM3 part 10 compliant file from
a DICOM device
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 107 of 140
8.2 Functional & Non Functional Requirement of Mobile Application: The mobile
application should be built on android, iOS, and windows platform. Mobile
Application will have following major (indicative) functionalities:
Scheduling an Appointment
Registration
List of Government Hospitals based on location, availability of beds,
availability of specialties/doctor, availability of specialty and super specialty
doctors (including OPD Roaster inquiry), availability of laboratory and
radiological tests, availability of ambulance, and real time status of
availability of different blood groups and components.etc.
Results of Laboratory and Radiological Investigations
MIS
Status of pending activities/ notifications visible user-wise
Facility for Specialist-end Doctor to issue instructions on mobile for treatment
of patient at Patient-end.
Non functional requirement for the Mobile Application
o Design the User Interface and User Experience to ensure that the
service is user friendly.
o Structure overall content to make it screen reader friendly.
o Design of consistent visual elements and Mobile Apps architecture that is
scalable and expandable.
o Resolution independent Mobile Apps that will automatically expand
/compress itself as per the screen resolution.
o Having some way for users to provide feedback on the mobile apps, a
quick way to report bugs or errors.
o Delivery should be in the form of a four published mobile applications on
each platform in the market place (Play store and Apple store)
o Integration with existing systems in governmental entities like SSO etc.
o The developed Mobile app should consider the performance measures in
terms of memory, CPU consumption.
o The user experience must be highly intuitive with push notifications and
smooth transitions between the Mobile App and 3rd party payment
services.
o The solution architecture should be able to address the future scalability
requirements, in terms of both application (to add new services) and
infrastructure and backend (adding more users).
o The solution architecture should be highly available and in harmony with
the existing backend systems. The solution should enforce network level
security, traffic to be encrypted using secured connectivity. The mobile
app should use token based authentication that is integrated with the
existing systems authentication services. The users can login through
Single Sign On Government of Rajasthan.
o The App should provide an update feature in case of newly published
version.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 108 of 140
8.3 Non Functional Requirement of Software solution- An indicative (this is only an
indicative and not an exhaustive list) requirement for the different modules for IT
solution for HMS is given below. Software solution will consist of different modules and
shall have a n-Tier architecture broadly comprising of following layers:
a. Presentation layer: It will provide a graphical way for users to interact with
the application. This will be the layer comprising all input form and reports.
This layer will be accessible through different devices like Computers,
PDA.UI should be screen responsive based on the devices used to view the
screens. User interfaces are implemented using different technologies to
render and format data for users and to acquire and validate data coming in
from them. This interface will be designed on user role based
authentication. User interface of all modules will support Unicode based Bi-
lingual versions (English and Hindi).
b. Business layer: It will facilitate communication between user interfaces
and database through predefined business rules of application modules.
This layer will provide middle ware supported application and tools.
Business layer will comprise of following components
Business Rules: It will define the business rules and support the business
processes and workflow. This layer will automate the processes. Each
module will have well-defined business logic and components for
implementation of business rules and performance of business tasks.
Web Services: Web services will provide a standard means of interoperating
between different software applications / modules. Web services share
business logic, data and processes through an interface.
c. Database Layer: Third layer, database abstraction layer is an application
programming interface which unifies communication between user
interface(s) and business layer(s). It will act on the queries submitted
though business rule / layer defined in the middleware and presentation
layer. The application and the services will be accessing data stored at
RSDC.
Additionally, Software solution shall have following features:
Content Management– Developed Web Portal shall be a dynamic portal
providing dynamic features for uploading / managing the content using the
stack mentioned in this RFP.
Document Management– Web Application developed for iHMS shall have
huge number of scanned documents as part of Pre-authorization requests
and for Claims Processing. Web Application shall provide comprehensive
functionality for searching, tagging of documents using the stack mentioned in
this RFP. The solution shall have facility for uploading documents, photos,
videos, etc.
Both Web Application and Web Portal will have a user access security layer.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 109 of 140
The Web Portal & Integrated HMS Web Application developed should be
compatible with all the common web browsers at least MS-Internet Explorer,
Google Chrome and Mozilla Firefox.
a) Integration with E-mail Gateway, SMS Gateway and Payment Gateway
E-mail gateway: Selected Bidder shall provide an interface for e-mail solution of
HMS with the newly built software solution.
SMS Gateway: The Software solution (Web Portal & Web Application) shall be
integrated with MSDG Gateway of Rajasthan, for automatically sending the
required details/ information through SMS to the designated officers of DHFW
and other stakeholders. Selected Bidder would be responsible for preparing
interfaces for integration with the MSDG Gateway and the proposed Software
solution.
Payment Gateway: Selected Bidder shall integrate the payment gateway(s) of
various banks/ Aggregators as decided by RISL, with the proposed Web Portal /
Application software, as required for HMS for facilitating online payments.
b) Web Portal: Web Portal shall be developed separately from the Web
Application as mentioned in this RFP titled “Software solution” above and
Web Portal shall have following functionalities
Web Portal shall be accessible to all citizens. Portal should allow any public user to
register on the Web Portal, the user should be permitted with defined role for
registered user. All the sections of the Web Portal would be of dynamic nature and
the contents of the Web Portal will be provided by Department of Medical, Health and
Family Welfare.
Web Portal envisaged should be multi lingual (both English and Hindi) and needs to
have the following:
o General Information about Integrated Health Management System
o Hospital details – name, address, contact details of hospital and of key officials, specialities and services available, no. of beds, etc.
o List and investigations done at the hospital
o List of doctors posted at the hospital along with their duty roster
o List of specialist doctor services available at hospital
Citizens shall have the following details on the Web Portal: Tenders section (as
per CVC no 29/09/2009 guidelines)
o Circulars and Notices with search facilities
o Track status of enquiries
o Progress Report
o Photo Gallery
o Feedback
o Downloads
o Sitemaps
o Terms of use
o Announcements
o Important notifications
o News and events
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 110 of 140
o Right to Information
o FAQ’s
o Important download of forms/legal documents
o Section for lodging grievances and tracking status of grievances
o Links to other related sites
o Integration of Payment Gateway
o Grievance
Portal Login:
Public Hospital login: Respective hospitals on logging in shall have following details:
o Details of the hospital
o Specialities available at the hospital and services provided through the hospital
o Speciality-wise number of beds available – occupied and vacant
o Details of patients admitted in the hospital
o Dashboard related to log-in ID
o Pending actions according to log-in ID
8.3.1 Additional Requirements
Additional Requirements: o Real Time MIS o System Wide Functionalities o System Management and User Management Requirements o Logs o Security Requirements o Legal and Regulatory Requirements o Interface Requirements o Common Technical Requirements
Integration Requirements: o UID Aadhaar (Biometric interface for Aadhaar authentication shall be
implemented for authentication devices of Make- Morpho, Secugen and Cogent)
o Bhamashah o E-Office o 108 ambulance o e-Mitra o Payment Gate Way o SMS Gate Way o E Mail Solution o e-Aushadhi o Existing Arogya Online o Rajasthan Sampark o Raj SSO o E-Vault o Additional Integration Requirement (If any)
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 111 of 140
Real Time Management Information System (MIS):
Requirement Description
Each user of Integrated HMS solution should have a customized MIS
view on logging into the system with key sections as-
• Activities pending
• Activities assigned
• MIS Reports
• Link to allowable modules/activities for particular User
System Management and User Management:
Requirement Description
Access
The Software solution should be accessible to
• Office user at head office with a user role
• Any other designated and authorized by DHFW / ME Dept
User management
The system should allow (admin user) creation and management of office
user with relevant details
The system should allow to create unique user name only
The system should provide feature to search a valid user name
The system should provide facility to block or unblock any office user
The system should allow admin user to create/modify user and roles and
privileges
New Hospital / Institution
The system should have facility to create new hospital/ institution with all
the relevant fields.
Designation Master
The system should have facility to create new designation
User Role
The system should provide facility to create user role as per the follows
• Office user at head office with a user role
• Principal Secretary, DHFW
• Joint / Special Secretary, DHFW
• Managing Director, Rajasthan Medical Services Corporation
• Mission Director, National Health Mission
• Additional Mission Director, National Health Mission
• Director (Public Health) / Director (RCH) / Director (AIDS)
• Additional Director (Hospital Administration)
• State Programme Manager, National Health Mission
• Demography and Evaluation Officer and Statistical Officers,
Directorate of Medical, Health and Family Welfare Services
• Office staff at Office of Joint Director (Medical & Medical) (Zone)
• Joint Director (M&H)
• Deputy Director (M&H)
• Office staff at Office of Chief Medical & Health Officer
• Chief Medical & Health Officer
• Deputy Chief Medical & Health Officer (Health)
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 112 of 140
• Deputy Chief Medical & Health Officer (Family Welfare)
• Office staff at government hospital
• Principal & Controller, Medical College with which the
hospital is attached, where applicable
• Medical Superintendent / Principal Medical Officer
• Operators at Investigations Registration Counter
• Operators in Departments conducting Laboratory
Investigations
• Operators in Radiology Department (for X-Ray, Ultrasound,
MRI, CT Scan, etc)
• Operators and doctors in Echocardiography / ECG Labs
• Operators in Wellness and Screening Clinics
• Operators and doctors in Telemedicine Unit – at Specialist
End and at Patient End
• Operators in different sections of the hospital
• Operators at Billing Counter
• Nursing Superintendent
• Dealing Assistant, Rajasthan Medicare Relief Society
• Operators in Mortuary / Medicolegal Section
• Operators in other sections of the hospitals (list to be
collected as part of SRS from Department of Medical, Health
and Family Welfare)
• Applicant
• Any other as specified by DHFW
• Common citizen who will be able to view his / her e-Health Card
based on his / her Bhamashah / Aadhaar Card after due verification
Assign Role to user
The system should allow system to assign user role to each user,
Additional Requirements:
Business Requirement Description
System Wide Functionalities
Web Application and Web Portal shall be modular in design and shall be designed using modular and reusable programming techniques for ease of maintenance.
Web Application and Web Portal shall have the capability to format output to support HTML, XML, text for data exchange/integration with various entities involved in the process.
Web Application and Web Portal shall be designed to permit easy insertion of new modules and new enhancements.
Web Application and Web Portal shall have the capability to complete all
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 113 of 140
requests (e.g., store, retrieve, update, etc.) without any data loss
Web Application and Web Portal shall maintain an audit log in of each transaction
Web Application and Web Portal shall have the capability to define and modify Client’s access privileges.
Web Application and Web Portal shall use open systems, standard-based architecture to meet functional requirements and to inter-operate with existing information systems.
Data inputs to the Web Application and Web Portal shall be validated prior to being processed
Input data shall be validated for out of range values, missing or incomplete data, and unauthorized or inconsistent control data.
Web Application shall prevent unauthorized users from accessing the system.
Registered users in Web Portal and Web Application shall be allowed to log-on only to those functions which they are authorized to access and use.
The logon process shall deny access if either the username or password is invalid without identifying the specific erroneous element.
The password management system shall include non-display of the password when being entered
The password management system shall require the storage of passwords in encrypted form.
Web Application and Web Portal shall have the capability to search and analyze payment transactions for enforcement purposes
The Software solution shall be capable of generating event notifications and interfacing with E-mail system and must support e-mail triggers as part of the solution’s workflow.
The product/project/application should not be specific hardware dependent.
Audit trail should be maintained, all deleted & edited records should be traceable and copy of all editions/ deletions should be available. The audit trail should be preserved in securely and No user other than authorized should be allowed to modify audit record.
Software solution shall maintain the life cycle of all the contents. The functionality should provide at least two features for lifecycle automation: (a) The ability to conduct scheduled releases of content and (b) The ability to set expiration date for a content element. Both automated processes ensure that content is published and expired on time, without manual intervention. CMS shall also provide facility for archival of historical records.
Proposed Deployment Architecture- o Software solution shall be deployed at RSDC. Selected Bidder shall deploy iHMS on middleware provided by RSDC to meet the functional requirements of Integrated HMS. o Selected Bidder may be asked to deploy the Web Application and Web Portal on RSDC cloud if the same is operational. o The traffic from all hospitals using Integrated HMS and other points like e-Mitra kiosks, etc would arrive at the central site i.e. RSDC, Jaipur. Sufficient internet bandwidth will be provided by RISL at RSDC, Jaipur for the Web/ Application Server access by the department officials and citizens.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 114 of 140
o DHFW shall be connecting RSDC, its Head office and its hospitals through sufficient WAN connectivity (preferably VPN). All the routing/ switching hardware and LAN at offices shall be done by DHFW.
Proposed Security Architecture o Envisaged security architecture for the Software solution for Integrated HMS is as provided below:
a) User Level Security: Restricted areas of the application should only
be accessible through pre-defined user access rights.
b) Developed Software solution should support both HTTP and HTTPS
(5 128 bit SSL certificate to be deployed by the Selected Bidder on the
Servers for the entire project duration)
c) Application Level Security: Application shall have Role based
access, encryption of user credentials and storing of user credentials
for users in separate repositories. Application level security controls
should be provisioned in the application for following
Prevent SQL Injection Vulnerabilities for attack on database
Prevent XSS Vulnerabilities to extract user name password
Secure Authentication and Session Management control functionality shall be
Prevent Failure to Restrict URL Access Vulnerabilities (By providing
authentication and authorization for each sensitive page, use role-based
authentication and authorization and make authentication and authorization
policies configurable
Prevent Insufficient Transport Layer Protection Vulnerabilities
Prevent invalidated Redirects and Forwards Vulnerabilities
d) Apart from the above:
To design web portal & application software, SI shall make use of eSAFE: e-
Governance Security Assurance Frame Work Guidelines for Implementation
of Security Controls issued by the Department of Electronics and Information
Technology (DeitY), Ministry of Communications & IT (MCIT), Government of
India”.
8.3.2 Approach and Methodology to be followed- The Selected Bidder is expected
to use industry standard design documents/ templates, coding practices for
development/ customization of Software solution. The technology / platform /
stack for development of Software solution is mentioned in this RFP. The
Selected Bidder is strictly to use this stack for the development/ customization.
8.3.3 Data Sizing, Named Users & Concurrency of Data- Data related to an
estimated 50 Crore to 70 Crore episodes will be entered into the system
annually – through different hospitals and through outreach services. The
estimated number of concurrent users will be about 10,000. However, this is
only an indicative number and the Successful Bidder will be required to assess
the number of estimated beneficiaries along with number of concurrent users
whose health-related data will be entered in the integrated HMS. Each hospital /
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 115 of 140
health institution (public and interested private hospitals / health institutions)
associated with integrated HMS shall have a login in the Web Portal which shall
be used to access the portal. Web portal shall also however be referred by the
citizens / unnamed users for getting relevant information.
Around 16,200 (± 500) government hospitals (as indicated below) shall be
using the internal Web Application for performing various functionalities in the
Software solution.
S.No. Type of Health Institution Number
1. Hospitals attached to Medical Colleges 34
2. District Hospitals / Sub-District Hospitals / Satellite Hospitals 58
3. Community Health Centers (CHCs) 568
4. Primary Health Centers / City Dispensaries 2,282
5. Subcenters 13,227
About 1,000 officers will also access the application for performing various
functionalities in the software solution from block level up to State level.
Provision for use of software by about 500 private hospitals / other private
health facilities or institutions would also have to be made.
The Selected Bidder is expected to carry out an independent exercise to see
that the conceptual design proposed to be provided by the Selected Bidder is
capable to meet RISL requirements including the performance requirements
and service level standards. Any major IT item required for meeting the
requirements of the bid should be pointed out by the Selected Bidders during
the pre-bid conference. After pre-bid conference, no such observations on RFP
shall be accepted.
8.3.4 Analytical Engine-
The system must have analytics engine to generate aggregate indicators at
various levels (facility, block, district, state etc.). This includes aggregating
patient level clinical information on- services, procedures, activities, diseases
in addition to administrative information such as human resources distribution,
service availability, and service quality etc. from the facilities participating in to
the iHMS. The dashboard should also be able to present all transaction
related information. The analytics should be made available for the individual
facilities and providers. The analytics engine should also facilitate analysis of
information contained in the registries (patient, provider, facility).
The Dashboard should provide role-based access to various levels of users
as per their role into the system.
The user should be able to drill-down, slice, dice, roll-up and pivot data
(OLAP) and compare data up to the most granular level as per the need. The
system should be able to define data marts and generate different kind of
static and dynamic reports based on the user needs.
It should also be possible that Dashboard provide ability to generate various
types of charts and graphs which can be customized by the users as per the
need.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 116 of 140
The Dashboard should support map-based analysis where data (multiple
indicators) could be plotted over maps where it can be drilled down up to
most granular level on the map.
The user should be able to generate, export and save data, report in PDF,
Excel, CSV format which could be printed or shared with the various users
outside of the system.
The Dashboard should be able to conduct population level analytics using
multiple query combinations and detect the presence of infectious diseases/
change in pattern for any disease, symptom etc. at an early stage of an
outbreak in addition it should provide insights into the patterns and trends of
disease throughout a population group.
It is also suggested that the dashboard should also be able to provide
aggregate information on specific queries which could be drilled-down up to
the most granular level.
The system must be able to generate standard and custom reports. All public
health program reports that are mandatory for submission to the concerned
departments should be generated from the system. There should be flexibility
to the users to create their own reports based on the need.
Functional requirement specifications provided above for various modules are only indicative
parameters and more parameters might be included depending upon the assessment done
by Selected Bidder during consultations with users and policy makers of DHMF / ME Dept.
Web Application and Web Portal developed by the Selected Bidder shall meet relevant
policies of DoIT&C and policies specified by DeiTy, Government of India for Web Application
development.
The solution architecture, deployment architecture and security architecture provided in the
RFP is indicative and purely for understanding of the Selected Bidder; however, Selected
Bidder will have to use the software development stack inclusive of Software solution,
middleware, database, etc mentioned in chapter 4.
Application and Web Portal shall as bilingual (English and Hindi). The users should see the
labels and captions on selected language and additionally be able to feed-in their data in
English language. Also, the SI must translate, at its own, the equivalent Hindi Captions for
the English version (without altering the meaning) of the Web Portal and the Software
solution and the same must be submitted to RISL for approval before implementation/
uploading or vice versa.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 117 of 140
ANNEXURE-2 - COVERING LETTER OF THE BID
(To be submitted on the Company Letter head of the Tenderer, sealed and signed)
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
[Reference No. F 4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017]
Dear Sir,
Ref: Request for Proposal (RFP) Notification dated............... No..........
1. I/We, the undersigned bidder, Having read & examined in detail, the Bid Document, the receipt of which is hereby duly acknowledged, I/ we, the undersigned, offer to supply/ work as mentioned in the Scope of the work, Technical specifications, Service Level Standards & in conformity with the said bidding document for the same.
2. I/ We hereby declare that our bid is made in good faith, without collusion or fraud and the information contained in the bid is true and correct to the best of our knowledge and belief.
3. I/ we hereby submit our token of acceptance to all the tender terms & conditions without any deviations. Hence, we are hereby submitting our Bid and offer to provide services to Purchaser for carrying out the project in accordance with your RFP.
4. Until a formal contract is prepared and executed, this bid, together with your written acceptance thereof and your notification of award shall constitute a binding Contract between us.
5. I/We agree to abide by this RFP for a period of days as specified in the NIT from the closing date fixed for submission of bid as stipulated in the RFP document.
6. I/ We undertake, for timely establishment of a local office in Jaipur (if the award is made to us) and within 30 days from the date of issue of Work Order.
Or
(strike out whichever is not applicable)
We have an existing office at Jaipur at the following address: ...........................................
7. I/We understand that the Purchaser is not bound to accept any bid received in response to this RFP.
8. In case we are engaged by the Purchaser, we shall provide any assistance/cooperation required by Purchaser, appointed auditing agencies (if any), state government officials and Other Stakeholders of the project for performing their duties with respect to this project. We understand that our non-cooperation for the same shall be grounds for termination of service.
Signature…………………
In the capacity of………………………
Duly authorised to sign Proposal for And on behalf of………………………..
Seal of the Organization: -
Date………………….. Place………………….
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 118 of 140
ANNEXURE-3 - PRE- BID QUERIES FORMAT
[Reference No. F 4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017]
Name of the Company/Firm:
Name of Person(s) Representing the Company/ Firm:
Name of Person Designation Email-ID(s) Tel. Nos. & Fax Nos.
Company/Firm Contacts:
Contact Person(s) Address for
Correspondence
Email-ID(s) Tel. Nos. & Fax Nos.
Query / Clarification Sought:
Sl. No. RFP
Page No.
RFP
clause
No.
Clause Details Query/ Suggestion/
Clarification
Note: - Queries must be strictly submitted only in the prescribed format (.XLS/ .XLSX/
.ODF/.doc/.docx). Queries not submitted in the prescribed format will not be considered/
responded at all by the tendering authority
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 119 of 140
ANNEXURE-4 - TENDER FORM
[Reference No. F 4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017]
• Addressed to:
Name of the Tendering Authority Managing Director, RajCOMP Info Services Limited (RISL)
Address First Floor, Yojana Bhawan, Tilak Marg, C-Scheme, Jaipur
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 120 of 140
ANNEXURE-5- BIDDER’S AUTHORIZATION CERTIFICATE
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
[Reference No. F 4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017]
I/ We <Name/ Designation> hereby declare/ certify that <Name/ Designation> is hereby
authorized to sign relevant documents on behalf of the company/ firm in dealing with Tender/
NIB reference No. ______________________ dated _________. He/ She is also authorized
to attend meetings & submit technical & commercial information/ clarifications as may be
required by you in the course of processing the Bid. For the purpose of validation, his/ her
verified signatures are as under.
Thanking you,
Name of the Bidder: - Verified Signature:
Authorised Signatory: -
Seal of the Organization: -
Date:
Place:
Please attach the board resolution / valid power of attorney in favour of person
signing this authorizing letter.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 121 of 140
ANNEXURE-6 - SELF-DECLARATION – NO BLACKLISTING
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
In response to the NIB Ref. No. _____________________________ dated ___________ for
{Project Title}, as an Owner/ Partner/ Director/ Auth. Sign. Of
____________________________________, I/ We hereby declare that presently our
Company/ firm _________________, at the time of bidding: -
a. possess the necessary professional, technical, financial and managerial resources and competence required by the Bidding Document issued by the Procuring Entity;
b. have fulfilled my/ our obligation to pay such of the taxes payable to the Union and the State Government or any local authority as specified in the Bidding Document;
c. is having unblemished record and is not declared ineligible for corrupt & fraudulent practices either indefinitely or for a particular period of time by any State/ Central government/ PSU/ UT.
d. does not have any previous transgressions with any entity in India or any other country during the last three years
e. does not have any debarment by any other procuring entity f. is not insolvent in receivership, bankrupt or being wound up, not have its affairs
administered by a court or a judicial officer, not have its business activities suspended and is not the subject of legal proceedings for any of the foregoing reasons;
g. does not have, and our directors and officers not have been convicted of any criminal offence related to their professional conduct or the making of false statements or misrepresentations as to their qualifications to enter into a procurement contract within a period of three years preceding the commencement of the procurement process, or not have been otherwise disqualified pursuant to debarment proceedings;
h. does not have a conflict of interest as mentioned in the bidding document which materially affects the fair competition.
i. will comply with the code of integrity as specified in the bidding document.
If this declaration is found to be incorrect then without prejudice to any other action that may be taken as per the provisions of the applicable Act and Rules thereto prescribed by GoR, my/ our security may be forfeited in full and our bid, to the extent accepted, may be cancelled
Thanking you,
Name of the Bidder: -
Authorised Signatory: -
Seal of the Organization: -
Date:
Place:
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 122 of 140
ANNEXURE-7 - CERTIFICATE OF CONFORMITY/ NO DEVIATION
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
[Reference No. F 4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017]
CERTIFICATE
This is to certify that, the specifications of Software which I/ We have mentioned in the
Technical bid, and which I/ We shall supply if I/ We am/ are awarded with the work, are in
conformity with the minimum specifications of the bidding document and that there are no
deviations of any kind from the requirement specifications.
Also, I/ we have thoroughly read the tender/ bidding document and by signing this certificate, we hereby submit our token of acceptance to all the tender terms & conditions of the bidding document
without any deviations.
I/ We also certify that the price I/ we have quoted is inclusive of all the cost factors involved
in the end-to-end implementation and execution of the project, to meet the desired
Standards set out in the Tender/ bidding Document.
Thanking you,
Name of the Bidder: -
Authorised Signatory: -
Seal of the Organization: -
Date:
Place:
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 123 of 140
ANNEXURE-8 - FINANCIAL BID FORMAT
(To be filled by the bidder in BoQ (.XLS file) on eProc website with a cover letter on his
Letter head)
To,
The Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur-302005 (Raj.)
[Reference No. F 4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017]
Sir,
We, the undersigned bidder, Having read & examined in detail, the Bidding Document, the
receipt of which is hereby duly acknowledged, I/ we, the undersigned, offer to supply/ work
as “System Integrator/ Implementing Agency/ Selected Bidder” as per the defined Scope of
the work, Technical specifications, Service Level Standards & in conformity with the said
bidding document for the same. We hereby offer our best price as per the details below and
would be valid as per the details mentioned in the NIT.
I/ We undertake that the prices are in conformity with the specifications/ requirements
prescribed. The price quoted is inclusive of all cost likely to be incurred for executing this
work. The prices are inclusive of all type of govt. taxes/ duties as asked in the financial bid
I/ We undertake, if our bid is accepted, to deliver the goods and services in accordance with
the requirements of RISL mentioned in the bidding document.
I/ We hereby declare that, in case, the contract is awarded to us, we will submit the
performance security for the due performance of contract and in the form prescribed by
RISL.
I/ We agree to abide by this bid for a period of days specified in NIT, after the last date fixed
for bid submission and it shall remain binding upon us and may be accepted at any time
before the expiry of that period.
Until a formal contract is prepared and executed, this bid, together with your written
acceptance thereof and your notification of award shall constitute a binding Contract
between us.
I/ We hereby declare that our bid is made in good faith, without collusion or fraud and the
information contained in the bid is true and correct to the best of our knowledge and belief.
We understand that you are not bound to accept the lowest or any bid you may receive.
We agree to all the terms & conditions as mentioned in the bidding document and submit
that we have not submitted any deviations in this regard.
Date:
Authorized Signatory:
Seal of the Organization:
Name:
Designation:
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 124 of 140
Financial Bid Format (Rates to be entered in Eproc Portal Only)
Item
No.
Item Description
Qty. Units
Per Unit Rate in INR (incl. all incidental charges and all Taxes but excl. Service Tax)
Total (incl. all incidental charges and all Taxes but excl. Service Tax)
1 2 3 4 5 6=5X3
1. Design, Development and Deployment of Integrated Health Management System (including Telemedicine and PACS)
1 No.
2. Support & Maintenance Cost of integrated HMS Software Solution for 1st year
1 Year
3. Support & Maintenance Cost of integrated HMS Software Solution for 2nd year
1 Year
4. Support & Maintenance Cost of integrated HMS Software Solution for 3rd year
1 Year
5. Support & Maintenance Cost of integrated HMS Software Solution for 4th year
1 Year
6. Support & Maintenance Cost of integrated HMS Software Solution for 5th year
1 Year
7. Composite man-month rates of resources to handle Change requests during Support & Maintenance Period
100 Man-Month
8. Data Migration Cost 153600 MB
9. Cost of Providing Training on Software solution as per scope of Work
5,000 Per Person per day
***Sub-Total in Figures
***Sub-Total in Words
Note- 1. Wherever per unit cost has been asked, payment shall be made on actual work done. 2. Cost towards telemedicine h/w mentioned at clause 4.2.14 is inclusive in the item no. 1 3. Cost of any hardware/ tool required to prove the functionality as per FRS is to be included in item
no. 1 and no separate/ additional cost will be claimed by the selected bidder.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 125 of 140
ANNEXURE-9- BANK GUARANTEE FORMATs
BANK GUARANTEE FORMAT – BID SECURITY
(To be stamped in accordance with Stamp Act and to be issued by a Nationalized/
Scheduled bank having its branch at Jaipur and payable at par at Jaipur, Rajasthan)
To,
The Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, C-Block, Tilak Marg, C-Scheme, Jaipur-302005 (Raj).
Sir,
1. In accordance with your Notice Inviting Bid for <please specify the project title> vide NIB
reference no. <please specify> M/s. …………………………….. (Name & full address of
the firm) (Hereinafter called the “Bidder”) hereby submits the Bank Guarantee to
participate in the said procurement/ bidding process as mentioned in the bidding
document.
It is a condition in the bidding documents that the Bidder has to deposit Bid Security
amounting to <Rs. ______________ (Rupees <in words>)> in respect to the NIB Ref.
No. _______________ dated _________ issued by RISL, First Floor, Yojana Bhawan,
C-Block, Tilak Marg, C-Scheme, Jaipur, Rajasthan (hereinafter referred to as “RISL”) by
a Bank Guarantee from a Nationalised Bank/ Scheduled Commercial Bank having its
branch at Jaipur irrevocable and operative till the bid validity date (i.e. <please specify>
days from the date of submission of bid). It may be extended if required in concurrence
with the bid validity.
And whereas the Bidder desires to furnish a Bank Guarantee for a sum of <Rs.
______________ (Rupees <in words>)> to the RISL as earnest money deposit.
2. Now, therefore, we the ……………………………….…… (Bank), a body corporate
constituted under the Banking Companies (Acquisition and Transfer of Undertaking) Act.
1969 (delete, if not applicable) and branch Office at…………………... (Hereinafter
referred to as the Guarantor) do hereby undertake and agree to pay forthwith on
demand in writing by the RISL of the said guaranteed amount without any demur,
reservation or recourse.
3. We, the aforesaid bank, further agree that the RISL shall be the sole judge of and as to
whether the Bidder has committed any breach or breaches of any of the terms costs,
charges and expenses caused to or suffered by or that may be caused to or suffered by
the RISL on account thereof to the extent of the Earnest Money required to be deposited
by the Bidder in respect of the said bidding document and the decision of the RISL that
the Bidder has committed such breach or breaches and as to the amount or amounts of
loss, damage, costs, charges and expenses caused to or suffered by or that may be
caused to or suffered by the RISL shall be final and binding on us.
4. We, the said Bank further agree that the Guarantee herein contained shall remain in full
force and effect until it is released by the RISL and it is further declared that it shall not
be necessary for the RISL to proceed against the Bidder before proceeding against the
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 126 of 140
Bank and the Guarantee herein contained shall be invoked against the Bank,
notwithstanding any security which the RISL may have obtained or shall be obtained
from the Bidder at any time when proceedings are taken against the Bank for whatever
amount that may be outstanding or unrealized under the Guarantee.
5. Any notice by way of demand or otherwise hereunder may be sent by special courier,
telex, fax, registered post or other electronic media to our address, as aforesaid and if
sent by post, it shall be deemed to have been given to us after the expiry of 48 hours
when the same has been posted.
6. If it is necessary to extend this guarantee on account of any reason whatsoever, we
undertake to extend the period of this guarantee on the request of our constituent under
intimation to you.
7. The right of the RISL to recover the said amount of <Rs. ______________ (Rupees <in
words>)> from us in manner aforesaid will not be precluded/ affected, even if, disputes
have been raised by the said M/s. ……….………………(Bidder) and/ or dispute or
disputes are pending before any court, authority, officer, tribunal, arbitrator(s) etc..
8. Notwithstanding anything stated above, our liability under this guarantee shall be
restricted to <Rs. ______________ (Rupees <in words>)> and our guarantee shall
remain in force till bid validity period i.e. <please specify> days from the last date of bid
submission and unless a demand or claim under the guarantee is made on us in writing
within three months after the Bid validity date, all your rights under the guarantee shall
be forfeited and we shall be relieved and discharged from all liability thereunder.
9. This guarantee shall be governed by and construed in accordance with the Indian Laws
and we hereby submit to the exclusive jurisdiction of courts of Justice in India for the
purpose of any suit or action or other proceedings arising out of this guarantee or the
subject matter hereof brought by you may not be enforced in or by such count.
10. We hereby confirm that we have the power/s to issue this Guarantee in your favor under
the Memorandum and Articles of Association/ Constitution of our bank and the
undersigned is/are the recipient of authority by express delegation of power/s and
has/have full power/s to execute this guarantee under the Power of Attorney issued by
the bank in your favour.
Date ………………… (Signature) ……………………………………….
Place ………………… (Printed Name) ………………………………….
(Designation) ……………………………………
(Bank’s common seal) ………………………….
In presence of:
WTTNESS (with full name, designation, address & official seal, if any)
(1) ………………………………………
………………………………………
(2) ………………………………………
………………………………………
Bank Details
Name & address of Bank:
Name of contact person of Bank:
Contact telephone number:
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 127 of 140
GUIDELINES FOR SUBMISSION OF BANK GUARANTEE
The Bank Guarantee shall fulfil the following conditions in the absence of which they cannot
be considered valid: -
1. Bank Guarantee shall be executed on non- judicial stamp paper of applicable value
purchased in the name of the bank.
2. Two persons should sign as witnesses mentioning their full name, designation, address
and office seal (if any).
3. The Executor (Bank Authorities) may mention the power of attorney No. and date of
execution in his/ her favour authorizing him/ her to sign the document. The Power of
Attorney to be witnessed by two persons mentioning their full name and address.
4. The Bank Guarantee should be executed by a Nationalized Bank/ Scheduled
Commercial Bank only.
5. Non – Judicial stamp paper shall be used within 6 months from the date of Purchase of
the same. Bank Guarantee executed on the non-judicial stamp paper after 6 (six)
months of the purchase of such stamp paper shall be treated as non-valid.
6. The contents of Bank Guarantee shall be strictly as per format prescribed by RISL
7. Each page of Bank Guarantee shall bear signature and seal of the Bank and B.G.
number.
8. All corrections, deletions etc. in the Bank Guarantee should be authenticated by
signature of Bank Officials signing the Bank Guarantee.
9. Bank should separately send through registered post/courier a certified copy of Bank
Guarantee, mentioning Bid reference, Bid title and bidder name, directly to the
Purchaser at the following address:
BANK GUARANTEE FORMAT – PERFORMANCE SECURITY (PBG)
(To be stamped in accordance with Stamp Act and on a Stamp Paper purchased from Rajasthan State only and to be issued by a Nationalized/ Scheduled bank having its branch at Jaipur and payable at par at Jaipur, Rajasthan)
To,
The Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, C-Block, Tilak Marg, C-Scheme, Jaipur-302005 (Raj).
1. In consideration of the RajCOMP Info Services Limited (hereinafter called "RISL") having
agreed to exempt M/s ..........................(hereinafter called "the said Contractor(s)" from
the demand, under the terms and conditions of an Agreement
No..................................dated .....................made between the RISL through
…………………… and .......................(Contractor) for the work .................(hereinafter
called "the said Agreement") of Security Deposit for the due fulfilment by the said
Contractor (s) of the terms and conditions contained in the said Agreement, on
production of a Bank Guarantee for Rs...................(rupees
........................................only), we ...................(indicate the name of the Bank),
(hereinafter referred to as "the Bank") at the request of ..................Contractor(s) do
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 128 of 140
hereby undertake to pay to the RISL an amount not exceeding
Rs...................(Rupees..................................only) on demand.
2. We................. (Indicate the name of Bank), do hereby undertake to pay Rs....................
(Rupees............................only), the amounts due and payable under this guarantee
without any demur or delay, merely on a demand from the RISL. Any such demand
made on the bank by the RISL shall be conclusive as regards the amount due and
payable by the Bank under this guarantee. The Bank Guarantee shall be completely at
the disposal of the RISL and We....................... (Indicate the name of Bank), bound
ourselves with all directions given by RISL regarding this Bank Guarantee. However, our
liability under this guarantee shall be restricted to an amount not exceeding
• 2+ years of post-qualification and relevant work experience
as Software Development/ Testing
8 Helpdesk
Executive
Onsite • Graduate in any discipline from a Govt. recognized
university
• Fluency in English/ Hindi
• 1+ years of relevant work experience in desired field
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 135 of 140
ANNEXURE 13- FORMAT FOR CVs OF KEY PROFILES
[Reference No. F 4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017]
Format for the Profiles
Name of the person
Current Designation / Job Title
Current job responsibilities
Proposed Role in the Project
Proposed Responsibilities in the Project
Academic Qualifications: • Degree • Academic institution graduated from • Year of graduation • Specialization (if any) • Key achievements and other relevant information (if any)
Professional Certifications (if any)
Total number of years of experience
Number of years with the current company
Summary of the Professional / Domain Experience
Number of complete life cycle implementations carried out
The names of customers (Please provide the relevant names)
Past assignment details (For each assignment provide details regarding name of organizations worked for, designation, responsibilities, tenure) Prior Professional Experience covering: • Organizations worked for in the past
• Organization name • Duration and dates of entry and exit • Designation • Location(s) • Key responsibilities
• Prior project experience • Project name • Client • Key project features in brief • Location of the project • Designation • Role • Responsibilities and activities • Duration of the project • Total team size
Please provide only relevant projects.
Proficient in languages (Against each language listed indicate if read/write/both)
Date:
Authorized Signatory:
Seal of the Organization:
Name:
Designation:
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 136 of 140
ANNEXURE-14- MEMORANDUM OF APPEAL UNDER THE RTPP ACT, 2012
Appeal No ………of ……………
Before the ………………………… (First/ Second Appellate Authority)
• Particulars of appellant:
• Name of the appellant: <please specify>
• Official address, if any: <please specify>
• Residential address: <please specify>
• Name and address of the respondent(s):
• <please specify>
• <please specify>
• <please specify>
• Number and date of the order appealed against and name and designation of the officer/ authority who passed the order (enclose copy), or a statement of a decision, action or omission of the procuring entity in contravention to the provisions of the Act by which the appellant is aggrieved: <please specify>
• If the Appellant proposes to be represented by a representative, the name and postal address of the representative: <please specify>
• Number of affidavits and documents enclosed with the appeal: <please specify>
• Grounds of appeal (supported by an affidavit): <please specify>
• Prayer: <please specify>
Place …………………………………….
Date ……………………………………
Appellant's Signature
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 137 of 140
ANNEXURE-15- ROLE OF RSDC (Rajasthan State Data Centre)
[Reference No. F 4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017]
• RSDC is the focal point of Integrated HMS ICT infrastructure. The core infrastructure of
Software solution (Web Application and Web Portal both) is expected to be hosted at the
RSDC. The data collected from all empanelled hospitals (public and private) covered
under Integrated HMS will be centrally stored at the RSDC.
• All services, applications and infrastructure to provide efficient delivery of G2G and G2C
services will be consolidated on RSDC.
• RSDC will be responsible to manage all servers and infrastructure to be use for
deployment of Software solution.
• RSDC will provide infrastructure such as firewall, Intrusion Detection/ Prevention,
service, directory service, management and data storage services, which could be a
shared infrastructure to all the applications /departments in the RSDC.
• RSDC shall provide required ports for application load balancers to configure Software
solution in high availability active-active mode.
• The RSDC will provide existing EMS server and tools for the SLA management, in
respect to monitor application downtime and application performance.
• RSDC will provide SAN Storage, high speed (Fibre Channel)
• RSDC will provide all SAN related infrastructure (e.g. SAN switch) for sharing to the
successful bidder.
• RSDC will provide SAN and Tape library support for data storage.
• Some of the key functionalities of RSDC are Central Data Repository of the State,
Secure Data Storage, Disaster Recovery, Remote Management and Service Integration.
• RSDC will provide required physical and remote access to Selected Bidder for
monitoring the Software solution applications at RSDC.
• RSDC Team will take the required backups of application and database as per its
policies
• RSDC will provide required number of Internal and external IP at data centre for the
Integrated HMS Web application and web portal.
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 138 of 140
ANNEXURE-16- TECHNICAL PROPOSAL
This section should present bidders’ proposed solution meeting technical and functional
requirements outlined in this RFP document. Bidders are required to present sound,
complete, and competent technical and functional architecture solution and are expected to
address the various technical / functional parameters mentioned in this RFP document in
their proposed solution. The section should also include the Bill of Materials (BOM) for all the
software components, products and tools that are proposed for the application development,
testing, deployment and maintenance. The solution description should minimally include the
following:
a) Bidder’s understanding of the requirements as stated in the RFP. Compliance to all the
functional requirements as specified in the RFP.
b) Detailed Solution design: Should be presented in the following format
Development approach, methodology and plan
Testing approach, methodology and plan
Project Governance and reporting structure
Training and Change management approach, methodology and plan including
Training schedule, content and handouts, trainer’s profile, batch size and
infrastructure plan
Integration with SMS, Payment, Email and other software
Details of Deliverables along with timelines
Detailed Work plan and Staffing Plan
a. The Bidder shall provide a detailed project plan with timelines, resource
allocation, milestones etc. in Microsoft Project/Excel format for carrying out
the scope of work activities.
b. The project plan should clearly indicate the deliverables at each milestone in
the project and staffing deployment of all resources.
c. Work plan:
No Activity/Deliverable Weeks
1 2 3 4 5 6 7 8 9 10 11 12 N
1
2
N
d. Staffing plan
No Name of
Staff
Staff input in Weeks(in the form of a bar chart)
Total staff
man-
months
proposed
Key
responsibilities/
Tasks/
Deliverables
1 2 3 4 5 6 7 8 9 10 11 12 n Total
1
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 139 of 140
N
Total
Team Composition and Task Assignments
The Bidder should provide the summary table of details of the manpower that will be
deployed on this project in following format along with detailed CVs of key personnel in
format provided in annexure 13 (“Detailed CV format for proposed staff”).
Resource
Category
Proposed
number of
staff
Qualifications Experience
Name Area of
Expertise
Position
Assigned
Task
Assigned
Date:
Authorized Signatory:
Seal of the Organization:
Name:
Designation:
RajCOMP Info Services Ltd. Draft RFP for iHMS (before pre-bid)
[Ref. No. F4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017] Page 140 of 140
ANNEXURE-17 - MANUFACTURER’S AUTHORIZATION FORM (MAF)
(This form has to be provided by the OEMs of the products proposed on its letter head)
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
Subject: Issue of the Manufacturer’s Authorization Form (MAF)
[Reference No. F 4.2(266)/RISL/Tech/2016/317 Dated: 10/04/2017]
Sir,
We <name and address of the OEM> who are established and reputed original
equipment manufacturers (OEMs) having factories at <addresses of manufacturing
location> do hereby authorize <M/s __________________________> who is our
<Distributor/ Channel Partner/ Retailer/ Others <please specify> to bid, negotiate and
conclude the contract with you against the aforementioned tender reference for the
following Hardware/ Software manufactured by us: -
<OEM will mention the details of all the proposed product(s) with their make/
model>
We undertake that to provide OEM Warranty for the offered Hardware/ Software for
years, mentioned in Annexure-2 (Bill of Material) of the Bidding document. We duly
authorize the said firm to act on our behalf in fulfilling all installations, Technical support
and maintenance obligations required by the contract.
Yours faithfully,
For and on behalf of M/s (Name of the manufacturer)