ICT Tender Final - Website - Before Prebid

Page 1 of 219
Dr Rajendra Prasad Government Medical

College,
Kangra at Tanda

RFP NOTICE No. RPGMC/IT-01/13(A)

Request for Proposal

` 10,000/- (Rs. Ten Thousand Only)

Automation of Hospital and Medical College.

Dr Rajendra Prasad Government Medical College,
Kangra at Tanda
Page 2 of 219

Disclaimer
The information contained in this Request for Proposal ("RFP") document or subsequently provided
information to bidders, whether verbally or in documentary form by or on behalf of the Dr.Rajendra
Prasad Government Medical College (RPGMC) of Government of Himachal Pradesh, or any of their
employees, consultants or advisers, is provided to bidders on the terms and conditions set out in this
RFP document and any other terms and conditions subject to which such information is provided.
This RFP document is not an agreement and is not an offer or invitation by the RPGMC to any other
Party. The purpose of this RFP document is to provide interested parties with information to assist in
formulation of their Proposal. This RFP document does not purport to contain all the information each
bidder may require. This RFP document may not be appropriate for all persons or entities, and it is not
possible for the RPGMC, their employees, consultants or advisors to consider the investment
objectives, financial situation and particular needs of each party who reads or uses this RFP
document. Certain bidder may have a better knowledge of the proposed Project than others. Each
bidder should conduct its own investigations and analysis and should check the accuracy, reliability
and completeness of the information in this RFP document and obtain independent advice from
appropriate sources. RPGMC, its representatives, their employees, consultants and advisors make no
representation or warranty and shall incur no liability under any law, statute, rules or regulations as to
the accuracy, reliability or completeness of the RFP document.
RPGMC may in their absolute discretion, but without being under any obligation to do so, update,
amend or supplement the information in this RFP document.
Some of the activities listed to be carried out by RPGMC as a part of the tendering process or the
subsequent implementation are indicative only. RPGMC has the right to continue with these
activities, modify the sequence of activities, add new activities or remove some of the activities, in the
best interests of RPGMC.

Kangra at Tanda
Page 3 of 219

Advertisement
TENDER NOTIFICATION
Dr Rajendra Prasad Government Medical College (RPGMC)
Kangra, at Tanda
Himachal Pradesh, India 176001
www.rpgmc.ac.in

Dr. Rajendra Prasad Government Medical College (RPGMC), Kangra at Tanda, Himachal Pradesh 176 001,
hereby invites sealed Proposals from experienced Firms for Automation of its Hospital and College.
The Proposals should be submitted according to two cover System consisting of Technical Bid and Commercial
Bid. The Request for Proposal Document can be downloaded from the Institutes website
http://www.rpgmc.ac.in/ starting at 10:00 hrs Monday, September 30
th
, 2013. The cost of Document is
`10,000/- (Rupees Ten Thousand Only) which needs to be deposited along with the Proposal as directed in the
Document. A Pre bid conference with the OEMs (by invitation only) is scheduled at 10:00 hrs on Thursday,
October 17
th
, 2013 and another pre bid conference with the prospective Bidders is scheduled at 14:00 hrs on
Friday, October 25
th
, 2013. The last date of submission of Bid is scheduled at 13:00 hrs on Friday, November
8
th
, 2013.

The Additional Director (Administration)

Kangra at Tanda
Page 4 of 219

Receipt
Receipt Number ______________

Issued to ___________________________________________________________________

Against request Number____________________ dated _____________________________

and payment vide Cash / Bank Draft drawn upon:

___________________________________________________________________________

Number ____________ dated _____________ for ` 10,000/- only (Rs. Ten Thousand Only).

Request for Proposal Documents issued on ______________________

Additional Director (Administration),
Kangra at Tanda.
176 001.

Kangra at Tanda
Page 5 of 219

Important Dates
S No Description Schedule
1

Date of uploading of Request for
Proposal Document on Institutes
website

Request for Proposal Documents can be downloaded from
the Institutes website http://www.rpgmc.ac.in/ starting
10:00 hrs Monday, September 30
th
, 2013. The Request for
Proposal Document cost needs to be deposited along with
the Proposal as directed in this document.
2

Pre bid conference with OEMs by
invitation only

At 10:00 hrs on Thursday, October 17
th
, 2013 at H P State
Health & Family Welfare Training Centre, Pari Mahal,
Shimla, 171 002. Minutes of this conference shall be
uploaded to the College website thereafter.
3

Pre bid conference with prospective
Bidders

At 14:00 hrs on Friday, October 25
th
, 2013 at Computer
Centre, National Institute of Technology, Hamirpur, 177
005.
4

Last date of submission of Bid

At 13:00 hrs on Friday, November 8
th
, 2013 at Office of The
Additional Director (Administartion), Dr Rajendra Prasad
Government Medical College, Kangra at Tanda, 176 001.
5

Date of opening of the Technical Bids At 15:00 hrs on Friday, November 8
th
, 2013 at Office of The
Additional Director (Administartion), Dr Rajendra Prasad
Government Medical College, Kangra at Tanda, 176 001.
6 Date of opening of the Commercial
Bids
To be announced during the opening of Technical Bids.

Kangra at Tanda
Page 6 of 219

Contents
S No Particulars Page
1 PREAMBLE 8
2 INVITATION TO BID 9
3
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12
INSTRUCTIONS TO BIDDERS
Definitions, Acronyms and Abbreviations
Cost of the Request for Proposal Document
Major Parts of the Request for Proposal
Schedule of the Request for Proposal
Procedure for Submission of Bids
Cost Incurred with Bidding
Clarification of the Request for Proposal Document
Amendment in the Request for Proposal Document
Language of Bids
Bid Currency
Validity
Modifications & Withdrawal
10
10
11
11
12
13
16
16
17
17
17
17
17
4
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.13
4.14
4.15
4.16
4.17
4.18
4.19
4.20
4.21
4.22
4.23
4.24
4.25
4.26
4.27
4.28
4.29
4.30
4.31
4.32
TERMS & CONDITIONS OF THE REQUEST FOR PROPOSAL
General Eligibility Criteria
Technical Eligibility Criteria for Schedules A & B
Commercial Eligibility Criteria for Schedules A & B
Technical Eligibility Criteria for Schedules C & D
Commercial Eligibility Criteria for Schedules C & D
Technical Eligibility Criteria for Schedule E
Commercial Eligibility Criteria for Schedule E
Technical Eligibility Criteria for Schedules F & G
Commercial Eligibility Criteria for Schedules F & G
General Conditions
Purchasers Right to Reject Any/All Bids
Bid Rejection Criteria
Bid Evaluation Process for Requirements in Schedules A, B, F & G
Bid Evaluation Process for Requirements in Schedules C, D & E
Responsibilities of the Bidder(s)
Responsibilities of the Institute
Schedule of Payment wrt Schedules A, B & F
Schedule of Payment wrt Schedules C, D & E
Schedule of Payment wrt Schedule G
Time Schedule
Earnest Money
Rates
Warranty
Penalties
Taxes and Duties
Performance Guarantee
Insurance
Indemnity
Confidentiality
Conflict of Interest
Trainings
Force Majeure During the Pendency
18
18
18
19
19
20
20
21
21
22
22
23
23
24
24
25
25
25
26
26
26
27
27
27
27
27
27
27
28
28
28
28
28

Kangra at Tanda
Page 7 of 219

S No Particulars Page
4.33
4.34
4.35
Other Conditions
Arbitration
Applicable Laws & Jurisdiction of Courts
29
29
29
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
5.13
5.14
5.15
5.16
5.17
5.18
5.19
DETAILED SCOPE OF WORK, SPECIFICATIONS & DELIVERABLES
General Note
Modular Data Centre
Servers
Storage
Network Switches
Wireless Equipment
Security Appliances
Load Balancer
Network Management System
Unified Communications
Desktops, Tablets & Peripherals
Institute Management Software
Collaboration Suite
Picture Archival & Communication System and Radiology Information System
Healthcare Management Information System
Database Management System
Passive Components
Surveillance System
System Integration & Services
30
30
31
34
37
39
47
53
56
59
63
75
79
105
110
126
188
189
192
194
6
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.11

6.12

6.13
6.14
6.15
BID PROPOSAL PROFORMAE
Bid Covering Letter
Proforma Technical Bid
Deviations from Detailed Technical Specifications
Deviations from the Terms and Conditions
Proforma Manufacturers / Developers Authorization
Bill of Material cum Compliance Sheet for Hardware
Bill of Material cum Compliance Sheet for Software
Proforma Commercial Bid
Rate Schedule for Data Centre, Servers and Storage (Schedule A)
Rate Schedule for Converged Data & Voice Network (Schedule B)
Rate Schedule for Automation Software, Collaboration Suite, Database Management System
and other Ancillary Servers (Schedule C)
Rate Schedule for Picture Archiving and Communication System and Radiology Information
System (Schedule D)
Rate Schedule for Healthcare Management Information System (Schedule E)
Rate Schedule for Desktops, Tablets, Peripherals and Surveillance System (Schedule F)
Rate Schedule for System Integration and Services (Schedule G)
197
197
199
201
202
203
204
205
206
208
209
211

212

213
214
215

A
B
C
ANNEXURES
Building wise Details of Switches and Locations
Logical Connectivity at the Core
Fibre Layout in the Campus
216
216
218
219

Kangra at Tanda
Page 8 of 219

1
Preamble
Dr Rajendra Prasad Government Medical College, Kangra at Tanda is one of the two Medical Colleges
in the Government Sector in the State of Himachal Pradesh. It is covered under The Pradhan Mantri
Swasthya Suraksha Yojna and is mandated to create state of the art infotech infrastructure including a
data centre, Institute wide converged IP network and automation applications. The objective of this
request for proposal, therefore, is the automation of all the activities of the College and its Hospital
and creation of all the necessary systems that may be needed for such a venture, in order to meet the
futuristic requirements of professional healthcare and medical education.
The components of the task for automating the operations of the Institute are varied in nature,
though interdependent. As the prospective vendors of individual component may or may not
specialize in all of these components this Request for Proposal is suitably split into sub components.
The motive in doing so is that of reduction of the overall cost of ownership to the Institute as well as
to procure the best goods and services as may be available.
It is also felt that the Institute should not get tied down to a particular technology or vendor now or in
future for further up gradation as well as expansion. Pertinent to this is the fact that all the equipment
and components must conform to open global standards and universal protocols. Consequently,
interoperability of heterogeneous components across vendor, make or model shall have to be
meticulously ensured.
The investment the Institute is intending to make vide this request for proposal needs to be protected
and it is expected that the vendors should undertake to supply spares as well as to ensure up
gradation / expansion for a reasonable period in future. In order to ascertain this, the vendors must
be willing to sign maintenance contract if awarded directly or through third parties.

Kangra at Tanda
Page 9 of 219

2
Invitation to Bid
No RPGMC/IT-01/13(A)
Dated, September 30
th
, 2013

REGISTERED POST

To:
-----------------------------------------------------------
-----------------------------------------------------------
-----------------------------------------------------------
-----------------------------------------------------------

Dear Sirs,
Pursuant to your request, I, the Administrative Officer acting for and on behalf of The Principal, Dr
Rajendra Prasad Government Medical College, Kangra at Tanda, H.P. 176 001, have pleasure in
forwarding the request for proposal documents to enable you to submit your binding offers.
a. This request for proposal is for:
b. Bidders are advised to study the Request for Proposal Document carefully. Submission of Proposal
shall be deemed to have been done after careful study and examination of the Request for
Proposal Document with full understanding of its implications.
c. Sealed offers prepared in accordance with the procedures enumerated in INSTRUCTIONS TO
BIDDERS should be submitted to the Principal of the Institute not later than the date and time
laid down, at the address given in Schedule of Request for Proposal. The bids shall be opened in
the presence of those Bidders who may wish to be present as per the Schedule of Request for
Proposal.
d. The Institute shall not be responsible for any postal delay about non-receipt / non-delivery of the
documents.
e. This Request for Proposal Document is not transferable; however OEMs are free to quote through
their authorized distributors or system integrators.

Yours Faithfully,

KANGRA.

Kangra at Tanda
Page 10 of 219

3
Instructions to Bidders
The Bidder is expected to have read and examined all the instructions, forms, terms and specifications
in the Request for Proposal Document with full understanding of its implications. Failure to furnish all
information required in the Request for Proposal Document or submission of a bid not substantially
responsive to the Request for Proposal Document in every respect will be at the Bidders risk and may
result in outright rejection of the bid.
3.1 DEFINITIONS, ACRONYMS & ABBREVIATIONS
The following definitions shall govern for the respective terms as hereinafter mentioned in this
document:
Institute Dr Rajendra Prasad Government Medical College
&
Hospital
KANGRA at Tanda.
176 001.
http://www.rpgmc.ac.in
Bidder Any party meeting the eligibility as hereinafter laid
down who has downloaded the Request for Proposal
Document from the Institutes website and intends to
offer the services mentioned in this document.
Consultant Department of Computer Science & Engineering,
National Institute of Technology,
HAMIRPUR.
177 005.
http://www.nith.ac.in
eMail: kumar@nith.ac.in
Phone: +91-9805225569, +91-1972-254404
Fax: +91-1972-223834(PP)
OEM
Original equipment manufacturer in case of hardware
and original assignee in case of software.
RPGMC
Dr Rajendra Prasad Government Medical College, Also
referred as purchaser
BG
Bank Guarantee
DD
Demand Draft
EMD
Earnest Money Deposit
IT/ICT
Information and Communication Technologies
PBG
Performance Bank Guarantee
RFP
Request for Proposal / Tender document / Bid
document
SLA
Service Level Agreement
SP/SI
Service Provider. The terms Systems Integrator/
Implementation Partner / Bidder / Vendor are also used

Kangra at Tanda
Page 11 of 219

interchangeably.
GoHP
Government of Himachal Pradesh
COTS
Commercially off the shelf:
The software application which is readily deployable
with or without configuration to suit the customers
specific process requirements and does not involve
developing the application from scratch.
The software application which is implementable or
deployable and maintainable by any other competent
agency other than the manufacturer or agency which
has developed the software.
The software solution available with complete
transparency including operation manuals, help
documents and source code.
The software solution which has preconfigured
templates of business processes, technical features and
provides a predictable operational performance.
3.2 COST OF THE REQUEST FOR PROPOSAL DOCUMENT
The Bidder shall deposit ` 10,000/- (Rupees Ten Thousand Only) being the cost of the Request for
Proposal Document. It can be done either by way of a Demand Draft favouring The Principal, Dr
Rajendra Prasad Government College, Kangra at Tanda payable at Kangra or by depositing it in cash
with the cashier of the Institute. Payments made through any other mode will not be accepted.
It is an absolute must that the cost of Request for Proposal Document is paid as directed; otherwise
the offer shall stand summarily rejected and no correspondence in this matter shall be entertained.
3.3 MAJOR PARTS OF THE REQUEST FOR PROPOSAL
This invitation for bid is for undertaking the following activities (grouped as Schedule A, B, C, D, E, F &
G respectively) according to the requirement of the Institute for undertaking the following activities
which are interdependent but mutually exclusive:
This quote comprises of
following schedule.
Schedule Name Activities
Schedule A Data Centre,
Servers and
Storage
Supply, Installation, Implementation, Integration,
Configuration, Commissioning and Maintenance of
the
Data Centre
Servers including Operating Systems
Storage
Operating Systems
As per the technical specifications mentioned in
the Sections 5.2, 5.3 and 5.4 of this RFP.
Schedule B Converged Data
& Voice
Network (both
wire-line and
wireless)

the
Network Switches
Wireless Equipment
Security Appliances
Load Balancer

Kangra at Tanda
Page 12 of 219

Passive Components
the Sections 5.5, 5.6, 5.7, 5.8, 5.9, 5.10 and 5.17 of
this RFP.
Schedule C Automation
Software,
Collaboration
Suite, Database
Management
System and
Other Ancillary
Servers

the
Automation Software
Collaboration Suite
the Sections 5.12, 5.13 and 5.16 of this RFP.
Schedule D Picture
Archiving and
Communication
System and
Radiology
Information
System
the
PACS & RIS
the Section 5.14 of this RFP.
Schedule E Healthcare
Management
Information
System
the
HMIS
the Section 5.15 of this RFP.
Schedule F Desktops,
Tablets,
Peripherals and
Surveillance
System
the
Desktops
Tablets
Printers cum Scanners
Laser Printers
Surveillance Cameras
Network Video Recording Software
the Sections 5.11 and 5.18 of this RFP.
Schedule G System
Integration and
Services
Integration of the complete system, management
of the project and other services as per the
technical specifications mentioned in the Section
5.19 of this RFP.
The Bidders are free to quote for any or for all of the activities.
3.4 SCHEDULE OF REQUEST FOR PROPOSAL
3.4.1 Request for Proposal Documents can be downloaded from the Institute website
http://www.rpgmc.ac.in starting 10:00 on Monday, September 30
th
, 2013. The Request for Proposal
Document cost needs to be paid along with the bid.

Kangra at Tanda
Page 13 of 219

3.4.2 A pre bid conference with the OEMs is scheduled to be held at 10:00 on Thursday, October 17
th
, 2013.
This conference is strictly by invitation only, where all the shortlisted OEMs will be invited. The
purpose of the meeting is to clarify issues and to answer questions on any matter that may be raised
upto that stage related with the detailed technical specifications. Upto a maximum of 2 (two)
representatives of each prospective OEM will be permitted to attend it.
The address for the above activity (3.4.2) is:
H P State Health & Family Welfare Training Centre,
Pari Mahal,
SHIMLA.
H.P.
171 002.
3.4.3 A pre bid conference with the Bidders is scheduled to be held at 14:00 on Friday, October 25
th
, 2013.
The purpose of the meeting is to clarify issues and to answer questions on any matter that may be
raised upto that stage related with the terms and conditions of this Request for Proposal. Upto a
maximum of 2 (two) representatives of each prospective Bidder will be permitted to attend it.
The address for the above activity (3.4.3) is:
Computer Centre,
National Institute of Technology,
HAMIRPUR.
H.P.
177 005.
3.4.4 The sealed bids will be accepted till 13:00 hrs on Friday, November 8
th
, 2013. The Institute may at its
sole discretion extend the bid submission date. The modified target date & time will be notified on
the website of the Institute.
3.4.5 The Technical Bids will be opened at 14:00 hrs at 15:00 hrs on Friday, November 8
th
, 2013. The
Bidder(s) or their authorized representatives may be present if they so desire.
3.4.6 The Commercial Bids of only technically qualified Bidder(s) will be opened at a date announced by the
Institute on its website. The Bidder(s) who have been declared eligible after evaluation of the
technical bids or their authorized representatives may be present if they so desire.
The address for the above activities (3.4.4, 3.4.5, 3.4.6) is:
Office of Additional Director (Administration),
KANGRA at TANDA.
H.P.
176 001.
3.4.7 The address for all the correspondences pertaining to this Request for Proposal is:
KANGRA at TANDA.
H.P., 176 001.
http://www.rpgmc.ac.in
PHONE 01892-267115/2678640/287187/287001
FAX 01892-267115/267115
EMAIL principal.tanda@gmail.com
3.5 PROCEDURE FOR SUBMISSION OF BIDS
3.5.1 It is proposed to have a three cover system for this Request for Proposal.
i. Covering Letter and Cost of Request for Proposal Document.

Kangra at Tanda
Page 14 of 219

ii. Technical Proposal.
iii. Commercial Bid and Earnest Money Deposit.
Please note that Rates should not be indicated in the Technical Bid. Only Commercial Bid should
indicate rates.
All the documents viz. Covering Letter and Cost of Request for Proposal Document, Technical Bid and
Commercial Bid and Earnest Money Deposit prepared and sealed as hereinafter directed are to be
kept in a single sealed cover super-scribed with the words PROPOSAL for INSTITUTE IT
INFRASTRUCTURE (RPGMC/IT-01/13), due at 13:00 hrs on Friday, November 8
th
, 2013, NOT TO BE
OPENED BEFORE TIME.
The cover thus prepared should also indicate clearly the name and address of the Bidder, to enable
the Bid to be returned unopened in case it is received after the specified date and time.
The Bid shall be in the prescribed format and shall be signed by the Bidder or a person duly authorized
to bind the Bidder to the contract.
All pages of the bid except un-amended printed literature shall be initialled by the person(s) signing
the Bid. The bid shall contain no interlineations, erasures or over writing except as necessary to
correct errors made by the Bidder, in which case such corrections shall be initialled by the person(s)
signing the bid.
The Bids prepared by the Bidders shall thus comprise of following components:
i. Covering Letter neatly typed on the letterhead of the Bidder, duly signed by the authorized
signatory in the proforma given in Section 6.1 post and a the cost of Request for Proposal
Document, and kept in a sealed cover super-scribed COVERING LETTER & COST OF REQUEST
FOR PROPOSAL DOCUMENT as detailed in Section 3.5.2 below.
ii. Technical Bid, as directed below in Section 3.5.3 and kept in a sealed cover super-scribed
TECHNICAL PROPOSAL.
iii. Commercial Bid, as directed below in Section 3.5.4 and kept in a sealed cover super-scribed
COMMERCIAL BID & EARNEST MONEY DEPOSIT.
3.5.2 Covering Letter & Cost of Request for Proposal Document:
i. Bid Covering Letter as per the proforma given post in Section 6.1 post neatly typed and duly
signed by the authorized signatory on the Bidders letter head.
ii. The Request for Proposal Cost of ` 10,000/- (Rupees Ten Thousand only) as required in
Section 3.2 ante should be kept in this envelope by way of
a. A Demand Draft in favour of Principal, Dr Rajendra Prasad Government Medical
College, Kanga at Tanda, H.P. payable at Kangra;
Or
b. The cash receipt issued by the Cashier of the Institute for that purpose.
3.5.3 Technical Proposal:
i. The Technical Proposal should be submitted in bound form and all pages continuously and
serially numbered in one lot as one document. Brochures / leaflets etc. should be submitted
in the bound document and not in a loose form. Bidders must ensure that all the documents
are sealed and signed by authorized signatory.
ii. Technical Bid as given in Section 6.2, neatly typed on the letter head of the Bidder, duly filled
in, signed and complete in all respects including annexure for detailed specifications of
equipment etc as directed. A soft copy (Word / Excel) of the bid should also be submitted on
a CD in the same envelope along with the Hard Copy of the Technical Offer. The bids shall
inter alia include detailed technical specifications of all the equipment / components in
brochure or written form. These brochures shall be used for technical evaluation of the bids
and in their absence the bids may not be evaluated.

Kangra at Tanda
Page 15 of 219

iii. Deviations from the Detailed Specifications as specified in the Bidding Document as given in
Section 6.3.
iv. Deviations from the Terms and Conditions as specified in the Bidding Document as given in
Section 6.4.
v. Manufacturers / Developers Authorization Certificate in specific reference to this Request
for Proposal as given in Section 6.5.
vi. Exact Bill of Material in the format given in Section 6.6 or Section 6.7 or both as the case may
be post. The Institute reserves its right to cross verify whether the offered components meet
the desired specifications.
vii. The Technical Bid submitted in response to this Request for Proposal Document along with
the supporting material, will become the property of the Institute.
3.5.4 Commercial Bid & Earnest Money Deposit:
i. Commercial bid proposal for the fine-tuned Technical Specifications neatly typed on the
letter head of the Bidder, duly filled in and signed by the authorized signatory in Prescribed
Quotation Proforma given in Section 6.8.
ii. The details of Rate Schedule for all the goods and services under all the components of this
Request for Proposal for which the Bidder is intending to quote, as given in Sections 6.9 to
6.15. The rates in these schedules shall be applicable in case the quantities of a particular
order vary from those mentioned in relevant Technical Specifications. In case the
consolidated rates quoted in the Prescribed Quotation Proforma as given in Section 6.8 differ
from the rate schedule, as given in Sections 6.9 to 6.15; later shall prevail.
iii. Please bid for all the sections of this Request for Proposal where the Bidder qualifies and
intends to bid.
iv. Earnest Money @ 2% of quoted value should be submitted along with the Request for
Proposal by way of
a. A Demand Draft in favour of The Principal, Dr Rajendra Prasad Government Medical
College, Kanga at Tanda, H.P. payable at Kangra;
Or
b. An FDR duly pledged in favour of The Principal, Dr Rajendra Prasad Government Medical
College, Kanga at Tanda, H.P. dischargeable at par at Kangra.
Or
c. A Bank Guarantee duly addressed to The Principal, Dr Rajendra Prasad Government
Medical College, Kanga at Tanda, H.P. in specific reference to this RFP, valid upto
September 30
th
, 2014.
It should be denominated in INDIAN RUPEES only. Bids without requisite Earnest Money shall
be summarily rejected.
v. Unsuccessful Bidders' bid security will be returned as promptly as possible but not later than
30 days after the expiration of the period of bid validity prescribed by the Institute.
vi. The successful Bidder's bid security will be discharged upon the Bidder accepting the
purchase order and furnishing the Performance Guarantee.
vii. The bid security may be forfeited:
a. if a Bidder withdraws its bid during the period of bid validity;
Or
b. if a Bidder makes any statement or encloses any form which turns out to be false,
incorrect and / or misleading at any time and / or conceals or suppresses material
information;

Kangra at Tanda
Page 16 of 219

Or
c. in case of the successful Bidder, if the Bidder fails to sign the agreement or to furnish
performance guarantee.
3.6 COSTS INCURRED WITH BIDDING
The Bidder shall bear all costs associated with the preparation and submission of its Bid, including
cost of presentation for the purposes of clarification of the Bid, if so desired by the Institute and the
Institute will in no case be responsible or liable for those costs, regardless of the conduct or outcome
of the Bidding Process.
3.7 CLARIFICATION OF REQUEST FOR PROPOSAL DOCUMENT
3.7.1 The shortlisted OEM(s) may like to attend a pre-bid meeting to be held on Thursday, October 17
th
,
2013 at 10:00. Upto a maximum of 2 (two) representatives of each shortlisted OEM will be permitted
to attend the pre-bid meeting. However the Institute, at its discretion, may permit any additional
representative of any shortlisted OEM or any representative or manufacturer of any related
equipment to attend the pre-bid meeting. All the clarifications / modifications requested by the
shortlisted OEM(s) should necessarily be submitted in writing latest by 17:00, Monday, October 14
th
,
2013 to the Consultant.
3.7.2 The prospective Bidder(s) may like to attend a pre-bid meeting to be held on Friday, October 25
th
,
2013 at 14:00. Upto a maximum of 2 (two) representatives of each prospective Bidder will be
permitted to attend the pre-bid meeting. All the clarifications / modifications requested by the
shortlisted OEM(s) should necessarily be submitted in writing latest by 17:00, Monday, October 14
th
,
2013 to the Consultant.
3.7.3 The purpose of these meetings is to clarify issues and to answer questions on any relevant matter
that may be raised upto that stage.
3.7.4 Outcomes of these meetings shall be published on the website of the Institute, allowing at least 7
days time prior to the last date for receipt of bids. Any modification of the Request for Proposal
Document, which may become necessary as a result of the Pre-bid Meeting, shall be made by the
Institute explicitly through revised Request for Proposal Document and shall be binding on all the
Bidders irrespective of whether they attended the meeting or not.
3.7.5 Non-attendance at the Pre-bid Meeting will not be a cause for disqualification of a Bidder.
3.8 AMENDMENT IN REQUEST FOR PROPOSAL DOCUMENT
3.8.1 At any time upto the last date of receipt of Bids, the Institute may, for any reason, whether at its own
initiative or in response to a clarification requested by a prospective Bidder, modify the Request for
Proposal Document by an amendment.
3.8.2 The amendment will be notified in writing or by email or fax to all prospective Bidders who have
received the Request for Proposal Document and the same will be binding on them. It will also be
uploaded to the Institutes website.
3.8.3 In order to afford prospective Bidders reasonable time to take the amendment into account in
preparing their Bids, the Institute may, at its discretion, extend the last date for the receipt of Bids.
3.9 LANGUAGE OF BIDS
The Bids prepared by the Bidder and all correspondence and documents relating to the Bids
exchanged by the Bidder and the Institute, shall be written in the English Language, provided that any
printed literature furnished by the Bidder may be written in another language so long as it is
accompanied by an English translation in which case, for purposes of interpretation of the Bid, the
English translation shall govern.

Kangra at Tanda
Page 17 of 219

3.10 BID CURRENCY
The Prices in the bid document shall be denominated in INDIAN NATIONAL RUPEES or any other
currency which can be converted to INDIAN NATIONAL RUPEES. For the purposes of evaluation of
bids, the exchange rate as advertised by the Reserve bank of India on the day of opening of
commercial bids shall apply.
3.11 VALIDITY
Bids shall remain valid for 180 days from the last date of submission. The Bidder(s) may be required to
give consent for the extension of the period of validity of the bid beyond initial 180 days, if so desired
by the Institute in writing or by fax. Refusal to grant such consent would result in rejection of bid
without forfeiture of the EMD. However, any extension of validity of bids will not entitle the Bidder to
revise / modify the bid. The decision of the Institute in this regard will be final, conclusive and binding
on the Bidder.
3.12 MODIFICATIONS & WITHDRAWAL
The bid submitted may be withdrawn or resubmitted before the expiry of the last date of submission
by making a request in writing to the Registrar of the Institute to this effect. No Bidder shall be
allowed to withdraw the bid after the deadline for submission of bids.

Kangra at Tanda
Page 18 of 219

4
Terms & Conditions of the Request
for Proposal
This RFP is open to all firms / Companies both from within India and outside India, who are eligible to
do business in India under relevant Indian laws as in force at the time of bidding and who fulfill the
minimum qualification Criteria as hereinafter laid down.
In addition to the above general requirements the Bidders must comply with additional qualifications
as laid hereinafter for those schedules of this Tender Document which they intend to respond for.
In case a Bidder is interested in more than one component or in case of consortiums, all the relevant
qualifying criteria must be met simultaneously.
4.1 GENERAL ELIGIBILITY CRITERIA
Criteria Documents to be submitted**
4.1.1 The Bidder should be a registered company in India under
Companies Act 1956 and should have been in operation for
at least Six years as on date of RFP.
Copy of the Certificate of
Incorporation should be enclosed as
Annexure EG 1.

4.1.2 The Bidder / Original Equipment Manufacturer (OEM)
should have Service and Support Centres for the
maintenance of the Items quoted by them in North India.
In case of OEM service and Support
Centre, copies of the land-line
telephone bills or rent agreement
dated before March 31
st
, 2013 should
be enclosed as Annexure EG 2 as a
proof.
In case of Authorized Service and
Support Centre, the Bidder should
submit a copy of the agreement
entered between the Franchisee and
the Bidder stating that the Franchisee
is rendering the service for the OEM
and the agreement should be valid as
on March 31
st
, 2013. It should be
enclosed as Annexure EG 2.
4.1.3 The Bidder should not have been blacklisted / debarred by
the Government of India or their undertakings, any State
Governments or their undertakings previously. In such
cases the bid will be summarily rejected and no
correspondence in this matter shall be replied by the
Institute.
Undertakings from the Bidder or the
OEM in this regard should be enclosed
as Annexure EG 3.
4.2 TECHNICAL ELIGIBILITY CRITERIA FOR SCHEDULES A & B

4.2.1 The Bidder(s) must either be OEMs or their authorized
business partners of repute as evidenced by copies of
relevant certificates or their consortia. In case of consortia
all the eligibility clauses shall be met by any combination of
Manufacturer Authorization Certificate
from OEM in Case of Channel Partner /
Distributor as per the Format given in
Section 6.5 post should be enclosed as

Kangra at Tanda
Page 19 of 219

the consortium partners. Annexure ETAB 1.
4.2.2 The Bidder should have the capability to execute the work
with respect to personnel and establishment facilities and
should have successfully executed at least two works of
similar value either of data centre or data / voice network.
Letters of Appreciation should be
enclosed as Annexure ETAB 2.
4.2.3 The OEM as well as the Bidder should be ISO 9000 certified
or of equivalent Standard having current validity.
ISO 9000 or equivalent certificates of
both the Bidder as well as OEM should
be enclosed as Annexure ETAB 3.
4.2.4 The Bidder(s) must be have valid VAT/ LST/ CST, Service
Tax Registration and PAN number allotted by the
respective authorities.
Copies of all the relevant certificates
should be enclosed as Annexure ETAB
4.
4.3 COMMERCIAL ELIGIBILITY CRITERIA FOR SCHEDULES A & B

4.3.1 In case of OEM as Bidder, should have a turnover of more
than ` 500 Million in the last successive three Audited
Financial years and in case of Authorized Channel Partner /
Distributor as Bidder, should have a turnover ` 150 Million
in the last successive three Audited Financial years
cumulatively.
Copies of the Audited Balance sheets
and Profit and Loss account for last 3
Financial years should be enclosed as
Annexure ECAB 1.
4.3.2 The Bidder as well as the OEM should not be involved in
any Bankruptcy filing or for protection from it.
Undertakings from the Bidder as well
as the OEM in this regard should be
enclosed as Annexure ECAB 2.
Otherwise, if they are so involved they
must furnish a bank guarantee valid for
three years of an amount equal to the
total value of their bid along with their
Commercial Bid and should mention
that they have done so in their
Technical Bid.
4.3.3 The Bidder should have been posting profits for last three
financial years and should have a net positive worth.
Annexure ECAB 1.
4.4 TECHNICAL ELIGIBILITY CRITERIA FOR SCHEDULES C & D

relevant certificates. The Bidders who are not OEMs for
the goods and services offered must enclose authorization
letters from the respective OEM in specific reference to
this tender clearly mentioning an undertaking that in case
of default by the Bidder the OEM shall take over all the
responsibilities of the Bidder. This undertaking should also
clearly mention that the spares availability will be ensured
for at least five years in future.
Annexure ETCD 1.
4.6.2 The OEM of the Application must have been certified at SEI
CMMi level 5.
Copy of the Certificate should be
enclosed as Annexure ETCD 2.

Kangra at Tanda
Page 20 of 219

should be enclosed as Annexure ETCD
3.
4.6.4 The OEM of the Application must be a national level IT
organization with experience in the field of ERP application
software conceptualization, design, development,
deployment, customization and maintenance for at least 3
years.
Copy of at least one purchase order
older than 3 years should be enclosed
as Annexure ETCD 4.
4.6.5 The Bidder(s) should have at least three campus solution
or PACS / RIS implementations in India as the case may be.
The technical committee at RPGMC Kangra may visit the
sites implemented to get a first-hand feedback on the
product and the implementer.
List of clients with their contact details
and addresses should be enclosed as
Annexure ETCD 5.
be enclosed as Annexure ETCD 6.
4.5 COMMERCIAL ELIGIBILITY CRITERIA FOR SCHEDULES C & D

cumulatively.
Annexure ECCD 1.
4.5.2 The Bidder as well as the OEM should not be involved in any
Bankruptcy filing or for protection from it.
enclosed as Annexure ECCD 2.
Technical Bid.
Annexure ECCD 1.
4.6 TECHNICAL ELIGIBILITY CRITERIA FOR SCHEDULE E

Manufacturer Authorization
Certificate from OEM in Case of
Channel Partner / Distributor as per
the Format given in Section 6.5 post
should be enclosed as Annexure ETE
1.

Kangra at Tanda
Page 21 of 219

4.6.2 The OEM of the Application must have been certified at
SEI CMMi level 5.
Copy of the Certificate should be
enclosed as Annexure ETE 2.
should be enclosed as Annexure ETE
3.
4.6.4 The Bidder(s) must be a national level IT organization with
experience in the field of ERP application software
conceptualization, design, development, deployment,
customization and maintenance for at least 3 years.
Copy of at least one purchase order
older than 3 years should be enclosed
as Annexure ETE 4.
4.6.5 The OEM of the Application should have presence in at
least 5 countries and should have deployed the
Application in at least 10 Hospitals / Medical Colleges
globally. The technical committee at RPGMC Kangra may
contact the sites implemented to get a first-hand feedback
on the product and the implementer.
List of clients with their contact details
and addresses should be enclosed as
Annexure ETE 5.
be enclosed as Annexure ETE 6.
4.7 COMMERCIAL ELIGIBILITY CRITERIA FOR SCHEDULE E

than ` 5 Billion in the last successive three Audited Financial
years and in case of Authorized Channel Partner /
Distributor as Bidder, should have a turnover ` 2 Billion in
the last successive three Audited Financial years
cumulatively.
Annexure ECE 1.
enclosed as Annexure ECE 2.
Technical Bid.
Annexure ECE 1.
4.8 TECHNICAL ELIGIBILITY CRITERIA FOR SCHEDULES F & G

Annexure ETFG 1.

Kangra at Tanda
Page 22 of 219

should be enclosed as Annexure ETFG
2.
be enclosed as Annexure ETFG 3.
4.9 COMMERCIAL ELIGIBILITY CRITERIA FOR SCHEDULES F & G

cumulatively.
Annexure ECFG 1.
enclosed as Annexure ECFG 2.
Technical Bid.
Annexure ECFG 1.
4.10 GENERAL CONDITIONS
4.8.1 Minimum validity of the Proposal must be 90 days from the date of its opening.
4.8.2 The Institute reserves the right, not an obligation, to carry out the capability assessment of the
Bidder(s) and pre dispatch inspections at the cost of the Bidder. This right inter alia includes seeking
technical demonstrations, presentations and live site visits.
4.8.3 The Institute reserves its absolute right to seek any clarifications from the respective Bidder(s).
4.8.4 The Institute will neither provide nor shall pay any charges for boarding, lodging and transportation
facilities for the Bidder(s) or their Representative.
4.8.5 The products / services offered should strictly conform to the specifications given in the product
literature. The models proposed / marked for withdrawal from the market or models under quality
testing should not be offered.
4.8.6 Equipment offered should be capable of being fully integrated with the existing network of the
Institute immediately on installation.

Kangra at Tanda
Page 23 of 219

4.8.7 The Bidder(s) are required not to impose their own terms and conditions to the bid and if submitted,
it will not be considered as forming part of their bids. The decision of the Institute shall be final,
conclusive and binding on the Bidder(s).
4.8.8 It is implicit that the Bidder has guaranteed that all the equipment supplied are original & new
including all its components and as per the technical specifications. All the hardware and software
supplied is licensed and legally obtained in the name of the Institute.
4.8.9 The Institute is registered with the DSIR for the purpose of availing Custom Duty Exemption and
Central excise Duty Exemption in terms of Govt Notification No 51/96-Custom dated Jul 23rd, 1996
and No 10/97-Central Excise dated Mar 1st 1997, so the rates must be quoted without Custom and
Excise duties, which if applicable, be quoted separately.
4.8.10 The Institute is also exempt from paying CST / ST / VAT applicable. Relevant exemption certificates
shall be issued as per law.
4.11 PURCHASERS RIGHT TO REJECT ANY / ALL BIDS
4.9.1 The Institute reserves the right to accept or reject any bid partially or fully or annul the bidding
process and reject all bids at any time prior to award of contract without assigning any reason,
thereby incurring no liability to the affected Bidder(s). The Institute is under no obligation to inform
the affected Bidder(s) of the ground for its action.
4.9.2 The Institute reserves the right to accept or reject any technology proposed by the Bidder(s).
4.9.3 The Institute reserves the right to re-issue the Request for Proposal or any part thereof without
assigning any reason whatsoever, at the sole discretion of the Institute.
4.9.4 The Institute reserves the right to issue Purchase Order in phases or to alter the quantities specified in
the offer. The Institute also reserves the right to delete one or more items from the list of items
specified in offer.
4.9.5 Any decision of the Institute in this regard shall be final, conclusive and binding on the Bidder(s).
4.12 BID REJECTION CRITERIA
The bid(s) will be rejected in case of any one or more of the following conditions:
4.10.1 Bids which are not substantially responsive to the Request for Proposal Document.
4.10.2 Bids not made in compliance with the procedure mentioned in this document or not substantively
responsive.
4.10.3 Failure on part of the Bidder to provide appropriate information as required in the bid proposal or any
additional information as requested by the Institute, including any supporting document.
4.10.4 Incomplete or conditional bids or bids that do not fulfil all or any of the conditions as specified in this
document.
4.10.5 Bids without earnest money deposit.
4.10.6 The submission of more than one bid under different names by one Bidder. If the same is found at
any stage, all the bids by that bidder will be rejected.
4.10.7 Material inconsistencies in the information submitted.
4.10.8 Misrepresentations in the bid proposal or any supporting documentation.
4.10.9 Bid proposal received after the last date and time specified in this document.
4.10.10 Bids found in unsealed cover, unsigned bids, bids signed by unauthorized person and unsigned
corrections in the bids.
4.10.11 Bids containing erasures or overwriting except as necessary to correct errors made by the Bidder, in
which case such corrections shall be authenticated by the person(s) signing the bid.

Kangra at Tanda
Page 24 of 219

4.13 BID EVALUATION PROCESS FOR REQUIREMENTS IN SCHEDULES A, B, F & G
4.11.1 The Bidder must meet all the eligibility criteria mentioned in Section 4.1, 4.2, 4.3, 4.6 and 4.7 as the
case may be.
4.11.2 The Technical Bids of all the Bidders who meet the eligibility criteria shall be evaluated further for
compliance of specifications and other such parameters as may be needed. The decision of the
Institute in this matter shall be final conclusive and binding.
4.11.3 The Commercial Bids of all the technically qualified Bidders shall be subjected to financial comparison.
It may be noted that the Gross Price and the AMC charges for one year shall be clubbed for the
purposes of arriving at the L1 Bidder(s).
4.14 BID EVALUATION PROCESS FOR REQUIREMENTS IN SHEDULES C, D & E
Bid evaluation process will be as follows:
4.12.1 The prospective Bidder must comply with general qualifications mentioned in Section 4.1, 4.4 and 4.5
as the case may be. In case the Bidder does not fulfil the eligibility criteria, their bids will be rejected
and shall not be considered for further evaluation.
4.12.2 The Bidder(s) will be evaluated on QCBS (Quality cum Cost Basis Selection) System. There will be 60%
weightage for Technical Bid and 40% for Commercial Bid.
4.12.3 A maximum of 100 marks will be allocated for the Technical Bid. These marks will be awarded based
on the compliances of the functional specifications asked for in this document as per following
details:
Response Marks
Standard 4
Work Around 3
Customization 2
Third Party 1
Not Possible 0
4.12.4 The Bidders scoring less than 80 marks (cut-off score) out of 100 marks in the technical evaluation
shall not be shortlisted for next stage of Commercial Bid evaluation process.
4.12.5 In case, less than two participating Bidders qualify on technical criteria and reach or exceed the cut-
off score of 80, then the Institute at its sole discretion, may qualify maximum three (total) Bidders on
the basis of the top three scores (but not less than 60 marks).
4.12.6 The Institute may, at its sole discretion, decide to seek more information from the Bidders in order to
normalize the bids. However, the Bidders will be notified separately, if such normalization exercise as
part of the technical evaluation is carried out.
4.12.7 The Bidders who are shortlisted based upon technical criteria may be asked, if necessary, to make a
presentation on their solution at The Institute, at their own cost.
4.12.8 The individual technical scores of the technically qualified Bidders, thereafter, will be normalized as
per the formula below:

where:
T
n
= Normalized technical score for the Bidder under consideration
T
b
= Absolute technical score for the Bidder under consideration
T
max
= Maximum absolute technical score obtained by any Bidder

Kangra at Tanda
Page 25 of 219

4.12.9 The bidders scoring at least 50 points in the technical evaluation shall be considered for further
financial evaluation. However, weightage will be carried forward from technical qualification stage to
financial bid evaluation.
4.12.10 Financial Bids of those who have technically qualified only shall be opened for further evaluation.
4.12.11 The Commercial Offer shall be the sum total of the Gross Price and the AMC charges for one year.
4.12.12 The commercial scores will be calculated as per formula given below:

where:
F
n
= Normalized financial percentage for the Bidder under consideration
F
b
= Evaluated percentage cost of the Bidder under consideration
F
min
= Minimum evaluated percentage cost of any Bidder
4.12.13 The overall score will be calculated as per the formula given below:

where:
B
n
= Overall score of the Bidder under consideration
T
n
= Normalized technical score of the Bidder under consideration
F
n
= Normalized financial score of the Bidder under consideration
4.12.14 Final Selection of Bidder will be done based on added individual score achieved by the Bidder in
techno-commercial evaluation. The Bidder getting the highest score (B
n
) shall be selected for award of
work.
4.15 RESPONSIBILITIES OF THE BIDDER(S)
4.13.1 The Bidder(s) shall supply, the equipment as FoR destination ie , Dr Rajendra Prasad Government
Medical College, Kangra at Tanda, H.P. 176 001 and the rates must include all the charges eg packing,
forwarding, insurance, freight, commissioning, demonstration etc if any.
4.13.2 They shall be required to erect, install, configure and commission the network and the data centre
and shall furnish necessary certifications.
4.13.3 They shall install, implement, configure and commission the software as per the requirements
specified in this document.
4.13.4 The Bidder(s) shall maintain the infrastructure provided by the Institute for the implementation and
operation of the project and allied services.
4.16 RESPONSIBILITIES OF THE INSTITUTE
4.14.1 The Institute shall provide space to install the network, equipment and components etc. On day to
day basis the officials of the Institute shall help the engineers deputed by the Bidder for the job in
their capacity.
4.14.2 The Institute shall provide layout for laying of fibre and cables needed.
4.14.3 In case of purchase in currencies other than INR, the Institute will open required LC. The Institutes
Custom Clearance agent at New Delhi shall assist the Bidder(s).
4.17 SCHEDULE OF PAYMENT WRT SCHEDULES A, B & F
4.15.1 No payment will be made in advance for any supplies under this invitation for bid.
4.15.2 70% of the payment due shall be released by the Institute upon successful delivery of equipment /
software and raising of relevant invoices thereof.

Kangra at Tanda
Page 26 of 219

4.15.3 Remaining 30% of the payment shall be released by the Institute after successful performance
certificate has been issued by the user within one month from the date of raising of relevant invoices
thereof.
4.15.4 The AMC for the supplies for the period after one year warranty will be paid at the end of each annual
quarter on post-paid basis.
4.18 SCHEDULE OF PAYMENT WRT SCHEDULES C, D & E
4.16.2 50% of the payment due for the COTS licences shall be released by the Institute upon successful
delivery of equipment / software and raising of relevant invoices thereof against a bank guarantee of
equal amount valid for at least two years from the date of delivery. This bank Guarantee will be
released after successful performance certificate has been issued.
4.16.3 Remaining 50% of the payment for the COTS licences shall be released by the Institute after successful
performance certificate has been issued by the user within one month from the date of raising of
relevant invoices thereof.
4.16.4 The cost of implementation services, including the cost of support for the COTS, the training, data
migration cost etc. will be paid based on the completion of the key milestones of the project and
acceptance of the deliverables associated with the milestones, by RPGMC.
4.16.5 The implementation service also includes three months of adoption support after go live declaration.
4.16.6 At the completion of Project Preparation phase, 15% of the cost of implementation services will be
paid against a bank guarantee of equal amount valid for at least two years from the date of delivery.
This bank Guarantee will be released after successful performance certificate has been issued.
4.16.7 35% of the cost of implementation services will be paid after the completion of the Blueprint phase
against a bank guarantee of equal amount valid for at least two years from the date of delivery. This
bank Guarantee will be released after successful performance certificate has been issued.
4.16.8 35% of the cost of implementation services will be paid at the successful completion of the
Realization phase against a bank guarantee of equal amount valid for at least two years from the date
of delivery. This bank Guarantee will be released after successful performance certificate has been
issued.
4.16.9 Remaining 15% of the cost of implementation services will be paid after one annual quarter of
successful operation.
4.16.10 The AMC for the COTS solution for the period after go-live will be paid at the end of each annual
quarter on post-paid basis.
4.19 SCHEDULE OF PAYMENT WRT SCHEDULE G
4.17.2 All the payment will be released by the Institute at the end of each annual quarter on post-paid basis
in eight equal instalments.
4.20 TIME SCHEDULE
The project should be completed within Eighteen months from the date of placing the supply order
and the Institutes decision in this regard will be final and binding. The supply shall actually be
deemed to have been complete on the actual date of installation / implementation and successful
demonstration to the duly constituted committee of the Institute.
The detailed schedule will be specified by the Institute at the time of placing supply / work orders
after due consultation with the successful Bidder(s).

Kangra at Tanda
Page 27 of 219

4.21 EARNEST MONEY
4.21.1 Earnest Money @ 2% of quoted value should be submitted along with the Proposal in the form of
Demand Draft payable to The Principal, Dr Rajendra Prasad Government Medical College, Kangra at
Tanda at Kangra, H.P. or Fixed Deposit Receipt duly pledged to The Principal, Dr Rajendra Prasad
Government Medical College, Kangra at Tanda at Kangra dischargeable at Kangra, H.P. or A Bank
Guarantee duly addressed to The Principal, Dr Rajendra Prasad Government Medical College, Kanga
at Tanda, H.P. in specific reference to this RFP, valid upto September 30th, 2014.
4.21.2 Proposals without Earnest Money shall be summarily rejected.
4.21.3 The successful Bidder(s) will be required to meet the schedule of job given by the Institute and
mutually agreed to by them and would abide by the terms and conditions of the contract, failing
which the Institute reserves the right to forfeit the full or part of the said deposit, as the case may be.
4.21.4 If the Bidder refuses to undertake the allotted work or delays the work deliberately and
unnecessarily, their allotment order will be cancelled, Firm will be black Listed and Earnest Money
shall be forfeited. In such a case decision of the Institute will be final and binding.
4.22 RATES
The rates quoted shall remain firm throughout the period of contract and this contract will remain
valid upto the date of completion of the job by the Bidder(s) and shall not be subject to any upward
modification whatsoever.
4.23 WARRANTY
All the goods and services quoted in response to this Request for Proposal shall have an onsite
warranty for 1 year from the date of commissioning.
4.24 PENALTIES
In case of delay in execution of works or delivery of goods & services penalties at the following rates
shall be imposed on the total amount (as per relevant rate schedule) of delayed goods/services:
1% for delay of the first two months
2% per month for subsequent delays
Maximum delay of six months is tolerable, beyond which the order may be cancelled.
The decision of the Institute in this regard shall be final, conclusive and binding.
4.25 TAXES AND DUTIES
The Bidder shall be solely responsible for the payment of all taxes including VAT, duties, license fees,
octroi etc. incurred until completion of the project.
4.26 PERFORMANCE GUARANTEE
The successful Bidder(s) shall furnish a security in the form of bank guarantee @ 5% of the total value
of the order to the Bidder, valid for 3 years from the date of order, which shall be discharged
thereafter.
4.27 INSURANCE
The Institute will not pay for any insurance charges against loss or damage incidental to manufacture
or acquisition, transportation, storage and delivery etc. The insurance shall be purchased by the
Bidder, naming the Institute as the beneficiary, in an amount equal to the exact value of the Goods up
to the installation at site on all risks basis, including war Risks and strike clauses etc.

Kangra at Tanda
Page 28 of 219

4.28 INDEMNITY
4.26.1 The Bidder(s) shall indemnify the Institute against all third party claims of infringement of
Intellectual Property Right, including Patent, trademark, copyright, trade secret or industrial
design rights arising from use of the Goods, or any part thereof in India.
4.26.2 The Bidder(s) shall, at their own expense, defend and indemnify the Institute against all third party
claims or infringement of intellectual Property Right, including Patent, trademark, copyright,
trade secret or industrial design rights arising from use of the products or any part thereof in India
or abroad.
4.26.3 The Bidder(s) shall expeditiously extinguish any such claims and shall have full rights to defend itself
therefrom. If the Institute is required to pay compensation to a third party resulting from such
infringement, the Bidder(s) shall be fully responsible therefore, including all expenses and court and
legal fees.
4.26.4 The Institute will give notice to the Bidder of any such claim without delay, provide reasonable
assistance to the Supplier in disposing of the claim, and shall at no time admit to any liability for or
express any intent to settle the claim.
4.29 CONFIDENTIALITY
4.27.1 The Bidder shall not, and without the Institutes prior written consent, disclose the contract or any
provision thereof, or any specification, plan, drawing, pattern, sample or information furnished by or
on behalf of the Institute in connection therewith to any person other than a person employed by the
Bidder in the performance of the contract. Disclosure to any such employed person shall be made in
confidence and shall extend only as far as may be necessary for purposes of such performance.
4.27.2 The Bidder shall not without the Institutes prior written consent, make use of any document or
information.
4.27.3 Any document other than the contract itself shall remain the property of the Institute and shall be
returned (in all copies) to the Institute on completion of the Bidders performance under the contract
if so required by the Institute.
4.30 CONFLICT OF INTEREST
Absence of, actual or potential conflict of interest on the part of the Bidder due to prior, current, or
proposed contracts, engagements, or affiliations with RPGMC needs to be meticulously ensured.
Additionally, they shall proactively disclose and address any and all potential elements, which would
adversely impact their ability to complete the requirements as given in the RFP.
4.31 TRAININGS
The Bidder shall be responsible for training the Institute personnel in the areas of implementation,
operations, management, error handling, troubleshooting, system administration and any other
related areas. This training can be arranged at the premises of the Bidder or at the Institute. At least
ten employees need to be trained by the Bidder who shall be identified by the Institute and shall
comprise of people having different levels of qualifications and responsibilities. The final training
schedule shall be decided according to a mutually agreed time table before the work order is finally
placed.
4.32 FORCE MAJEURE DURING THE PENDENCY
During the pendency of the contract if the performance in whole or part thereof by either party is
prevented / delayed by causes arising due to any war, hostilities, civil commotion, act of public
enemy, sabotage, fire, floods, explosion, epidemics, non-availability of raw material, and other
consumables, or any other causes including breakdown of equipment beyond their reasonable
control neither of the two parties shall be made liable for loss or damage due to delay or failure to
perform the contract during the pendency of forced conditions provided that the happenings are

Kangra at Tanda
Page 29 of 219

notified in writing within 7 days from the date of occurrence. The work shall be resumed under the
contract as soon as possible after the restoration of normalcy.
4.33 OTHER CONDITIONS
If some latest technology or equivalent is introduced the Bidder is duty bound to offer their proposal
on mutually agreed rates on similar terms and conditions during the pendency of the agreement /
contract.
4.34 ARBITRATION
All disputes, differences, claims and demands arising under or pursuant to or touching the contract
shall be referred to the sole arbitrator to be appointed by the Principal, Dr Rajendra Prasad
Government Medical College, Kangra at Tanda, H.P. The award of the sole arbitrator shall be final and
binding on both the parties under the provisions of the Arbitration and Conciliation Act, 1966 or by
statutory modification/re-enactment thereof for the time being in force. Such arbitration shall be held
at Hamirpur.
4.35 APPLICABLE LAWS & JURISDICTION OF COURTS
In all matters and disputes arising hereunder, shall be governed in accordance with the Laws of India
for the time being enforced and will be subject to the exclusive jurisdiction of Courts having
jurisdiction in Kangra, H.P.

Kangra at Tanda
Page 30 of 219

5
Detailed Scope of Work,
Specifications & Deliverables
5.1 GENERAL NOTE
5.1.1 The given specifications are minimum requirements. Bidders should enclose relevant printed or
neatly typed detailed specification sheets of their offerings, which shall also be kept in mind at the
time of evaluation of offers.
5.1.2 The given specifications may be met either in the same unit or in any combination of units.
5.1.3 The quantities mentioned herein are indicative and shall be used to arrive at L1 Bidder. However, they
may vary and shall be paid for by the Institute as per actual. In case of variations in quantities the
rates mentioned by the Bidder in the relevant rate schedule shall apply.
5.1.4 Following are the approved makes for the goods and services mentioned in this Request for Proposal.
Other makes of comparative workmanship and quality may also be accepted after both the Institute
and the Consultant are satisfied. The responsibility of satisfying the Institute and the Consultant lies
with the Bidder.
5.1.5 The Bidders may quote for any of the following lots but they are necessarily required to quote for all
the sections within a lot.
Section
No
Bidding Schedule Item / Material
Description
Approved Makes
1 A:
Data Centre, Servers and
Storage
Modular Data Centre Rittal / Emerson / IBM
2 Servers IBM / Hewlett Packard / Oracle
3 Storage IBM / Hewlett Packard / Oracle
4 B:
Converged Data & Voice
Network (both wire-line and
wireless)

Network Switches Cisco / Juniper / Brocade
5 Wireless Equipment Aruba / Juniper / Motorola /
Cisco / Brocade / Alcatel-Lucent
6 Load Balancers Array / Radware / F5
6 Security Appliances Cisco / Juniper / Checkpoint /
Fortinet
7 Network Management
System
Hewlett Packard / IBM / CA
8 Unified Communications Cisco / Alcatel-Lucent / Avaya
9 Passive Components Tyco / Systimax / Leviton /
R&M
10 C:
Automation Software,
Collaboration Suite,
Database Management
System and Other Ancillary
Servers
Database Management
System
Oracle / SAP / IBM
11 Collaboration Suite Oracle / IBM / Novell / VMware
12 Automation Software Oracle / SAP

Kangra at Tanda
Page 31 of 219

13 D:
PACS / RIS
Picture Archiving and
Communication System,
Radiology Information
System
Cerner / GE / Siemens / Isoft /
SAP
14 E:
HMIS
Healthcare Management
Information System
Cerner / McKesson / Isoft / SAP
15 F:
Desktops, Tablets,
Peripherals and Surveillance
System
Desktops and Tablets Lenovo / Hewlett Packard /
Dell
16 Peripherals Hewlett Packard / Canon / Wep
17 Surveillance System Pelco / Dvtel / Mobotix / Vicon
18 G:
System Integration and
Services

5.2 MODULAR DATA CENTRE
5.2.1 SCOPE OF WORK
a. Supply: Supply of Modular Data Centre including peripherals, completely described in the BID,
and their installation, maintenance at on-site/off-site locations provided by the Institute.
b. Installation:
i. Fixing and setting up the data centre at the Institute.
ii. Configuring all the software associated with the data centre management.
iii. User training to the IT staff of the Institute
c. Uptime: The Bidder will ensure an uptime of 97% for the Data Centre.
d. Reliability: The equipment offered should be robust and reliable.
e. AMC: The technical maintenance of the Data Centre will be the responsibility of the Bidder. The
charges for such AMC shall be borne by the Institute after the expiry of one year standard
warranty only.
5.2.2 SPECIFICATIONS
S No Item Description Quantity
Needed
1. 10 kVA (N+N) UPS with 15 minutes each battery pack. Total UPS system backup
of 30 minutes
UPS 10kVA (N+N)-i.e 10kVA x 2 , true online double conversion UPS UNIT having
IGBT based inverter & rectifier with THDi less than 5% at rated load with battery
modules to provide about 15 minutes backup on load of 8 kW.
Should be 19" rack mountable arrangement with rack mounting kits.
The batteries should be rack mountable.
The UPS should have an SNMP card for remote monitoring.
The UPS should be housed in a 42U rack, 800mm wide, and 1000 mm (minimum)
depth with front & rear glazed door having 19" mounting arrangement for IT
equipment.
The Battery pack should have colour and construction matching the UPS system.
The UPS should have built in SNMP card for remote monitoring.
01

Kangra at Tanda
Page 32 of 219

The UPS should have built-in output distribution with 16A circuit breakers and
IEC type connectors.
16A Automatic Transfer Switch
The Modular Data Centre should include a 1U rack mounted 16A Automatic
transfer switch of electromechanical type, with SNMP interface and built in IEC
outlets. It should remotely monitor the current supplied by the ATS.
Main MCCB panel, wall mount
100A 3P MCCB box (RAL 7032 powder coated) wall mountable having suitable
cable entry and termination. (Incomer MCCB, 100A, 4 pole, 25kA).
Main electrical panel, rack-mount
1 nos, of 19" Rack mounting electrical panel box complying to relevant Indian
electrical codes for Panel fabrication and support structure with following
specifications:
a. All MCB should be type D
b. Bus-bar : 100A rated TPN copper busbar
c. Outgoing:
MCB, 25A DP - 6 Nos. (4nos for A/C, 1no Spare & 1no for Enclosure
Light)
MCB, 80A Three Phase - 2 Nos. (for 10kVA UPS)
Panel box should not use more than 4 U space in the IT Rack
All mounting & connection accessories - 1 set (including termination, ferruling,
nuts, washers, etc.)
4C X 25 sq.mm copper conductor, XLPE unarmoured cable in a metal hose for
Main Panel I/c
4C x 10 sq.mm copper cable for UPS units
Depth Variable Slide Rail 590-930mm / 80kg
3C x 2.5 sq.mm copper flexible PVC cable for lighting, access control, fire
detection system and body grounding
Power / Data / Refrigerant piping, floor mount covered cable tray supply
Cable Trough of size: 200W x 50H mm with Cover Lid & necessary accessories for
fixing (Length of Each Cable Trough = 2.5Mtrs)
Cable Trough with Cover Lid should be made of 2mm thk Sheet Steel & Powder
Coated to Light Grey.
7kW sensible cooling capacity; high CFM high sensible close coupled cooling
units in N+N configuration for redundancy
Rack mount closed coupled cooling system:
High CFM high sensible cooling Indoor and Outdoor units.
The cooling system should be of DX type, with separate indoor units
(evaporator) and outdoor units (condenser). The compressor should be part of
the outdoor unit and should eliminate noise and vibration inside the indoor unit.
The indoor unit should be rack mountable, horizontal throw type, suitable for
rack contained, close coupled cooling architecture.
The sequence controller should run one cooling unit at a time, and should
perform a changeover, in case of failure of any of the cooling units.
Should Include an integrated heat exchanger mounted on the inner side of side
walls with 4 fans. The air routing in the Rack should run horizontal, i.e. the cold
air exits in front of the IT components and the warm air drawn in at the rear.
Super Digital Inverter external Air-Condition unit, Cooling output range 5 # 7 kW
with >>40% energy saving instead of on / off system with 100% climate control

Kangra at Tanda
Page 33 of 219

redundancy.
Redundancy control unit
Zero Power monitoring for total cooling group (indoor and outdoor) with N.C.
alarm contact.
Drain for condensation water (without pump)
Set-point 23 C (server inlet temperature)
Refrigerant Type : R410a
Power connection for indoor and outdoor unit: 230 VAC / single phase / 50Hz
Copper piping
Refrigerant copper piping with (19 mm / 13 mm thick) closed cell elastomeric
nitrile rubber tubular insulation between each set of indoor & outdoor units as
per specifications, all piping inside the room will be properly supported with MS
hanger. Transmission wiring between indoor to outdoor unit in a suitable
PVC conduit - 1.5 mm
2
4 core. PVC Drain Piping - 25mm dia. Rigid PVC piping
complete with fittings duly insulated with 6mm thick nitrile rubber tubular
sleeves.
Access control to each IT rack with CMC III Transponder Reader
The transponder reader unit is used to release enclosure or room doors when a
transponder card is held without contact in its vicinity. The card UID should be
checked in the connected CMC III PU and, if validated, an appropriate door
should get released. The transponder reader unit should have an identification
that allows it to be detected automatically by the CMC III PU.
Rack-mountable fire detection and suppression system (Master)
1U rack mountable device with high sensitivity smoke detection with active
sampling. It should have a built-in NOVEC 1230 suppression system sufficient for
1 IT rack with integrated fire panel. This device should be able to monitor using
potential free contacts. With actuator, discharge nozzle, piping complete with
accessories. The system should also include a manual abort option.
Rack-mountable fire detection and suppression system (Slave)
1U rack mountable device that should integrate with the Master device, and
provide NOVEC 1230 fire suppression to 1 IT rack. With actuator, discharge
nozzle, piping complete with accessories. Master and slave should be able to
support all the 4 racks.
Video surveillance system with 2 units (wall mount USB colour cameras)
2 nos. high resolution colour camera with USB connectivity. The camera should
draw power from a central monitoring unit, and should store video on
networked storage device via the central monitoring system.
Door contact: Should enable a monitoring tool appliance to detect the act of
opening a door, which triggers surveillance recording.
42U Closed IT Racks
19 DKPS Frame, 800W x 2000H(42U) x 1000D, plain top cover, bottom cover
with standard gland plates with foam insert for cable entry, 2 pairs of 42U 19" L-
type angle & special assembly kit for mounting 19" angles & punched sections.
Colour: RAL 7035
Glazed Front Door with single-pane safety glass, right / left hinged, provided with
3-point locking system and ergoform handle with lock Insert with unique key.
Sheet Steel Rear Door, right / left hinged, provided with 3-point locking system
and ergoform handle with lock Insert with unique key.
Set of Side Panel 2000H X 1000D screw fixed.

Kangra at Tanda
Page 34 of 219

Based channel / Plinth - 800Wx1000Dx100H.
2nos of Vertical PDU, 16A with 10 x 5/15 sockets with 4m power chord with IEC
C20 plug.
Captive Hardware (pack of 20).
Air Baffle Plates.
Metal Shunting Rings 90x60 (pack of 10).
Copper earth rail 15x3x500 with 10 points with screws and insulators.
Component shelf 720mm deep
Baying kit (pack of 6)
Foam insert for vertical shielding, installed between racks
Closed rack, very low noise level.
Total two (02) racks are needed in the complete unit.
Monitoring system with GUI and with e-mail alerts
Critical system like UPS, Cooling, Fire alarm, Fire suppression (options like DG
set) should be monitored through central monitoring system.
Automatic Door control feature is required for emergency remote operation as
well as in case when temperature inside the rack goes high during UPS battery
mode operation.
The tool does not require any CPU/Computer. It should need a Virtualized server
only in case we want to deploy a tool for parameter trending reports.
All critical alarms should be communicated to user group through emails or
optionally thru SMS.

The OEM should have a Installation base of at least 5 modular Data centre in
India.
5.3 SERVERS
5.3.1 SCOPE OF WORK
a. Supply: Supply of the servers including peripherals, completely described in the BID, and their
installation, maintenance at on-site / off-site locations provided by the Institute.
b. Installation:
i. Fixing and setting up the servers on the racks of data centre at the Institute.
ii. Installing the Operating System.
iii. Configuring all the software associated with the server management.
iv. User training to the IT staff of the Institute
c. Uptime: The Bidder will ensure an uptime of 99% for the Servers deployed by them.
e. AMC: The technical maintenance of the Servers will be the responsibility of the Bidder. The
warranty only.
Needed

Kangra at Tanda
Page 35 of 219

1. Blade Chassis
1. Chassis
Upto 10U Chassis to house at least 10 Blade servers and Provide common
resources shared by blade servers like power, system management, cabling,
ethernet management Fibre Channel Switches for storage connectivity, and
I/O and ports for USB. Should have redundant connectivity feature to I/O on
blades.
2. Ethernet Switch Module
Layer 3 10G Ethernet Switching Modules to be provided in redundant
configuration for Connecting to all the blade servers to external Switch.
Configuration should help minimize the Ethernet Cables Coming out of the
chassis and the Ports to be used in external Ethernet Switches. Ethernet
Switch provided should support Virtualization on Network layer. Chassis
should support 40GB uplink as well if required in future
3. Fibre Channel Modules
8 Gbps fibre Channel SAN Switch modules to be provided in redundant
configuration for option of connecting all the server blades to external SAN
Fabric. Configuration should help minimize the fibre Channel cables coming
out of the chassis and the Ports to be used in external SAN Fabric. Chassis
should support 16GB FC Channel as well if required in future
4. Management Module
The enclosure has to be configured with Management Modules in
Redundant configuration in order to provide IP Based management of the
Blade Servers and the vital components like FC and Ethernet modules,
Health monitoring, Inventory management and Remote Console to each
blade.
5. Power Modules
N+N Redundancy to be provided on the Power supplies powering the
chassis. Redundant connectivity for power to each blade to be provisioned
using independent paths to the Blade Servers.
6. Mid Plane
The enclosure should have completely passive mid plane for providing
connectivity of the shared resources to the blade servers in Dual Redundant
Manner.
7. Cooling
100% Redundant Cooling fans to be provided inside the enclosure.
8. CD ROM
The enclosure should have at least one pair external/internal of CD RW/DVD
Combo Drive.
9. Supported Hardware Platform.
The enclosure should support simultaneous running of blades based on x86 /
RISC / EPIC.
10. Chassis Management
Blade Chassis should configured with Hardware/Software tool for
comprehensive management of servers, networking, and storage and also
integrate with virtual server management with hypervisor management
tools.
Should provide for the following Network Management Capabilities:
02

Kangra at Tanda
Page 36 of 219

Management of network switches from a variety of vendors.
Discovery, inventory, and status monitoring of switches.
Graphical network topology views.
Support for KVM, pHyp, VMware virtual switches, and physical switches.
VLAN configuration of switches.
Integration with server management.
Per-virtual machine network usage and performance statistics provided
to VM Control.
Logical views of servers and network devices grouped by subnet and
VLAN
Should provide for the following Virtualization Management Capabilities:
Create virtual servers.
Edit virtual servers.
Manage virtual servers.
Relocate virtual servers.
Discover virtual server, storage, and network resources and visualize the
physical-to-virtual relationships.
Should provide for the following Storage Management Capabilities:
Discovery of physical and virtual storage devices
Support for virtual images on local storage across multiple chassis.
Inventory of the physical storage configuration.
Health status and alerts.
Storage pool configuration
Dynamically create Storage volumes
Disk sparing and redundancy management.
Virtual volume management.
Support for virtual volume discovery, inventory, creation, modification,
and deletion
2. Blade Servers
1. Processor
2 x Intel Xeon Quad Core E5-2609 CPU @ 2.4 GHz or better.
2. Chipset
Intel Chipset C600 or higher.
3. Memory
16GB DDR-3 Memory Upgradeable to 768GB (24DIMMS Slots).
4. Hard Disk Drive
Upto two 300 GB 10 K SAS HDD.
5. Controller
One integrated RAID Controller supporting RAID 0,1 .
Two PCIe Slots for further Ethernet or Fiber expansion cards.
6. Networking
Dual 10G Ethernet ports.
Wake on LAN / Serial over LAN / Full Duplex /TCP/IP Offload Engine / Load
balancing or teaming. Dual Connections to the Redundant Ethernet switches
to be provided.
7. SAN Connectivity
Connectivity to External Storage Using fibre Channel HBA Card (8 Gbps).
Card should have dual ports connected to two separate controllers through
the mid-plane to shared fibre channel modules at back of the chassis.
8. Pre Failure Alert Diagnostics
Server should be able to give alert for maximum component before it before
it actually fails. The component covered under pre failure alert should cover
atleast processor/Hard drive/ memory/Fan and Voltage regulator.
16

Kangra at Tanda
Page 37 of 219

9. Systems Management Processor
An integrated systems management processor to provide system and
environmental monitoring, event recording, alert capability.
10. Security
Power-on password / administrator password / unattended boot /
selectable boot / unattended start mode.
11. OS Compatibility
Microsoft Windows Server 2008 /2008 R2 Standard x64 Editions, Microsoft
Windows Server 2012, Enterprise Edition Red Hat Linux.
5.4 STORAGE
5.4.1 SCOPE OF WORK
a. Supply: Supply of the storage devices including peripherals, completely described in the BID,
b. Installation:
i. Fixing and setting up the storage devices on the racks of data centre at the Institute.
ii. Mounting of the Storage devices on the servers.
iii. Configuring all the software associated with the storage management.
iv. User training to the IT staff of the Institute
c. Uptime: The Bidder will ensure an uptime of 99% for the Storage deployed by them.
e. AMC: The technical maintenance of the Storage will be the responsibility of the Bidder. The
warranty only.
Needed
1. Unified Storage
RAID Controller
Dual Active Controller with no single point of failure in the storage array.
Protocols Supported
Proposed storage should support both block level protocols like FC, FCoE and
iSCSI and File level protocols CIFS and NFS.
Cache
The Storage subsystem shall be configured with minimum of 16 GB usable cache
for block level data and minimum 64 Gb scalable to 128 GB of cache / memory
for file level data.
It shall support de-staging of cache to disks on power down or shall support
internal battery backup of cache for at least 48 hours. The data in cache shall not
be lost in the case of power failure.
Host Interface
Storage system should be configured with sufficient number of 4/8Gbps FC,
front-end ports for the aggregate FC bandwidth to the host should be 32 Gbps
and should be scalable to 198 GBPS or more.
Storage system should support 1/10 Gbps front-end iSCSI ports, for the
01

Kangra at Tanda
Page 38 of 219

aggregate iSCSI bandwidth to the host should be 40 Gbps.
Drive Interface
Storage should support at least 4 numbers of ports with 6Gbps or higher SAS 2.0
for connectivity to disk drives.
Supported Drives
The storage subsystem shall support 300/600 /900/1200 GB FC/SAS disk and 1
TB or higher SATA/FATA /Nearline SAS disk drives.
Storage should support SSD drive. The storage shall also support the
functionality to automatically move the data from lower performing disk to SSD,
based on the performance requirement. Required licenses for the same shall be
provided.
RAID Level Supported
0,1,5,6,10
San Supported
All Standard SAN Switch needs to be supported.
Disk Scalability
The storage should be configured with 6 TB raw capacity using 300GB 15K RPM
SAS disk and 23 TB raw capacity using 1 TB 7.2K RPM NL-SAS disk. The storage
should be scalable to at least 500 drives.
Availability
Should offer dual active-active and failover controllers Should offer redundant
power supplies and cooling units Should support hardware based RAID 0, 1, 5
and 10 Should support LUN Masking and software for the same should be
configured.
It should support Non-disruptive component replacement of controllers, disk
drives, cache, power supply, fan subsystem etc.
The storage shall support the following High Availability Clusters solution from
HP, IBM, Symantec, EMC, SUN and Windows.
Performance
Proposed storage system should offer cache IOPS of minimum 700,000 or should
have SPC-1 benchmark on minimum 50,000.
Licensing
Licenses for software (Storage Array Management, Point-in Time Copy, Volume
Copy, multipathing software for host) should be provided as part of the solution.
System should be configured with necessary multipathing components for high
availability.
Required licenses for Snapshots/clones/ remote replication should be
configured.
Management
The storage system shall be configured with GUI based management software as
below:
Monitor and manage the storage array
Configuring PITs
Remote Storage base replication
Storage front end port monitoring
Disk Monitoring
LUN management.
Storage Component replacement, etc.
Snapshot/ Full Volume copy

Kangra at Tanda
Page 39 of 219

The Storage should support Point-in-time copy and full volume copy for
heterogeneous storage arrays. It should support these operations from storage
of one OEM to storage from another OEM.
Remote Replication
The Storage arrays shall support data replication in both synchronous and
asynchronous modes across heterogeneous storages from third party OEM's.
Operating System Support
The storage system shall support the latest OS releases & Cluster of the
following mentioned servers / OS:- CISC/RISC/EPIC-based Servers running
Microsoft, HP, IBM, Sun, Linux.
Heterogeneous Storage Support
The storage system shall support the third party storage system of all major
OEMs and should be able to virtualize them.
NAS features
Storage shall have flexibility for provisioning of storage resources with its
support of NFS, CIFS, FTP, HTTPS and SCP file protocols.
The storage should support file replication and file-level snapshots for business
continuity and disaster recovery.
The storage should be scalable upto 2 PB and should based on
Journalised/Parallel File system
The storage shall include the local capabilities, designed to deliver policy-based
management of files to reduce costs through use of tiered storage, and improve
data governance and should support movement of files across all tiers of storage
including Tape Media.
Storage management software shall provide detailed monitoring, reporting, and
management within a single console.
Additional Features (should support)
Unified storage should be managed from single console i.e both block and file
level storage management should be from one GUI.
All specifications stated are minimum required. Proposed system may have
features over and above the minimum specification stated. Bidder
should ensure that the performance of storage is not negatively affected for the
entire duration of the contract
5.5 NETWORK SWITCHES
5.5.1 SCOPE OF WORK
a. Supply: Supply of the switches including peripherals, completely described in the BID, and their
installation, maintenance at on-site/off-site locations provided by the Institute.
b. Installation:
i. Fixing and setting up the switches including mounting them on the racks provided by the
Institute.
ii. Configuring all the software associated with the switches excluding the Network
Management Software but includes all the plugins needed.
iii. User training to the IT staff of the Institute
c. Uptime: The Bidder will ensure an uptime of 99% for the Switches deployed by them.

Kangra at Tanda
Page 40 of 219

e. AMC: The technical maintenance of the Switches will be the responsibility of the Bidder. The
warranty only.
Needed
1. Core Switches with following configuration
Hardware Architecture
Modular Chassis based Architecture with minimum 8 usable slots.
Each Chassis should have Redundant Power Supply and required software
license.
Chassis should be equipped with Redundant Supervisor / Controller card /Switch
fabric. Failure of one CP card should not degrade the performance of the switch.
It should have non-blocking wire-speed architecture.
It should have hot swappable modules.
It should be architected to support real time applications like voice, video, data
by having distributed architecture.
It should support policy based port mirroring.
Port Densities Needed
1. 24 ports of 10Gbps (LR interface) on minimum 4 line module in non-
blocking operation.
2. 48 ports of 10/100/1000 in non-blocking operation.
3. Additional ports for configuring 2 such switches in high availability.
Port Densities Supported
Minimum interfaces type supported on a single chassis:
1. Minimum 40 ports of 10 Gig in Non-blocking operation
2. Minimum 24 interfaces of Gig Fiber
3. Minimum 48 ports of 10 / 100 / 1000 base TX in Non-blocking operation
Performance
Switching fabric should be 800 Gbps or more and scalable
Forwarding rate should be Minimum 600 Mpps for IPv4 and IPv6
Should support 9K Jumbo frames
Switch Should support min 100Gbps bandwidth per slot
L2 Features
IEEE 802.1Q VLAN
Support for at least 4000 active VLANs.
802.1s and 802.1w
IP v4: IGMP v1, v2 and v3
IPv6 : MLD v1 & v2 / MSDP
Link Aggregation based on 802.3ad across line cards
Minimum 30 LAG needs to be supported
Minimum 100K MAC address support and scalable
Layer 3 Features
IP v4 : Static Routing, OSPF, RIP, BGPv4, VRRP, ECMP, PIM Spares Mode, SSM
IP v6: Static Routing, RIPng, OSPFv3, VRRP,
Router Discovery Protocol
Policy Based Routing
Min of 256K IPv4 & IPv6 unicast routes and 100K IPv4 and IPv6 multicast route
should be supported
Quality of Service
8 hardware queues per port
Ingress Policing / Egress Shaping
02

Kangra at Tanda
Page 41 of 219

802.1p / Tos / Diffserv marking and mapping
WRR and SP
Switch Should support min 50K security and QoS hardware ACLs
VRF (for IPv4 & IPv6)
Security and Management
Standard ACLs on all ports
Many to one port mirroring based on port, VLAN and flow based
Radius and TACACS+
Secure Shell (SSH) Protocol, HTTPS, LDAP and DoS protection
IEEE 802.1x, IP Route Filtering
Switch needs to have console port and dedicated Ethernet port for
administration & management,
SNMPv1, SNMPv2/v3
Switch should support real time performance monitoring
Support management using CLI, GUI using Web interface. Additionally,
management can also be done using NMS.
Support FTP / TFTP for upgrading the operating System
Standards
RoHSv6 Compliant
NEBS Compliant
IEEE 802.1x support
IEEE 802.3x full duplex on 10BASE-T and 100BASE-TX ports
IEEE 802.1D Spanning-Tree Protocol
IEEE 802.1p class-of-service (CoS) prioritization
IEEE 802.1Q VLAN
IEEE 802.3x be on 10 BaseTx / 100 Base Tx / 1000 Base Tx
IEEE 802.3u 10 BaseT / 100 Base Tx / 1000 Base Tx
EAL3 certified
2. Distribution Switches with following configuration
Modular Chassis based Architecture with minimum 7 slots.
Each Chassis should have Redundant Power Supply and required software
license.
Chassis should support Redundant Supervisor / Controller card/Switch fabric.
Failure of one CP card should not degrade the performance of the switch.
It should have hot swappable modules.
It should have Security features like policy-based access control, IP source guard,
dynamic ARP inspection, and DHCP snooping, etc.
It should support policy based port mirroring.
1. 12 ports of 10Gbps (LR interface) distributed on minimum two line cards in
non-blocking operation.
2. 48 ports of 10 / 100 / 1000 in non-blocking operation.
3. 96 ports of 1 Gig SFP polulated with LX ports.
4. Additional ports for configuring 2 such switches in high availability
Port Densities Supported
Minimum interfaces type supported on a single chassis:
1. Minimum 30 ports of 10 Gig in Non-blocking operation
2. Minimum 24 interfaces of Gig Fiber in Non-blocking operation
3. Minimum 144 ports of 10 / 100 / 1000 base TX
Performance
04

Kangra at Tanda
Page 42 of 219

High back plane speed 600 Gbps or more
Forwarding rate should be Minimum 400 Mpps for IPv4 and IPv6
9K Jumbo frames
L2 Features
HW based Source Learning
IEEE 802.1Q VLAN
Support for at least 4000 active VLANs
Minimum 20K MAC address support
802.1s and 802.1w
IP v4: IGMP v1, v2 and v3
IPv6 : MLD v1 & v2
Link Aggregation based on 802.3ad across line cards
Minimum 30 LAG needs to be supported
Layer 3 Features
IP v4 : Static Routing, OSPF, RIP, BGPv4, VRRP, ECMP, PIM Spares Mode, SSM
IP v6: Static Routing, RIPng, OSPFv3, VRRP.
Router Discovery Protocol.
Should have 128 K IPv4 and IPv6 unicast routes and 50K IPv4 and IPv6 multicast
route.
Policy Based Routing.
Quality of Service
8 hardware queues per port
Ingress Policing / Egress Shaping
802.1p / Tos / Diffserv marking and mapping
WRR and SP
Security and Management
Standard ACLs on all ports
Many to one port mirroring based on port, VLAN and flow based
Radius and TACACS+
Secure Shell (SSH) Protocol, HTTPS, LDAP
IEEE 802.1x, IP Route Filtering
Switch needs to have console port and dedicated Ethernet port for
administration & management,
SNMPv1, SNMPv2/v3
Support management using CLI, GUI using Web interface. Additionally,
management can also be done using NMS.
Support FTP / TFTP for upgrading the operating System
Should support In-Service-Software upgrade or equivalent mechanism
Standards
RoHSv6 Compliant
NEBS Compliant
IEEE 802.1x support
IEEE 802.1Q VLAN
EAL3 certified
3. Server Aggregation Switches with following configuration
Enterprise class rack mountable switch.
04

Kangra at Tanda
Page 43 of 219

It should have Redundant Power Supply.
1. Minimum 20 ports of 10G interfaces SR
2. Minimum 12 ports of 1G interfaces TX
3. High Speed Dedicated stacking ports (Minimum 40 Gbps) Stacking Kit.
Port Densities supported
Minimum interfaces type supported on a single switch:
1. Minimum 20 ports of 10G interfaces SR
2. Minimum 12 ports of 1G interfaces TX
3. High Speed Dedicated stacking ports (Minimum 64 Gbps) Stacking Kit.
4. 10G/Gigabit Ethernet port - 32 ports & scalable
5. Support consolidating IP and traditional Ethernet protocols into single
media-FCOE capabilities
Performance
Each switch should have non-blocking switching fabric of minimum 640 Gbps or
more.
Each switch should have Forwarding rate of minimum 480 Mpps for IPv4 and
IPv6.
9K Jumbo frames.
BootP / DHCP Relay
L2 Features
Minimum 20k MAC addresses
Minimum 1000 active VLANs
Datacenter bridging exchange, IEEE 802.1Qbb
Switch support auto device discovery and storm control
DNS,TFTP and NTP protocol
Layer3 Features
It should support both IPv4 and IPv6 routing
Should have features enabled for RIP, RIPng, OSPF, OSPFv4 for IPV4 & MLDv2
VLANs
IEEE 802.1Q
Port based
Dynamic VLAN
Spanning Tree
IEEE 802.1s
IEEE 802.1w
IEEE 802.1d
QoS / ACLs / Policies
802.1X Network Security and Radius/TACACS ,AAA authentication
MAC Address filtering based on source and destination address
Support for various ACLs like port based, VLAN based and Standard / Extended
ACLs L2- L4
minimum 8 number of hardware queues per port
Policy based traffic classification based on Layer 2 to Layer 4
Classification on L1, L2, L3 and L4 parameters
IGMP v1,v2,v3, IGMP snooping
Other features supported -
standards such as ieee802.3.ieee802.3u,ieee803z,802.3ab,
IEEE802.3ae, ieee802.1D,ieee802.1w,ieee802.1s,
IEEE802.1p, ieee802.1Q, 802.1x,802.3ad,802.1X,ieee802.3x
Security / Management
SNMP v1, v2, v3, RMON/RMON-II enabled, SSH,telnet,GUI, Web management

Kangra at Tanda
Page 44 of 219

and should have out of Band Management port
Standards
RoHSv6 Compliant
NEBS Compliant
IEEE 802.1x support
IEEE 802.1Q VLAN
EAL3 certified
4. Stackable PoE Edge Switches with following configuration
In a standalone mode, the switch should provide minimum 24 usable ports.
The switch should support IEEE 802.3af and IEEE 802.3at standard.
Port Densities Needed and Supported
1. Minimum 24 ports of 10 / 100 / 1000 base TX(PoE)
2. Minimum 2 Combo ports populated with LX modules
Performance
Switching fabric of each switch should be minimum 48 Gbps or more.
Packet forwarding throughput should be 36 Mpps for packet size of 64 Bytes.
Minimum 10K MAC addresses
It should support minimum 1000 Active VLANs and should be possible to
configure port based VLAN.
High availability Features
It should support 802.1w, 802.1s, 802.1d and 802.3ad.
The operating system should same as that for offered Core, Distribution and
Aggregation Switches with same command lines.
The Switches should support quality of service (QoS), granular rate-limiting,
Access Control Lists (ACLs), and multicast services. It should support Ethertype
classification, port disable rules, and port redirect action.
It should support profile based role assignment functionality
Quality of service
It should support advanced L2 features.
It should support 802.1p, DSCP marking
It should support Flow-based QoS for traffic prioritization
It should support Eight hardware-based queues per port with Weighted Round
Robin (WRR).
It should support Flow-based bandwidth management, ingress policing; egress
rate shaping per port.
Should have Static routes and support RIP, OSPFv3 in future.
Management Features
It should support SNMPv1, v2 and v3, Telnet , FTP, HTTP, SSH, SSL
IGMP v1 / v2 / v3 snooping to optimize Multicast Traffic.
Should support dual image and multiple configuration file.
Web Based and CLI based management.
Port Mirroring for troubleshooting.
BootP / DHCP client.
Syslog support.
RFC 2819 RMON Groups.
IPv4 and IPv6
170

Kangra at Tanda
Page 45 of 219

Should support both IPv4 and IPv6.
Security Features
802.1x port based user authentication with multiple host mode.
802.1x Multi-client, multi-VLAN support for per-client authentication and VLAN
assignment.
Should support minimum 8 supplicants of 802.1x per port.
Guest VLAN.
MAC address lockdown.
RADIUS and FTP security extensions
Access control lists to filter out unwanted traffic including denial of service
attacks
STP root guard and BPDU guard.
Standards
RoHSv6 Compliant
NEBS Compliant
IEEE 802.1x support
IEEE 802.1Q VLAN
EAL3 certified
5. Routers with following configuration
Performance
The Router should have a minimum routing performance of 900 kpps.
The Router should have a minimum IPSec forwarding performance of 600
Mbps and 1000 VPN tunnels.
The Router should have IPS performance of 600 Mbps.
Router should have minimum 6 slot for WAN connectivity
Router should have 4 x 10/100/1000 ports for LAN and WAN connectivity.
Router should support modular LAN and WAN connectivity options
including 10 Gigabit, Gigabit Ethernet (copper and fiber) and T1/E1 physical
interface modules.
Router should have a modular architecture and should comply to all the
features asked within or using external box. The external box should meet
all the redundancy features asked for the router.
Router should have internal redundant Power supply.
Minimal performance degradation when running advanced services such as
stateful firewall, NAT, and IPSec.
The Router should support Firewall, IPSEC, IPS from day 1.
High Availability
Should support redundant GE connection to LAN
Should support Redundant Power supply
Should support fast reboot for minimum network downtime
Should support Non-Stop forwarding for fast re-convergence of routing
protocols
Should support multiple storage of multiple images and configurations
Should support link aggregation using LACP as per IEEE 802.3ad
Should support VRRP or equivalent
Protocol Support
The Router should support IPv4 and IPv6 routing
The Router should have VRRP
The Router should have Static Routes
02

Kangra at Tanda
Page 46 of 219

The Router should have RIPv1 & RIPv2
The Router should have OSPFv2 and IS-IS routing features
The Router should have MPLS, BGP & BGPv4+
The Router should support Policy Based Routing
The Router should support Routing over IPSec Tunnels
The Router should support ECMP
Router should support IPv6 Routing features
QoS Features
Router should support Class-based queuing with prioritization
It should be possible to configure maximum bandwidth and guaranteed
bandwidth
Router should support Queuing based on VLAN, DLCI, interface, bundles, or
filters
Router should support Marking, policing, and shaping
Router should support congestion management features like WRED
Classification and Marking: Policy based routing, IP Precedence, DSCP, MPLS
exp bits
Congestion Management: WRED, Priority queuing, Class based weighted fair
queuing
Traffic Conditioning: Committed Access Rate/Rate limiting
Signalling: RSVP
Link efficiency mechanisms: cRTP, LFI, MLPPP
Per VLAN QoS
Should be able to handle and prioritize VoIP traffic.
Security Features
Router should support AAA using RADIUS or TACACS
Router should support Packet Filters
Router should have Stateful Firewalling
Router should have Network attack detection
Router should have DoS and DDoS protections
Router should support Tunnels (GRE, IP-in-IP, IPSec)
Router should have DES (56-bit), 3DES (168-bit), AES (256-bit)
encryption support
Router should support MD5 and SHA-1 authentication
Router should support Prevent replay attack
Router should have role based access mechanisms.
Router should support Network address translation (NAT).
Debug, Alarms & Diagnostics
Support for monitoring of Traffic flows for Network planning and Security
purposes
Display of input and output error stats on all interfaces
Display of Dynamic Arp table
Trace-route, Ping and extended Ping
Should have extensive support for SLA monitoring for metrics like delay,
latency, jitter, packet loss, and MOS
Management
Router should have Console, Telnet and Web for management
Router should support Software upgrades through Web
Router should support SNMPv2 and SNMPv3
Standards
NEBS certified
EAL3 certified

Kangra at Tanda
Page 47 of 219

5.6 WIRELESS EQUIPMENT
5.6.1 SCOPE OF WORK
a. Supply: Supply of the indoor as well as outdoor access points including peripherals, completely
described in the BID, and their installation, maintenance at on-site/off-site locations provided by
the Institute.
b. Installation:
i. Fixing and setting up the access points at relevant positions.
ii. Mounting the Wireless LAN controller on the racks provided by the Institute.
iii. Configuring the Wireless LAN Controller and its integration with the wireline switch network
of the Institute.
iv. Configuring the Wireless Management Software and its integration with the Network
Management Software.
v. Configuring all the software associated with the access points as well as Wireless LAN
controller excluding the Network Management Software but includes all the plugins needed.
vi. User training to the IT staff of the Institute
c. Uptime: The Bidder will ensure an uptime of 99% for the access points and the WLAN controller
deployed by them.
e. AMC: The technical maintenance of all the Wireless Equipment supplied will be the
responsibility of the Bidder. The charges for such AMC shall be borne by the Institute after the
expiry of one year standard warranty only.
Needed
1. WLAN Controller with following modules / licenses
Controller Redundancy working in load sharing mode
Power Supply Redundancy
In Campus Access Point License 512
Enforcement Module for 4000 users
Intrusion Detection and Prevention System
Voice QoS License - 128 Users
Should support 802.11n
Rogue AP Detection and Containment License
It should be chassis/appliance based with minimum 2 interfaces of Gigabit.
It should support minimum 1024 campus connected Access points including
Mesh AP and 1024 remote access points.
It should be possible to use the same controller for Wi-Mesh architecture
without replacing any hardware.
It should be an integrated appliance with inbuilt security features - stateful
firewall, IPS, VPN, QoS etc.
It should support minimum 32K Mac addresses
It should support minimum 2000 IPSEC VPN Tunnels
It should support minimum 100,000 concurrent sessions
Key Capabilities
Centralized architecture with thin APs (Access Points) and intelligent controller.
Solution should support for centralized encryption
02

Kangra at Tanda
Page 48 of 219

Solution should be capable to support roaming across AP and Central Controller.
Solution should support centralized AP management to provide simplified
administration.
Support for AAA authentication with need for external Radius / LDAP server.
Support for web based authentication built in to solution, to support non 802.1x
clients.
Traffic Separation / User Segmentation Capability
Captive portal, 802.1X and MAC address authentication
Username, IP address, MAC address and encryption key binding for strong
network identity creation
Per-packet identity verification to prevent impersonation
Endpoint posture assessment, quarantine and remediation
NAC Support
Internal user database for AAA server failover protection
Role-based authorization for eliminating excess privilege
Robust policy enforcement with stateful packet inspection
Per-user session accounting for usage auditing
Web-based guest enrolment with GuestConnect
Configurable acceptable use policies for guest access Dynamic PSK
User Authorization Capability
Dynamic VLAN assignment based on user credentials.
Time of Day user Authorization.
User based QoS assignment.
User Based Encryption Type selection.
Traffic Filtering Based on User credentials.
Roaming Support
Support roaming between APs on one WLAN switch
Support roaming between APs on different WLAN switches on different subnets
(cross-subnet roaming)
Support for Security and Authentication Standards
System-wide bi-directional traffic monitoring by Packets captured and delivered
across any L2/L3 boundary.
Packet Capturing by port/virtual-port, user, radio or SSID
XML-based API for external captive portal integration
WPA/WPA2
802.11i/802.1x
EAP-TLS, EAP-TTLS, EAP-MD5, EAP w/MS
CHAP v2 and PEAP, PEAP-TLV
MAC authentication
Stateful Firewall Features
Stateful packet inspection tied to user identity or ports
802.11 station awareness for WLAN fire walling
Session mirroring and per-packet logs for forensic analysis
Application Layer Gateway (ALG) support for SIP, SCCP, RTSP, Vocera, FTP, TFTP,
PPTP
Source and destination Network Address Translation (NAT)
Wireless Threat Protection
Flood attack detection
RF jamming protection
AP MAC address masquerading detection
Weak WEP IV detection
Rogue AP protection
3rd party AP performance monitoring and troubleshooting
ASLEAP, death broadcast, null probe response detection
EAP handshake and sequence number analysis

Kangra at Tanda
Page 49 of 219

Denial of service attack protection for APs and stations
Valid AP impersonation detection
Support for Access Control on WLAN
User / group identity
Multiple SSID
MAC filtering
Layer 3 deny filters
Time-of-day restrictions
Day-of-week restrictions
Location-based policies
Client blacklisting
Subnet classification
VLAN assignments
Roaming restrictions
Dynamic RF Management Capabilities
Support for dynamic channel assignment
Support for dynamic interference avoidance
Support for dynamic user load balancing by automatically adjusting client-to-
access point associations to optimize user performance during peak usage
periods.
Support for dynamic power control by automatically adjusting AP radio power
transmission levels to optimize user performance when RF conditions change.
Support for dynamic coverage hole protection by automatically increasing power
levels of neighboring APs and automatically adjusting channels to compensate
for an unexpected outage.
Load Aware Scanning to avoid disruption to user sessions during heavy loads.
Traffic Shaping for guaranteeing airtime for downstream traffic to each client
depending on its type b/g/n or a/n.
Airtime Fairness for controlling received wired data to regulate downstream
throughput for involving packet processing changes on the controller and also
involving per client buffering of TCP frames at the AP.
Voice Call Admission Control
Voice Call Admission Control for optimizing call reliability and voice quality by
limiting the number of active voice calls that an AP will support and load-
balancing or ignoring excess calls.
Automatic Voice Prioritization.
WMM Queue Enforcement for ensuring that QoS policies are properly enforced
by preventing users from transmitting non-voice traffic using voice WMM
queues.
2. Indoor Access Points (802.11a/b/g/n)
The Access Points should be connected to the network infrastructure and work
with a Wireless LAN switch which will be located in the network core.
APs should have the option to connect the WLAN switch over an IPSec
connection to support remote APs, especially when APs are placed behind
NATing device.
Integral Antennae
Integral, diversity supporting dual, tri-band omni-directional high gain antennas
with 180 degree movement.
Integral antenna gains (minimum)
a. 2.4-2.5 Ghz / 4.4 dBi
b. 5.150-5.350 Ghz / 6 dBi
c. 5.6 Ghz / 5 dBi
Radio Specs - 802.11a
275

Kangra at Tanda
Page 50 of 219

Frequency band
a. 5.150 ~ 5.250 Ghz (lower band)
b. 5.250 ~ 5.350 Ghz (middle band)
c. 5.725 ~ 5.825 Ghz (higher band)
Radio technology: orthogonal frequency division multiplexing (OFDM)
Modulation type: BPSK / QPSK / 16-QAM / 64-QAM
Transmit power: configurable by system administrator / professional installer
MAC: CSMA/CA with ACK
Data Rates: 6, 9, 12, 18, 24, 36, 48, 54 Mbps per channel
Radio Specs - 802.11b
Frequency band
a. 2.4 ~ 2.483Ghz (US, Canada & ETSI)
b. 2.4 ~ 2.497Ghz (Japan)
Radio technology: Direct Sequence Spread Spectrum (DSSS)
Modulation type: CCK / BPSK / QPSK
Transmit power: configurable by system administrator
Data Rates: 1, 2, 5.5, 11 Mbps per channel
Radio Specs - 802.11g
Frequency band
a. 2.412 ~ 2.462Ghz (US, Canada)
b. 2.412 ~ 2.472Ghz (ETSI)
c. 2.412 ~ 2.484Ghz (Japan)
Modulation type: CCK / BPSK / QPSK / 16-QAM / 64-QAM
Multi-mode radio band 802.11a or 802.11b/g selectable via software
Radio Specs - 802.11n
Frequency band
a. 2.4 ~ 2.5 Ghz
b. 5.15 ~ 5.85 Ghz
Available channels: WLAN switch-managed, dependent upon configured
regulatory domain
Modulation: 802.11n draft 2.0
Transmit power: Configurable in increments of 0.5 dBm
Association rates (Mbps): MSC0 - MSC15 (6.5Mbps - 300Mbps)
Radio: 3x3 multiple-in, multiple-out (MIMO)
High-throughput (HT) support: HT 20/40
Packet aggregation: A-MPDU, A-MSDU
Manageability
Management of all 802.11 parameter
Network-wide AP management via:
a. CLI
b. WEB GUI
c. SNMP
Access point profiles Management by:
a. Geographical location
b. BSSID
c. Radio type
d. Encryption support (AP and Switch)
e. 64-bit / 128-bit WEP, TKIP, AES
Interfaces (Electrical)
Minimum 2 x 10/100 Base-TX auto-sensing Ethernet RJ-45 Interface

Kangra at Tanda
Page 51 of 219

Auto-sensing MDI/MDX
Serial and power over Ethernet - 48V DC / 200mA power over Ethernet (802.3af
compliant)
Power Requirements
48V DC / 200mA Power Over Ethernet (802.3af compliant)
External AC power or PoE
Standards
Ethernet IEEE 802.3 / IEEE 802.3u
Power Over Ethernet IEEE 802.3af
Wireless IEEE 802.11a/b/g
Safety
CSA/NTRL (CSA 22.2 No. 950 & UL 1950)
EN60950 (TV/GS), IEC60950 (CB)
3. Outdoor Access Points (802.11a/b/g/n)
The Access Points should be connected to the network infrastructure and work
with a Wireless LAN switch which will be located in the network core.
APs should have the option to connect the WLAN switch over an IPSec
connection to support remote APs, especially when APs are placed behind
NATing device.
Capable of communication with centralized controller over Layer 2 VLAN or
Layer 3 routed network
Capable to tunnel Wireless traffic from subscriber to the Controller in a
dedicated layer 2 VLAN ID Capable of Service VLAN
NEMA 4X-modified enclosure.
Available transmit power should be up to 20 dBm
Integral Antennae
Integral, diversity supporting dual, tri-band omni-directional high gain antennas
with 180 degree movement.
Integral antenna gains (minimum)
a. 2.4-2.5 Ghz / 4.4 dBi
b. 5.150-5.350 Ghz / 6 dBi
c. 5.6 Ghz / 5 dBi
Radio Specs - 802.11a
Frequency band
a. 5.150 ~ 5.250 Ghz (lower band)
b. 5.250 ~ 5.350 Ghz (middle band)
c. 5.725 ~ 5.825 Ghz (higher band)
Modulation type: BPSK / QPSK / 16-QAM / 64-QAM
Transmit power: configurable by system administrator / professional installer
Radio Specs - 802.11b
Frequency band
a. 2.4 ~ 2.483Ghz (US, Canada & ETSI)
b. 2.4 ~ 2.497Ghz (Japan)
Radio technology: Direct Sequence Spread Spectrum (DSSS)
Modulation type: CCK / BPSK / QPSK
Data Rates: 1, 2, 5.5, 11 Mbps per channel
Radio Specs - 802.11g
50

Kangra at Tanda
Page 52 of 219

Frequency band
a. 2.412 ~ 2.462Ghz (US, Canada)
b. 2.412 ~ 2.472Ghz (ETSI)
c. 2.412 ~ 2.484Ghz (Japan)
Modulation type: CCK / BPSK / QPSK / 16-QAM / 64-QAM
Multi-mode radio band 802.11a or 802.11b/g selectable via software
Radio Specs - 802.11n
Frequency band
a. 2.4 ~ 2.5 Ghz
b. 5.15 ~ 5.85 Ghz
Available channels: WLAN switch-managed, dependent upon configured
regulatory domain
Modulation: 802.11n draft 2.0
Transmit power: Configurable in increments of 0.5 dBm
Association rates (Mbps): MSC0 - MSC15 (6.5Mbps - 300Mbps)
Radio: 3x3 multiple-in, multiple-out (MIMO)
High-throughput (HT) support: HT 20/40
Packet aggregation: A-MPDU, A-MSDU
Manageability
Management of all 802.11 parameter
Network-wide AP management via:
a. CLI
b. WEB GUI
c. SNMP
Access point profiles Management by:
a. Geographical location
b. BSSID
c. Radio type
d. Encryption support (AP and Switch)
e. 64-bit / 128-bit WEP, TKIP, AES
Interfaces (Electrical)
Minimum 2 x 10/100 Base-TX auto-sensing Ethernet RJ-45 Interface
Auto-sensing MDI/MDX
Serial and power over Ethernet - 48V DC / 200mA power over Ethernet (802.3af
compliant)
Power Requirements
48V DC / 200mA Power Over Ethernet (802.3af compliant)
External AC power or PoE
Standards
Ethernet IEEE 802.3 / IEEE 802.3u
Power Over Ethernet IEEE 802.3af
Wireless IEEE 802.11a/b/g
Safety
CSA/NTRL (CSA 22.2 No. 950 & UL 1950)
EN60950 (TV/GS), IEC60950 (CB)
4. Power Injectors 50
5. Administration
Web Based Configuration, Role Based Admin, Multiple Administrators & User
01

Kangra at Tanda
Page 53 of 219

Levels, Upgrade via Web UI
System Management
Web UI, CLI (Serial, SSH, Telnet) SNMP (V1, V2, V3) Network Maps,
Configuration, Alerts, Notifications, Reporting, and Management Console
Comprehensive Security
Multiple Zone Security, Access Scheduling, DOS Attack Prevention, External
Authentication( RADIUS, LDAP, Windows Domain Controller & Active Directory
Integration), Intra VAP & Inter VAP Isolation, Gateway Anti-Spam, Anti-Virus,
Anti Spyware, Inspection Firewall, Content & Application Filtering, External
ELDAP, Intrusion Prevention System, Blocking Malware-Phishing-Pharming URL
Reporting
Intrusion Reporting, Policy Violation Reporting, Web Category Reporting (User &
Content), Key Words Reporting, Data Transfer Reporting, Virus Reporting
Bandwidth Management
Auto RF Channels Administration , Bandwidth Optimization, Auto RF Power
Adjustment, Time Restriction, Multi WAN Bandwidth Reporting, Load Balancing
Enterprise Management
Data Collection, User Management, Event Management, Multiple Link
Managements, On Appliance Reporting, Email Notification, Log Management,
Access Time Managements, Data Quota Management, Alert & Failover
Management
Firewall
DoS attack prevention
Walled Garden
Basic Firewall
Bandwidth and QoS Management
Subscriber based Bandwidth restriction
Bandwidth quota allocation based on individual and shared basis
Committed (CIR) and Burstable (CBR) bandwidth allocation
Time and date based Variable bandwidth allocation
Authentication , Authorization & Accounting (AAA)
Authentication based on user name and password
MAC address and IP address-based authentication
Accounting based on hours, days and usages-basis
Leased line and dedicated subscriber support through transparent
authentication through MAC address
Built-in Radius server
Subscriber redirection on login
Supports PPPOE, RADIUS, SOAP protocol based authentication
Web based authentication redirection for unauthenticated users
5.7 SECURITY APPLIANCES
5.7.1 SCOPE OF WORK
a. Supply: Supply of the UTMs including peripherals, completely described in the BID, and their
installation, maintenance at on-site/off-site locations provided by the Institute.
b. Installation:
i. Mounting the UTMs on the racks provided by the Institute.
ii. Configuration and Setup of the UTMs according to the requirements of the Institute.
iii. Configuring all the software associated with the UTMs.
iv. User training to the IT staff of the Institute.

Kangra at Tanda
Page 54 of 219

c. Uptime: The Bidder will ensure an uptime of 99% for the UTMs deployed by them.
e. AMC: The technical maintenance of the UTMs will be the responsibility of the Bidder. The
warranty only.
Needed
1. Internet UTM
General Specifications
Should be an appliance based UTM with built in OS
Should have 10 Gbps throughput and IPSec VPN performance should be 2 Gbps
Vendor must have ICSA and EAL certification if not the exact platform
Should support more than 6 million Concurrent sessions
Should have 190,000 new sessions per second
Should have minimum of 8 10 / 100 / 1000 interfaces with 2 10-gig interfaces for
future use
Antivirus Throughput for the UTM should be 2 Gbps along with IPS throughput of
minimum 5 Gbps (IPS throughput shouldnt be of default value)
Operational Modes
The UTM should support Layer 2 (Transparent) mode and Layer 3 mode
Firewall
Should support DoS and DDoS protection on any/all interfaces
Should provide TCP reassembly for fragmented packet protection
Should be able to support more than 1024 VLAN's
Should support integration with any third party security solution.
Should support Application Gateways for SIP and H.323
Should support integrated Bandwidth management and traffic shaping per
session
VPN
Should support up to 2,000 Concurrent VPN tunnels and SSL VPN should be
provided (separate appliance can be given) with license for 1000 Users
Should support DES, 3DES and AES encryption
Should support MD-5 and SHA-1 authentication
Should support client based IPSec VPN Tunnels
High Availability
Should support Active/Standby High Availability
Should support Stateful Failover of Firewall and VPN Sessions
Should support authentication for HA members
Should support encryption of HA traffic
UTM Features
Solution should provide license for Category Based web-filtering, IPS,
Antivirus,Anti-malware, Anti-bot , DLP and Application Control
IPS should support various technologies like Protocol detection, Signature based
etc.
Category based web-filtering should have support 60+ category and should be
applicable to IP addresses or User based
UTM should support ISP failover and Load-balancing.
ISP load-balancing must have Policy-based routing, weighted Round-robin,
Threshold load balancing and Source-IP based load-balancing ( if UTM doesnt
support all this methods than additional ISP Load balancer should be provided)
02

Kangra at Tanda
Page 55 of 219

Antivirus should be able to detect viruses in Zip files and should able to do
scanning over SSL encrypted sessions as well
User Authentication
3rd Party user authentication RADIUS, RSA SecurID, TACAS+,AD directory and
LDAP
Logging
Should support Syslog server logging
Should have support for SNMP V1, V2c and V3
Administration
Should support multilevel administration privilege
Should support Software upgrades using TFTP or USB
2. Intranet UTM
General Specifications
Should be an appliance based UTM with built in OS
Should have 40 Gbps throughput and IPSec VPN performance should be 2 Gbps
Vendor must have ICSA and EAL certification if not the exact platform
Should support more than 10 million Concurrent sessions
Should support more than 200,000 new sessions/second
Should have minimum of 8 10 / 100 / 1000 interfaces with 8 10-gig interfaces for
future use
Antivirus Throughput for the UTM should be 2 Gbps along with IPS throughput of
minimum 8 Gbps (IPS throughput shouldnt be of default value)
Operational Modes
The UTM should support Layer 2 (Transparent) mode and Layer 3 mode
Firewall
Should support DoS and DDoS protection on any/all interfaces
Should provide TCP reassembly for fragmented packet protection
Should be able to support more than 1024 VLAN's
Should support integration with any third party security solution.
Should support Application Gateways for SIP and H.323
Should support integrated Bandwidth management and traffic shaping per
session
VPN
Should support up to 2,000 Concurrent VPN tunnels and SSL VPN should be
provided (separate appliance can be given) with license for 1000 Users
Should support DES, 3DES and AES encryption
Should support MD-5 and SHA-1 authentication
Should support client based IPSec VPN Tunnels
High Availability
Should support Active/Standby High Availability
Should support Stateful Failover of Firewall and VPN Sessions
Should support authentication for HA members
Should support encryption of HA traffic
UTM Features
Solution should provide license for Category Based web-filtering, IPS,
Antivirus,Anti-malware, Anti-bot , DLP and Application Control
IPS should support various technologies like Protocol detection, Signature based
etc.
Category based web-filtering should have support 60+ category and should be
applicable to IP addresses or User based
UTM should support ISP failover and Load-balancing.
ISP load-balancing must have Policy-based routing, weighted Round-robin,
Threshold load balancing and Source-IP based load-balancing ( if UTM doesnt
02

Kangra at Tanda
Page 56 of 219

support all this methods than additional ISP Load balancer should be provided)
Antivirus should be able to detect viruses in Zip files and should able to do
scanning over SSL encrypted sessions as well
User Authentication
3rd Party user authentication RADIUS, RSA SecurID, TACAS+,AD directory and
LDAP
Logging
Should support Syslog server logging
Should have support for SNMP V1, V2c and V3
Administration
Should support multilevel administration privilege
Should support Software upgrades using TFTP or USB
5.8 LOAD BALANCER
5.8.1 SCOPE OF WORK
a. Supply: Supply of the Load Balancer including peripherals, completely described in the BID, and
their installation, maintenance at on-site/off-site locations provided by the Institute.
b. Installation:
i. Mounting the Load Balancers on the racks provided by the Institute.
ii. Configuration and Setup of the Load Balancers according to the requirements of the
Institute.
iii. Configuring all the software associated with the Load Balancers.
c. Uptime: The Bidder will ensure an uptime of 99% for the Load Balancers deployed by them.
e. AMC: The technical maintenance of the Load Balancer will be the responsibility of the Bidder.
The charges for such AMC shall be borne by the Institute after the expiry of one year standard
warranty only.
Needed
1. DMZ Load Balancer (Layer4-7 Switch) with following configuration
Architecture
Should be appliance based solution with purpose built hardware for high
performance to support multiple load balancing function with ipv6 network.
The appliance should have 5 Gbps of system throughput and scalable to 10 Gbps
on same appliance.
The appliance should have minimum 4 triple speed gigabit 10/100/1000 copper
ports and support for 10G interface for future requirements on same appliance.
Should provide 3M concurrent connections and scalable to 4M on same
appliance.
Appliance should provide full ipv6 support and OEM should be IPv6 gold-
certified. OEM should be listed vendor for ipv6 phase-2 certification to support
all the ipv6 function from day one.
Load balancing Features
02

Kangra at Tanda
Page 57 of 219

Able to load balance ANY IP based application.
Able to support application based monitoring, such as HTTP/HTTPS, FTP
(passive/active), POP3, IMAP, DNS, SMTP, telnet, RADIUS, LDAP, RTSP, RDP
Able to support both TCP and stateless UDP (User Datagram Protocol)
applications.
Shall be able to support the following load balancing algorithms that can be
simple to set up and configure:
round robin,
weighted round robin,
least connection,
Persistent IP, Hash IP,
Hash Cookie, consistent hash IP,
shortest response,
proximity, snmp,
SIP session ID,
Hash header etc.
Shall be able to support sticky connections to servers based on the
following switching mechanisms:
URL/content switching policies
URL hashing
Cookie-based
SSL ID based
Extensible policies (ePolicy)/ TCL scripts to implement business logic on network
without any changes in application code to support complex application load
balancing.
Able to support single arm, reverse and transparent proxy mode deployment
scenarios and should support nested layer7 and l4 policies.
Able to support a mixed combination of IPv6 and IPv4 virtual addresses and
nodes.
Optimization
Able to provide integrated SSL termination / acceleration, and SSL re-encryption
to the servers.
SSL throughput 2Gbps and scalable to 3Gbps with 25,000 SSL transactions per
second.
Able to aggregate multiple connections to a single server side connection
connection multiplexing.
Able to provide real time Dynamic Web Content Compression to reduce server
load and selective compression for Text, HTML, XML, DOC, Java Scripts, CSS, PDF,
PPT, and XLS Mime types..
Able to provide support for customized cache rules including max object size, TTL
objects, refresh time interval etc.
High Availability
Able to be deployed in both Active-Standby and Active-Active setups.
Able to synchronize configurations at boot time and run time, connection-states
to provide stateful-failover of applications.
Able to detect system failure, SSL card failure, process health check, CPU
overheated or shutdown/reboot, and perform failover to ensure high
availability, by using either network or serial-connection based heartbeat.
Security & management

Kangra at Tanda
Page 58 of 219

Able to support Dos/DoS mitigation through connection reverse proxy to secure
internet facing applications.
Able to support Rate shaping & QoS Support so that all applications work
optimally without impacting user experience
Role based access control for granular authentication and authorization.
Administrator should able to define multiple roles namely Admin, Security-
admin, Network-Engineer, Network Monitor, Network Manager on the appliance
The appliance should have SSH CLI, Direct Console, SNMP, and Single Console
per Cluster with inbuilt reporting.
2. Server Farm Load Balancer (Layer4-7 Switch) with following configuration
Architecture
Should be appliance based solution with purpose built hardware for high
performance to support multiple load balancing function with ipv6 network.
The appliance should have 10 Gbps of system throughput from day one
The appliance should have minimum 4 triple speed gigabit 10/100/1000 copper
ports and 2*10G SFP+ interfaces from day one.
Should provide 4M concurrent connections and 100K L4 connection per seconds.
Appliance should provide full ipv6 support and OEM should be IPv6 gold-
certified. OEM should be listed vendor for ipv6 phase-2 certification to support
all the ipv6 function from day one.
Load balancing Features
Able to load balance ANY IP based application.
Able to support application based monitoring, such as HTTP/HTTPS, FTP
(passive/active), POP3, IMAP, DNS, SMTP, telnet, RADIUS, LDAP, RTSP, RDP
Able to support both TCP and stateless UDP (User Datagram Protocol)
applications.
Shall be able to support the following load balancing algorithms that can be
simple to set up and configure:
round robin,
weighted round robin,
least connection,
Persistent IP, Hash IP,
Hash Cookie, consistent hash IP,
shortest response,
proximity, snmp,
SIP session ID,
Hash header etc.
Shall be able to support sticky connections to servers based on the
following switching mechanisms:
URL/content switching policies
URL hashing
Cookie-based
SSL ID based
Extensible policies (ePolicy)/ TCL scripts to implement business logic on network
without any changes in application code to support complex application load
balancing
Able to support single arm, reverse and transparent proxy mode deployment
scenarios and should support nested layer7 and l4 policies.
Able to support a mixed combination of IPv6 and IPv4 virtual addresses and
02

Kangra at Tanda
Page 59 of 219

nodes.
High Availability
Able to be deployed in both Active-Standby and Active-Active setups.
Able to synchronize configurations at boot time and run time, connection-states
to provide stateful-failover of applications.
Able to detect system failure, SSL card failure, process health check, CPU
overheated or shutdown/reboot, and perform failover to ensure high
availability, by using either network and serial-connection based heartbeat.
Security & management
Able to support Dos/DoS mitigation through connection reverse proxy to secure
internet facing applications.
Able to support Rate shaping & QoS Support so that all applications work
optimally without impacting user experience
Role based access control for granular authentication and authorization.
Administrator should able to define multiple roles namely Admin, Security-
admin, Network-Engineer, Network Monitor, Network Manager on the appliance
The appliance should have SSH CLI, Direct Console, SNMP, and Single Console
per Cluster with inbuilt reporting.
5.9 NETWORK MANAGEMENT SYSTEM
5.9.1 SCOPE OF WORK
a. Supply: Supply of the NMS Licence including peripherals, completely described in the BID, and
their installation, maintenance at on-site/off-site locations provided by the Institute.
b. Installation:
i. Configuration and Setup of the NMS according to the requirements of the Institute.
ii. User training to the IT staff of the Institute.
c. Uptime: The Bidder will ensure an uptime of 99% for the NMS deployed by them.
d. AMC and Upgrades: The technical maintenance of the NMS will be the responsibility of the
Bidder. The charges for such AMC and Upgrades shall be borne by the Institute after the expiry
of one year standard warranty only.
Needed
1. Network Management Software having following specifications
Fault Management
NMS should provide secured web-based consoles to monitor 500 nodes and
should run on any flavor of Unix / Linux OS.
The solution should provide for future scalability of the whole system without
major architectural changes. Therefore the system should support distributed
hierarchical architecture.
NMS should process all fault and event related information in memory and in
real time. It should be capable of processing in excess of 500 events per second,
allowing visibility of all alarms. It should also support an interface to an external
database for archiving and reporting.
NMS module should capture all the events that are generated across the multi-
vendor network infrastructure, correlate them and automate suitable actions as
defined.
01

Kangra at Tanda
Page 60 of 219

NMS should consolidate and de-duplicate repeated alarms collected from
throughout the network and provide a clear, coherent and noise-free list of fault
messages.
NMS should be able to filter off repeated alarms of the same device. The start-
time, end-time, and number of repetition of the alarm should be indicated.
The Fault management module must support auto-forwarding and manual
forwarding of alerts to service desk.
NMS should have out-of-box capability to perform predictive analysis and
generate events that represent predictions for systems that are in danger of an
impending threshold violation, and which require attention.
Polling intervals should be configurable on a need basis through a UI tool, to
ensure that key systems are monitored as frequently as necessary. Where there
are severe bandwidth problems, it should be possible for poll intervals to be
changed to reduce network traffic.
The system should support discriminated polling, whereby certain critical
interface of routers or switches may be polled more frequently than others.
NMS should have the ability to correlate events across the entire spectrum of
infrastructure components that support our critical applicationsrouters,
switches provided by heterogeneous vendors.
NMS architecture should be object-oriented, open, distributed, scalable, and
multi-platform and open to third party integration.
The framework should be sensitive and be aware of the impact of management
traffic on the network and provide mechanisms to limited use of network
resources.
NMS should provide fault and performance management for multi-vendor
TCP/IP networks.
NMS should support dynamic object collections and auto discovery. The
topology of the entire Network should be available in a single map.
Product should be able to update router configuration changes like re-indexing
of ports, addition / deletion of ports on Network Map with each polling cycle
without rediscovery of complete network / individual device.
The NMS should trigger automated actions based on incoming events / traps.
The NMS should be capable of login authentication to restrict / enable access to
the manager.
NMSs event correlation should be built-in, tightly coupled with NMSs event
sub-system and should be able to suppress events for key systems / devices that
are down for routine maintenance.
NMS should have out of the box tools for building MIB Application used for
testing devices on multiple MIB parameters. Data Collection should be possible
on MIB Expressions using specific formulas like Utilization of Links in Kilo Bits per
Second, Mega Bits Per Second.
NMS should provide custom visual mapping of layer 2 and 3 devices, connectivity
and relationships.
NMS should provide inbuilt Correlation Composer Graphical User Interface (GUI),
which enables users to tailor the event correlation behavior of the correlators
that are shipped with product. No need of any special programming knowledge
should be required.
The NMS should provide information regarding capacity utilization and error
statistics for WAN links.
Performance Management
Performance Manager should be able to produce reports for 500 nodes.
Should provide the comprehensive insight into how network devices, LAN and
WAN interfaces, network segments, and VLANs are performing providing the
total view of how well the most critical components of the network fabric are
functioning.
Should monitor threshold variables and send alerts and SNMP traps when

Kangra at Tanda
Page 61 of 219

thresholds are exceeded. Alerts can be forwarded to Network Fault
Management software, combining availability and performance characteristics
for a more complete picture.
Should make use of default thresholds that can be configured per interface.
Should support industry-leading, multi-slot network devices, including those
from Cisco, Alcatel-Lucent, Brocade and Juniper.
Should be scalable to monitor performance for elements include the following,
frame relay, LAN / WAN management information base II (MIB-II) interfaces
asynchronous transfer mode (ATM), QOS, MPLS routers device resourcesCPU,
memory, and buffers on devices.
Should help diagnose performance problems using recent and historical data.
Should report on metrics from performance agents or data collected into the
Host Resources MIB (RFC 1514) to monitor system performance.
Should provide reports on generic system performance metrics and metrics
specific to performance agents.
Should provide near real-time, hourly, daily and monthly reports provide insight
from whats happening now to a long term planning perspective.
Should enable advanced report to report navigation for faster troubleshooting
and easy location of the information you need.
Should generate traps based on service level thresholds.
Should have customer orientation, meaning that customers are able to log in
and see only their information displayed.
Reports
Executive Summary reports:
Should provide a series of reports designed to summarize utilization of and
traffic patterns on network interfaces.
Should display statistics for CPU, memory, buffer and interface traffic
metrics.
Summary reports :
Summarize performance by customer, site or region with drill-down
graphs (sorted by exception count, highest to lowest) that show more
detailed CPU, buffer, memory utilization and QoS information over the
previous 24 hours, previous 90 days and previous 12 months.
Forecast reports:
Highlight possible hot spots and rank items by number of exceptions
forecasted to occur within the next 90 days with drill-down charts that
show utilization 30, 60 and 90 days out with comparisons to actual
performance over the baseline period, day-of-week forecasting and
historical values.
Forecast CPU, buffer and memory utilization based on all devices in a
customers network.
Exceptions reports:
Should list elements that have exceeded a performance threshold during
the previous day.
Should list interfaces with highest number of discard, error and utilization
errors and should show exception counts, maximum utilization and
average utilization.
Hot Spots reports:
Identify the devices, trunks, interfaces and VLAN interfaces with the
highest number of exceptions.
Top Ten reports:
Should identify devices, trunks, interfaces and VLAN interfaces with the
highest and lowest utilization rates.
Should list top 10 customers based on CPU, memory and buffer utilization.
Should list locations with the highest and lowest volumes.

Kangra at Tanda
Page 62 of 219

Should identify protocols with the highest and lowest volumes.
Near Real Time (NRT) reports:
Should show utilization, error and discard data for active interfaces and
trunks, based on the most recent six hours of data.
Should show current trouble spots, such as elements that are experiencing
high CPU or buffer utilization.
Should show peak utilization for active interfaces and trunks in context of
a customer, the customers location and the corresponding device.
Should show packets and percentage of errors per interface from the most
recent poll cycle and the past 12 hours.
Should show interface data with percentage of broadcast and multicast
packets from the previous day; can be used to track broadcast storms.
Should provide drill-down graphs that trace increases and decreases in
utilization over the last 24 hours or for the previous month.
Quick-View / Snapshot reports:
Show the devices with the highest daily utilizations with drill-down graphs
that provide utilization and frequency distributions.
Backplane reports:
Show backplane utilization for both single and multiple backplane
switches.
Consist of Switch Historical Summary, Snapshot, Quick-View, NRT
Snapshot and NRT Quick-View reports.
Service Level Management reports:
Should identify devices, locations and protocols with the lowest
availability and highest response times.
Traffic Utilization reports:
Should capture comprehensive traffic data across VLAN interfaces for
utilization.
Interface reports:
Capacity Planning: Forecasts busy-hour utilization and sorts interfaces or
protocols by rate of growth.
Unreachable: Lists interfaces for which no data has been received for 35
minutes; excludes interfaces for which no data has been received in the
previous six hours.
Availability Detail: Shows the availability of interfaces for the previous day
in terms of percentage of availability and what that means in actual
seconds; includes graphical summaries for the past hour, day and month.
Administration reports:
Inventory: Shows which devices and their interfaces have been
provisioned by a customer and the property data associated with them.
Mapping Log: Shows log entries for diagnosing reporting system failures
and for displaying the configuration of property import options.
RMON Ethernet Statistics reports:
Inventory: Lists all interfaces supporting RMON Ethernet Statistics.
Drop Events: Shows the total number of events in which packets was
dropped by a probe due to a lack of resources and displays devices polled
the previous day.
Historical Packet Size Distribution: Shows packets and percentage of errors
per interface from the previous day.
Historical Broadcast + Multicast Packet Analysis: Shows interface data with
the percentage of broadcast and multicast packets from the most recent
poll cycle and the past 12 hours; identifies excessive (>10%) multicasts and
broadcasts.
Error reports:
Identify error packets for the most recent poll cycle and the past 12 hours

Kangra at Tanda
Page 63 of 219

(real time) and for previous hours and days (historical), including
Fragments, CRC Align Errors, Underutilized, Over-utilized, Jabbers and
Drop Events.
5.10 UNIFIED COMMUNICATIONS
5.10.1 SCOPE OF WORK
a. Supply: Supply of the IP-PABX and IP Phones including peripherals, completely described in the
BID, and their installation, maintenance at on-site/off-site locations provided by the Institute.
b. Installation:
i. Mounting the IP-PABX on the racks provided by the Institute.
ii. Configuration and Setup of the IP-PABX according to the requirements of the Institute.
iii. Configuring all the IP Phones.
c. Uptime: The Bidder will ensure an uptime of 99% for the IP Telephony deployed by them.
e. AMC: The technical maintenance of the IP Telephony will be the responsibility of the Bidder. The
warranty only.
Needed
1. IP-PABX
System Architecture
The Switch should be designed with IP at the core, allowing fully distributed IP
solutions across data networks. It should support following traditional TDM or
mixed IP-TDM or full 100% IP configurations.
IP Communication Devices e.g. IP Phones, Mobile IP Phones, multimedia PCs, SIP
phones, or H.323 terminal devices etc.
Legacy TDM communication devices (Digital and analog 2 Wire telephone
instruments with or without caller-id (Both FSK and DTMF), Fax, modems etc.)
The system should be server based kept outside the cabinet, scalable,
distributable and modular and the operating system shall be LINUX based.
The system should manage CAC (Call Admission Control) mechanisms to optimize
the usage of the bandwidth in the WAN for multi-site configurations.
The Call Server should be able to handle minimum traffic 300K BHCA, 300K BHCC
& support up to 15000 users. it shall be scalable to 100000 users in a virtual and
multi-servers network group.
The voice and signalling frames should be marked [tagged] in order to be
recognized. The standards of marking supported will be: Level 2: IEEE 802.1p/Q
and Level 3: TOS / DiffServ
The system should support for voice encoding the following standards:
(i) G.711
(ii) G.723.1
(iii) G.729A
(iv) G.722
Call Switching Typically, internal calls (i.e., limited to a single location) should be
01

Kangra at Tanda
Page 64 of 219

based on the G.711 uncompressed PCM standard and G.722 (wide band band),
but WAN calls outside the location should use the G.723.1 or G.729/A
compression algorithm.
The System must support Network Time Protocol V4.1.2 (RFC 1305) to
synchronize the system data/time of network devices.
The system should be suitable to accommodate both Decadic Pulse (DP) and
DTMF telephones. The system should support outgoing DTMF transmission even
from Digital phones.
The system should have non-blocking architecture at all levels like System
processing, Switching fabric, power supplies, other resources like DTMF
receivers, R2 Receivers, Unlimited 3 party conference circuits.
VoIP Support System should support VOIP solutions as an integral part of the
system. The VOIP should be implemented through plug in interface boards in any
slot of the system. It should not involve any external gateways, routers etc.
The system should be fully compliant to VOIP standards like H.323 and SIP
(Session Initiation Protocol). Vendor to give clear compliance for the requested
standards.
The system should be able to operate with any H323 compliant device and it
should be able to support internal gatekeeper for the same. If required it should
be able to inter operate with H323 standard based external gatekeepers.
The SIP proxy, SIP registrar should be inbuilt in the system and should support
any SIP compliant hard phones or soft phones. Standard messaging software like
XP Win messenger should be supported as the voice client by the system without
the need of any hard phone.
System should support the QOS features for the VOIP implementation. It should
be compliant with both QOS standards (Layer 2 802.1 p/q) and Layer 3- Diffserv
/ TOS).
System reliability
Proposed IP PBX architecture shall have 99.999% availability. to ensure such High
availability of the telephony network in the campus the architecture shall have
Hot standby Redundancy for the IPPBX servers by employing identical servers
deployed as Active and Standby servers. Each server should be capable of
handling the entire load without any performance degrades. The proposed
solution should have the following capabilities:
Redundancy should be ensured for all critical elements like call server, sip
server, gate keepers, configuration Databases, TFTP servers, DHCP servers,
The system should offer maximum availability, with the switchover of call
control processing functions to the hot standby redundant server in the event
of a failure in the Active server. The redundancy scheme should conform to
the model used in most computer systems: the complete "mirroring" of the
information (both static and dynamic data.) The switch over between 2
redundant call control processors should not interrupt existing and
established communications. The complete set of programs and software
modules must be running in real time. In case of failure of the main Server
(hardware or software), the standby Server (emergency mirror) must take
over the control of communications instantaneously.
Also system should have 3rd call server over and above main and standby call
server for any disaster recovery.
In addition to the server redundancy, solution should support adequate
Redundant features for server Ethernet, Media gateway Redundancy
including Power supplies & ring generator redundancy (even better if the
power supplies distributed at the board level), media gateway control
redundancy, DSP resources, DTMF receivers, Tone detectors etc.

Kangra at Tanda
Page 65 of 219

The management Platform must provide a backup mechanism for all critical
system information in both a manual and an automatic/scheduled archival
and a Disaster Recovery mechanism.
The system must support Remote Location Units on IP.
Replacement of cards without powering down the Media gateways (Hot
swappable) including the control cards and peripheral/interface cards.
All the conferencing, tone generation and tone detection should be local to
the gateway.
The system should be able to restart automatically without human
intervention when the external ac power supply is resumed after complete
power failure i.e. Even after the batteries are discharged
The call server should support two or more different geographical locations
more than 10 km in the network.
Remote Unit
Survival Media Gateways should be supported for extending IP Telephony to the
remote locations. The Media Gateway should have the intelligence to survive
through a survivable server, in case of the connectivity with main system fails.
In such a situation, the remote unit shall work independently and if the
connectivity is restored back it shall automatically re-establish its connection
with the main Servers.
The hardware and software of the survivability server installed at the remote
location should be exact replica of the main server to ensure transparent
telephony environment to the users during survivable mode.
The survivable server should be able to survive all the H323 and SIP IP end points,
trunks SIP, H323, PRA.
Media Gateways should support survival mechanisms that allow them to
maintain 100% of the telephony services for their users, in case of failure in the
WAN links where the signalling with the call server drops.
It should have voice guidance facility.
It should have capability to provide operator console connectivity.
It should have redundant IP connectivity card with main system.
System Security
The proposed system and its components must be certified by a well-known
quality agency as per Common Criteria international standard (ISO/IEC 15408) for
computer security Certification, the minimum Evaluation Assurance Level must
be equal to 2+ (ie EAL2+ ). Documentary evidence must be submitted along with
the compliance.
The System must support Syslog services for both internal and external
command and configuration control accounting with a minimum of 5 day history.
The Operating System used by the call server must not use or natively support
network resource sharing services such as NFS, samba, LPR etc.
The call Server must be provided adequate protection from possible virus, worm
and trojan infestation points such as internal e-mail servers.
The password and access control must include at least:
(i) Shadow Passwords to prevent the possibility of an aggressor to easily read or
deduce system or account access passwords.
(ii) Password Aging with configurable time periods.
(iii) Usage of MD5 algorithm (or stronger) for password encryption
(iv) Internal OS controls for remote point of access restriction and service
availability. (i.e. TCP Wrappers & Trusted Hosts)
(v) Account access authentication/restriction using external RADIUS resources.
Media Gateways should not host services such as proxy, FTP, Telnet or local

Kangra at Tanda
Page 66 of 219

dynamic routing to prevent exploitation in Distributed Denial of Service attacks.
IP Phones should not support direct, external initiated, connections via HTTP,
telnet, FTP, TFTP or any other protocol as means to prevent distributed Denial of
Service attack exploitation.
IP Phones must support 802.1x (EAP-MD5 or better) for authentication and
access control to the network, this mechanism must allow the user to be
connected to the call server once he has passed the authentication process; not
before.
The system should have the capability to, based on standard mechanisms (such
as 802.1Q and DHCP), assign automatically the corresponding voice VLAN
number to the IP station clients during IP station initialization, allowing for the
separation of voice and data traffic at IP station.
System Management
The system must include a dedicated management server/platform that will be
based on the latest technologies, such as JAVA/JEE. This server should support a
minimum of five or more clients having different access rights to the
applications.
The management platform must provide a single graphical client (Graphical User
Interface GUI) as well as a web based interface.
The Management platform must provide web access allowing the administrator
to manage the system to use any PC with an internet browser
The management platform should support the following tasks:
(i) Configuration and programming of services, users, categories and all
system parameters and features. This module must provide centralized
management in local or remote environments of a single system or a
network. The network manager will be able to quickly and easily edit,
create or delete any network object by the use of import/export functions
and multiple operations.
(ii) Faults and Alarms management of all the incidents and fail reports
generated by the system itself informing date, hour, severity level and
action recommended to take. This module must be able to centralize the
alarms and events of the system, and Give colors according the severity
level of the alarm, Notify an alarm depending to the severity level sending
an e-mail or activating an script performing an specific action, Register and
generate statistics for the alarms and events in the network in a daily
scheme etc.
(iii) Fault diagnosis Generate reports and graphics about the statistics of the
alarms and its correspondent resolution time.
(iv) Accounting of all calls generated by the users including cost, date, hour.
Must provide different options to group the monitoring of the calls (cost
centre, extension number, trunk, user, city/area associated to dialled
numbers).
Network Topology
The management server should provide an application that offers a topological
view of the telecommunications system in graphical form such as main, remote
unit and connectivity.
Security
(i) Administration users connecting directly to the Call Server (console) must
be authenticated via a RADIUS server before gaining access to the call
server.
(ii) All management traffic between a remote console/session and the call
server must be encrypted. (SSH for direct command line sessions, HTTPS
(SSL) for web sessions, SFTP for file transfers, etc.)

Kangra at Tanda
Page 67 of 219

(iii) The management platform must provide Role Based Account Management
to define different levels of administrator access depending on specific
function responsibility.
System Features
Numbering scheme:
The EPABX should be suitable for upto 8 digit extension numbering scheme. This
numbering scheme should be flexible. System should also allow mixed
numbering scheme. For the numbering plan may contain digits 0 to 9 and also
allow use of alphabets like abcd and special symbols *,#
The system should provide distinctive ringing for internal calls, junction calls,
auto call back, wake up service and emergency reporting service.
The system should support the attribution of an external number DDI or
individual line or a bundle head to a trunk, a bundle, an attendant, a group of
attendants, a subscriber, a group of subscribers or virtual equipment. The
unanswered DDI communication can overflow, to Attendant or attendant group,
Local subscriber, Network subscriber, Voice mailbox, automated attendant,
abbreviated number, External number.
The proposed system should support automatic route selection (ARS) and least
cost routing (LCR) features to route the calls based on priorities related to user
profile, tariff, and network availability, along the most cost-effective path. This
service will be transparent for users and irrespective of the physical carrier
connection.
Voice guidance for Telephone features to be offered as standard. There shall be
minimum 50 voice prompts stored in the system. The voice prompts shall be
downloadable from the management application. The system should have 48
minutes of memory for Voice prompt download partition into 4 areas to store
multiple language prompts and also 15 minutes of memory where the dynamic
voice prompt recorded at the site through any IP Phone.
DTMF and Busy Tone Resources Minimum - 50 DTMF receivers to be offered.
Busy tone detectors for every circuit to be offered ( if there are 100 trunks - 100
busy tone detectors to be offered).
IP PBX should enable advanced conferencing features:
50 x 3 party adhoc conferencing from any phones
1 x 14 party meet me conferencing from any phone
Basic Telephone Features:
Abbreviated dialling - 25000 abbreviated numbers
Appointment reminder
Automatic call-back on busy trunk/bundle/network link
Automatic DISA, user authentication
Call forwarding unconditional on busy/no reply to extension, hunting group,
Voice mail, operator, paging, etc.
Immediate forwarding
Call pick-up
Call parking
Call tracing
Call waiting indication / voice prompt
Calling line identification restriction for internal calls
Camp on busy telephone/hunting group/voice mail
Controlled private call by Pin code and password
Do not disturb
Dynamic call baring
General night service

Kangra at Tanda
Page 68 of 219

Hunting group (fix head, cyclic, longest idle time, parallel)
Internal/external music on hold
Internal/external inquiry call
Individual hold
Instrument locking to prevent the outgoing
Last internal/external number redial
Personal code modification
Priority call
Priority cut in
Store and redial external number
Transfer in conversation on free/busy telephone
Voice prompts on/off per telephone
Voice message deposit on forwarded telephone
Waiting call and waiting call consultation
Multiple appointment reminders per extensions up to 4 simultaneous per
extension.
Reminder Voice guide should be provided
System Network Support
The system should support international telephone standards such as QSIG (BC
and GF) , DPNSS, DSS1, H.323 and SIP enabling interconnection with other 3rd
party systems.
QSIG-BC-SS
(i) Heterogeneous, open numbering plan
(ii) Calling/Connected Line Identification Presentation and Restriction.
(iii) Calling/Connected Name Identification Presentation and Restriction.
(iv) Call Forwarding Unconditional, Busy, No Reply ,Call Transfer
(v) Call Completion to Busy Subscriber, on No Reply, call Offer.
The system should have options to network over any of ATM, IP, ISDN, Frame
Relay technologies.
The system must support the following external telephony interface signalling:
(i) E1 CCS PRI (VN3-4-6-7 /ETSI) DASS2
(ii) E1 CAS (R2, Q421, MFC Ericsson, Q23, Decadic)
(iii) T1 CCS generic
(iv) T1 CAS
(v) T0 ISDN BRI (VN3-4-6-7 / ETSI)
(vi) E&M
(vii) Analogue Loop Start and Ground Start.
Analogue Subscriber Card
Should support 16 or more ports.
Each port should support CLIP features ( FSK or DTMF).
Loop Resistance >1800 ohms
Trunk Cards
CO Trunks
(i) Should accept/extend CLIP features ( FSK or DTMF)
(ii) Should allow line impedance to be modified to identify the caller and to
detect the metering pulses.
E1 Trunks
(i) Should be able to take on E1-CCS: ISDN, Q-SIG and DPNSS streams.
(ii) Should have dual ports.
Operator Consoles
Operator Console PC based (On IP Only)

Kangra at Tanda
Page 69 of 219

(i) General
Should be based on Windows XP or Windows 7 OS. The PC should not be
dedicated solely to this application and should handle telephone
applications and business software simultaneously. It should support online
Directory , BLF (Busy Lamp Field) indications etc
(ii) Survivability
Operator application must be associated with an IP Phone, which should provide
the voice capabilities to the operator console.
Even if there is a PC failure, the Phone should be available for the operator to
handle calls with basic telephony features to ensure business continuity, until the
PC application is restored.
(iii) Telephone application keys
Audio keys and speaker allow activation/deactivation of the speaker or
the hands free mode, as well as volume control.
Switchover key allows the attendant to shift quickly from a business
application to an MAC call application, and vice versa.
Call handling keys dedicated to managing call flow and provide the
following functions (one key, one function) :-
Store and redial, Redial, Cancel consultation (inquiry), Release call,
Broker call, Call selected party, Answer internal call, Transfer/hold call,
End of dialling, Next call
Programmable keys with LEDs keys with LEDs can be assigned the
following functions:
User speed dialling, Privileged call, User supervision, Abbreviated
(speed dialling) number, Telephone function, Individual hold, General
hold, Trunk group supervision, Transfer with/without privilege,
Individual routing, Transfer in private network.
Information LEDs
Night forwarding, Auto-answer, Auto-transfer, Trunk reservation, Mail,
System message
Standard External PC keyboard (105 keys)
(iv) Software application keys
Application should display following information on screen:
Call handling fields, First-party call field, Routed calls field, Calls on hold
field, Waiting queues fields, Context-sensitive soft keys, Station status,
Busy lamp field window, System or user programmable keys window,
Menu bar
Menu bar should display:
Attendant - allows configuration of the operating mode
Application activated
Activate/deactivate the microphone
Activate/deactivate the speaker and switch to hands free
Open a dialog box with the last ten users dialled
Open a dialog box with a list of users
Directory - allows searches in various directories
Directory(s) previously selected in the Option menu
Attendant's personal directory
Enterprise system directory
Extension - allows access to a range of management services
Centralized directory
System management
Customization of the attendant station
Appointment reminder
View - allows screen and environment configuration
Hide or display date and time

Kangra at Tanda
Page 70 of 219

Window customization
Background colour
Switch between busy lamp field and programmable keys
Switch between soft keys and programmable keys
(v) Attendant Services
Chained call: allows a transferred call to return to the attendant at the
end of the conversation. The attendant may also route the same call to
several users in succession.
Charged call: allows a terminated call to return to the attendant with
call accounting information.
Routing in controlled release: allows the attendant to put the call on
hold if internal user is busy.
Attendant forwarding: allows the attendant to forward an
internal/external party to another free attendant.
Q23 DTMF dialling: allows the attendant to use voice frequency dialling
to retransmit a number on the line to a party.
Record: allows each call to be recorded when the attendant console is
not in automatic record mode.
Pulse dialling: allows the attendant to use decimal pulses (rotary
dialling) to retransmit a number on the line to a party.
Flashing pulse: allows the attendant to transmit a flashing pulse on the
line to activate the MF receiver and to indicate to the party that voice
frequency dialling (DTMF) will follow.
Temporary deactivation of automatic transfer
(vi) Busy Lamp Field Application Should have icons for phones, fax, hunt
groups etc. to indicate:
Idle state
Busy (including ringing for multi-line phones)
Busy: in conversation with internal party
Busy: in conversation with external party
Inaccessible (including ringing for single line phone and out of service
state)
Absent (automatic if forwarding to absence text message or manual on
internal attendant entering)
DND (do not disturb)
Unified Communications solution shall be proposed along with IP PBX to enable
RPGMC Kangra to improve user efficiency and better collaboration. Both the
IPPBX and Unified Communication System must be from the same OEM.
The Features delivered by Unified Communications system must be :
Unified Messaging / Voice Mail
Unified Directory Access
Collaboration
Mobility
Unified Messaging / Voice Mail Features
General
Advanced Unified Messaging system which can provide both simple Voicemail
services and unified Messaging services shall be offered from the same OEM as
that of the IPPBX.
Solution should support Voice, Fax and Email messaging access from different
client interfaces like web browser, email client and Phones.
The UM application shall be fully software based using following open standards:

Kangra at Tanda
Page 71 of 219

SIP
VXML
TTS
Https
SMTP/POP3
The voice mail must work as a centralized resource in case remotes are
connected to the main exchange.
It should have tight integration with Microsoft Exchange 2010 and IBM Lotus
Domino Rel 7, 8.0.x, 8.5.x
It shall provide the flexibility to store the voice messages locally or in the email
server.
The voice and fax messages along with Emails shall be accessible from an email
client or from the IP Phone.
UM shall provide advanced features within the email client to access messaging
like playback, call back the sender, forward, click to call etc. it shall work both in
Outlook 2003,2007,2010 and Lotus Notes 7,8.0.x,8.5.x
Voice mail features
Must support Voice messaging features allowing the owner of a mailbox to send
messages to other mailbox users, whether they are part of the same system or
remote users
Should support Automated attendant (automatic switchboard) features allowing
the voice mail system to act like an attendant: answer incoming calls, transfer
them to a requested or predefined number or mailbox, using addressing by name
or by number. A graphical User interface must be available to build the Auto
attendant call flows with drag and drop features.
Must support Voice Recording features allowing the owner of a mailbox to
record the running conversation with others.
Mailboxes and Access Control
Number of Mailboxes for all users
Voice Messaging System
(i) Call answering or call/record answering function with time stamp.
(ii) Customization of an announcement
(iii) Call forwarding to the voice mail
(iv) System should support on line conversation recording
Message notification via message indicator LED and voice prompts.
Unified Directory Access
Web Interface to Directory
The exchange directory should be available on web. The LDAP server and
web server application should be integral to the exchange.
Directory module to manage the telephone directory
This must be LDAP compatible to be synchronized with other directory
applications, must also allow web access and provide information on all
desktops allowing click to call features to the users.
Integrated Directory
It shall be possible to provide display equipped voice terminals with access
to system directory on IP phones. Also System should support internal and
external LDAP directory. Any internal user can use by browsing the URL link
from his laptop/PC to see the directory and dial the required no. by
selecting under LDAP directory.

Kangra at Tanda
Page 72 of 219

Collaboration
The collaboration application must be able to manage the following
collaboration tools for all users:
Audio Conference with Recording Capability (32 port)
Presence and Instant Messaging for All the IP PBX users.
Buddy List with Group
Data Collaboration and Applications Sharing (32 port)
Video Collaboration (16 port).
System connectivity via TDM or SIP to any PBX or PSTN
The collaboration application must be thin client - web based using a
browser, without any other client installed/maintained on the PC
The session must be secured by the use of HTTP over TLS (HTTPS).
The collaboration application must use standard and state of the art
technologies such as HTTP, HTTPS, SIP, XML, and VXML at the core to
manage the IP flows and sessions
The Collaboration application must provide a web browser based
management application that allows:
Configure and maintain the service
Generate reports about calls established by period of time, exportable in
HTML or XML
Generate reports of statistics of usage in HTML or XML
Register the alarms and events
The collaboration application must be able to support SNMP for integration
with other management systems
Users must be able to create their own buddy lists and user groups for all
team collaboration functions.
The collaboration application must provide recording capabilities for both
audio conferences and online presentations. These recordings must be
available for replayed via a simple link to both registered users and external
users.
The collaboration suite must include self-service audio conferencing
capabilities. These capabilities must be accessed by the user through the
web interface including:
Ad-Hoc/On Demand Conferences, allowing the users to start an audio
conference at any time by just aggregating the participants from the buddy
list or by calling them at any telephone number (internal or external)
without access codes.
Reservation-less Conferences (conference rooms), that the user can create
by himself that include a "number to call" and an "access code" that can be
used at any time to establish a conference call. Participants just dial the
number and access code, and the conference is established.
Scheduled Conferences that the user can schedule through the application
user interface. The conference is scheduled for a specific date, time and
duration. The application must generate an access code, a URL for this
conference and provide a dial in number. Participants can join the
conference by dialing the number and entering the access code.
If enabled participants must be able to ask the application to call them to
join the conference by clicking on the URL provided by the application
Scheduled conferences must include recurrence (daily, weekly or monthly)
The audio conferencing bridge must allow dial-in as well as perform dial-out
tasks to join the participants in the conferences
Users must have the option to specify access codes for a conference or have
them generated automatically by the application.
The application must generate different access codes for participants and
leaders

Kangra at Tanda
Page 73 of 219

Users must have the option to create either leader required or leaderless
conferences
Conference leader must be able to:
Mute participants
Add/drop participants via the web UI
Initiate web presentations, share their desktop and provide remote control
The application must be able automatically generate e-mails invitations to
the participants including: date, time, number to call, access code and URL
for scheduled conferences.
The application must be able to generate ICAL compliant calendar
appointments that can be uploaded into calendar tools such as Outlook for
calendar updates.
Users accessing the conference by phone must have DTMF commands
available to control his participation in the conference
Presence and Instant Messaging
The Instant Messaging System must be secure, auditable and provide the
ability for users to store IM threads locally
The instant messaging application must have a friendly, intuitive and easy
to use graphical interface that informs in real time the multiple states of
presence using the buddy list created by the user.
The presence must use icons and colors and must include at least:
On-Line Presence
Telephony Presence when calls are initiated through the conference bridge
Video Presence, displaying the capability of the user to establish a video
call.
Calendar Presence, coming from Outlook calendar
User-Choice Presence, (Busy, Be right back, Away, Out to lunch and Appear
off-line)
The instant messaging application must allow instant messaging (chat)
sessions between members of the buddy list and perform actions as:
Generate a call between buddy list contacts
Send an e-mail
Invite someone else to the conversation
Share an application
Launch an ad-hoc conference
The instant messaging application must include a log of all Instant
Messaging sessions by a conversation history list on the interface indicating
date, hour, contacts, content
The Instant Messaging service must be available during the audio
conference sessions.
During a conference the collaboration tool must allow the ability to attach
any kind of document to the conversation. This document must be
available for download by the participants at anytime
The data collaboration application must allow the leader to launch a web
presentation, allowing the user to show MS Word, Excel or Power Point
documents. In this feature the participants must not be able to access the
documents, only view. Advance control must be granted to the leader.
Participants must not be required to have MS Office installed on their client
machines.
The collaboration application must enable the leader to record the
conference including the documents used. This recording must be available
for future replays
The data collaboration application must allow the ability to Share
Applications providing all participants with the ability to visualize and
change documents shared in real time during the conference assuming

Kangra at Tanda
Page 74 of 219

control is granted.
The data collaboration application must allow the ability to share the
leader's entire desktop or a single application.
The data collaboration application must allow the individual with control of
the shared application to pause the session and resume it subsequently.
System should have 16 port video conference in built/ external bridge and
provide the conference in ad-hoc presenter mode.
The video conference bridge should have voice activated mode
functionality.
During a conference the collaboration tool must allow the ability to attach
other participant into the conference.
by selecting several contacts through a user interface (e.g. from UC Desktop
or Collaboration client) and pressing call button (e.g. from Phone) or by
calling additional people during a communication.
Casual, immediate, on the fly, 3 ways, 3 party or 6 party conference operate
in the same way as Ad hoc conferences. No conference identification is
provided or required. No conference resources are reserved. They are
acquired from a pool of resources.
Schedule conference
All the IP users must have facility of the Presence, IM (instant messaging)
2. VoIP Telephone Sets (Type 1)
IP Characteristics
(i) Dual 10BT/100BT/1000BT connection
(ii) 802.1x, LLDP compliant
(iii) VoIP standard SIP voice compliance, RTP, RTCP
(iv) Voice compression standards G711, G723.1, G729a and G.722
(v) Quality of Service
Integrated Ethernet switch with QoS support
TOS diffserv
802.1p/q.
(v) IP addressing Static or dynamic IP parameter configuration.
(vi) Both local and LAN powering
IEEE 802.3af Power over LAN full standard compliance
(vii) Display
7 16/9 color with backlight
WVGA (800*480)
Capacitive Touch screen
Haptic feedback
(viii) Keys
4 audio, 4 application, home
External keyboard port option
(ix) Audio
Narrow & wide band, handsfree
Bluetooth handset (BT embedded)
3.5 mm headset port
(x) Foot
Adjustable foot (25 to 60)
(xi) Application openness
Homepage
Unified Communication Features
i. Contacts - Interactive communications log with rich contact
cards,
ii. IM and telephonic presence information
iii. Should support video calling
120

Kangra at Tanda
Page 75 of 219

iv. User Services - presence status management and
communications routing
Agenda
Email
Multimedia Manager
Screensaver eg photo frame
Ringtones Uppload mp3 for personal ringing melodies
VoIP Telephone Sets (Type 2)
IP Characteristics
(i) Dual 10BT/100BT/1000BT connection
(ii) LLDP, 802.1z
(iii) Voice compression standards G711, G723.1, G729a and G.722
(iv) Quality of Service
Integrated Ethernet switch with QoS support
TOS diffserv
802.1p/q.
(v) IP addressing Static or dynamic IP parameter configuration. A DHCP client
should be integrated in the set.
(vi) Both local and LAN powering IEEE 802.3af Power over LAN full standard
compliance
(vii) Graphical display
Four Line text display screen
Number of pixels: 64 x 128 or better
Dot pitch: 0,5 x 0,5 mm or better
Visible area size:(min) : 70 X 38 mm or better
6 soft keys (or more)
Four-way navigator with exit and validation keys to navigate inside
the graphical interface.
Standard handset with enhanced audio quality
Hands free and group listening modes
Integrated alphabetic keyboard (34 or more keys) to access to dial
by name, text mail, etc.
Direct access to text and voice mailboxes
180
5.11 DESKTOPS, TABLETS & PERIPHERALS
Needed
1. DESKTOPS 150
Processor Intel Core i7-2600, 3.4 GHz, 8 MB Cache or better
Chipset Intel Q67 Express or higher on OEM Motherboard
Bus Architecture 4 PCI (PCI/ PCI Express)
Memory 2 GB 1066 MHz DDR3 RAM with 8 GB Expandability
Hard Disk Drive 320 GB 7200 rpm Serial ATA HDD or higher
Monitor 47 cm (18.5 inch)larger LED/ TFT Digital Colour Monitor
TCO- 05 certified
Keyboard 104 keys or more

Kangra at Tanda
Page 76 of 219

Mouse Optical with USB interface
Bays 3 Nos. or above
Ports 6 USB Ports (with at least 2 in front), audio ports for
microphone and headphone in front
Cabinet Small form factor (Max. 16 Litres)
DVD ROM Drive 8X or better DVD ROM Drive
Networking 10/100/1000 on board integrated Network Port with
remote booting facility remote system installation, remote
wake up, out of band management using any standard
management software
Operating System

Windows 7 Professional with Media and Documentation
and Certificate of Authenticity
OS Certifications Windows 7 OS and Linux certification
Power
Management
Screen Blanking, Hard Disk and System Idle Mode in Power
On, Set up Password, Power supply SMPS Surge protected
Preloaded
Software
Norton or McAfee or eTrust or e-Scan or ForeFront or
TrendMicro or PC Tool or QuickHeal Antivirus (Latest
Version) with 60 days License
Warranty One Year comprehensive warranty for all parts
2. TABLETS 350
Processor Intel Atom processor Z2760
Dual Core 4-thread, up to 1.80 GHZ processor
Operating System Windows 8 x86 (32-bit)
Windows 8 Pro x86 (32-bit)
Display 10.1" (16:9) IPS, LED backlight, anti-glare, 5-finger
multitouch
Resolution HD WXGA (1366x768) 720p
Integrated
Graphics
Intel HD SGX545 GFX (12-bit, 1080p video @30fs, DX9)
Memory 2GB LPDD2 SDRAM
HDD 64GB (e-MMC)
Battery 25 days: Connected Standby
150 hours: MP3 playback (LCD off, HW off-loading)
10 hours: Video streaming (720p, HW off-loading)
A/C Adaptor 5v 10w AC/DC Adaptor
Microphones Dual-array digital mic with noise cancellation & VOIP
Speakers 2 Stereo 1w, 8ohm
Camera Front: 2MP, 720p HD webcam with LED (inside LCD)
Rear: 8MP, auto-focus with LED flash (outside LCD), motion

Kangra at Tanda
Page 77 of 219

JPG
Ports 1 USB 2.0
1 Mini HDMI
1 MicroSD slot
1 Docking connector
13.5mm mic / headphone combo
Sensors GPS
Compass
Ambient light sensor
Proximity sensor
Sensor hub
WLAN 802.11 a/b/g/n
Bluetooth 4.0
WWAN Gobi 4000 (LTE/HSPA+) (available in select models with
AT&T only)
Keyboard Bluetooth Keyboard With Stand
Sleeve Leather sleeve to house a tab and keyboard
3. Network Printer / Scanner 50
Print Speed Up to 35 ppm, letter; Up to 33 ppm, A4
First Page Out As fast as 8 sec
Print Resolution Up to 1200 x 1200 dpi
Processor 800 MHz
Memory 256 MB, Not expandable
Duty Cycle
(monthly, A4)
Up to 50,000 pages
Copy Copy Resolution Black: Up to 600 x 600 dpi
Copy Speed4 Black: Up to 35 cpm, letter; Up to 33 cpm, A4
Maximum Number of Copies Up to 99 copies
Copier Resize 25 to 400%
Scan Colour Scanning Yes
Scan Type Flatbed, ADF
Scan Resolution Optical/Hardware/Enhanced: Up to 1200 x
1200 dpi
Scan Speed Black (normal): Up to 20 ppm; Colour (normal):
Up to 9 ppm
Gray Scale Levels 256
Paper Input: 250-sheet input tray
Output: 150-sheet output bin
Two-sided Printing: Automatic (Standard)
Sizes:
Tray 1: A4, A5, A6, B5 (JIS), envelopes, 16K, 76 x 127 to 216
x 356 mm;

Kangra at Tanda
Page 78 of 219

Tray 2: A4, A5, A6, B5 (JIS), 8.5 x 13 in, 105 x 148 to 216 x
356 mm;
Tray 3: A4, A5, A6, B5 (JIS), 8.5 x 13 in, 105 x 148 to 216 x
356 mm (optional 500-sheet feeder/tray)
Weights:
Tray 1: 60 to 163 g/m (straight through paper path for
special media);
Tray 2: 60 to 120 g/m;
Tray 3: 60 to 120 g/m (optional 500-sheet feeder/tray)
Types: Paper (plain, Green mode (thin 60 g/m), light 6075
g/m, heavy 90105 g/m, bond, card stock 10576 g/m,
colour, letterhead, pre-printed, pre-punched, recycled,
rough); envelopes; labels; transparencies
Interfaces 1 Hi-Speed USB 2.0; 1 Host USB; 1 Ethernet 10/100/1000
Base-TX network; 1 Walk-up USB

Compatible
Operating
Systems
Full software installs supported on:
Microsoft Windows 7 32-bit and 64-bit, Windows Vista
32-bit and 64-bit, Windows XP 32-bit (SP2 or higher);
Driver only installs supported on:
Microsoft Windows Server 2008 32-bit and 64- bit,
Windows Server 2003 32-bit (SP3 or higher); Mac OS X
v10.5, v10.6, v10.7; Linpus Linux: 9.4, 9.5 Red Hat Enterprise
Linux: 5.0, 6.0 OpenSuSE: 11.3, 11.4 Fedora: 14, 15 Ubuntu:
10.04, 10.10, 11.04 Debian: 5.0, 6.0 and HPUX11i
Network
Protocols
Via built-in networking solution: TCP/IP, IPv4, IPv6; print:
TCP-IP port 9100 Direct Mode, LPD (raw queue support
only), Web Services Printing, IPP 2.0, Apple AirPrint, HP
ePrint, FTP Print; DISCOVERY: SLP, Bonjour, Web Services
Discovery; IP CONFIG: IPv4 (BootP, DHCP, AutoIP, Manual,
TFTP Config, ARP-Ping), IPv6 (Stateless Link-Local and via
Router, Statefull via DHCPv6); Management: SNMPv2/v3,
HTTP/HTTPs, Telnet, TFTP Config, FTP FW Download, Syslog;
Security: SNMPv3, SSL Cert Management, Firewall, ACL,
802.1x
Certifications Safety:
IEC 60950-1:2005/EN 60950-1:2006+A11; IEC 60825-
1:2007/EN 60825-1:2007 (Class 1 Laser/LED Product); IEC
62479:2010/EN 62479:2010; GB4943-2001
EMC:
CISPR22:2005 +A1/EN 55022:2006 +A1- Class B; EN 61000-
3-2:2006 +A1 +A2; EN 61000-3-3:2008; EN 55024:1998 +A1
+A2; FCC Title 47 CFR, Part 15 Class B/ICES-003, Issue 4;
GB9254-2008, GB17625.1-2003

4. Laser Printer 125
Print Technology Laser
Print Speed Black (normal, letter): Up to 26 ppm;
Black (normal, A4): Up to 25 ppm
Print Resolution Black (best): Up to 600 x 600 x 2 dpi (1200 dpi effective

Kangra at Tanda
Page 79 of 219

output); Black (normal): Up to 600 x 600 dp
Standard
Connectivity
Hi-Speed USB 2.0 port, 10/100 Ethernet networking
Control Panel 4 LED indicator lights (Go, Ready, Attention, Toner Low), 2
buttons (Go, Job cancel)
Memory 32 MB
Media Types Paper (laser, plain, photo, rough, vellum), envelopes, labels,
cardstock, transparencies, postcards
Media Sizes
Supported
Letter, legal, executive, postcards, envelopes (No. 10,
Monarch)
Paper Handling Input Capacities: 10-sheet priority feed slot, 250-sheet input
tray, Up to 260 sheets, Up to 15 envelopes;
Output Capacities: 150-sheet face-down bin, Up to 150
sheets, Up to 15 envelopes, Up to 100 sheets transparencies
Duplex Print Automatic
Processor Type: Tensilica
Speed: 400 MHz
Compatible
Operating
Systems
Microsoft Windows 7 (32-bit/64-bit), Windows Vista
(32-bit/64-bit), Windows XP (32-bit/64-bit), Windows
Server 2008 (32-bit/64-bit), Windows Server 2003 (32-
bit/64-bit), Mac OS X v 10.4, v 10.5, v 10.6, Linux, Unix6
Operating
Environment
Operating Humidity Range: 10 to 80% RH;
Operating Temperature Range: 15 to 32.5 C
5.12 INSTITUTE MANAGEMENT SOFTWARE
a. Supply: Supply of the Software Licence including peripherals, completely described in the BID,
b. Installation:
i. Configuration and Setup of the Software according to the requirements of the Institute.
c. Uptime: The Bidder will ensure an uptime of 99% for the Software deployed by them.
d. AMC and Upgrades: The technical maintenance of the Software will be the responsibility of the
e. Estimated number of users of application is mentioned below. User License should be complete
in all sense i.e. only Full Usage User License has to be quoted. All licenses shall be of Perpetual
Nature only. No time restriction licenses shall be entertained.
S No Name of Module Number of Users
1.
2.
3.
4.
Student Lifecycle Management
HRMS Application
Institute Financials
Inventory
1,200
10
5
5

Kangra at Tanda
Page 80 of 219

5.
6.
7.
8.
9.
10.
Supply Chain Management
File
Workflow
Notings
Daak & Correspondences
Archiving
5
300
300
300
50
5
The software should necessarily run on any flavour of Unix / Linux OS.
S No Item Description
1. Basic Requirements:
General Features
The requirements in this section will apply to all proposed systems and / or components,
irrespective of functional areas.
The proposed solution should be best-of-breed solutions supporting industry best practices in
their respective functional areas. They should:
1.1 Be fully web-enabled, supporting the Web 2.0 tools.
1.2 Be capable of supporting de-centralized as well as centralized processing.
1.3 Provide user oriented self-service capabilities wherever appropriate.
1.4 Support multiple languages.
1.5 Have a robust set of communication and reporting tools.
1.6 Utilize modern workflow capabilities in streamlining interactions among functional processes.
1.7 Provide application development tools to support the continuous development/refinement
of applications.
1.8 The database should also be available independent of the application and be a proven-
solution in the database space (eg. Oracle, DB2, MS SQL Server, etc.).
1.9 All offered products should be full use and unrestricted. This includes licenses for the
Application Modules, Database, Application Server and any of their components or any other
software required to run the application successfully.
1.10 Software source code should be offered.
Target Users
The proposed solution should be targeted at supporting a broad spectrum of users, including:
1.11 Administrative offices (centralized operations and backend support)
1.12 Departmental administration (distributed operations and support)
1.13 End-users (students, alumni, faculty, and staff)
1.14 Management (informational and analytical)
Access and Authorization
Only authorized users should have access to the system(s). As such, the system(s) should
therefore have the ability for the specification of who will have access to which functions.
Where appropriate, further discrimination at the data level (e.g. Respective departments may
only have access/update to data related to their own departments) is required. In this regard,
the capability to support multi-role differentiation based on a single user sign-on will be
essential.

Kangra at Tanda
Page 81 of 219

The proposed system(s) must support a comprehensive access and authorization mechanism,
including:
1.15 Single Sign-On for all system components,
1.16 Support for a central authentication scheme,
1.17 Ability to define multi-level authority, comprehensive set of user roles and permission lists,
and flexible segmentation of data,
1.18 Ability to manage access to authorized functions based on the roles represented in the
account,
1.19 Ability to manage access to different segments of data depending on the role (e.g. a
department user may only have access to data that are related to his/her department,
personal information of a user can only be accessed by the user himself/herself and
administrators that are responsible).
Single and Minimal Data Entry
1.20 Data should be entered at source only once and be used throughout the system(s)
1.21 There should be provisions to facilitate and minimize data input (e.g. use of intelligent default
values, inheritance from previous entries, etc.)
1.22 Facility to strictly avoid any duplication of data. Search/match facility required that that help
restrict the entry of duplicate data by providing interactive alert messages.
Import / Export Data
1.23 Upload data from all the existing local student records held by the institute.
1.24 Facilitate to Import/Interface with the third party applications in the Institute.
1.25 Extract data in various formats.
1.26 Import and Export to the archived files.
1.27 Produce reports on all areas of data that can be exported to standard office suites.
1.28 Facilitate the cut-copy-paste function from the application to standard office suites.
Archiving
The application should:
1.29 Provide a Data Archival utility as a part of the standard offering.
1.30 Facilitate the query and reporting on archived data.
Audit Trail
The application should:
1.31 Record changes in data in every field with user ID and time stamp, with ability to record
reasons in some cases.
1.32 Enable which fields or tables are to be audited through a delivered tool.
2. Technical Requirements
General features
The proposed solution should:
2.1 Be fully integrated.
2.2 Allow users with security access to override rules where appropriate.
2.3 Allow students and other constituents to be identified and maintained e.g. tutorial group,
class groups, assignment groups, international students, research students etc.

Kangra at Tanda
Page 82 of 219

2.4 Support version control of key data concepts, including, but not limited to, awards, courses,
units and organizational units etc.
2.5 Incorporates extensive and powerful data import and export facilities
2.6 Incorporate a powerful, extensive and user definable set of data query tools.
2.7 Display information graphically without the need for users to download data to a third party
product e.g. system provides the facility to display charts of active courses by organizational
unit, students by mode of study, student types etc. Respondents should be able to detail fully
the extent to which the solution meets this requirement.
2.8 Provide the infrastructure to allow screen, form and report field names to be changed to suit
Institution nomenclature.
2.9 Provide the ability to view transactions for a student by term within each module. For
example, the user can view all applications for admissions for a student on the Application
Summary screen; the user can view all enrolment transactions for a student for a specific
term using the Enrolment screen. Similar summary screens are available in Financial Aid,
Student Finance, Correspondence, Event participation and to audit specific transactions such
as name changes, grade changes, etc.
2.10 Deliver very robust Search/Match functionality. Anywhere that a new ID (student ID) can be
created (manually, tape load, test score load, transcripts, etc). The solution should be
configurable to automatically run Search / Match to ensure that the institution is not creating
duplicates.
2.11 Provide users with the ability to restrict/encumber/sanction students so that they are
stopped from accessing various functions or receiving certain services, e.g. block on academic
transcripts, graduation, viewing exam results, online enrolment etc.
2.12 Record special requirements at a student, course attempt and unit attempt level e.g.
Immunizations records etc. This information cannot be stored in free-text notes fields, but
fields specifically designed with start and end dates, reference numbers etc.
2.13 Support standard browser cut and paste functionality.
2.14 Be configurable to automatically send an email to a student when a staff member exercises
an override, indicating approval or otherwise. The contents of the email are user defined and
customizable.
Security / System Administration
2.15 Facilitate that most of the security functions, if not all, should be capable of being managed
by the user system administrators without the need for institutional IT support. Respondents
are to detail all areas of the solution where IT support is required. Following initial one-time
IT-based setup of integration with LDAP, SSO, registration of digital certificates, on-going
security functions are web-based and may be distributed across campuses.
2.16 Provide varying granularity for data level security. Respondents to explain fully the level of
granularity and an overview of how the security system is structured - e.g.
roles/groups/menu functions etc. Security should be based around roles that collect users
into logical groups. Roles are assigned permission lists, granting access to system objects such
as menus, pages, background jobs, reports and row-level security provisions.
2.17 Ensure that at logging-on, users are required to enter a unique user ID and a password.
2.18 Allows for date effective user accounts (i.e. start dates).
2.19 Allow for password ageing.
2.10 Enforce password maintenance upon first user access.

Kangra at Tanda
Page 83 of 219

2.11 Allow user system administrators users to maintain security at form, report, and job level or
data field for roles and / or users without the need for IT / DBA support.
2.12 Provide the facility to link security roles to individual users.
2.13 Allow for the creation of an unlimited number of security roles.
2.14 Allow user system administrators to link menus, forms, reports etc to security roles.
2.15 Allow user system administrators to link multiple security roles to an individual user.
2.16 Allow roles and/or users to be configured to have restricted update access for specific forms.
E.g. User can only update course information for those courses for which the user is
responsible.
2.17 Be capable to limit data operations (insert, update, delete or query only) assigned to
particular roles.
2.18 Allow user system administrators the ability to re-set user passwords.
2.19 Provide appropriate security to restrict student access to their own details.
2.20 Provide the facility to set up menus and sub-menus for classes of users.
2.21 Allow selected security roles/users to override and/or waive rules e.g. a small number of
'super' users with access to most or all functions.
2.22 Allow user system administrators to immediately suspend individual user access privileges.
2.23 Have an automatic timeout of connected but inactive users.
2.24 Provide the facility for user administrator to contact all, or selected, users connected via
standard web browsers, via on screen display or email (e.g. to advise users to disconnect
prior to the system being taken down).
Ease of Use
2.25 Provide a feature of shortcut navigation to be provided via navigational collection portlets,
favourites and hyperlinks, etc.
2.26 Carry forward context values (at least student ID, course code, citizenship, gender, title) from
one form to the next. Within a given page, basic context values are carried through on the
top of all of the tabs (Student Name and ID and other relevant context values). In addition,
Student ID and other data items appear in context for search when moving between screens.
2.27 Provide the facility to display multiple student indicators (which should be user-definable,
with logic), displayed along with student personal details:
Examples of student indicators include but not limited to:
International student indicator, students under 18, articulating students, students at
academic risk based on GPA etc. These may be displayed with a combination of service
indicators and student attributes.
2.28 Have an ability to move directly from one form to another without the requirement to move
up and down menu structures. In particular, the solution provides the ability for a user to
create a user-defined list of links to access pages directly.
2.29 Inserts default values automatically where possible.
2.30 Have intuitive form navigation across all modules, minimizing the need for special training.
2.31 Have a consistent form design across all modules.
On-Line Help

Kangra at Tanda
Page 84 of 219

2.32 Have a comprehensive electronic user manual for processes, configurations etc and can be
easily printed or exported.
2.33 Have a context sensitive help on all screens and for all data elements.
2.34 Have a comprehensive on-line technical documentation.
2.35 Provide an on-line tutorial facility for staff.
Workflow
2.36 Provide an integrated workflow engine enabling user definition and modification of business
rules. It should include an inbuilt workflow engine, designed for intra-application workflow
and integration with external notification mechanisms. The workflow should be based
around the concepts of rules, roles and routings allowing work to be routed to individuals or
pools of users, evaluated dynamically.
2.37 Provide workflow routes information and notifications via the institutes email solution using
a protocol such as SMTP.
2.38 Allow workflow to be maintained by business administrators. Normal day-to-day
administration of workflow should be based on role membership and web-based
administration pages. Only structural changes to workflow processes will exceed the scope of
business administrators.
2.39 Provides staff with a list of current workflows/tasks awaiting action.
Data Integrity
2.40 Provide for comprehensive data validation at point of entry to the maximum extent possible.
2.41 Cross-validated data at point of entry against other data held within the solution to the
maximum extent possible, ensuring data integrity at all times.
2.42 Provide solution architecture for extensive and comprehensive implementation of business
rules and constraints within the application logic tier.
2.43 Provide extensive validation reports for all batch data creation & update processes. Batch
reports log their progress to a batch messages area. They may be viewed readily via the
browser.
2.44 Adopt an open format interface that doesnt require proprietary tools.
2.45 Be able to input data item/objects from other sources efficiently and easily.
2.46 Support date effective data to the maximum degree possible, thereby enabling the
maintenance of comprehensive data history.
Audit
2.47 The solution should include comprehensive audit-trail functionality.
2.48 The solution should provide a history of all on-line transactions especially in the self-service
environment.
Batch System
2.49 All reports / jobs should be able to be run on-line and in batch.
2.50 Have ability to run any number of jobs / reports in a single batch request; jobs must be set to
run in sequence or in any order.
2.51 Have ability to send reports via email as an attachment. User must have a flexibility to choose

Kangra at Tanda
Page 85 of 219

formats such as pdf, csv, doc, etc).
2.52 Provide a comprehensive and clear run logs including error reports.
Reporting
2.53 The solution should provide the facility for users to generate reports that may be defined as a
type correspondence and stored in the solution appropriately.
2.54 The solution should provide a reporting interface is functional, flexible and user friendly.
2.55 The solution should have a reporting wizard which will assist staff in the creation of reports.
2.56 The reporting wizard should contain, but is not limited to, the following types of functions:
Data Field Selection
Sort Order Selection
Condition Selection
Aggregation of measurements (such as grades, credit points, fees, etc)
Chart Options (types of charts, axis and field labels)
Drill Options (drill down to more detailed information) in reasonable circumstances
Data Field labelling.
2.57 The solution should allow:
Staff to print, save, export or email the report.
Staff to save the report and parameters as a favourite so that so that it can be selected
and run on demand.
Users to grant access to saved reports to other users
Creation of charts e.g. pie, bar etc.
Drill down into reports to gather more detailed information.
2.58 The solution should produce reports that can trigger a workflow event.
2.59 The solution must allow staff to select templates to assist in report formatting / presentation.
2.60 The solution should allow staff to apply mathematical functions to data fields (e.g.. Sum,
count, average).
2.61 Include a standard set of reports based on industry best practice.
2.62 Have ad hoc reporting capability that is user friendly and easy to use.
2.63 Support downloading capability in a variety of formats as well as direct import from software
such as MS Excel.
Customizability
With the expected best practice process flows as well as the best-of-breed functionalities, the
institute would consider implementation of the requested systems on a vanilla basis. The
customization/development would be considered only as a last resort.
To minimize the need / impact of customization, the proposed system should, wherever
appropriate, support:
2.64 Flexible customization capabilities.
2.65 Flexible data structures with user-definable fields.
2.66 Callable functions to access data/functions with application conforming to industry
standards.
2.67 Ability to extend/change existing pages without much impact on the application.
2.68 Ability to add / modify the existing workflows.
2.69 A bolt-on approach without affecting the core functions should be supported to minimize
future maintenance and upgrade efforts.

Kangra at Tanda
Page 86 of 219

Correspondences
2.70 The solution should be able to generate correspondence to students, staff, sponsors and
other people maintained in the database.
2.71 The system should facilitate faculty to advice students.
2.72 Provide an online methodology to communicate with students.
2.73 The portal should provide the sole access to email service, class schedule, assignment, billing
and payment, and a suite of student services including course registration, and other events
organized by the institute.
2.74 Ability to create, track and tie communication records to individual and external
organizations.
2.75 The solution should enable user-definition of correspondence types / style (by email, post,
etc.).
2.76 The solution should allow the correspondence to be printed, emailed or delivered via the
student self-service facility.
2.77 The preferred method of communication should be tracked and be maintained for each
student.
3. Student Lifecycle - Functional Requirement
Institute Structure
3.1 Incorporate a sophisticated organizational unit functionality enabling user definition of
terminology (e.g. Faculty; School, Division etc)
3.2 Maintain locations within organizational units.
3.3 Support an alpha numeric coding schema.
3.4 Maintain organizational unit types e.g. institutions, sponsors, schools, research centers,
international agencies, external organizations, benefactors, third party debtors etc.
3.5 Differentiate between academic and non-academic organizational units.
3.6 Differentiate between internal and external organizational unit.
3.7 Maintain status codes e.g. planned, current, inactive, with start and end dates.
3.8 Allow for multiple address types to be stored against organizational units.
Student Admissions
3.9 The solution should be capable of maintaining prospect / applicant information in the
system.
3.10 Automatically evaluate applicants based on user-defined criteria.
3.11 Coordinate concurrent prospect and application records.
3.12 To provide facilities for applicants / students to apply and register on multiple programmes.
3.13 To have admission period to invite applications from new applicants or students before each
semester starts. Able to apply through different means such as mailing of an application
form, online through the Internet, etc.
3.14 The system should perform screening / validity check according to a set of pre-defined
criteria such as pre-requisite requirements to ensure that the students / applicants are
eligible to register on the courses / programme.

Kangra at Tanda
Page 87 of 219

3.15 The system should allow students to change their course / programme choices, and
applicants to change their personal information as well. Relevant validity checking should be
done on the new course / programme choices.
3.16 Apart from running the admission process in a first round, second round concept, the
system should provide flexibility to process in other ways and/or at different times of the
year and / or different set of criteria for prioritization of applicants.
3.17 The system will also allow users to skip the normal procedures to register students directly
subject to verifications such as no double registration on the same course.
3.18 The system should be integrated with the finance system in relation to the students
payment of tuition fees.
3.19 The system should allow various entry points such as area of interests, level of study,
education background, etc. and display the relevant University programmes for the
applicants to consider.
3.20 To provide facilities to let students transfer, defer and withdraw from programmes / courses.
3.21 The system should be able to record the receipt date and the details of the applicants on an
individual basis and/or by a batch process for setting up the records in the database. Details
of the applicants should include personal data such as name, address, and contact phone
number and so on.
3.22 The system should perform screening / validity check according to a set of pre-defined
criteria such as pre-requisite requirements to ensure that the students / applicants are
eligible to register on the programmes / courses.
3.23 The system should be able to maintain different status for students i.e. Active or Non Active,
Special Leave, Postpone Semester.
3.24 Reporting and Analysis at each level of the application-filing process.
Registration & Course Enrolment
The proposed solution should have:
3.25 Ability to exchange data with external class timetabling software.
3.26 Capacity to manage regular and non-regular course offerings.
3.27 Ability to populate classes based on student demands.
3.28 Robust course enrolment facilities, including add, change, drop, swap, and wait listing of
coerces, complemented by ability to search class schedules and simulate an attendance
timetable based on selected courses.
3.29 Automatic checking of enrolment conditions (e.g. Prerequisites, co-requisites, exclusions,
credit loads, and variety of such) based on curriculum and course settings).
3.30 Support for advisors/faculty administrators that should be notified of situations requiring
review/approval and ability to act on such situations.
3.31 Availability to derive/predict demand for courses and sections of both required courses and
electives from the curricular and student data.
Curriculum Management
The curriculum system should be used to define information regarding the academic
offerings of the university including courses, study areas (majors, minors, etc), units, classes
and related activities (lectures, tutorials, laboratory, etc.) and their awards.
As the institute moves forward towards a much more flexible, wide-open curriculum with
implementation of the course, the student information system must have the ability to
manage all aspects of a complex curriculum.

Kangra at Tanda
Page 88 of 219

The solution should:
3.32 Cater for institution's policy for students in combined degrees (2 or more).
3.33 Be capable of defining and maintaining the following, but not limited to, rules in a manner
that can be applied automatically by the appropriate functions within the system:
admission
enrolment
progression (probation/exclusion)
completion
3.34 Provide quota management functionality including, but not limited to, enrolment quota,
reserved places, dedicated/designated assignment of places, wait-listing.
3.35 Store course, study area and unit information in such a way as can be used to display on the
web and be extracted in a format appropriate for preparation of handbooks, brochures and
other publications.
3.36 This function should be supported by:
Workflow
Extensive use of management and operational reports.
3.37 Allow the definition of offering a course version that allows different course structures at
different teaching locations.
3.38 Provide the ability to put in a future start date and only accept commencing students after
that date
3.39 Provide the ability to put in a future discontinued / expiry date and still accept commencing
students into the course version
3.40 Allow courses to be linked to one or more course offering / careers / awards.
3.41 Allow easy grouping of all courses that lead to the same degree offering.
3.42 Facilitate capture and storage of unit related information including, but not restricted to:
Unit credit points enrolled and achieved when completed
Indicator that specifies whether it is possible to override the enrolled and/or achieved
credit points at the student unit attempt level
Total unit contact hours, broken down by components
Unit version activities (seminars, tutorials etc)
3.43 Record and maintain timetable information for unit versions, their modules (if any) and
activities including, but not limited to:
Primary lecture
Linked secondary activities (tutorial, laboratory etc) and their quotas
Mode of delivery for each activity
Location / venue
Time slot and duration
Contact person for each activity
Whether or not the unit is assessed
Grading schemas
Classes offered
Unit rules (pre-requisites, co-requisites, translations, incompatibles, quotas etc, )
3.44 Roll unit versions to a future teaching period / academic year.
3.45 Provide the facility to store comments / notes
3.46 Incorporate rules for calculating a student's study area GPA.

Kangra at Tanda
Page 89 of 219

3.47 Support multiple study areas in a single degree course.
3.48 Provide for personalized student course plans to be dynamically generated at time of offer /
acceptance.
3.49 Provide a student-friendly solution for managing student self-managed choice. It must
deliver the ability for students to manage his / her course of student by performing what-if
analysis against other degree plans that he / she may be considering so that the degree
progress can be evaluated personally.
3.50 Once a student has been offered a place and admitted to the course, they can be pre-
enrolled in classes also by using a number of features: mass enrolment of prescribed units;
quick selection of units by a staff member or the student self-service. Any student self-
service actions will be cross-validated against their academic progression rules.
3.51 Enable students to view / modify their course plan via the self-service portal.
3.52 Incorporate enrolment checks against a student course plan e.g. restrict the set of unit
attempts that the student can select from to those that are part of a personalized student
course plan or which otherwise can contribute to the satisfaction of course requirements.
3.53 Record and maintain details of course plans at the course offering level, including, but not
limited to:
Course plan coordinator.
Course plan status (e.g. approved for enrolment, approved for graduation).
Course components (Majors, Minors etc) associated with course plan.
Units of study within course components.
Units of study within years of course.
Other study options within years of course.
3.54 Provide a student-friendly solution for managing student self-managed choices (e.g. selecting
units from a list of options).
3.55 Incorporate checking of academic progress against a student course plan.

Class Time Tabling
3.56 Should enable creation of class schedule with:
Pattern of the dates on which class is scheduled.
Assignment of single or multiple faculties to the same lecture.
Association of topics of study with each scheduled class.
Management of different sections (if more than one) during the teaching pattern.
Assignment of facility to the class / section of the class.
Prompting of errors / warning messages in case there is a conflict of facility.
Integration with:
Learning management system in case the class is done over an LMS application /
online.
Finance system in case the class is charged otherwise the tuition fee of the student.
3.57 System should have a feature to search:
The availability of a facility at a given time / date / building.
List of the rooms available depending upon the type of meeting (Lecture, laboratory,
conference hall, auditorium, etc.)
Schedule / free hours of the faculty under consideration.
3.58 The solution should provide a web-based facility for enquiries on the published class
timetable.
3.59 The solution must use a "shopping basket" concept, where students can select a variety of
classes and validates their enrolment eligibility (i.e requisite checking).

Kangra at Tanda
Page 90 of 219

3.60 The solution should be configurable to import a generated class timetable from an external
package.
Students Records
The system should:
3.61 Search facility using multiple parameters like first name, last name, Student ID, etc. using
features like begin with, end with, contains, etc.
3.62 Date effective address details, including:
Home address.
Preferred address for the receipt of official correspondence.
Preferred billing address.
Emergency contact details.
Work details.
Other address types (e.g. email).
Other contact data (e.g. telephone, personal web page, mobile number and a separate
SMS phone number).
3.63 User definable titles e.g. Mr, Ms, Dr etc.
3.64 Record and maintain text notes that apply at the person level with user definable levels of
security governing who can access what notes.
3.65 Record and maintain the following information about students and other persons as a single
model.
Name (title, surname; first, second, and other given names).
Awards / honours.
Preferred name (for use in most system related applications).
Official name (for academic record and graduation purposes).
Date of birth.
Gender (including a value of 'undisclosed' or similar).
Any special requirements e.g. first aid etc.
3.66 Based upon a flexible model enabling all persons of interest to the institution to be modelled
as a single individual with multiple distinguishing roles over time.
3.67 The solution maintains a history of name changes.
3.68 Depending on the module, advanced search capabilities include Search by:
Student ID.
Campus ID.
National Student ID.
Career.
Term.
Last Name.
First Name etc.
Search should also include a variety of usages to expand Search capability including
operands such as 'begins with', ' = ' , 'contains', 'not =', plus others.
3.69 Records and maintain a person's secondary education details e.g. school, subjects, grades
achieved, year achieved, aggregate scores etc.
3.70 Record and maintain a person's tertiary education studies undertaken at other institutions,
including course title, level, year(s) undertaken, progression status, aggregate scores (e.g.
GPA) and individual subject marks and grades, exclusion details.
3.71 Record and maintain a person's tertiary education studies undertaken at overseas
institutions, including course title, level, year/s undertaken, progression status, aggregate

Kangra at Tanda
Page 91 of 219

scores (e.g. GPA) and individual subject marks and grades, exclusion details.
3.72 Record and maintain work experience.
3.73 Enable users to record assessment details, rankings and other decisions / outcomes both in
the context of individual qualification assessments and admission application instances.
3.74 Enable users to indicate applicant education details - test results, previous studies such as
degrees, diplomas and subject details - and use these as a basis of the applicant basis of
admission. Using this information, users can manually weight or rank these qualifications,
add feedback and order in priority.
3.75 Ability to assign to do items grouped by checklist to individuals, organizations, or events.
3.76 System must be able to maintain private or public comments of each student.
3.77 System must be able to maintain incoming and outgoing communication between the
university and the student, i.e. through phone, email, etc.
3.78 Ability to define person-to-person relationships and send one communication to both parties.
3.79 Ability to personalize communication with salutations.
3.80 Report enrolment, graduation or demographic statistics.
3.81 Provide summaries of student statistics, facility occupancy and class section availability.
3.82 Able to maintain grading information.
3.83 The system should also alert applicants on the course choices if there are any associated
compulsory / advisory pre-requisites.
3.84 The system should provide flexibility to maintain a complete, accurate and updated record
for a student to include his/her study in the university offered in different modes, e.g. in
distance learning and/or full-time study, etc.
3.85 A set of criteria used to determine the number of tutorial groups and their capacity for each
course will be set up in the system to include courses on offer, enrolment number,
permissible number of students in a tutorial group, etc. Based on the criteria, tutorial groups
led by tutors for each course will be created.
3.86 Based on the tutorial groups assigned/chosen by students, each student should have his/her
own tutor to contact for telephone tutoring and for the marking of assignments for the
course he / she has registered.
3.87 Upon the resignation of a tutor, the system should allow user to reallocate the students led
by the resigned tutor to another tutorial group or to redistribute the students across the
tutorial groups of the same course.
3.88 Provide facility to create, define and update the codes for the various category and sub-
categories of disciplinary offence and the disciplinary actions to be taken into the system.
3.89 Allow for the recording of details of each disciplinary case during the processing of
assignment / examination records.
3.90 Provide for facilities to take appropriate follow-up action if there are any sanctions imposed
on the students to include such as suspension of study, withholding conferment of academic
awards, etc.
3.91 Provide facilities for maintaining a student record to trace the complete academic history for
the pursuit of study within the Institute, whether they have attended full-time or part-time
programmes / courses.
3.92 Ability to include special GPAs and test scores in the transcript.
3.93 Ability to have different calculations for GPA every year.

Kangra at Tanda
Page 92 of 219

3.94 Ability to
Use the old curricular description instead of the new curricular description in the
transcript, based on when the student takes the class.
Personalize appearance of transcripts, reports and letters such as logo, colour, font
formatting, etc.
Define a selected / targeted population for the distribution of communication and
updating of data in selected functional areas.
Have a tool to select groups of people or organizations, based on a variety of criteria.
Support multi-currency.
Provide a view of mid-term grades.
Clone the user security setup based on existing user ID, in batch.
Control enrolment and dropping of classes using class permission / instructor consent.
Configure enrolment workflow request for classes that require approval.
Limit some classes where only elite students can enrol.
Do block enrolment based on student Ids.
Academic Advisements / Course Plan
A course plan should be a road-map of what units/subjects a student must complete in
order to attain the award into which they are enrolled. It should show units/subjects passed,
enrolled, credited/advance standing and those yet-to-be completed and be ordered in a
coherent, student friendly, flexible structure.
The system should:
3.95 Analyse degree progress and provide recommendation for working towards achieving the
degree.
3.96 Evaluate transfer credit from recognized program university / institutions
3.97 Tailor academic program for each student.
3.98 Alert students with any information using notifications / workflows from the systems.
3.99 Provide flexibility to handle examination result process, which may include programme
progression according to the specified programme rules as maintained in the system. The
system will provide facility to handle examination results of students on different mode of
study or programme.
3.100 Help students with their study plan for graduation, the system will match the requirements
for an award against the progress made so far by the student (including any advanced
standing granted and topping-up list approved) and identify the courses and options /
alternatives that the student is required to complete for the award.
3.101 Each programme of study has its own set of criteria for graduation, which will stipulate the
no. of credits, level of credits and the specific courses to complete, and the language of
instruction of the programme. These criteria will need to be set up into the system as the
necessary parameters governing graduation. For the degree with honours, each programme
will have a set of criteria for the classification of the degree.
3.102 Have an online planning tool for students to plan their yearly studies.
3.103 Enable students to view the entire academic requirements and academic progress online in a
quick and user friendly view.
3.104 Be able to advise students online on their next course of action to fulfil graduation
requirements. The solution should cater to a student-friendly feature to manage his choice of
courses.
3.105 Be able to do a full analysis of requirements used to search for courses, classes based on
degree requirements.

Kangra at Tanda
Page 93 of 219

3.106 Allow students to create scenarios for graduation (What-if) online based on their academic
goals and review the previous reports online.
3.107 Advise students online how much grade they need to obtain in order to achieve the result.
3.108 Provide for personalized student course plans to be dynamically generated at time of offer /
acceptance.
3.109 Once a student has been offered a place and admitted to the course, they can be pre-
enrolled in classes also by using a number of features: mass enrolment of prescribed units;
quick selection of units by a staff member or the student self-service. Any student self-
service actions will be cross-validated against their academic progression rules.
3.110 Incorporate the checking of academic progress against a student course plan.
3.111 Enable linking of degree requirements to individual students entry qualifications,
exemptions, credit transfers, etc.
Grading Methodology
3.112 When a course starts to run at the beginning of a semester, the assessment parameters
should be set up in the system to define the criteria for the calculation of the assignment
marks and the overall continuous assessment score.
3.113 The system should provide for data capture of the attendance of day school / laboratory and
assignment marks including those from other sources.
3.114 The system should generate letters to inform students about their attendance, change of
assignments scores due to error in marking, rejection of late assignment, etc.
3.115 The system should provide flexibility to handle the assignment process for students on
different mode of study with a different timetable.
3.116 Before the semester starts, the permissible range of course score, overall examination score,
overall continuous assessment score governing the determination of course result grade
should be set-up and maintained in the system.
3.117 Before the final examination of a course starts, the parameters should be set up in the
system to define the criteria for the calculation of the overall examination marks based on
component scores, if any, and the final course score based on the continuous assessment and
examination scores.
3.118 The system should have the capability to create / maintain / amend / transfer assessment
parameters, scores and records for students on each programme / course in the system from
the existing or from the previous presentation according to the criteria set by the Institute.
Self Service Capability
The student should be able to:
3.119 Access information via Student Centre
3.120 View personal information such as addresses, contact numbers, emails, emergency contacts,
extracurricular activities, work experiences, honours and awards online
3.121 Update personal information
3.122 View announcements and open enrolment periods
3.123 View program advisor that has been assigned
3.124 View course schedule in a list view or calendar view
3.125 View lecturer, venue, date, time information for each class
3.126 Have date range and day range to view calendar view

Kangra at Tanda
Page 94 of 219

3.127 Perform search for available courses / subjects and view information of each course
3.128 Add classes to a shopping cart before checking out
3.129 Drop classes from enrolled classes
3.130 Add classes to wish list (pre-registration)
3.131 View grade (current and history) online
3.132 View assignment information such as due date online
3.133 View degree progress report to check progress towards completion of program
3.134 Request for official and unofficial transcript
3.135 Provide flexibility of payment through credit card / electronic check and maintain the
payment profile for future use
3.136 View outstanding payment amount details and payment history
3.137 Communicate with program advisors online
3.138 Search for courses on multiple search criteria such as lecturer, time, credit unit range, etc
3.139 Search course catalogue to integrate with the course planner
3.140 Display final exam schedule to students and advisors
3.141 View their course history
The faculty should be able to:
3.142 Access information via Faculty Centre
3.143 View personal information online
3.144 View teaching schedule online
3.145 Access class roster to view student who have enrolled, dropped, waitlisted
3.146 Access grade roster to view, add, update final grades
3.147 Access grade book to view and grade assignments
3.148 Import grades from Excel
3.149 Access to student information such as personal information, degree progress report and view
service indicators
3.150 Communicate with students online (selected students, all students)
3.151 Allow administrators and faculty members to view information of the students from the
student's perspective
3.152 The solution should give ability for faculty and advisors to review the advisement report of
individual students to guide students in their academic goals
Students Financials and Scholarship
The system should be able to:
3.153 Calculate tuition based on institute-defined criteria
3.154 Bill and manage student and third party receivables
3.155 Process and control credit card payments
3.156 Post financial aid disbursements
3.157 Age accounts and manage collections

Kangra at Tanda
Page 95 of 219

3.158 Generate debit notes for students to register on those courses/ programmes which they are
eligible
3.159 The system should allow for de-registering students from courses that have been refunded or
the tuition fee being deferred for a specified period and calculate the amount of refund due
3.160 When an application is accepted, application information including claim details, personal
data and payment details will be captured into the system.
3.161 Provide facilities to maintain students repayment records and repayments status and
generate reminders according to the normal repayment schedule and to link with the
defaulter and deferment subsystem as appropriate for the appropriate follow-up actions
3.162 Provide facilities for a defaulter subsystem to maintain the students records, calculate
surcharge and penalty charge and initiate actions on hold for some University processes, e.g.
withholding students final course results, withholding student graduation, etc. for students
who fail to repay the loan or instalment according to a defined schedule.
3.163 Allow students to make purchases of items online such as sweat-shirts, magazines or tickets
to events organized by the institution
3.164 Ability to block students from exam if they have not paid the tuition fees or if the student pay
the minimum amount defined, allow them to sit for exam but block from next year
registration
3.165 Ability to refund money to students if they receive scholarship
3.166 Ability for students to convert the payment to instalment basis
3.167 Ability to calculate the fees for student after the student register in classes
3.168 Ability to interface to the bank for payment made via the bank
3.169 Ability to make payment online and interface to bank payment gateway
3.170 Ability to maintain the scholarship received by students (internal and external aids from
government, from university, etc.)
3.171 Ability to calculate student's eligibility for the scholarship based on user-defined criteria
Event Management
The system should be able to:
3.172 Create and maintain data about institutional events and committees.
3.173 Organize information about events and committees.
3.174 Provide ability to record event attendees.
3.175 Provide ability to create reusable committee templates.
3.176 Provide ability to allocate committee resources.
Alumni Management / Contributor Relations
3.177 Alumni membership registration
3.178 Alumni membership renewal
3.179 Alumni members directory and enquires
3.180 Alumni members info update
3.181 Membership registration can be link to graduation database.
3.182 Ability to maintain the contributions made by alumni, friends or even external organizations
3.183 Ability for alumni to make contributions online

Kangra at Tanda
Page 96 of 219

3.184 Ability to manage fund raising campaigns goals, initiatives, budget, activities, resources, etc
3.185 Ability to manage institution events, budget, resources such as open day, orientation day,
sports day
Online Learning
3.186 The solution should be capable of being configured to interface with a 3rd party system such
as Blackboard / WebCT, Moodle, Sakai, etc.
Management Information
To support resource allocation and decision-making, it is desirable that robust and user-
friendly facilities be available with the system(s) using a web-based environment.
Pre-packaged analytic functions that
3.187 Provide interactive dashboards for faculty, students, etc.
3.188 Integrate well with source data
3.189 Support easy reporting with export facility to desktop suites like MS Excel, MS Word etc.
4. Human Resource Management System
Employee Related Processes
The system should have:
4.1 Capability to facilitate recruitment of faculty and staff.
4.2 Manpower planning.
4.3 Facilitation of promotion & deputation.
4.4 Support for the tracking and renewal of multiple concurrent appointments of same or
different durations.
4.5 Support multi categories of appointment types.
4.6 Maintaining staff records including personal particulars, terms of employment, salary and
benefit entitled, family, qualification, etc.
4.7 Recording and tracking changes to employment terms and employment history.
4.8 Generating various reports related to staff information, appointment and movement,
manpower allocation, and staff statistics.
4.9 Ability to provide benefits to the employees (including loans and advances).
HR (Workforce) Administration
4.10 Should maintain detailed and ongoing history of personal, employment, job and benefits-
related data; built-in workflow features automate the many notifications and approvals
typically required; performs many administrative tasks - hire new employees, add concurrent
or multiple jobs, enter job changes such as promotions and transfers, update personal
information.
4.11 Facilitates adding a persons human resources record into the system, like:
Personal data, such as name, address, personal relationships, and organizational
relationships, such as employee or contingent worker.
Job data, such as supervisor, department, job code, and compensation details.
4.12 Entering additional data into the record. In addition to the data that is entered when the
institute add a new record, it should also include:
Tenure with the institute.
Prior work experience.
Business expenses.

Kangra at Tanda
Page 97 of 219

Emergency contact information.
Visas, passports, and other identification data.
Driver's license information.
Bank accounts.
Volunteer activities.
4.13 Employee membership in unions, works councils, or labour agreements.
4.14 Over time, the institute will need to enter changes to a persons human resources record,
such as changes of name, address, marital status, and organizational status; promotions;
transfers; and leaves of absence. The institute should also be able to track employee
grievances and disciplinary actions imposed on employees.
4.15 The institute should be able to view summary information about its workers and run a
variety of different reports to review and analyse the workforce.
Training Administration
The system should:
4.16 Administer Institutes internal and external training programs and manage training budgets.
4.17 Track instructors, training facilities, contract vendors, and standard equipment required for
courses.
4.18 Define training courses and groups courses into training programs.
4.19 Identify trainer / instructor competencies and match to courses.
4.20 Establish pre-requisite requirements for the course.
4.21 Enrol students / participants / employees individually or by group (internal or external
participants).
4.22 Generate letters to students via hardcopy or email.
4.23 Identify competencies gained from course completion.
4.24 Budget and track training expenses.
4.25 Have capability for an internal employee or an external body to choose a scheduled training
and enrol online.
4.26 Have capability of wait-listing candidates for training
4.27 Have online enrolment for the training courses.
4.28 Reporting capabilities.
Employee Benefits
The system should facilitate in:
4.29 Enabling basic benefits system architecture and manually enroll employees and their
dependents into the benefits system. This comprehensive benefits management solution
should supports a full range of benefit programs and plans, and provides the institute with
everything that needs to maintain benefit records and to respond to inquiries from decision
makers, managers, and other employees.
4.30 Configuring benefit program.
4.31 Manually enrol employees and dependents into benefit programs.
4.32 Calculation of accrued leave awards and maintains employee leave balances.
4.33 Managing qualified savings plans and pension plans.
4.34 Managing vacation buy and sell programs.

Kangra at Tanda
Page 98 of 219

4.35 Processing retroactive benefits and deductions.
4.36 Sending enrolment data to third-party administrators.
Payroll and Absence / Leave Management
4.37 Using Salary Planning, the institute should be able to:
Establish salary plans by Business Unit and Company - including grades, ranges and
steps.
Maintain multiple salary plans to differentiate between locations and currencies.
Develop salary increase guideline matrices.
Develop salary increase budgets by department / groups.
Administer salary increase by group.
4.38 Generate payment to staff in accordance with the type and terms of appointment, with
capabilities to:
Generate basic salaries of varying intervals (e.g. monthly, hourly).
Capture / generate additions and deductions, gratuity, back-pay / arrears due to salary
revision, etc.
Payment of benefits.
Handle contributions to various retirement schemes.
Produce electronic and / or hard copy pay slip.
Support payment in a variety of forms (e.g. auto-pay, cheque) with the necessary
corresponding controls/interfaces (e.g. with banks).
4.39 For recurrent and / or dated additions / deductions, ability to set up a schedule as such.
4.40 Keeping staff pay history to enable staff cost projection, estimation and analysis.
4.41 Generate the corresponding accounting entries regarding staff payments for the financial
systems.
4.42 Capability to manage all the different pay scales and grade as prescribed by the pay
commission of India.
4.43 Run payroll in a central location by using a single database and code line, yet enter and
access payroll data from anywhere.
4.44 Use a global payroll rules engine to create unlimited campus extensions for the institute.
4.45 Isolate campus-specific regulations, processes, reports, self-service, and user-defined rules
from the core application.
4.46 State, calculate, and distribute an employee's pay in multiple currencies, if required.
4.47 Statutory and customary components specific to India.
4.48 Comply to the Indian tax rules.
4.49 Self-service applications that enable employees and managers to access pay slip information
as well as process absence requests and approvals.
4.50 Should have the ability to specify arrears processing rules, retroactivity processing, off-cycle
payroll runs, and bank-related information.
4.51 Ability to furnish claims and other expenses.
4.52 Management of leaves / absences.
4.53 Online access to employees to apply for various types of leaves and for managers to approve
/ decline the same.
4.54 Ability to manage LTC.

Kangra at Tanda
Page 99 of 219

4.55 Capability to provide medical reimbursement.
4.56 The application should have Employee Self-Service Features (not limited to) the following:
Submit absence requests and view their status.
View current and projected absence balances.
4.57 The application should have Manager Self-Service Features (not limited to) the following:
Submit absence requests on behalf of their employees.
View current and projected absence balances for their employees.
Approve or deny absence requests.
4.58 The application should have Administrator Features (not limited to) the following:
Configure request approval functionality, including multilevel approvals and alternate
approvers.
Configure absence accrual functionality, including a rules engine to compute the most
complex accrual logic.
Configure absence consumption functionality, including a rules engine to compute the
most complex consumption logic.
4.59 Configure absence terminology.
Self Service Features
4.60 Department and managers should be able to use this employee administration application to
update employee demographic information as well as manage an employee's status within
the organization, all within an intuitive web environment.
4.61 Workflows should is used throughout the application to streamline processes.
Employee and Supervisor Functionality:
The system should aid to:
4.62 Manage location and job changes, promotions, terminations, and retirements.
4.63 Change an employee's full-time or part-time status.
4.64 Streamline employee administration processes using workflow.
4.65 Receive reminders to change or re-evaluate employee status.
4,66 Drill down, through the entire institute and view or perform transactions on employees
within the reporting chain.
4,67 Enable employees and faculty to manage information about professional education, honours
and awards, licenses and certificates, and professional training.
4.68 Enable faculty members to review, add, update, or delete information about professional
memberships, administrative posts, committees, presentations, significant special projects,
student advising, and teaching responsibilities.
4.69 Enable employees and faculty to review training opportunities and request training
enrolment.
4.70 Enable managers to approve employee-training requests and review the status of training
enrolment approval.
4.71 Find detailed employee information quickly, including for the direct reports of terminated
managers or open positions.
4.72 Review address, phone number, and other personal data.
4.73 Ensure that data changes comply with Institute policies.
Integrated Directory Services:

Kangra at Tanda
Page 100 of 219

4.74 Establish a centralized location for user authentication and security.
4.75 Publish user identity information throughout the enterprise, automating security
administration.
4.76 Create dynamic organizational charts, email distribution lists, locator maps, or custom
reports.
Analysis and Reporting
4.77 The system should provide a robust and user-friendly information access tools that support
multidimensional HR data analysis at institutes management level as well at individual unit
level to facilitate day-to-day HR management and for manpower planning purpose for
recruitment, retention and succession strategies.
4.78 Both standard and ad-hoc querying / reporting functions are required.
5. Financial Management Systems: Functional Requirements
A fully integrated, online, real-time Financial Management System (FMS) is being sought by
the institute. The FMS should be designed with the best-practice financial process workflow
in a education environment, capable of supporting the best-of-breed functionalities and
common financial operation practices and come with integrated modules for general ledger,
budgetary management and control, accounts receivable, accounts payable, purchasing and
receiving, cash flow management and fixed asset management, etc.
It is expected that the FMS can be part of a seamless and scalable ERP (Enterprise Resources
Planning) platform that can be fully integrated with such systems/modules as the Human
Resources, Student Information System, and so on, or can operate as a standalone system
with easy integration/interface capabilities with other external systems.
The major expected functions of the FMS are as follows:
General Ledger
5.1 A robust, multi-campus, multi-currency, multi-book and multi-period general ledger engine.
5.2 A flexible structure for chart of accounts with:
Ability to define / add / remove accounting segments for varying accounting needs.
Definable grouping of accounts in the form of family trees (flexible parent-child
relationships) or equivalent.
Ability to associate and group accounts into a variety of categories for reporting /
extraction / analysis and budgetary control.
5.3 Support for activity-based costing.
5.4 Real time preparation, validation, and posting of a variety of accounting and budgetary
transactions while maintaining best practice accounting control.
5.5 Provision of standard, and ability to support ad hoc, financial reporting.
5.6 Best practice month end and year end processing capabilities.
5.7 Strong integration with, and serving as central financial repository of, all other financial
related modules such as budgetary management, payable, receivable, payroll, funds
accounting, student billing, etc.
5.8 Recurring journal functions.
5.9 Consolidation and inter-business unit accounts handling.
Receivables
In general, the receivable system should be able to
5.10 Record and track incomes / receivables from various sources.

Kangra at Tanda
Page 101 of 219

5.11 Access charges and generate billing, reminders, etc.
5.12 Manage and project income / cash flows.
5.13 Handle various forms of payments.
Student billing is an integral component of the receivable system. Its requirements are
discussed separately in the section on Student Accounting.
Payables and Payment
5.14 Identification of payees (vendors, staff, students, ad hoc / one-time payees, etc.) and
associated information for validation and pay processing, drawing as necessary from other
systems such as human resources, student, purchasing).
5.15 Capture of various forms of demands for payment (e.g. invoices from vendors, claims for
reimbursement).
5.16 Automatic verification and matching of invoices against required purchase orders and goods
received.
5.17 Setup and maintenance of schedules of payments for payables of recurrent nature and auto
generation of such payments against pre-definable dates.
5.18 Generation of payments and corresponding financial transactions (including the realization of
commitments as actual expenses).
5.19 Automatic period-end accrual accounting.
5.20 On-line access to status / progress of payable / payment processing with a variety of
selection criteria.
5.21 Strong integration with general ledger and other financial modules.
Student Accounting
5.22 Debit note preparation for students, with ability to:
Flexible definition of charge types (e.g. tuition, residence, caution money, mess fees,
hostel fees, etc.) and related accounts and corresponding entries.
Contribution amounts / percentage.
Personalized non-standard charge details.
Incorporate offsets from scholarships / studentships / financial aids, and government
grants / loans.
5.23 Support requests for deferred payment, with ability to specify a schedule of due dates and
generating corresponding debit notes accordingly.
5.24 Payment / Receipt support, with:
Interface with bank services for various forms of payments / receipts (ATM, PPS,
electronic transfers, direct deposits, etc.).
Auto-matching of payment receipts against charges.
5.25 Interface with financial systems to support the accounting of receivables and receipts /
payments (e.g. scholarships).
5.26 Support for consolidated student accounts:
To include all charges irrespective of debit note issuing department and all payments
Provide statements in electronic/hardcopy forms
5.27 View of statement and debit note details by all authorized persons.
Research Project Grants / Funds Accounting
5.28 Multi-year project accounting data, with options to define data presentation, e.g. on

Kangra at Tanda
Page 102 of 219

aggregate life-to-date or year-by-year basis.
5.29 Strong integration with the General Ledger and other financial related modules
5.30 Research project contract administration front-end supporting various standard types of
project: industrial, commercial and governmental.
6. Supply Chain Management - Purchase and Stores requirements
The aim of the integrated purchasing and procurement system is to facilitate the Institute to
acquire goods and services in the most cost effective manner consistent with procedural
propriety.
The Procurement System should incorporate supplier information, issue of purchase orders,
goods receiving and damage claims. It should interface with RFQ / purchase requests, funding
availability / approval, inventory control, settlement of payment and disposal.
Supplier Information Support
6.1 Capturing of supplier information including contact, product specialty, classification, etc.
6.2 Searching by name, type, and product / commodity to facilitate procurement activities.
6.3 Where applicable and preferable, linking with electronic catalogues published by vendors.
6.4 Support for user-oriented suppliers assessment and evaluation and to feed such results as
required to the procurement process.
6.5 Interface with quotation / tendering and purchasing processes for supplier activity history.
6.6 Facilitate payment processing.
Purchase Order
6.7 Facilities to support the processing of purchase orders that are:
Pre-generated from the quotation / tendering module.
Entered directly by procurement officers.
Created by authorized departmental staff, where permitted by tendering regulations.
6.8 Handling of term contracts.
6.9 Support for multi-currency (with extended decimal places), discount computation, authority
and approval verification.
6.10 Ability to specify various payment terms.
6.11 Order tracking and automated expediting facilities.
6.12 Interfacing with financial systems for budgetary commitments.
6.13 Maintain an order register that could be accessed for information by authorized users via a
variety of criteria.
Procurement of Consumables
6.14 The system should facilitate generation of Requisitions for purchase of consumables.
6.15 Ability to configure approval workflows based on appropriate limits to be automatically
routed to the Purchase Committee.
6.16 Purchase Orders have to be automatically sent to the vendors maintained in the system
based on approved rate contracts.
6.17 System should facilitate receipt of consumables by the stores department.
6.18 The system should facilitate the user departments to raise necessary indents for the
consumables items as required by them.
6.19 The system should facilitate the maintenance of stock of consumables.

Kangra at Tanda
Page 103 of 219

6.20 The system should facilitate ABC analysis of consumables.
6.21 System should facilitate the preparation of necessary budgets for the consumables.
6.22 System should facilitate necessary reports to analyse the trend of consumption of
consumables.
Procurement of Capital Goods
6.23 System should have the ability to generate a Capital Acquisition form for purchase of capital
items.
6.24 The Capital Acquisition form should be subject to due approvals from the Head of
Departments.
6.25 Ability to invite quotations from various vendors.
6.26 System should facilitate quotation comparisons and analysis to help decide on the lowest
bidder.
6.27 Ability to generate a Purchase Order for capital Items.
6.28 Ability to configure approval workflows based on appropriate limits.
6.29 The system should automatically route the information to the Purchase Committee.
6.30 System should facilitate the delivery of the Capital Items directly to the user departments.
6.31 Ability to receive the Capital Items by the user department that has requisitioned the item.
6.32 The System should support the maintenance of the Daily Stock Register, which details the
capital items owned by the institute.
6.33 The System should have the facility to automatically update the Fixed Asset records
maintained by the financial department to facilitate timely capitalization.
6.34 System should provide necessary tools to generate appropriate reports as required by the
Head of Departments, top Management, Directors etc.
6.35 System should facilitate classification of Assets based on the requirements of various user
groups.
6.36 System should have the facility to capture details of assets owned by individuals.
6.37 In case of assets used by various projects, the details of the project have to be captured as a
part of the asset information and vice versa.
6.38 Systems should facilitate transfer of assets between departments.
6.39 In case of imported capital items e.g. Computers, system should facilitate various payment
methods like Letters of Credit, Wire Transfers etc.
6.40 The asset information should form the basis for the Manager Utilities to carry out effective
maintenance of the assets.
6.41 The system should facilitate maintenance of insurance related details of the asset and
prompt for premium payments as and when due. It should have the capability to disclose
warranty related information to the manager utilities at the time of releasing an order for
annual maintenance of assets.
7. File
7.1 Defined key fields which can be changed for every file template and Unique File Numbering
7.2 Unique file numbering
7.3 Attachment upload into file

Kangra at Tanda
Page 104 of 219

7.4 Numbered documents within file
7.5 Attachment upload into file, Document versioning within a file and Numbered documents
within file
7.6 Logical foldering for attachments
7.7 Save File as a Draft
7.8 Graphical view of file status and the level where the file is located
7.9 Attach the Incoming post (Daak) to a file
7.10 Attach the file to a file
7.11 Ability to put a file 'on hold'
7.12 A digital file cabinet to store files
7.13 Ability to re-submit the file to in-tray from the file cabinet on a specified date
7.14 Print File description and noting with private noting
7.15 Print File cover page and workflow
7.16 Print File description and noting without private noting
7.17 File sent items
7.18 Creation of different workflow levels for each file
7.19 Institute calendar is available while assigning the processing days in the workflow
8. WorkFlow
8.1 Association of predefined sequential / parallel workflow to the file
8.2 Insertion of ad-hoc workflow while file is in process
8.3 Assigning a substitute for a period when approver is not available
8.4 Approve (send) the file to next approver
8.5 Allow the file initiator / Creator to change the existing workflow (Or) create a new workflow
8.6 Assigning a specific activity to approver in the workflow
9. Noting
9.1 Records approvers observation, review, approval and feedback
9.2 Generation sequentially Noting numbering
9.3 Note summary to view all notings together
9.4 Private noting
9.5 Provided the exist to write a BADI for digital signature while post the noting
10. Daak and Correspondences
10.1 Create dispatch item for scanned documents, email and notification from internal SAP user
10.2 Additional attributes are given in Daak and customer can configure with their own
requirements
10.3 Attach the Incoming post to a file
10.4 Send Incoming post for review
10.5 Attach documents to Incoming post

Kangra at Tanda
Page 105 of 219

10.6 Post Comments(Noting) in the incoming post and track
10.7 Automatic Unique Daak numbering for Daak
10.8 Configuartion is provoided to have the reference numbering in Daak
10.9 Daak can be send to more than one user
10.10 Graphical representation of the Status and location of the Incoming post
10.11 Reason for the Daak, review comments and feedback can be given in the Daak
10.12 Create correspondence through electronic media to internal OR external stake-holders
10.13 Attach documents to correspondence
10.14 Reply and Forward a correspondence
10.15 Attach the correspondence to a file
10.16 Integrated correspondence inbox for external emails and internal correspondence. User can
receive the internal and external mails and Sent Item, store all the mails (correspondence)
sent, subject, message content, receipts (can be internal and external) and attachments.
5.13 COLLABORATION SUITE
b. Installation:
S No Roles Number of Users
1.

2.
Faculty, Staff and other
Executives
Students
400

1,200
The Backend Server of the Solution should necessarily work on Linux OS.
1.

Messaging Server
Messaging Server must be high-performance, highly secure messaging platform. The
proposed system should have following features for messaging:
1.1 Backend Messaging server should be work on INTEL / AMD based hardware
1.2 Email and message management

Kangra at Tanda
Page 106 of 219

1.3 Standard Webmail features (compose, reply, forward, delete)
1.4 Webmail Spellchecker. Spell check should not depend on the browser spell check capability
and work on most browser versions IE 8, Netscape, Firefox, Chrome etc.
1.5 Messaging filtering
1.6 Vacation or out-of-office messages
1.7 Webmail Proxy
1.8 HTML editing in Webmail
1.9 Migration Tools
1.10 Encrypted Secure Messaging
1.11 Foundation for Unified and Mobile communications ("push" email) for faculty members
1.12 Open Adoption for Internet Standards
1.13 Proven, High Performance MTA
1.14 Universal Access Message Store
1.15 Centralized Administration
1.16 Flexible Delegated Administration
1.17 Seamless Integration with LDAP
1.18 Domain Provisioning
1.19 Anti-Spam controls
1.20 High Availability Support
1.21 Message Store Utilities
1.22 Monitoring tools, both internal and via SNMP support
1.23 Support for archiving and journaling for faculty members
1.24 Indexing and Search Service (for real-time indexing and search of email content, including
attachments)
1.25 Quota Management in messaging server.
Message quotas are required to limit the number of messages stored in a user's
mailbox.
by disk space.
1.26 Messaging Server shall allow to control the following features that define how the system
responds to a quota violation:
Quota notification sends users a warning message when they have reached a disk quota
threshold.
Quota enforcement halts delivery of messages into the message store once the quota is
exceeded, or it allows message delivery even if the quota is exceeded.
1.27 The software should be able to allow configuration of storage volumes for older messages
Out of the Box with no additional use of any third party application. To manage your email
storage resources i.e. Messages and attachments are moved from a primary volume to the
current secondary volume based on the age of the message. The messages are still
accessible.
2. Calendar Server
System Calendar Server must facilitates personal calendaring and team collaboration by
enabling users to manage and coordinate appointments, events, tasks, and resources. End

Kangra at Tanda
Page 107 of 219

users should be able to access their personal, public, or group calendars anytime, anywhere
from any Web-enabled device. The Calendar Server shall provide major features mentioned
below:
2.1 Support for multiple calendars
Public or shared; personal or private
Multiple owners per calendar
Event calendars - corporate, personal and others
2.2 Resource scheduling
Conference rooms, overhead projectors and other resources can be managed
2.3 Group scheduling
Create an event and invite others, including e-mail invitations
Create and invite personal groups to events
Free / busy search on multiple calendars
First available free time
LDAP Group support (Can invite LDAP group to meetings)
2.4 Text search for events and tasks
2.5 Attachment support
2.6 Publish calendars
Export calendar data in iCalendar (iCAL) or XML formats
2.7 Accept all / decline all options
2.8 Information sharing via embedded HTML in events
2.9 Web-based client
2.10 Integration with corporate directory
2.11 Private events and tasks in user calendars to enable privacy and confidentiality
2.12 Automatic e-mail notifications for invitations and localized time zone to enhance efficiency
and productivity.
2.13 Support for scalable and distributed calendar deployments based on LDAP lookup.
2.14 Synchronization with multiple offline devices and applications
2.15 Cumulative search and invitation capability.
3. Instant Messaging
Instant Messaging shall provide a standards-based, real-time communication and
collaboration application as well as a platform for presence-based application development.
It shall delivers presence information and extended, real-time messaging capabilities,
including instant messaging, conferences, alerts, news, polls, and file transfers. Instant
Messaging shall provide the following major features:
3.1 Chat or Instant Messaging for one-to-one or group messaging.
3.2 Availability or Presence to identify users, their availability and location.
3.3 XMPP based architecture to enable interoperability with other IM solutions.
3.4 Alerts to notify users of time sensitive information either in individual messages or as
broadcasts to multiple users
3.5 Contact Lists to create and manage groups of contacts.
3.6 Polling for rapidly surveying a group.

Kangra at Tanda
Page 108 of 219

3.7 Conference Rooms and Moderated Conferences for persistent, pre-established, private
discussions.
3.8 User Configurable Content to allow users to input presence information and to indicate the
mood of a message with fonts, colours or emoticons.
3.9 User access controls for users to control over who can "see" and communicate with them.
3.10 Message archiving for keyword search and retrieval of message transcripts. Messages can be
archived to the email store or to the Instant Messaging Server. The native search mechanisms
of either solution can be leveraged. Archiving provides institutions in the financial and
healthcare industry the tools to comply with industry regulations.
3.11 Secure remote access for access to instant messaging and presence services from any
browser inside or outside a corporate firewall.
3.12 Ease of installation and administration to allow for both rapid deployment and lower total
cost of ownership.
3.13 Simple server-to-server configuration to facilitate the rapid deployment of distributed servers
across and organization's data centres.
3.14 Support for scalable and distributed deployments utilizing server pooling so that multiple IM
servers can be pooled together to serve a single IM domain.
3.15 Provides an XMPP to HTTP gateway for traversing firewalls or communicating to mobile
clients.
3.16 Logging for storage of chat and conference transcripts on the server.
3.17 Auditing of message transcripts is possible through the message archiving feature.
4. Webmail Client
Solution must provide AJAX-powered Web 2.0 user interface that provides the power and
look and feel of a desktop client but within a Web browser. Drag and drop, drag and resize,
address auto-completion, contextual menus, and more are required. Web interface shall
integrates mail, calendar and address book into an intuitive, highly integrated, highly
extensible interface capable of integrating web services into rich mashups to create new
services.
Webmail shall provide a rich client experience inside a Web browser that integrates mail,
calendar and contacts into a unified communications interface. Webmail shall be AJAX Web
client that is customizable. Web Client should provide following major features:
4.1 Secure email with spam management
4.2 Encrypted email using existing or a third party PKI Infrastructure
4.3 Efficient organization of email
4.4 Return receipts for read email
4.5 Attachment (not email) search and viewing
4.6 Attachment filtering
4.7 Multiple calendars
4.8 Delegation of calendars
4.9 Drag and drop email messages and calendar events
4.10 Powerful search of email content
4.11 Common address book
4.12 Auto-completion from personal and corporate address books

Kangra at Tanda
Page 109 of 219

5. Indexing and Search Service
Indexing and Search Service is required to provides a server-side general-purpose indexing
and search capability. With server-side indexing, email does not need to be copied to the
client system for indexing, resulting in lower bandwidth costs. Server-side functionality shall
enables mobile and Web-based clients to take advantage of the indexing service which exists
in the cloud. Following features are needed:
5.1 Indexing:
Rapid Indexing of Existing Email: Email messages in a user's mailbox needs to be
indexed.
Real-time Indexing: As email messages are received, sent, and moved to various folders,
the index is to be updated in real-time.
5.2 Search:
Attachment Search: Users should be able search the body of attachments for keywords
or phrases. Attachments should be in a variety of formats such as PDF; Microsoft Word,
Excel, PowerPoint, and Visio; StarOffice/Open Office; HTML; and more.
Body Search: Users should be able search the body of a message for any relevant
content. With Indexing and Search Service, body search includes search of supported
attachment types as well as the plain text body of a message.
Email messages indexed in real-time
Should provide support for the following document formats:
PDF
Open Office
Microsoft Word, Excel, PowerPoint and Visio (except Office 2007 format)
JPEG (EXIF metadata within is indexed)
HTML, XML and plain text
vCard
6. Security Handling
Solution should offer single sign-on, access control, policy enforcement, identity
management, secure SSL connections and secure remote access. Following features need to
be supported:
6.1 Messaging Server must provide secure communications through a variety of techniques such
as TLS, S/MIME, and Certificates.
6.2 The Messaging Server should offer secure connections for client and administrative sessions
through its Secure Sockets Layer (SSL) and Transport Layer Security (TLS) support. This
enables all communication between clients and servers shall need to take place inside an
encrypted session.
6.3 Messaging Server should support Secure / Multipurpose Internet Mail Extensions (S/MIME).
Webmail users who are set up to use S/MIME can exchange signed or encrypted messages.
7. Solution Administration
System should provide Delegated Administrator utility for provisioning and administrating
users. Administrative tool must have support for command line as well as a graphical user
interface for administering and provisioning users through a Web interface.
Suite shall be built on a common directory and identity management infrastructure to
provide a common interface for user administration, authentication, provisioning, and access
policy for customers.
Delegated Administrator should perform the following functions:
7.1 Create, modify, and delete users
7.2 Create, modify, and delete calendar resources such as conference rooms

Kangra at Tanda
Page 110 of 219

7.3 Create, modify, and delete user groups
7.4 Create, modify, and delete calendar groups
7.5 Manage service packages that define the type of service applied to a user
7.6 Delegated Administrator should be able to provision the directory to support Messaging
Server and Calendar Server.
7.7 Reporting:
Messaging Server shall allow the administrator to configure various logging options
depending on the need. The level, or priority, of logging defines how detailed, or verbose, the
logging activity is to be. System should generates a report to lists defined quotas and limits,
and provides information on quota usage. Following reports are required:
number of domains
number of users
disk quota setting
size used
% used
message quota setting
number of messages
% used
user name
7.8 Utility to periodically check the server state, disk space, service response times and, if
specified, it can issue alarms in the form of email messages to the postmaster. Some such
stored reports that need to be supported:
disk space availability
server response time in seconds
largest msg
last uid (to access)
last append (modification)
oldest message
oldest uid (to access)
quota used
7.9 The server shall also be able to track statistics on http, pop & imap connections, server disk
space utilization, each message routed through, rejected msg size (bytes).
7.10 The Messaging Server must provide utilities for backing up messaging and calendar data.
These utilities shall support backing up individual accounts or the entire database.
5.14 PICTURE ARCHIVAL & COMMUNICATION SYSTEM AND RADIOLOGY INFORMATION SYSTEM
b. Installation:

Kangra at Tanda
Page 111 of 219

1.
2.
3.
4.
5.
6.
7.
Doctors
UG students
PG students
Nurses
Finance Executives
Pharmacy Staff
Laboratories / Technicians
120
1,200
1,80
400
10
20
50
1. Web Based Image Distribution
1.1 Should support the following standard tools:
Automatic, adaptive display sizing
Complete image manipulation (W/L, Zoom/Pan, Flip/Rotate, Cine, Image Filters, etc.)
True-resolution magnifying glass
Anatomical 3D cross-reference
Slab scrolling
Global stack
True size viewing
Annotations and measurements
1.2 Should support the following standard tools:
Automatic, adaptive display sizing
Complete image manipulation (W/L, Zoom/Pan, Flip/Rotate, Cine, Image Filters, etc.)
True-resolution magnifying glass
Anatomical 3D cross-reference
Slab scrolling
Global stack
True size viewing
Annotations and measurements
Intrinsic support for the following advanced 3D tools:
MIP / MPR
OB measurements
Spine labels
PET / CT fusion
3D Volume Rendering with embedded Voxar with
Live Image captures
Orthogonal, oblique, double-oblique MPR rendering
MIP, AveIP, MinIP, and color volume slabs
2D review and compare
Color, MIP, and grayscale volume rendering
Shaded surface display
Fly-through navigation
Targeted color volume review
3D segmentation and volume measurement
Sculpting and automatic 3D bone removal

Kangra at Tanda
Page 112 of 219

MPR shape selection
Vessel analysis for CTA and MRA studies
Intrinsic Integration with Terrarecon (To be purchased separately)
Intrinsic Integration with Traumacad Ortho tools (To be purchased separately)
Intrinsic Integration with Advanced Server Based Post Processing Engine
Intrinsic Integration with PeerVue
1.3 Workflow enhancement tools covering
Flexible, Individual, User-Defined on the Fly Worklists
Drag and Drop Hanging Protocols
Key Image Viewer
Image Navigation
Integrated to most dictation systems that can accept communication on a TCP/IP port,
such as PowerScribe, Provox, Winscribe and MedQ.
CD import
DICOM send
DICOM print
Assign to worklist
Grant temporary access
Data is centrally managed in one
Study status changes
Exam notes,
Presentation states,
Key image notes and preliminary reports,
Exam locking capabilities to prevent double reading of exams.
1.4 Should support a variety of monitor configurations up to a total of six monitors:
1 Color Landscape
2 Color Landscape
3 Color Landscape (same res)
3 Color Landscape (1 low res + 2 high res)
1 Color Landscape + 2 Color Portrait
1 Color Landscape + 2 Grayscale Portrait
1 Color Landscape + 2 Color Portrait + 2 Grayscale Portrait
4 Color Landscape (2 low res + 2 high res)
4 Color Portrait
1 Color Landscape + 3 Grayscale
1.5 Should support for display of the following DICOM Image Types:
CR Image
Digital X-Ray Image (Presentation)
Digital Mammography Image (Presentation)
Digital Intra-oral Image (Presentation)
CT Image
US Multi-frame Image (Retired)
US Multi-frame Image
MR Image
US Image (Retired)
US Image
Secondary Capture Image
Multi-Frame Grayscale Byte

Kangra at Tanda
Page 113 of 219

Secondary Capture Image
Multi-Frame True Color Secondary
Capture Image
Grayscale Softcopy Presentation State
X-Ray Angiographic Image
X-Ray Radiofluoroscopic Image
X-Ray Angiographic Bi-Plane Image (Retired)
Nuclear Medicine Image
VL Endoscopic Image
VL Microscopic Image
VL Slide-Coordinates Microscopic Image
VL Photographic Image
Positron Emission Tomography Image
RT Image Display
1.6 Web-based viewer that can provide easy, quick access to exams and reports on PACS from
virtually any location with an Internet connection and a qualified browser
1.7 Adaptive Streaming:
Should maximize the transmission of both large and small datasets across a variety of network
bandwidths. This helps to maximize user productivity and minimize any issues with
manipulating large datasets across smaller network bandwidths.
1.8 Should be FDA approved for diagnostic viewer
Support intelligent hanging protocols with smart reading protocols with the ability self-
learn the
Advanced applications should be embedded in the viewer ( not new window launch
preferred)
Supports the following specialty tools :
MIP/MPR
PET/CT
Vessel analysis
Oncology workflow
Automated registration
Bone removal
OB measurements
Spine labels
PET/CT fusion
Optional third-party integrations for orthopaedic templating
1.9 2D Features
User selection of layouts
Grayscale Softcopy Presentation State (GSPS)
Multitasking on mobile devices
Cine (including cardiology)
Pan
Zoom
Window width/level
W/L (window/level) presets and their relationship between the web viewing stations and
mobile clients
Orientation including image flip (horizontal/vertical) and image rotate
(clockwise/counterclockwise)
Text annotation
Freehand annotation
Linear measurement
Angle measurement
Orientation labels

Kangra at Tanda
Page 114 of 219

Reset To original view settings
DICOM Secondary Capture (screenshot)
1.10 3D Features
MIP
MPR
Volume rendering
GPU/server-side volume rendering
2. Advanced Clinical Applications
2.1 3D visualization capabilities throughout the enterprise and at any remote reading location to
convert virtually any PC1 or PACS2 to a high-end 3D post processing station.
2.2 Pre-processing automates processing tasks in the background, thus increasing productivity.
Tasks such as bone removal, segmentation of cardiac structures, colon, etc. are performed
automatically upon DICOM exam transfers to AW Server based on rules. The rules can be
configured based on DICOM series description field. Instantly makes interactive 3D post
processed results available on any PC.
2.3 Seamless integration at the front and back ends with any PACS
2.4 Three different flavours 8000, 16,000 and 32,000 slices can be concurrently processed.
2.5 Unique Smart compression technology automatically displays full fidelity static images even
when compression is turned on for increased interactivity. This allows for diagnostic reads on
full fidelity images even at low bandwidth.
2.6 Enterprise directory integration for single sign on user authentication.
2.7 Standalone user management system in case of no integration with enterprise directory
2.8 Web based administration interface for configuration, diagnostics, usage and day to day
management of server
2.9 Enterprise Audit trails capturing user access to patient data using industry standard protocols:
IHE ATNA compliant audit messages (RFC3881), TCP, Bsd Syslog, Reliable Syslog (Cooked
profile Experimental) transport to the 3rd party audit repositories. Local storage with log
rotation (size+number of rotation)
2.10 Stateful firewall on the server to track network connections and improved detection of
malicious intrusion attempts
2.11 Built in No Execute CPU security technology to prevent malicious software attacks
2.12 Ability to allow thin client access over internet by using either http port (80) or https port
(443)21
2.13 Option to roll passwords for remote service
2.14 Group privileges to allow full access to exams or to enforce mandatory exam search by
configurable criteria
2.15 Ability to open up to 3 simultaneous application sessions per user and instantly switch
between these sessions
2.16 Ability to save the state of post processing any time and restore it from any client, allowing
multiple radiologists or technologists to contribute to post processing results
2.17 The compression level is selected by the user on the client application. The server supports
the following compression levels:
Lossless
Lossy 15:1 (compression ratio is 15:1)

Kangra at Tanda
Page 115 of 219

2.18 Advanced Applications Supported across Cardiology, Vascular, Neurology and Oncology across
modalities such as CT, MR, PET, Interventional and RT including the following:
Advantage 4D
AdvantageSim MD
AngioCARD 1.0
AngioViz
Autobone & VesselIQ Xpress CT
BrainView
BrainWave
CADstream
CardEP
CardIQ Function Xpress
CardIQ Fusion
CardIQ Physio
CardIQ Xpress Reveal
Colon VCAR EC
Cortex ID
CT Perfusion 4D
Dentascan
Dynamic Shuttle
Dynamic VUE
FlightPlan for Liver
Flow Analysis 4.0
GSI Viewer
Innova 3D and Innova CT
Innova EPVision
Innova TrackVision
Innova Vision
Integrated Registration
Left Ventricle Analysis
Lung VCAR
Motion VUE
MR VesselIQ Xpress
OncoQuant
PET VCAR
READY View
ReportCard 4.0
Smartscore 4.0
Starmap 4.0
Stenosis Analysis
Thoracic VCAR
VesselIQ Xpress X-Ray
3. Radiology Workstation
3.1 The user can configure his/her user interface. Configurations are specific to a users log-in.
Palettes, image display and tools can all be configured to adapt to each users preferred work
style
3.2 The Radiology WS software allows creation of Default Display Protocols (DDPs) so that each
user can view specific types of exams exactly as desired without any manual configuration.
DDPs allow users to configure monitor and region layout, historical exam display, W/L, flip,
rotate, zoom, linking, and cross reference to automatically apply upon opening of exams.
3.3 The Radiology WS software application may be downloaded to any PC that meets the
minimum requirements (Windows XP) on the hospital network from the Portal. The RA1000

Kangra at Tanda
Page 116 of 219

application automatically checks for newer versions of software installed on the system.
3.4 The remote workstation feature enhances the usability of the software in remote locations
served by low-bandwidth connections. The remote workstation allows images to be pushed to
that workstation by any user who has privileges to do so. The image data is cached on the
hard drive of the remote RA1000 software, but only the image data is cached. Database data,
such as reports, exam status and image presentation (W/L, annotations, etc.) are stored in the
main database.
3.5 The WS software is worklist-driven and users can define any number of worklist filters based
on particular workflow needs. Worklists can be filtered using various attributes, including:
Exam status (e.g., unread)
Modality (CT, MR, CR, etc.)
Patient location (ICU, ED, etc.)
Referring physician
Interpreting radiologist
Exam type (e.g., neuro, body)
Exam date and time
3.6 The WS software offers a wide variety of basic and advanced image manipulation tools. The
user can configure quick access tools based on modality and can configure each of the three
buttons of the mouse as a default tool. The list of image manipulation tools includes:
Pointer/selector
Window/level
Image orientation
Measurement
Manual cine
Invert grayscale
Magnification glass
Continuous zoom
Pan
Annotation
Angle measurement
Significant image
Pixel lens
Cross reference
Region of interest (ROI)
Lock mouse for cine
Image mask
Image information
Drag and drop
Spine labelling
3.7 Image overlay information can be configured by modality and user can specify both essential
and non-essential overlays. Non-essential overlay information can be toggled on and off by
the user. Overlay information can be pulled from either the database (populated by the RIS) or
the image DICOM header.
3.8 Individual or series of images can be identified as significant images to allow quick access to
only those images with significant pathology as identified by the reading radiologist. All
images with annotations are identified as significant by default.
3.9 The WS software supports multiple monitor configurations, including two high-resolution
grayscale or color monitors and a third lower-resolution color monitor. Mixed monitor is ideal
for displaying the WS worklist palettes and third-party applications, as well as color diagnostic
images such as ultrasound. The third monitor may also be used with DDPs.
3.10 Users can export images to a specified directory using three common image formats: JPEG,
PNG, and TIFF. Images may optionally include overlay information, image annotations and

Kangra at Tanda
Page 117 of 219

statistics.
3.11 Users can export images to a specified directory using three common image formats: JPEG,
PNG, and TIFF. Images may optionally include overlay information, image annotations and
statistics.
3.12 Can import DICOM images from any DICOM-compliant storage device.
3.13 User to select multiple Image Display Series that are all in the Stack mode, and synchronize
them so that all the series show the same relative anatomical location.
3.14 Users can create teaching folders with lists of exams for quick and easy access. Exams can
easily be added to or removed from folders.
3.15 Conference display protocol allows the user to save a presentation layout for later access. The
presentation layout of multiple exam types is preserved so the user can return to that layout
with one mouse click.
3.16 PET/CT image viewing is improved by allowing the users to quickly identify a specific
anatomical location across same-study PET/CT images
3.17 Provides the ability for users to bookmark a particular state to quickly return to at a later
time
3.18 Ability to create, save and hide notes for a particular exam. Site also has the ability to create
canned exam notes for commonly used notes
3.19 Provides enhanced navigation mechanisms by providing right mouse context menus to drive
exam level actions such as save, dictate, print, show report, etc.
3.20 Display thumbnail view of the center image of a series as a pictorial representation of the
series in the series hot zone drop-down.
3.21 Provides users with an efficient mechanism to browse Significant images.
3.22 This feature provides the ability to link two series of images having the same frame of
reference. It enhances workflow for multi-modality studies such as PET/CT. It also creates easy
link navigation with any two series having the same frame of reference.
3.23 This is a tool that captures the minimum and maximum pixel values in a specific area of the
image to calculate the optimal window level. This easy-to-use feature entails drawing a
rectangle on an image and the window level calculated from that area is applied to the entire
image.
3.24 This allows a user to save more than one viewing state on the Workstation. The system will
allow a user to save 1-n presentation states from the RA1000 and it will also allow the display
of images that may have had a presentation state saved.
3.25 Some facilities have a need to mark certain patients as confidential, which allows only specific
system users to access their data. All patient data is hidden from unauthorized users. A patient
can be marked / unmarked as confidential as required.
3.26 Exam Manager functions, such as patient and exam merge, are supported.
3.27 This solution provides enhanced capabilities to assist in handling high-priority exams in a
timely fashion.
3.28 This solution allows a user to configure the RA1000 Workstation to respond to various voice
commands for your most frequently used mouse or keyboard commands.
3.29 This feature provides the capability for a user to attach a sound clip to a particular exam file.
3.30 Enhanced bookmarks and CDP provide the ability to save what you see
3.31 Allow users to automatically synchronize image sizes from different scanners, thus saving
radiologists time in reading multi-scanner CT and MR studies.

Kangra at Tanda
Page 118 of 219

3.32 An intuitive GUI-based feature that allows users to assign/un-assign any shortcut key to
various workstation functions, based on personal preference. One-key shortcuts are now also
available.
3.33 Users can now hide, unhide, or hide all individual buttons/icons from the palettes in each of
the Browse/Verify/Dictate modes. The buttons and icons on the title bar can be removed,
relocated, and left- or right-justified.
3.34 When new images are loaded to a currently opened study, the user is notified accordingly and
the series hot zone menu will also refresh
3.35 Indicator on overlays to identify CAD, which means images have been processed through
CAD.
3.36 CAD display can be set up in step protocols
3.37 Users can propagate changes like Window/Level and Quad Zoom over common views or views
with historicals, for Quad Zoom and Window/Level features with Mammo Images
3.38 Seamlessly launch all AW advanced applications from within the Radiology Workstation
Viewer to perform advanced reconstructions (Note: Need Aw Server Specified above to
accomplish the same). Tools include but not restricted to:
Advantage 4D
AdvantageSim MD
AngioCARD 1.0
AngioViz
Autobone & VesselIQ Xpress CT
BrainView
BrainWave
CADstream
CardEP
CardIQ Function Xpress
CardIQ Fusion
CardIQ Physio
CardIQ Xpress Reveal
Colon VCAR EC
Cortex ID
CT Perfusion 4D
Dentascan
Dynamic Shuttle
Dynamic VUE
FlightPlan for Liver
Flow Analysis 4.0
GSI Viewer
Innova 3D and Innova CT
Innova EPVision
Innova TrackVision
Innova Vision
Integrated Registration
Left Ventricle Analysis
Lung VCAR
Motion VUE
MR VesselIQ Xpress
OncoQuant
PET VCAR
READY View
ReportCard 4.0
Smartscore 4.0

Kangra at Tanda
Page 119 of 219

Starmap 4.0
Stenosis Analysis
Thoracic VCAR
VesselIQ Xpress X-Ray
3.40 A mammography workflow module to further supplement mammography reading efficiency
with user-configured, multi-step display protocols. These display protocols allow the user to
lay out the various mammography image view positions and literalities, and the available
historical images, in a way that best meets the individual users needs. The user can easily step
through the multi-phased reading protocol.
Customizable, dynamic display protocols
CAD image display support (DICOM Overlay)
Linked image manipulation tools
(e.g., mag glass, pan, zoom, W/L)
3.41 Support for the following IHE Profiles should be supported:
Consistent Presentation of Images (CPI). This IHE profile defines equivalent viewing
characteristics of the images to provide equivalent views of exams if they are viewed on
modality, PACS, or third-party workstations or printed to compliant devices.
Key Image Note (KIN). This IHE profile allows a user to create a note and attach it to a
specific image in an exam. RA1000 will allow the creation of this note, and/or display if it
was created from another source such as a modality.
Presentation of Grouped Procedures (PGP). This IHE profile allows a PACS to correctly
split a scan performed at a CT scanner into specific orders (exam splitting). Radiology WS
also provides the functionality to split the exam at the WS, should a modality not support
PGP.
Consistent Time (CT). This IHE profile provides time synchronization across applications in
PACS
3.42 The WS software should offer Open Desktop solutions with the following third-party
applications:
Cerner Radnet (Millennium)
Talkstation Voice Recognition
PowerScribe Voice Recognition
GE Healthcare Xeleris
3.43 Support for a plethora of image types (DICOM) including:
CR Image Storage
Digital X-Ray Image (Presentation) Storage
Digital X-Ray Image (Process) Storage
DX Mammography Image (Presentation) Storage
DX Mammography Image (Process) Storage
DX Intra-oral Image (Presentation) Storage
DX Intra-oral Image (Process) Storage
CT Image Storage
Enhanced CT Image Storage
US Multi-frame Image Storage (Retired)
US Multi-frame Image Storage
MR Image Storage
Enhanced MR Image Storage
MR Spectroscopy Storage
NM Image Storage (Retired)
US Image Storage (Retired)
US Image Storage
Secondary Capture Image Storage
Multi-Frame Single Bit Secondary Capture Image
Multi-Frame Grayscale Byte Secondary Capture Image

Kangra at Tanda
Page 120 of 219

Multi-Frame Grayscale Word Secondary Capture
Multi-Frame True Color Secondary Capture Image
Standalone Overlay Storage
Standalone Curve Storage
General ECG Waveform Storage
Ambulatory ECG Waveform Storage
Hemodynamic Waveform Storage
Cardiac Electrophysiology Waveform Storage
Basic Voice Audio Waveform Storage
Standalone Modality LUT Storage
Standalone VOI LUT Storage
Grayscale Softcopy Presentation State Storage
X-Ray Angiographic Image Storage
X-Ray Radiofluoroscopic Image Storage
X-Ray Angiographic Bi-Plane Image Storage (Retired)
Product Data Sheet
Dated Material Subject to Change
Nuclear Medicine Image Storage
Raw Data Storage
VL Image Storage (Retired)
VL Multi-frame Image Storage (Retired)
VL Endoscopic Image Storage
Video Endoscopic Image Storage
VL Microscopic Image Storage
Video Microscopic Image Storage
VL Slide-Coordinates Microscopic Image Storage
VL Photographic Image Storage
Video Photographic Image Storage
Basic Text SR
Enhanced SR
Comprehensive SR
Mammography CAD SR Storage
Key Object Selection Document
Chest CAD SR
Encapsulated PDF Storage
Positron Emission Tomography Image Storage
Standalone PET Curve Storage (Retired)
RT Image Storage
RT Dose Storage
RT Structure Set Storage
RT Beams Treatment Record Storage
RT Plan Storage
RT Brachy Treatment Record Storage
RT Treatment Summary Record Storage
4. Image Storage and Archival
4.1 A Single Solution for all DICOM and non-DICOM Objects
Radiology images
Cardiology images
Pathology images
XDS documents
Other DICOM objects such as structured reports, presentation states, key image notes and
visible light images
4.2 Access to the patients longitudinal image records through the optional Patient Information
Viewer (PIV). PIV 1 can image-enable enterprise systems such as an EMR or department

Kangra at Tanda
Page 121 of 219

systems such as a radiology PACS or cardiology PACS. PIV can also provide access to patients
DICOM and non-DICOM image objects across departments, facilities or metropolitan-wide to
referring physicians or other clinicians who dont have access to an EMR.
4.3 Open Architecture compliant with major standards
DICOM
HL-7 v2
HL-7 v2 Structured Reports
XDS
XDS-I
IHE
4.4 Efficiency in usage of storage media through a variety of rule-based policies such as delete,
move and compress, the Enterprise Archive is capable of managing storage.
Clinicians can move, compress, and delete imaging studies where they want, how they want,
and when they want. The Image Life Cycle Management allows administrators to not only set
retention policies, but more effectively manage the image data throughout the technology
lifecycle:
Configure rules for virtual archives or storage libraries
Lossless and Lossy Compression of data (JPEG, JPEG2000)
DICOM tags: Institution Name, Station Name, Department, Modality, Study Description,
Study Age, and Patient Age for a total of 128 different rule combinations
Rules workflow engine for creation, approval and audit of rules
Rules worklist to view studies eligible for movement, compression, deletion
Quarantine features to place affected studies and patients on hold
4.5 VIRTUAL ARCHIVES to allow the creation of departmental archives or the sharing of the
archive between multiple institutions.
4.6 THE BROADVIEW FEATURE to aggregate the departmental archives into a single view. Patient
level query and retrieve will get results from all partitions with one command.
4.7 QUERY SPANNING AND MOVE FORWARDING to make Enterprise Archive the single point of
access to virtual and existing third-party DICOM archives, protecting past investments
4.8 Management Console:
A rich administrator console that can be used to configure the system.
Administrator privileges can be managed at a very granular level.
Usage and performance reports are available on the Console.
The console can be run from any web console with Connection to the server.
4.9 Using its Shadowing feature, EA automatically replicates itself to a second, off-site archive.
This provides full system redundancy superior to only replicating the storage. An added
advantage of this configuration is that the software on the two systems can be upgraded
independently providing minimal disruption to operations.
4.10 Support for a plethora of storage devices fibre channel and network attached storage
solutions. Uses CIFS (Common Internet File System) or NFS (Network File System) protocols to
connect to network attached storage.
Vendor should work closely with EMC, Hitachi Data Systems, HP and Network Appliance
storage systems
Types of Storage Supported:
EMC Centera Storage Solution
SAN Storage Solutions
NAS Storage Solutions
4.11 Multiple storage systems can simultaneously be connected to one Enterprise Archive server.

Kangra at Tanda
Page 122 of 219

4.12 Supports Business continuance and disaster recovery options for added assurance and
security.
High-availability Configuration.
Using its shadowing feature, Archive should automatically replicate itself to a second off-
site archive. This provides full system redundancy, superior to replicating only the
storage. An added advantage of this configuration is that the software on the two
systems can be upgraded independently, providing minimal disruption to operations.
Load Balancing Configuration.
For sites that produce extreme procedure volumes, Archive should provide a load balanced
configuration. Separate dedicated load balancers need to be proposed for PACS. Archive can
deploy up to four application servers to handle loads for single, multi-site, regional or
nationwide configurations.
4.13 ARCHIVE FEATURES :
Should be an Vendor Neutral Archive
Support XDSi
The PACS ARCHIVE should be able to store NON-DICON data set PDF, WORD, JPG, AVI
etc.
Should have the Ability to display the data set stored in the viewer in a grid, time-line
view
5. Image Management System
5.1 Short Term Image and database data management
5.2 System storage and pre-fetching management
5.3 Patient folder creation
5.4 Teaching folder creation
5.5 Worklist creation
5.6 User preferences management
5.7 PACS based reporting capability
5.8 Validated IHE Profiles covering
Scheduled Workflow (SWF)
Access to Radiology Information (ARI)
Patient Information Reconciliation (PIR)
Instance Availability Notification (IAN)
Consistent Time (CT)
Consistent Presentation of Images (CPI)
Presentation of Grouped Procedures (PGP)
5.9 Modular DICOM Acquisition Service (DAS) as the input interface for all DICOM modalities into
the PACS system. This modularity enables both scalability and load balancing high volume
transactions from multiple modalities.
5.10 All standard DICOM service classes such as Store, Query/Retrieve, and Storage Commitment
SCP/SCU (DICOM Storage Class Provider/User) are Supported at the DICOM Acquisition
Service. Thus supporting exam matching, compression and movement to an imaging volume
or Short Term Storage
5.11 Support for Image Volumes or Short Term Storage
Option to have enough Image Volume capacity to keep all exams on line, or exams can
be purged from the Image Volume and retrieved from the Archive when needed.
Support for complex and configurable set of business rules is used to determine which
images are least likely to be needed and those images are purged first when short-term
storage reaches a high watermark.

Kangra at Tanda
Page 123 of 219

Support for a plethora of SAN/NAS devices from HP, EMC and DELL as Image Volumes
Multiple image volumes can be supported ensuring high scalability
5.12 Gateway:
Gateway to provide an HL7 interface between PACS and other information systems in the
hospital, such as Radiology Information systems (RIS), Cardiovascular Information Systems
(CVIS) and Hospital Information Systems (HIS). The Interface accomplishes this translation with
via a configurable mapping engine, thus allowing PACS to fit Seamlessly into the enterprise
messaging environment. In this sense, Gateway is a middleware component in the integration
between HIS/RIS/CVIS and PACS.
Gateway provides an interface to PACS for orders and scheduling information, and update
messages to patient Demographics and orders. With this information, PACS is able to:
Automatically link images with patient and order data
Provide reports to Workstations
Pre-fetch priors from the long-term archive
Gateway is also a DICOM Modality Worklist Provider, greatly reducing data entry
mistakes at the time of image acquisition
5.13
Image Transfer Service (ITS) is used to move Image files between Short Term Storage (STS)
nodes as an example when deployed in 2 remote sites.
5.14 DICOM Print Server (CDPS) allows PACS users to print right from their workstation. The
implementation of IHE Consistent Presentation of Images ensures that the printed images
look the same as at the workstation.
5.15 The PACS Server environment can, optionally, be setup for Image Management Services
redundancy, a feature called Database Replication. This high-availability option helps minimize
the risk from IMS failures. The users that are connected to the IMS are automatically switched
over to the hot-standby IMS server.
5.16 Support for PIX methodology resolves multiple patient identifiers presented to the PACS,
providing a single view for a particular patient record. It internally manages multiple patient
identifiers resulting from orders provided by multiple Information Systems (e.g. multiple RIS
systems or a RIS and CVIS system in a Rad /Card environment) and links them to a Single
patient record.
5.17 The PACS configuration that supports images from multiple departments E.g. Radiology and
Cardiology on the same system while maintaining separation of images using virtual archives ,
separate Imaging Volumes and specialized radiology and cardiology workstations
6. Radiology Information System
6.1 SCHEDULER
The scheduler provides a wide range of functions for an electronic management of patients,
workplaces, devices and staff members
Configurable search for free appointments
Full drag & drop support
Import external appointments from an enterprise scheduler via HL7 SIU
Full support of HL7 order entry management
Order entry validation
Multi-step appointments
Free text appointments
Block/protect appointments against overbooking
Mammo Screening Scheduling
RIS should contain several features dedicated to the advanced Mammo Screening invitation
workflow.
Searching the patient worklist considering age and last mammography date
Batch Scheduling, re-Scheduling

Kangra at Tanda
Page 124 of 219

Automatic printing of invitation letters
Statistics
6.2 PATIENT REGISTRATION
Management of patient, case and request data
Automatic data registration from magnetic cards and barcode readers
Patient- and visit-data registration via interface to a Hospital Information System (HIS)
Electronic Order Entry via HIS-interface or Referral Web Order Module
Trigger CD/DVD burning
Patient arrived management; When a patient enters the radiology department, the
receptionist registers the patients arrival in RIS. The patient-, visit- and procedure-data
can be entered manually or be retrieved from a Hospital Information System (HIS) and
completed in RIS. If an appointment or an electronic order already exists, the procedure
status will simply turn to registered/patient arrived.
In an emergency case, a quick registration can be done with incomplete or even without
patient data. The Emergency Notification Module informs all performing staff members
about the emergency patient.
If RIS is integrated with PACS (Picture Archiving and Communication System), image and
image archive data are administered to provide access to all available information
already when registering.
6.3 EXAM RECORDING
Patient selection from user configurable worklists
Auto-complete of performed procedure steps via DICOM MPPS
Regional billing code generation
Configurable course of Procedures Registration
Assigning patients to conferences
The medical and technical services actually carried out are registered in connection with the
examination. The radiographer will retrieve the patient data from the acquisition work list.
During the registration of medical procedures, all patient related information along with a
description of the procedure is available. If the necessary access rights are granted, data from
previous examinations and related reports are also available.
Procedures Registration means indicating the examination date, the initials of the responsible
radiographer as well as the consumption of film sheets, contrast media and the technical
parameter settings of the modality. Provided input screens are related to the examination
type and can be adapted by the customers according to the specific demands. At the same
time, billing codes belonging to this examination can be specified. The codes are presented
depending on the cost bearer (i.e. the insurance company).
RIS can combine standardized diagnostic questions with procedures and examination
methods. In order to facilitate and standardize the workflow, procedures can be automatically
assigned to diagnostic questions.
6.4 Should allow the user to create rules, based on medical, billing or organizational reasons at
procedure or billing code level, to avoid conflicts between procedures in RIS-i 4.2 Plus. Every
time a procedure will be entered or updated in the system (Scheduler, Registration, Exam
Recording), the conflict rules will be checked. Depending on the configured level of severity,
the user can either proceed after reading an information dialog, proceed after entering a
reason for breaking the rule or be prevented to proceed.
6.5 Enables instant messaging, showing on-line radiologists, administrators and radiographers in a
buddy list. By clicking a person, a message can be sent directly to the desktop of the user.
6.6 An emergency notification module automatically informs all performing staff members about
waiting emergency patients. The emergency patient appears on top of the performing
technologist worklist, red labeled. As soon as the procedure has been performed the reporting
radiologist gets an emergency message with all medical information on top of the screen to
immediately do the reporting.

Kangra at Tanda
Page 125 of 219

6.7 RIS RadCockpit should be an integral reporting solution. To maximize productivity, the RIS,
RadCockpit should integrate with PACS, dictation system, speech recognition and MS word.
The RIS RadCockpit should be the valuable key between diagnosis, administration and patient:
Read all medical information like suspected diagnoses, medical history, reason for exam,
etc.
Synchronized worklist entry selection and image display on the PACS
Direct on demand access to patient history tree.
Dictate the findings
Read scanned Documents
Create the final findings report
Sign off the report electronically
Create and carry out demonstrations
Assign examinations to Teaching Folders
Automatically or manually trigger DVD/CD burning station to burn report and/or images
Print, Fax E-mail reports
The RIS should display patient data simultaneously with the images in PACS. The Radiologist
can bookmark preferred images for referral conferences in the demonstration room, together
with a direct on demand access to historical examinations.
6.8 The integrated dictation system should close the information chain: from exams through
reports to invoicing. The reporting process should become transparent and should keep
abreast of the daily work routine.
Fast availability of dictations on all authorized workstations
Dictations can be easily modified or completed before being transcribed
Dictation transcripts are easily corrected
User-friendly search and sort functions
Possibility to use the Speech Mike with integrated Mouse / Microphone as the main
device to control all applications.
6.9 The speech recognition system embedded into RIS should translate voice into text. What you
say is what you see. The offline recognition mode should allow a transcriptionist to check and
correct the recognized text, whereas the online recognition mode allows the radiologist to
immediately approve the report. In both modes speech recognition helps improving the
report turnaround time.
6.10 Provided that a fax option is installed, the report can be directly sent to the corresponding
addressee with the help of a fax card.
Another option would be to render the report in PDF, RTF or DOC Format and send it to a
defined repository.
6.11 The voice commands should allow to format texts, combine canned text with speech
recognition and navigate through the document. This enables the Radiologist to complete
templates hand free via voice commands. Standardized text blocks can be selected via
command, during the recognition.
6.12 BUSINESS INTELLIGENCE REPORTS
Integrated InfoCockpit for one-click live statistics, providing real-time data about waiting
times, pending procedures and dictations
Standard statistic package as for example the daily journal in MS Excel
The workplace journal and diagnostic statistics are directly retrievable at any time
Criteria for requests are simple and can be modified as required
Results can be documented by printing
Evaluation of the whole database via ODBC. Every user having sufficient privileges should be
able to retrieve statistical results. As many statistical calculations as needed can be
simultaneously run. Most statistical parameters should be freely definable in order to provide
meaningful and prepared data material for scientific evaluations.

Kangra at Tanda
Page 126 of 219

6.13 The system can generate predefined, statistical or accounting- relevant codes and transmits
them to local billing systems via interface.
6.14 MASTER PATIENT INDEX
RIS should support a Master Patient Index (MPI) generated by an MPI-manager in order to
support multi-hospital-installations, where different HIS systems share one RIS-PACS system.
Master Patient Index allows patient identification of different hospital-patient-Ids via a master
patient ID supported by the RIS
6.15 The RIS Plus panel configuration should provide flexible configuration of field position, size or
mandatory fields. Panels, work lists and fields can be customized and labelled.
6.16 The RIS Plus information letter configuration provides flexible configuration of Patient
information printouts, which are configurable by authorized user similar to the management
of report letter layouts.
6.17 HIS INTERFACE
In order to exchange patient and procedure data with a Hospital Information System (HIS), RIS
provides an interface that is easy to use and adaptable to a specific environment. The
provision of procedure data by RIS and their transfer to the HIS can be triggered either
manually or automatically by the system by defined triggering events. The interface to a HIS
system is a bi-directional communication.
Interfaces should support the HL7 version 2.3, 2.4, 2.5 and the HCM standard for SAP HIS
systems.
6.18 RIS Plus provides the functionality of master file synchronization. The data of requesting
physicians and materials will be synchronized between RIS and HIS, based on HL7
MFN.
6.19 Context based front and back end integration with PACS
6.20 Can be configured to supports over 300 concurrent users. RAC Real Application active-active
Clustering for high availability
5.15 HEALTHCARE MANAGEMENT INFORMAIN SYSTEM
b. Installation:
1.
2.
3.
Doctors
UG students
PG students
120
1,200
1,80

Kangra at Tanda
Page 127 of 219

4.
5.
6.
7.
Nurses
Finance Executives
Pharmacy Staff
Laboratories / Technicians
400
10
20
50
1. General
1.1 The system should be web-enabled
1.2 The system will be able to seamlessly handle inbound and outbound HL7 (Bidirectional)
messages from any system that has similar capabilities
1.3 The system should support DICOM standard for image communication
1.4 The system will support ICD-10 and similar kind of catalogue feature.
1.5 The front-end hospital-specific functionalities should have online real-time integration with
the back office finance/Inventory modules. The integration should be built as a part of
product design - no batch updation or interfacing between two separately developed
products.
1.6 The application should have highly secure web interface for doctors and radiologists & secure
application should protect the patient data
1.7 The administration modules in application should be client server based enabling effective
customer interaction at the point of providing care
1.8 The application should have capability to compile reports using inbuilt tools
1.9 The application should be easy to customize and configure workflow engine to customize the
workflows
1.10 The application should have customization editor features (where you can customize the
screen as per the user needs)
1.11 The application should have defined view tool to create and use views for reporting purpose
1.12 The application should have ability to design customized form
1.13 Interface Capability with Medical Equipment
1.14 Integration with Non-Medical Administration application
1.15 Work List approach with auto refresh facility to get updated list of pending works.
1.16 Application should have capability to build user workstation catering to particular users roles
and responsibilities with multiple, flexible views of same information for different purposes.
Single landing page approach for performing all the tasks of an user.
1.17 Hospital process is complex and may vary. Application should provide a tool to design UI and
process to address different situations for same activity, for an example normal admission vs.
emergency admission
1.18 Catalogue-based input for diagnosis, procedures, treatments, drugs etc.
1.19 Workflow based approach for approval need. A workflow wngine should be provided to
design additional workflows if required in a graphical manner.
1.20 Flexible, multiple options to quickly search patients, drugs based on different fields.

Kangra at Tanda
Page 128 of 219

1.21 Hide/Show facility of UI sections to work comfortably in a particular section
1.22 Material Set concept for frequently ordered materials.
1.23 Application should provide a flexible tool to design additional medical documents (layout,
content etc) to store clinical information about patient.
1.24 Centralized patient EMR updated from different sources on real-time basis to reduce
communication need, manual error and processing time.
1.25 Application should have the capability to store frequently used long text into user-defined
short abbreviation so that same text can be entered fast and easily.
1.26 Application should have user-friendly functionalities like Favorites, Hit List, Hot Spots,
adjustable column widths, Sorting, Filtering, Hide/Show Columns, drug & drop facility etc
1.27 Embedded Microsoft Office, adobe pdf tools for documentation purpose.
1.28 Centralized flexible planning for physicians, facilities etc.
1.29 Seamless communication among departments for patient movement with Arrival List
facility for preparatory activities.
1.30 Other quick input help like default user values, search & report variants, patient smart card
integration, etc.
1.31 The core solution should be able to demonstrate a clear and easily expandable roadmap for
next 5 years without disruption to any business
1.32 Application vendor should provide additional functionalities not necessarily through next
higher release, but as additional packs. Company will exercise the right of implementing only
the relevant packs or functionalities.
1.33 The solution should also have Implementation / Support / Administration tool which is
integrated seamlessly and will be used during the implementation life cycle to carry on the
critical activities of the project
1.34 Same Implementation/Admin tool should enable all end user to log in issue and seek support
from the support help Desk
1.35 As a security procedure, only Implementation/Admin tool shall be the window for 24/7
support to resolve product related issue resolution activities by the OEM
1.36 Following types of system implementation tools should be provided:
Quick implementation / configuration tools
Development tools (e.g. report writer, screen painter, programming language, etc.).
Debugging, auditing and testing tools (for both functional and performance testing)
Provision for remote patch and version administration
1.37 The solution server should run on any flavor of Unix / Linux
2. Master Patient Index
2.1 Identification of each patient for life with a unique patient number and a central patient
master record.
2.2 Establishing the Uniqueness of a patient by using multiple parameters or by authenticating or
using external generally accepted identification numbers
2.3 Patient master data contains essential attributes, which will not change with time as well as
those which could edited for change like address
2.4 Master data contains key family relationships wherever essential
2.5 When patients are readmitted to the hospital, or revisit the hospital their master data is
immediately available.

Kangra at Tanda
Page 129 of 219

2.6 Patient master records are stored in a central patient database that can administer either for
a single institution or for multiple institutions in the case of group of hospital groups.
2.7 Patient data to include the relationship with employer, insurance provider, or
hospital/external physicians/consulting doctors in the case of referrals
2.8 The patient admission procedure enabled by searching the patient database for existing
patient records.
2.9 Searching by a broad range of attributes, including last name, first name, pseudonym, sex, or
an external patient ID.
2.10 Use any combination of patient attributes for a patient search.
2.11 For last names, using a phonetic search based on a freely selectable phonetization method.
2.12 Facility for importing the data stored on a patients health insurance card for a patient search.
2.13 To ensure the critical requirement of the consistency of the patient database, by creating only
one patient master record per patient.
Convenient patient search options
A mandatory search for any existing master record when creating a new record
An automatic check to ensure that no duplicate records are present before the new
patient master record is saved
2.14 If, despite these mechanisms, more than one patient master record has been created for a
patient, facility to locate the duplicate records and merge them into one master record.
2.15 Facility to retain dependent data, such as movements, when the records are merged.
2.16 The system will assist in detecting and minimizing duplication of patient registration
2.17 The system should provide facility so that ; Demographic details captured will include
Name, Gender, Date of Birth, Age, Marital Status, Contact Address and Telephone
Number (land-line and mobile), next-of-kin details, emergency contact information, etc.
2.18 The system will generate a sequential Unique Patient ID Number (UPIN) for each new patient
registration. If the UID of the patient is available then this can be used as a second identifier
2.19 The UPIN will be truly unique for every patient and will be valid throughout the lifetime of
the hospital
2.20 The system will generate a sequential Visit Number for each new patient visit
2.21 The system should provide facility so that visit number will be unique for each visit and will be
used for all billing purposes
2.22 The system will allow existing patient record details to be amended for fields, such as the
address, profession, next of kin details. All such modifications will be logged with the identity
of the person making the changes with auto time stamping. An audit trail will be maintained
for such acts
2.23 The system will make some information like date and place of birth to be non-amendable
3. Patient Administration
3.1 The gender of the patient admitted into the ward will be coded, and the system would
validate this during the admission process
3.2 All rooms within the ward will be codified
3.3 All beds within the ward will be codified, according to class (paying, free, etc.)
3.4 Specifies classification of wards
3.5 Specifies classification of beds, and can be used to set up entitlements

Kangra at Tanda
Page 130 of 219

3.6 Doctors will be coded into system. The wards to which the doctors have admitting rights will
be specified and validated at time of admission
3.7 Nurses will be coded into system. The wards to which the nurses have admin rights will be
specified and validated at the time of admission
3.8 Specifies nature of admission
3.9 Specifies the specialty to which the patient is admitted and can be used for analysis
3.10 Indicates where the patient came from
3.11 Provision should be there to create hospital organization with the following details, entities
The structure of the hospital
The catalogue of Services of the hospital
Services master data of the hospital
Catalogues for entering diagnoses, risk information etc.
Business partners of the hospital
3.12 The hospital should consist of the three types of structures
Organizational structure of the hospital
Building structure of the hospital
Cost-centre structure of the hospital
3.13 Representation of the structures and the relationships among them should be based on the
real-life situation of the hospital.
3.14 Flexibility to modify the structure depending on the need and change in
situation/circumstances
3.15 Flexibility to create multiple layers (any number) in each of the structures in an hierarchical
fashion
3.16 Rolling up the lower elements to higher elements in the structure based on the need for
consolidation and reporting
3.17 Provision should be there to capture the physical characteristics of the institution.
3.18 Creation of rooms and bed locations and defining the facilities and availability of each
building unit.
3.19 Facility to uses this information when scheduling resources, such as beds or treatment units
in outpatient clinics.
3.20 Defining the building hierarchy based upon the physical characteristics of the hospital.
3.21 Facility to link the organizational structure to the building structure by making assignments
between the upper level of the building structure (sickrooms, for example) and the lower
level of the organizational structure (care units, for example).
3.22 Provision to define cost centers and their hierarchy in the cost accounting components
3.23 Facility for Cost centers to serve as the basis for internal activity allocation.
3.24 Facility to automatically post the costs for requested and performed services to the
appropriate cost centers
3.25 Creating relationships between the organizational structure, building structure and the cost-
center structure.
3.26 Repository of the cases containing the complete history of all of a patients treatments
(outpatient and inpatient) in the hospital.
3.27 Facility to view all of a patients cases with their respective movements (admissions,
outpatient appointments, surgeries, transfers, discharges, and absences) and the assignment

Kangra at Tanda
Page 131 of 219

data.
3.28 Creation of selective and appropriate authorization, to access all of a patients cases, related
movements, and case- and movement-related information from the case list.
4. Appointment Scheduling
4.1 The system should provide facility so that there will be an appointment book for each
department and individual appointment books will be available for each doctor within that
department
4.2 The system will allow user defined slots to be created on the basis of individual
preferences
4.3 The system will factor in the ability of individual clinics to operate on different slots or
timetables
4.4 The system will allow a pre-determined number of visit types like new, follow-up, per clinic
session
4.5 The system will allow fixed as well as variable time slots within the same clinic session
4.6 The system will allow appointment rosters to be set up for weekly, fortnightly or monthly
cycles
4.7 The system will allow schedules to be generated for any date in the future as per the
hospital policy and different clinics can have different periods for which schedules are to be
generated
4.8 There will be the ability to block or unblock individual appointment slots or a block of slots
temporarily for a specified period. The blocked days will be highlighted for the viewer when
the list of available dates are displayed at the time of booking appointments
4.9 The system will allow blocking off days for holidays and offs as per the hospital rules
4.10 The system will allow de-centralized appointment scheduling
4.11 The system will allow users to quickly select a specialty and then the physician within that
specialty or the physician by name to make appointments
4.12 The system will allow the querying on the first available appointment slot for a patient based
on different parameters.
4.13 The system will allow for a one-time appointment or recurring appointments to be
scheduled within the same user interface
4.14 The system will allow appointments to be cancelled
4.15 The system will allow the cancellation of one or all appointments for a particular patient,
physician, department, clinic, service, etc.
4.16 The system will maintain an audit trail of any changes or cancellation made to an existing
appointment
4.17 The system will allow users to 'check-in' patients once the patient has registered his visit at
the hospital reception counter
4.18 The system will allow users to 'check-out' patients once the patient has completed his
visit which will include completion of consultation, receipt of services, paid his bills, etc.
4.19 The system will display the time when they arrived and their waiting status
4.20 The system will capture the time when they are actually attended to
4.21 Appointment scheduling for outpatient clinics and service facilities of the hospital.
4.22
Making or change outpatient appointments according to the resources available, using the

Kangra at Tanda
Page 132 of 219

appointment scheduling function
4.23 Ability to define physicians, treatment rooms, or organizational units as resources, for
appointment planning and scheduling
4.24 Schedule and plan display to set up appointments by displaying the daily schedules of the
available resources.
4.25 Daily calendar to shows the free and occupied time slots and the times at which the resource
does not accept appointments.
4.26 Ability to search open time slots, using predefined search variants.
4.27 Searching open time slots for:
Single appointments
Group therapies
Treatment units composed of several consecutive single appointments for the same
treatment
Recurrent single or group appointments and treatment units
5. Registration
5.1 Case-independent appointment booking with provisional data on a patient when making an
appointment.
5.2 Booking and appointment for a patient with a few specifications and planning available
capacities based on appointments
5.3 Planning an appointment as early as possible and with a minimum amount of data.
5.4 Ability to treat a patient in an outpatient clinic or a service facility, such as the radiology
department, as an outpatient appointment.
5.5 Ability to treat/diagnose inpatient for preadmission and post-discharge treatments as
outpatient appointments
5.6 A sequential and unique Patient Identification Number (UPIN) is generated for each
new patient registration
5.7 This number will be a life-long number for any given patient. Should the patient lose it, The
system will be able to search and locate the same.
5.8 The system should provide facility so that a sequential Visit Number will be generated for
each previously registered patient visit.
5.9 Visit Number should be unique for each visit and will be used for all service and billing related
purposes
5.10 Registration screen will have the ability to accept detailed demographic information as
determined and fixed by the hospital
5.11 It will have the ability to capture billing and insurance related details to enable correct
bills/claims processing
5.12 System will have the ability to make certain fields mandatory during patient registration
process
5.13 The system will capture next-of-kin demographics
5.14 The system will allow recording of the death of a patient with UPIN and mark the records as
such
5.15 The system will allow quick registration with minimal mandatory registration information
requirements
5.16 The system will allow registration of patients with appointments. No appointments will be

Kangra at Tanda
Page 133 of 219

possible without registration of the patient first
5.17 The system is additionally able to handle bed management of all beds within the hospital
thereby enabling registration personnel to locate available beds within a department or
location and assign beds during admission process at the registration counter itself.
5.18 The system will further automatically timestamp all activities - registrations, admission,
discharge, transfer and will have the ability to capture billing and insurance information at
registration or admission time.
6. Admission
6.1 All admissions will be performed using the same admission function, regardless of the type of
care setting (inpatient, outpatient, or A&E).
6.2 Will allow pre-admission booking of beds and OT timing
6.3 Will allow admission from a waiting or pre-admission list, using information already keyed in
during the pre-admission process
6.4 The system will automatically record admission date/time
6.5 Will allow the reception clerk to look up from the list of available and ready beds and select
a suitable bed for the patient
6.6 Will allow cancellation of errors in admission
6.7 The system will alert the reception clerk to any previous outstanding owed by or to the
patient
6.8 Creation of a case, treatment and services for a patient for admission
6.9 Admission of patient for an inpatient stay or for outpatient treatment.
6.10 Creation of a case that is assigned to the patients master record and is identified by a unique
number.
6.11 Creation of all the data required for administrative, medical, or nursing purposes during the
patients hospital stay.
6.12 Capturing an extensive amount of information during the admission procedure;
6.13 Admission encompassing the following data sets:
Patient data
Admission data
Referral data
Insurance data
Information about physicians (attending physician, admitting physician, and so on)
Accident data
Employer data
Contact persons
6.14 There should be a provision to handle different admission situation from the same screen like
admitting inpatients, emergency cases, or newborns
6.15 Capturing the data in these screens and the check for data completeness can vary according
to the admission situation.
6.16 Emergency admissions should be flagged as such and creating lists of emergency admissions
as a basis for completing missing data.
6.17 Assigning admission variants to the users who require them in their daily routine.
6.18 Admission variants for cases like
Quick admission

Kangra at Tanda
Page 134 of 219

Standard admission
Emergency admission
Admission of newborns
6.19 Ability to assign patients either centrally or with a decentralized, two-step procedure based
on the nature of the structure of the hospital.
6.20 With the two-step procedure, first making the organizational assignment of the patient to the
department and the care unit during admission. The patient is then assigned to a room and
bed directly on the care unit.
6.21 For the central assignment of patients to rooms and beds, ability to search for free beds in
specific facilities or by planning attributes for the room or bed, such as paediatric bed,
intensive care bed, and so on.
6.22 Ability to admit the Newborns as patients.
6.23 Integrating the newborn admission function into the mechanisms of capturing of delivery and
birth data, issue of advice for birth certificate
6.24 Transferring specific data from the mothers master data into the patient master data record
of the newborn.
6.25 Creating an assignment and family relationship between the mother and the newborn.
6.26 Ability to admit all the newborns, in one step in the case of multiple births
7. Patient Care Management
7.1 Enabling the nursing staff to schedule and administer case-related and patient-related data
from the care unit perspective.
7.2 Facility to see the patient lists and a personalized user menu.
7.3 Facility to provide all of the patient lists and functions required for day-to-day work.
7.4 Ability to see the details for the currently selected patient list for specific tasks.
7.5 Assigning or changing a bed location by dragging a patient name from the occupancy or
arrivals list and drop it onto a free bed in the occupancy list.
7.6 Ability to edit patient or case data, for example, transfer a patient
7.7 Ability to transfer a patient to a different department, dragging the patient name from the
occupancy list of the care unit and drop it onto the transfer function in the user menu.
7.8 Quick access to patient information through call functions using hot spots in patient lists -
Certain columns in patient lists have hot spots, which links directly to a desired function. For
example, clicking on a hot spot to take to a patients medical record list, to the display, or to
the diagnosis or risk factors.
7.9 Creation of decentralized material requisitions - From the care unit workstation, requesting
materials from the central pharmacy or central purchasing department.
7.10 Allocation of a specific requisition to an actual patients treatment or to a care unit, for
example, to replenish its drug closet.
7.11 Allocating the material consumption at the care unit to a patient
7.12 Allocation of services to a patient from the catalogue, as the services should be delivered to a
specific patient at the care unit.
7.13 Occupancy statistics providing aggregated statistical data on every level of the organizational
hierarchy to determine the number of free and occupied beds for each level within the
organizational hierarchy.
7.14 Managing, processing, and scheduling outpatient treatments in outpatient clinics, functional

Kangra at Tanda
Page 135 of 219

areas, and service facilities.
7.15 Ability to see appointment overview and waiting lists essential for the typical outpatient
clinic to schedule and book appointments effectively.
7.16 Creation of follow-up appointments for patients, patient admissions, diagnoses, and service
documentation.
7.17 Entering or capturing diagnoses for a case using the diagnosis overview function from the
perspective of a department that can specify additional attributes of diagnoses.
7.18 Entering a diagnosis as free text or in coded form, based on two parallel diagnosis coding
catalogues (for example, ICD-9 and ICD-10).
7.19 Defining and storing parallel diagnosis coding catalogues as required or desired, as part of the
system settings
7.20 When entering diagnoses, classifying them by assigning each to a diagnosis category: referral
diagnosis or treatment diagnosis.
7.21 Qualifying treatment diagnoses using diagnosis classes, for example, as the hospital main
diagnosis or DRG (Diagnosis Related Group) principal diagnosis, admission, or discharge
diagnosis.
7.22 Support for the surgical procedure documentation that is legally required by the billing
system and necessary for determining charges.
7.23 Managing the risk factors on the patient level. The Risk factors are valid independent of the
case.
7.24 Assigning the status to Medical documentation, which supports the basic medical
documentation workflow both from the case and department perspective and ensures that
the medical documentation for a case is complete before billing is initiated.
7.25 Facility to evaluate the completion of a cases medical documentation with the case
involving different departments the hospital/institution.
7.26 Facility to enable each department to decide when the medical documentation is complete
from its own perspective.
7.27 Ensuring that the medical documentation for the case is only complete when all involved
departments have set the department status to Complete.
7.28 Describing the case status of the medical documentation for the entire case, rather than on a
department level.
7.29 Setting the case status to released when all department statuses are Complete
7.30 Ensuring that a case isnt billed until the basic medical documentation is complete, with
activity-based billing for flat-rate cases, and the definitive flat rate has been determined for
the case.
7.31 Supporting medical records management by handling the availability of medical records to all
the relevant care units and their assignment to patients.
7.32 Supporting the borrowing of medical records and creating reminders for borrowed records
that are overdue.
7.33 Evaluating borrowed medical records according to different criteria to determine the medical
records for which reminders are to be created.
7.34 Creating, changing displaying, and cancelling medical records from the system as required for
specific cases
7.35 Ability to request, borrow, transfer and return existing medical records.

Kangra at Tanda
Page 136 of 219

7.36 Security guarantees that only authorized users have access to medical records, with audit
trails of access and modification
7.37 Facility to display all of the medical records that exist for a patient using the medical record
list, providing all the functions for processing medical records, with appropriate authority for
the specific task
8. Transfers
8.1 Transfer can be between beds in same wards or between wards or between departments or
between departments but on the same bed with automatic time-stamping
8.2 No timestamps can be altered after save
8.3 Will allow the reception clerk to look up the list of available beds and transfer the patient to a
suitable bed
8.4 The system will keep a chronological sequence of events - admission, transfer and
discharge throughout the course of inpatient stay to keep track of the history of patient's
movement
8.5 The system will always reflect the latest location of the patient
8.6 Once a transfer request is made, the reception clerk as well as the nurse on duty can
perform the transfer
8.7 The current bed will be automatically blocked immediately after the confirmation of
transfer to enable housekeeping activities to be carried out
8.8 Will allow the changing of priority of waitlist
8.9 Online bed availability status in various wards or departments to be displayed in real time on
a location map whose view may be displayed ward or department or hospital wide
8.10 The system will perform automatic calculation of bed charges based on the number of
days stayed
8.11 The system will perform automatic calculation of bed charges based on the financial class of
the patient
8.12 Ability for change of department, a change of care unit, or a change of room or bed.
8.13 Documenting the patient transfers as changes to an inpatients organizational or physical
assignment.
8.14 Editing the information, such as diagnoses or attending physicians, when a patient is
transferred
8.15 Automatic assignment of facilities. Services, physicians if required when a patient is
transferred
8.16 Automatically adjusting services (such as departmental per diem charges or personal items
that are associated with particular organizational units) in line with the transfer data.
8.17 When a patient changes departments, automatically ends the nursing charge of the
transferring department and creates a new nursing charge for the department to which the
patient is transferred.
8.18 Documenting the periods of time during which a patient temporarily leaves the hospital as
absences.
8.19 Recording absences to keep constant track of a patients whereabouts, calculating nursing
and care effort, and react to changes in patient billing.
8.20 Documenting future periods of absence by entering the start and end of an absence in
advance and then simply confirm the absence when it actually occurs.

Kangra at Tanda
Page 137 of 219

8.21 Storing the reason for the absence, an approval, and the approving physician.
9. Patient Billing
9.1 Creation of catalogue of the complete set of services of the hospital.
9.2 Creation and storing of multiple services multiple catalogues and multiple services in a
catalogue
9.3 Enhancing the existing service catalogues or create new ones at any time.
9.4 Defining the services to use for entering services for Patient Management
9.5 Defining different service groups for base rate, special rates, discounts etc
9.6 Facility for capturing the services rendered based on the activities of service performer
9.7 Remapping the services for the purposes of billing or statistical reporting.
9.8 Remapping the services from the in-house service catalogue to one or more services in other
catalogues.
9.9 A service master data record containing the name of a service and a unique ID number
9.10 Service description and relevant information for entering services or billing.
9.11 Defining the basic price of each service for billable services.
9.12 Price information with a validity period, along with price changes.
9.13 Specifications including the minimum and maximum length of stay defined for flat rates.
9.14 Service master data qualifying a service for the purposes of documentation, billing, or cost
accounting.
9.15 Qualifying a service purely relevant for billing, such as per diem fees.
9.16 Entering/capturing services to document the case and to facilitate billing, cost accounting,
and reporting.
9.17 Entering performed services directly or the application can generate them automatically
based on context using service rules.
9.18 Automatically receiving/updating services from medical or clinical subsystems, eliminating
time-consuming multiple entries and manual data entry errors.
9.19 For each service entered, the service master data should contains specific data that
influences service entry and billing, for example, the indicator that a service is billable.
9.20 All services are managed in service catalogues.
9.21 Service catalogues to systematically classify directories of master data that are either
statutory or hospital specific.
9.22 The in-house service catalogue to contain all the services provided by the hospital, for
example, medical, nursing, accommodation, and catering services or services from functional
areas, such as radiology.
9.23 In addition to the in-house service catalogue, storing the service catalogues as billing
catalogues or external service catalogues.
9.24 Services to be entered by case and may also be assigned to movements.
9.25 Documenting non-billable services and transfers and evaluating these for cost accounting
purposes, for example, cost-object accounting.
9.26 Combining services into service groups to simplify searching for specific services in the in-
house service catalogue.

Kangra at Tanda
Page 138 of 219

9.27 Setting the indicators in the service master data (for example, the billable indicator) to serve
as default values when the services are entered.
9.28 Possibility to enter services using service forms that can be designed based the paper forms
for the service
9.29 Plausibility checks minimize errors prior to billing. These checks search for service exclusions,
service combinations, and maximum values.
9.30 Automatically generating most insurance verification requests from entered services. For
services that have already been billed, displaying the billing information directly in service
processing.
9.31 Interim bills will be available at any time during the course of a visit/admission and will
display both the paid and unpaid portions
9.32 There will be instant availability of patient- dues and the various charges incurred
9.33 The system should provide facility so that it is possible to analysis of the hospitals income
under various service account heads
9.34 The system will allow the ability to capture various paying categories including but not
limited to non-paying, paying cash, with credit, with insurance etc.
9.35 Requirement is that the system will allow users to define various service classes like paid bed,
etc. and these will be determined and entered during admission/transfer time
9.36 The system will allow setting of bed charges based on the location, room or bed
9.37 The system will allow the printing of inpatient bills periodically for all inpatients or
individually at discharge
9.38 The system will allow the printing of interim inpatient bills
9.39 The system will automatically calculate all relevant taxes and add it to the bill
9.40 The system will allow bills to be settled at any counter manned by users who have the
appropriate access privileges
9.41 The system will have the facility to process various types of receipts, like:
Collection against a bill
Collection against account receivables for patients with credit facility
Collection of deposits
Collection of advance payments
10. Discharge
10.1 The system will have the ability to ensure that all formalities have been completed and to
trigger alerts/warnings as necessary
10.2 Will have the ability to capture the discharge type (routine, death, etc.)
10.3 The system will end the current visit after a discharge has been completed and not permit
any further transaction on that Visit Number
10.4 The system will ensure that a discharge summary is generated automatically on discharge for
a patient's stay in IPD, which will become a part of the patient's EMR
10.5 The system will automatically block a immediately on patient discharge to enable
housekeeping activities to be carried out and an appropriate alert/work list item will be
posted on the nursing work list
10.6 In addition to the actual discharge data, capturing the data such as discharge type, date and
time, post-discharge physician, or hospital,
10.7 Including the certain discharge activities in the processing flow, much like transfer processing,

Kangra at Tanda
Page 139 of 219

like entering the discharge diagnosis and the main hospital diagnosis.
10.8 For different discharge situations, such as discharge to an external hospital or discharge of a
deceased patient, defining the variants that contain only the information relevant for specific
situations.
10.9 Automatically terminating specific items, such as nursing charges and personal items.
10.10 If desired, initiating a billing run so that an invoice can be issued to the patients or the
employers or the insurance providers, when they are discharged.
10.11 Settlement of the invoices through direct payment by patients (through different modes of
payment), through the insurance providers, or through the employers.
10.12 Facility for a planned discharges for a future date like patient movements
10.13 Facility to create the discharge reports or treatment completion reports or referrals for
different care units, with the information captured in the entire care cycle made available
with the patient information.
11. Planning & Documentation Facility
11.1 Capability of exchanging of requests and findings between care units, outpatient clinics, and
service facilities., the patient-related documentation, the clinical order, service management
and findings
11.2 Planning all the appointments of a patient in all areas consistently.
11.3 Supporting various scenarios from long term appointment allocation with connected waiting
list management and outpatient visit planning to the planning of appointments in service
facilities.
11.4 Building cooperation between the requesting care unit or outpatient clinic and the addressed
service facility:
11.5 While creating a clinical order, the requesting user should be able to plan an appointment for
the requested clinical procedures in the calendar of the addressed service facility.
11.6 The requesting care unit or outpatient clinic will be able to use a desired appointment to the
addressed service facility to communicate any preferences.
11.7 Both the desired appointment and the appointment planned in the calendar of the service
facility should be displayed in the order overview for the patient and are therefore visible to
all those involved in the treatment process.
11.8 Appointments can be assigned on a day or time basis as well as for several types of resources.
The planning employee can choose between graphical and list-orientated variants. Using
proposals searching for free appointments and provide additional help, in particular in case of
very busy appointment calendars.
11.9 With its central appointment management, It should gurantee an up-to-date display of
booked appointments from the point of view of the care units, outpatient clinics, and service
facilities as well as from the patients point of view.
11.10 Together with the inpatient occupancy management, providing comprehensive time and
resource-related planning for all treatment-providing facilities.
11.11 All functions for inpatient or outpatient care should be amanged using the clinical work
station. Physicians and patient care staff individually configure the views necessary for their
everyday work using overviews and evaluations.
11.12 Depending on requirements, relevant information for various work situations should be
presented on one interface with standardized navigation and operation.
11.13 System should provide different types of medical documentation like parameterized

Kangra at Tanda
Page 140 of 219

documentation, unstructured documentation like outpatient clinical notes or PC document
categories for processing PC-supported office documents.
12. Electronic Medical Records
12.1 The EMR will enable the physician access to all other applications relevant to their role
through this application. For example, physicians would be able to:
View patient demographics
Manage allergy information
Manage diagnosis
Manage Orders from within the EMR Module
Perform results review with ability to interface with LIS, RIS & PACS
View patient bill including settled and outstanding values
View vitals and I/O charting entered by nurses
12.2 The module will have the following capabilities:
Ability to capture diagnosis with codes and status
Ability to capture outcomes
Ability to interface with devices like ECG, EEG etc.
12.3 The system will allow the management of patient lists where care providers will be able to
add, remove, assign and view patients who are under their care
12.4 The system will allow the unit/department to have a patient list for all care providers
attached to that unit/department
12.5 The work-list format will be user-definable
12.6 Whenever any alert or report arrives, it will be prominently displayed on the work-list and
there will be an option to print work-lists
12.7 The system will allow the management of list where care providers will be able to view, add,
update and remove the diagnosis with associated codes or problems of a patient who is
under their care as a list
12.8 The system will allow the search of problems or diagnoses with associated codes and if the
search item is not found then it will report the fact
12.9 The system will allow authorised users to enter data under history, past illnesses with ability
to indicate whether these are currently active or inactive, family history with relation
12.10 The system will allow authorised users to enter clinical findings data, both structured and
unstructured, under observations with each entry having the user ID of the person making
the observation and the timestamp associated with it
12.11 The system will allow authorised users to enter diagnosis/problems with current status along
with applicable codes that will be searchable by codes or descriptions
12.12 The system will allow authorised users to enter progress notes as free text for all admitted
patients
12.13 The system will interface with the Nursing Module to allow authorised users to view records
of vitals and I/O graphically and textually
12.14 The system will allow authorised users to capture patient current health/clinical status
including outcome status
12.15 The system will allow the capture and display of pre-admission medications for all admitted
patients
12.16 The system will allow the capture and display of medications added or discontinued for all
admitted patients
12.17 The system will allow the capture and display of discharge medications for all admitted

Kangra at Tanda
Page 141 of 219

patients with patient instructions
12.18 The system will allow special clinical data entry requirements specific to each department.
The details should be collected from each Individual department and tailored made data
entry form should be used.
12.19 The system will allow data to be presented as required by a particular department while the
same data will be presented in a different manner for some other department
12.20 The system will have the facility for nurses to conduct patient assessments based on current
diagnosis, past history including surgical, anaesthesia and hospitalisation, observations,
diagnosis with status, clinical summary and treatment plan
12.21 The system will allow the entry of vitals like blood pressure (systolic and diastolic), pulse rate,
temperature (with source like oral, armpit, rectal), respiration rate, height, weight etc.
12.22 The system will have the ability to capture nursing notes as free text
12.23 The system will be able to capture outcomes associated with each nursing activity performed
on the patient
12.24 The system, on being triggered by events for medication, should include non-medication
related events such as new laboratory results or changes in persons condition for the
evaluation of medication therapy
12.25 The system will allow the attending physician or his assignee to make referral requests to
another consultant from any department including the same department
12.26 The system will allow the referred to physician or his assignee to review the clinical summary
and results review parts of the patient referred
12.27 The system will allow the referred to physician or his assignee to make referral notes that will
include assessment, treatment plan
12.28 The system will allow the preparation of medical certificates for leaves, fitness, etc and will
keep a record of all such certificates issued including details of users who ordered, prepared
and authorised it
12.29 EMR module will be integrated with the MPI, Nursing Management, Order Management,
Investigation Management (Pathology, Microbiology, Biochemistry, and Radiodiagnostics), OT
Management etc.
12.30 Capturing Initial assessment, patient vitals ,I/O charts, allergy information etc. in the patient's
EMR by Nurses
12.31 The medical documentation to provide both an overview of the course of treatment for a
disease and a record of services performed.
12.32 Containing functions for clinic-wide basic documentation as well as for special departmental
documentation.
12.33 Document to include patient-related text and images that are stored in the medical record,
including anamnesis forms, medical findings, discharge summaries, and medical reports.
12.34 The system should support the following forms of documents in the clinical system:
Parameterized document categories for entering structured data
PC document categories for processing PC-supported office documents
Progress-orientated documentation for various areas of the clinic
12.35 Integration capability with a digital dictation system to accelerates the documentation
process (findings/ discharge summary creation).
12.36 Taking into account various forms of clinical documentation in all areas of patient treatment
as part of the documentation

Kangra at Tanda
Page 142 of 219

12.37 Supporting the capture of all media, such as text, graphics, images and speech, necessary for
general or highly specific documentation tasks
12.38 Centrally managing and make available all the medical and administrative data on a patient in
electronic form.
12.39 Facility for all of the medical professionals involved in the patients treatment can access this
data, depending on their profile and security authorization.
12.40 An electronic patient record to contain personal data and all related medical data from any
clinical systems, including data and documents from medical services, such as service
requests and findings, diagnoses, surgery documentation, discharge summaries, and any
other documents (x-rays, for example).
12.41 Electronic Patient Record should also be connected to data and documents that do not
originate directly in the system and that are managed in connected medical clinical systems.
12.42 Displaying the data on a patient according to user-defined viewpoints, like for example,
collectively displaying findings from the radiology department or all existing discharge
summaries.
12.43 Making the management and provision of personal data strictly subject to general data
protection legislation. Special technical measures to be put in place to protect patient rights.
12.44 The electronic patient record contains the clinical information of all treatment cases of the
patient, from the initial contact right through to the last documentation step.
12.45 System should provide a tool to display all information regardless of the structure, format and
physical storage location. The user therefore does not need to search and navigate in
different interfaces.
12.46 To enable tracking, each access to the patient record can be logged in a separate application
log.
13. Clinical Order Management
13.1 The system will be able to handle single and multiple orders that affect multiple
departments
13.2 The system will allow the setting up of customised order-sets by users that may be used by
the user for posting orders. The user must have appropriate privileges and the order- sets
may be set for an individual or a department or hospital-wide basis
13.3 The system should have a panel for customising order-set - either the system
administrator or the department administrator or the individual may run the
maintenance
13.4 The system will allow the setting up of recurring orders
13.5 Each order type will have its own set of pre-determined data fields
13.6 The system will be able to send outbound orders to any third party systems requiring those
using HL7 messages. These could include laboratory, radiology etc.
13.7 The system should print requisition forms (if required for a particular procedure) to be
printed automatically at time of the order
13.8 Provision to define mandatory fields for an order.
13.9 Provision to define urgency of the order
13.10 The system should provide facility so that; Requests for procedures will normally be
entered into the system at the source (wards/clinics/departments) using the Order Entry by
care providers and the results in the Results Reporting application by the reporting
department.

Kangra at Tanda
Page 143 of 219

13.11 The following information will be captured during the order entry:
Patient UPIN and Visit Number
Source of order
Care Provider Identifier
Request Urgency (routine, urgent, stat)
Investigation Details
Unique Order ID (generated for one or a set of orders posted together)
13.12 Procedures can be ordered either individually or as a set of orders
13.13 There will be the facility to order future procedures for a patient
13.14 The system will alert the user if a repeat order is being placed within a certain time frame, to
prevent duplication of orders and the rules for these alerts will be user customizable
13.15 The system should provide facility so that results may be entered into the system either
direct manual entry or via an interface of the sub-system.
13.16 Audit trail of all entries will be kept that will record all result entries / modifications, details
of date / time and operator identifier of the who made the entry / modifications
13.17 The system should provide facility so that ; The results will automatically made available in
the EMR upon verification of the result
13.18 The system will automatically post a charge to the patients bill for any investigation that is
carried out but not yet paid for (as in inpatients) or reconcile where the payment has
already been made (as in outpatients)
13.19 There will be an option to reverse a charge if required by an authorised user. An audit trail
will be kept of this
13.20 System should enable flow of information between the requesting care unit or outpatient
clinic and the treatment documentation at the service facility.
13.21 System would provide flexibility to issue a clinical order for a variety of departments and their
processes.
13.22 System will provide a order profiling facility and templates to provide quick input options for
request situations
13.23 Provision to creating work flows depending on the requested medical services e.g.
confirmation or authorization steps.
13.24 Depending on the requested medical services various workflows may be necessary, e.g.
confirmation or authorization steps. The clinical order should support this with its flexible
status concept and should therefore be the central means of communication between the
responsible persons in the clinical process.
13.25 Solution should provide integrated completeness and consistency checks at time of input as
well as in downstream processing steps reduce the number of potential queries and
guarantee a smooth workflow.
14. Nursing Management System
14.1 The system will allow the management of patient lists where care providers will be able to
add, remove, assign and view patients who are under their care
14.2 The system will allow the unit/department to have a patient list for all care providers
attached to that unit/department
14.3 The system will allow a user to maintain patient lists of their own
14.4 The system will be able to generate work-lists to assist the nurses to organize their work by
grouping together tests that are carried out together on the same equipment

Kangra at Tanda
Page 144 of 219

14.5 The work-list format will be user-definable
14.6 The system should have the provision of displaying any order or alert on report whenever
they arrive ; the system should display the same on the work-list
14.7 The system will provide the ability to view orders posted
14.8 The system will provide the ability to view posted results per patient
14.9 The system will provide the ability to view patient details
14.10 The system will provide the ability to indent supplies from inventory and pharmacy
14.11 The system will provide interfacing with appointment scheduling to allow users to
manage appointments
14.12 The system will provide interfacing with the discharge and transfer modules to allow
users to discharge or transfer patients
14.13 The system will provide interfacing with bed management module to allow users to locate a
bed for allocation or performing housekeeping on them
14.14 The system will provide the ability to run housekeeping maintenance on beds and keep track
of linen including counts of fresh, used, discard, indented, received, returned, etc.
14.15 The system will provide information on the scheduled time of administration, actual time of
administration, and when the user charted the administration. With this information,
variance analysis concerning the effectiveness of the medication therapy could be
performed.
14.16 The pharmacy system will provide instructions and monitoring guidelines for each
medication will be administered
14.17 The system will have the facility for nurses to conduct patient assessments based on
current diagnosis, past history including surgical, anaesthesia and hospitalisation,
observations, diagnosis with status, clinical summary and treatment plan
14.18 System will support the patient care process documentation, i.e. the mapping of standard
patient care planning, including the processing of the patient care procedures which result
from the created patient care plans.
14.19 System will be flexible to construct a clinic-individual patient care concept using powerful,
generic master data/context management similar to ontology.
14.20 System will create standard patient care plans, consisting, for example of (but not limited to)
the three usual categories:
Problems / Resources
Goals and goal achievement criteria
Procedures and interventions
14.21 System will help planning of procedures including a powerful iteration management
(cyclically repeated activities, etc.)
14.22 System will help to process planned procedures, whereby various patient care models
(departmental patient care, functional patient care, etc.) can be supported as generic work
station concept.
14.23 It will enable continual patient care progress documentation, either free or related to
individual content of the patient care plan.
14.24 Nursing report creation
14.25 System will providing methods for determining planned and actual nursing categorizations
and updates relevant nursing services

Kangra at Tanda
Page 145 of 219

15. Medication Order Management
15.1 The type of the order can be either normal or repeat
15.2 The normal orders can be a one-time or bulk prescription, where the prescribed quantity is
entered directly or in terms of the dosage details, in which case the prescribed quantity is
calculated
15.3 The repeat order is a repeating prescription, which specifies the start date, end date or the
duration of the prescription and also the frequency (in days) at which the order for the
prescribed dosage need to be automatically raised again with the pharmacy
15.4 Partial filling of orders will be allowed with the rest filled subsequently
15.5 The system should provide facility to enter the drug item that will only be prescribed as a
mnemonic or generic name or by the therapeutic category
15.6 The system will display the description and the form in which the drug is packed and the
method of administering
15.7 The system should provide facility so that mnemonic, trade or generic name search will easily
and quickly retrieve the drug item codes
15.8 The system would allow order entry in centralized or decentralized locations throughout
the hospital, by various categories of staff such as physicians, nurses, clerks or technicians
15.9 The system would enable users to enter all medications into the system from the same
screen. Medications can be selected by brand name and therapeutic category only
15.10 The system should provide facility so that common order entry sets will be site (hospital wide,
department wide) or user defined to further expedite the order entry process by having the
most commonly used items pre-selected for activation and the less customary items available
for activation.
15.11 The system should provide facility so that; Medication orders will be linked during order entry
to provide clear directions for medication administration.
15.12 The system should provide facility so that if there have been medication orders earlier for
the same inpatient, then medications issued to the patient will be checked for inclusion
of these drugs and warnings issued for duplicates where appropriate
15.13 The system should provide facility to initiate an approval process for controlled drugs by a
competent authority before the transaction can be processed
15.14 The system will support interfacing with external drug databases which are suitable
to the local environment (e.g. MIMS or First Data Bank, etc)
15.15 The system would have provision for returns against prescriptions
15.16 The system will provide support for all medication orders, processing, administration, and
dispensing in a paperless environment
15.17 The system would have facility for the online recording medication administrations in
Medication Administration Record (MAR)
15.18 The system will automatically update the status of any order in real-time to enable the
users to have an online review of the status of any order for any patient
15.19 The system should provide facility so that authorised users will be able to review the status
of any order online from anywhere within the hospital
15.20 Medication should integrate all medicinal therapy processes into the hospital information
system. Medication acts as an end to end tool and satisfies the requirements of so called
closed loop medication.

Kangra at Tanda
Page 146 of 219

15.21 The core processes of the solution will be
Ordering
Provision of drugs to care units and outpatient clinics
Administration documentation in the hospital
Creation of prescriptions
15.22 System will enable the display of drug specifics pursuant to the corresponding process step.
For example, drugs are presented to the ordering physician in the care unit in a different
(highly personalizable) way than to the pharmacist during provision (who requires various
administrative information concerning package sizes, for example).
15.23 The medication order to provide a comfortable search function which takes into account
hospital specific search lists and favourites.
15.24 Ability to cope with various order categories (tablets, injections, complex intravenous
therapies, etc.) using different order screens, ranging from extremely fast ordering of oral
therapies based on templates, through to the definition of sophisticated schemes such as
chemo therapies or the definitions of flow rates for intravenous treatments.
15.25 System will enable clinical checks which go beyond the scope of the extensive master data
(e.g. interaction checks) by integrating external subsystems via standardized interfaces and
completely integrated into the overall medication process.
15.26 System will enable hospital pharmacy or a decentralized location to provide drugs for
administration in the care unit or the outpatient clinic.
15.27 System should provide the required content for unit dose systems.
15.28 It should enable role based work lists and overviews are generated, for example fill lists for
stock keeping.
15.29 The administration documentation to enable a depth to satisfy the relevant documentation
requirements of the institution and representing a basis for patient related drug profiles.
15.30 Posting the issue of drugs and reservations in materials management.
15.31 It will enable creation of prescriptions in hospital outpatient clinics and within the framework
of the discharge process.
15.32 Drugs can be searched in a hierarchical manner.
16. Surgery Management
16.1 The system will allow scheduling of surgeries from any location within the hospital
16.2 The systems will have automatic scheduling conflict alerts and present the user with a
choice of the best available alternative appointment slots
16.3 Authorised users will be able to query on the first available appointment slot for a patient
based on criteria specified like main OT, side OT, etc.
16.4 The system will allow the setting up of specific resources for each procedure and
automatically book all these resources at the time of booking a procedure
16.5 The system will allow users to re-schedule an individual appointment for a patient
16.6 The system will allow appointments to be cancelled
16.7 The system will automatically calculate the duration for each procedure, based on the
surgeons most recent average, historical average, and hospital specific default times
16.8 The system should provide facility so that there will be the ability to efficiently maintain
Procedure Order-sets for surgical supplies, equipment and instruments
16.9 The system should have the ability to prepare one generalized procedure card for the

Kangra at Tanda
Page 147 of 219

hospital and tailored Procedure Order-sets for each surgeon and procedure
16.10 Surgical supplies will be managed by Procedure Order-sets to enable easy and accurate
charging to the patients bill
16.11 The system will provide standard, comprehensive surgical documentation templates to
enable users to document accurately all data in the preoperative, intra-operative and
postoperative phases of a patients surgery
16.12 Documents should be in checklist format as well as textual format
16.13 The system should automatically post a charge to the patients bill for any procedure that is
carried out but not yet paid for (as in inpatients) or reconcile where the payment has already
been made (as in outpatients)
16.14 There should be an option to reverse a charge if required by an authorised user. An audit trail
will be kept of this
16.15 The system will allow the capture and display of observations that may include:
Patient Vitals
Details of previous history of anaesthesia
Anaesthetist's observations
Consent taken status
Blood requisition orders and status
Region of interest for procedure
Date and time for procedure
Fitness for surgery with reasons for not fit for surgery and orders
16.16 The system will allow the capture and display of observations for pre-operative
anaesthesia that may include:
Cross-checking of patient, consent, region of interest
Type of anaesthesia
Date and time of induction
Mode of induction
Drugs used for induction
Outcome of induction
Date and time of reversal
Mode of reversal
Drugs used for reversal
Outcome of reversal
Date and time of shifting to recovery
16.17 The system should provide facility so that post-operative Order Details are captured
16.18 This module should offer flexible, easy-to-use planning tools for both long and short-term
planning, overviews for the organization and monitoring of surgical activity, and comfortable
support for all documentation tasks.
16.19 It should enhance the clinical order with the addition of surgery-specific attributes for surgery
registration, which represents the basis for surgery planning. It contains the diagnosis, the
surgery to be performed, possibly the operating surgeon and status information on the
preparation for surgery and therefore forms the basis for the often multi-level planning
process.
16.20 The system should provide table-oriented and graphical tools for planning a surgery
appointment, which, depending on requirements, can be used for long-term planning as well
as for surgery room and personnel planning.
16.21 In situations where the demand for specific surgeries exceeds the current planning horizon, a
connection to waiting list management to offer a way of registering a patient for surgery
until the allocation of an appointment.

Kangra at Tanda
Page 148 of 219

16.22 Provision for requesting preoperative examinations and planning using the clinical order and
appointment management. All findings for these examinations are entered in the electronic
patient record and are therefore available centrally to all involved parties.
16.23 System will provide a surgery documentation work station to offer a standard initial screen
which serves as an information and documentation tool for all information which is entered
in the context of a surgery. This includes both the process-accompanying entry of log
information (incision and suture times, materials consumed, count checks, etc.) and the entry
of medical information such as diagnoses, procedures, and the surgery report.
16.24 The parts of surgery documentation which are administratively relevant must be available for
billing purposes as soon as they have been released.
16.25 Provision to create surgery report quickly using text modules, electronic dictation or speech
recognition.
16.26 All information during surgery must be visible in the electronic patient record and can be
used for informational purposes in the further treatment of the patient.
17. Radiology Department Solution
17.1 This module should have the capability to interface with PACS
17.2 The system will be able to seamlessly handle inbound and outbound HL7 messages from any
system that has similar capabilities
17.3 The system will be DICOM compliant
17.4 The system will enable users to schedule radio-diagnostic appointments
17.5 The system will allow the users to set up time-slots for each modality depending on
modality type and hospital requirements
17.6 The system should provide facility to set up appointment lists in the future
17.7 The System will have report templates or text blocks that can be called up by radiologist ad-
hoc or on investigation basis
17.8 The application should have the capability to support voice recognition for dictation and
transcription of reports
17.9 The system will allow for entry of start and end times for investigation, radiographer /
radiologist, technician involved and room used
17.1 There would also be provision for entry of films and drugs used per investigation
17.11 There would be a real-time interface to Pharmacy Management modules and Inventory
Control modules for inventory update
17.12 There would also be a real-time interface to the Patient Billing system for charging of
consumables
17.13 The module should meet the requirements of integrated mapping of the radiology
department within the hospital information system
17.14 System will provision that image studies can be called (in an external viewer) in context-
specific form from all relevant work environments in all the other modules (even outside the
radiology department).
18. Clinical Pathways
18.1 System will provide medical treatment pathways as an integral part of treatment delivery
which will support and simplify users' everyday work with flexible work lists, but without
restricting his/her necessary freedom of decision.
18.2 System will provide a graphical editor for the creation and maintenance of the structure of

Kangra at Tanda
Page 149 of 219

treatment pathways.
18.3 The tool will help to create process steps and chronological sequences of them.
18.4 Same tool will help to define individual steps and link them to standard functions.
18.5 Each activity might be assigned to physicians or nurses or technicians.
18.6 The physician should be able to see at a glance which potential treatment pathways are
stored for which patients, based on the documented diagnoses.
18.7 The physician will be able to choose the suitable pathway from those which exist in the
system. Following this assignment the system to provide the attending physician with an
extensive tool for processing the work steps.
18.8 Ability to capture notes for each steps during treatment process if required.
18.9 Ability to store progress notes chronologically
18.10 Ability to make some steps mandatory and some of them optional
18.11 Facility for the physician to access the corresponding function without additional navigational
steps, the processing efficiency is increased further by context-dependent presetting.
18.12 The tool should have the flexibility so that the physician can deviate from the proposed steps
or leave the pathway entirely at any time. In these cases the reasons for aborting the
pathway can be documented and evaluated at a later time. These evaluations can be used to
verify the quality of the pathway and the results used to optimize the pathways.
18.13 Ability to close or complete a step by competent authority.
19. Hospital Transport Management System
19.1 Integrated Transport module for supporting the transport service within the care institutions.
19.2 It should be also linked to the organizations and building structures
19.3 System will enable management of transporters, means of transport and transport types
19.4 Solution will enable management of transport times between the building units of an
institution
19.5 Transport requests might be individually entered at any work station. Patient related
transports can also be created as part of a clinical order for the examination or treatment of
the patient. The clinical order presets specific transport information (e.g. starting point and
destination, transport type) and therefore reduces the input outlay.
19.6 Patient related transport requests should be connected with the patient's planned
appointments in the outpatient clinic, service facility. In this case, depending on the
appointment, automatically system will propose the times at which the patient should be
collected from the starting point and when he will arrive at his destination, based on the
stored transport times.
19.7 System should have provision for automatically adapting these times if the examination or
treatment appointment of the patient is postponed.
19.8 System will have provision to manage all transport requests centrally with features of
modification or cancellation.
19.9 System will provide an overview of upcoming transport requests as well as the available
transporters and their assigned requests. Transport requests are assigned to transporters in
one simple step. The connection of mobile end devices for informing the transporters is
possible via an interface. The dispatcher work station also provides entry and management
functions for transport requests, for example, for entering requested transports by telephone
or cancelling any transport requests which are no longer required.

Kangra at Tanda
Page 150 of 219

19.10 Facility to document status of transport requests like patient collected, transport request
complete, etc.. Any number of statuses can be defined and adapted to suit the necessary
documentation steps. The status is set using the corresponding entry function at the
dispatcher work station or other clinical work stations.
19.11 System should have capability to document this status over mobile device.
19.12 System will provide an evaluation program by listing transport requests according to various
criteria (e.g. relating to a specific route) with their transport times.
20. Ward Management System + Charting
20.1 System should provide a pre-built documentation work station for supporting the work
processes of employees on the wards of the hospital.
20.2 The solution should include task management for the standardized completion of tasks in
varying situations of the treatment context, enabling a multi-disciplinary team process
oriented view of upcoming tasks.
20.3 Tasks can be displayed in patient-related or occupational group-related form, thus enabling
optimum support in work organization.
20.4 Provision should be there so that all tasks can be cooperatively completed, a planned date
enabling effective organization even in the future.
20.5 The entire task should have access to the necessary documentation screens of the clinical
system, so that documentation can be completed promptly and completely.
20.6 During execution of the task user should have required information at hand like
The entire patient record, extensive filter functions can be used to display the section of
the record which is relevant to the task.
The charting component as a graphical, time-oriented view, this tool can also display
specific chart layouts in task related form.
The clinical overview displays relevant information on the patient and his treatment, can
be used for overview information on the treatment
20.7 Provision of graphically displaying all information in chronological order, in a way that the
clinical staff is accustomed to from its paper chart.
20.8 Provision of tooltips and detailed displays to provide access to information which is not
included on a paper chart.
20.9 Information from the chart can be transferred for further processing or new data entered at
the click of a mouse button.
20.10 Solution should have provision to select time periods and a continuously adjustable zoom
function should enable a complete overview and the necessary access to details.
20.11 There should be extensive warnings, reference areas and further information facilities to help
the clinical staff to make quick and safe decisions about the relevant patient.
20.12 Availability of standard charts for usage
20.13 Tool to create additional chart layouts so that the user is presented with a chart suitable to
the current situations and tasks.
21. Mobile Electronic Medical Record Management
21.1 Mobile application will be able to connect back-end clinical systems, PACs or LIS systems
21.2 Application will provide access based on login id and password in a secured manner
21.3 Based on roles and responsibilities, patient data ans access rights will be determined.
21.4 Application should support both iOS and Android platform

Kangra at Tanda
Page 151 of 219

21.5 After login, physician will have access to his all patients ward-wise and room-wise or
favourites.
21.6 In addition to above, patient can be searched in the existing list or in the back-end system.
21.7 After selection of a particular patient, a summarized information will be displayed consisting
information like demographic information, allergy/risk information, gender, recent images,
documents, clinical orders, progress notes etc.
21.8 There will be a patient header consisting image of the patient, gender information, age, DoB,
location, etc.
21.9 There will be very flexible UI which can be modified by end user also.
21.10 There will multiple views of patient information like Charts, Documents, Lab Results, Clinical
Orders, Coding information, Patient Demographics, Progress Notes, Clinical Tasks for different
physicians/nurses etc.
21.11 Selection of a particular view will show the detailed information in detailed area section.
21.12 User will be able to show/hide view selection panel to see the required information
comfortably. Or sequence of views can be changed by users as per their comfort.
21.13 User can hide/show patient header to increase the detailed view of a particular section.
21.14 User will be able to define the ranges of information to be displayed like Current Case, Older
Cases, All data or current year data etc.
21.15 There will be chart view of all vital signs with color-coding for exceptional values. By selecting
a particular value will provide details of that particular measured value.
21.16 User will be able to put a patient into his particular group with color-coding to easily identify
and process in future easily.
21.17 All images and albums can be organized. Several images from different studies can be stored
in a particular album.
21.18 There will be provision to take patient's picture directly by the handheld device and upload in
the system.
21.19 Creation or modification of image albums for storing different pictures for a particular
context.
21.20 Provision should be there to compare images by putting them side by side.
21.21 There should be easy to use documentation feature which is absolutely required like creating
progress note, personal note or clinical task. Progress note is part of patient record and
should be visible to concerned persons. Personal note is individual note by the user which is
not part of patient record. Clinical task is patient briefing to support the care unit workflow.
21.22 Clinical tasks should support the care unit workflow. They contain a category and a selection
of the user role that shall handle the task.
21.23 User should be able to enter text and attach images or speech memos which can be created
or recorded directly in the App.
21.24 Clinical Task can be confirmed after the task completion.
21.25 Application should provide a provision to store a text as text template and then insert it while
creating clinical task.
21.26 In lab results screen, user will be able to see measured values, threshold values or normal
range of particular parameter and if measured values if not within the range or exceeds
threshold value, it should be highlighted with red.
21.27 Lab comments should be displayed for further information.

Kangra at Tanda
Page 152 of 219

21.28 Lab results can be shown in tabular or graphical format.
21.29 In the same screen, trend can be checked for a certain lab value.
21.30 All the documents of common file formats like PDF or MS Word can be accessed which are
stored in clinical system or archive.
21.31 There should be provision to filter documents to get relevant documents only.
21.32 All the devices where this application is installed should be managed remotely. If device is
lost, data can be destroyed.
22. Hospital Connectivity to other Institutions
22.1 Facility for the communication between care institutions in the healthcare branches and to
take on the role of sender or recipient.
22.2 Connectivity for the communication of clinical orders, appointments or documents. This
means, for example, that a hospital can make electronic service requests of an external
laboratory and also receive the findings created for the examination.
22.3 Connectivity to be used in homogenous single system environment as well as in
heterogeneous system networks.
Between different institutions with similar systems
Between various partners on different clients within the same system between the two
systems
Between clinics which use different systems from other manufacturers
Between institutions which use specialist systems
22.4 The solution should enable the construction of web-based applications for external system
users. For example, family physicians can enter referrals using a web application, book an
appointment for the desired treatment and review findings once the treatment has taken
place (providing they have a corresponding agreement with the hospital).
23. Integration of Dictation System
23.1 It will provide generic dictation interface which can be used to integrate any dictation system
into the objects in standardized form.
23.2 This should enable recording free texts on the objects in the system using digital speech
recording or using speech recognition to support and accelerate the processes during the
creation of medical documentation.
23.3 In the clinical work station, work lists can be configured in such a way that they can be used
by a physician to create and manage dictations and also by clerks for processing dictations.
24. Occupancy management
24.1 It should address the process of inpatient admission planning with any SAP or non-SAP
Patient management system
24.2 The solution should enable the occupancy manager to act as the central contact person for
internal and external referrers and, coordinating with the ward staff, plans the resources of
the care unit.
24.3 The occupancy managers work station should offer an overview of a specific group of
resources in a graphical, time-related display. For example, the beds of a specific specialist
assignment or hospital class are displayed on several patient care units with the currently
planned occupancy or lengths of stay.
24.4 It should have the capability to manage resources of the care unit, room, and bed
types.
24.5 The user will be able to plan definite beds or provide a capacity (quota of resources).

Kangra at Tanda
Page 153 of 219

24.6 Tool to find a suitable bed quickly for the patient based on many parameters.
24.7 There should be utilization indicators with threshold values to enable fast orientation and
warn of overbooking.
24.8 Enable an appointment search to propose possible free admission appointments and thereby
accelerating the planning process.
24.9 The actual length of stay of a patient, compared with that estimated at time of planning,
often changes numerous times over the course of inpatient stay. The tool will continuously
calculate the actual length of stay of admitted patients as well as any discharges which may
already have been entered, and outputs the actual occupancy situation of the committed
resources.
25. Gastro
25.1 The solution should be an integral part of hospital's clinical processes
25.2 The solution should comprises the ordering and findings documentation of the most
important examination procedures in the gastroenterology department namely
Esophagogastroduodenoscopy (EGD)
Coloscopy (COLO)
Endoscopic retrograde cholangiopancreatography (ERCP)
Sonography (SONO)
Endosonography (ENDOSONO)
Sample covering letters for biopsies and further examinations
25.3 During the creation of findings documentation the clinical user should be optimally supported
by automatic input helps and text modules. The delivery of findings documents contains
gastroenterological-specific findings hit lists, specific to the individual examination, which
contains the most important and most common diagnoses and procedures for the relevant
examination.
25.4 The solution should be able to interface to digital image management so that the
management and transmission of image documents on the examination is simple and
comfortable.
25.5 The specialist documentation of gastro should be integrated into the clinical system so that
documents entered immediately become part of the patients electronic record and all
standard functions and any other implemented modules are also available to
gastroenterologist specialists.
26. Cardiology
26.1 The cardiology departmental solution should comprise the ordering and findings
documentation of the most important examination procedures in the cardiology department:
Cardiac catheter: Log and diagnostics and intervention findings
Echolab : TTE, TEE and stress echo
ECG: Resting ECG, 24 hour ECG, ergometry
Cardiac MRI
Doppler duplex sonography
24 hour blood pressure
Spirometry/spiroergometry
26.2 The clinical order should have specialist components for requesting the aforementioned
examination procedures.
26.3 The solution should provide optimized use of image integration for graphically aided
documentation for fast and comfortable creation of examination documentation and
findings.
26.4 This solution should enable interfacing devices from different manufacturers (Siemens,

Kangra at Tanda
Page 154 of 219

Metek, Schwarzer, GE, Scheller, Sorin, Reynolds), and should enable fast, complete
documentation, tailored to suit the requirements of the professional associations.
26.5 The specialist documentation of cardio to be integrated into the clinical system so that
documents entered immediately become part of the patients electronic record and all
standard functions from basis and any other implemented modules are also available to
cardiologists.
27. Organisation Structure, Master Data & General
27.1 Facility to define central purchase department to carry out purchase for entire company
27.2 Maintaining central store and sub-store
27.3 Enabling project storage location concept
27.4 Maintaining multiple storage locations under an area
27.5 Creating a warehouse structure with bin information under a storage location
27.6 Creating item groups
27.7 Enabling flexibility in item code definition
27.8 Provision for changing, deleting and blocking the item code
27.9 Provision of making the item code inactive
27.10 Allocation of different item numbering to different group of items
27.11 Provision for handling item having different unit of measurement (UOM) for Production,
Sales, Purchase, Stock etc.
27.12 Provision of converting the measurement of unit at all levels automatically
27.13 Enabling categorization of items based on its type like capital goods, equipment, spare parts
etc.
27.14 Provision of searching item based on its characteristics
27.15 Storing supplier item code along with the item code created
27.16 Defining all the required planning parameters during the item code creation
27.17 Storing variety of general information in Vendor Profile like name, address, email id etc.
27.18 Classifying vendor on criteria like indigenous/foreign, PSU/Non PSU etc
27.19 Storing Telephone number, E-Mail Addresses, contact name, and Fax Numbers, in Vendor
Profiles
27.20 Defining Payment Profile for each Vendor (including currency, bank, account number, PAN,
Taxes as applicable and mode of payment)
27.21 Capturing Vendor details namely Line of business & Products.
27.22 Online provisional registration by the Vendors and with minimum of two levels of verification
& authorisation for Final registration and vendor code allocation
27.23 Maintaining information regarding material and vendor combination like planned delivery
time, price, payment terms etc.
28. Purchase & Inventory Management
28.1 Pharmacy Management
The system will maintain balances and a transaction history for each medication item
including cost and suppliers
Movements will be input manually and automatically from the sales/purchase

Kangra at Tanda
Page 155 of 219

order processing systems and transfer requests would automatically update stock
balances
Stock would be valued on any of the following basis standard or, weighted average
When a stock line is created the standard cost will be input
An issues note would be optionally be printed for all issues
There would be no restriction on the number of stores held on the system
There would be no restriction on the number of bin locations held on the system
The system would interface with the purchase order processing system so as to produce
purchase order recommendations.
A list of available and authorised medications with their suppliers will be maintained
A list of suppliers/rate contractors will be maintained
Code and description for the various forms in which drugs should be available
Code and description for the different methods in which a drug could be administered,
e.g. Intravenous, Oral, Rectal, Vaginal, Topical, etc.
Code and description for brief instructions on the method of administering a drug to
patients
This table allows the user to maintain the various trade names under which the same
drug is available in the market
These are codes and associated descriptions for the Anatomic, Therapeutic and
Chemical groupings of the drugs. Each drug in the Drug Master file can be associated
with one set of ATC codes
The pharmacist will be able to set the stock levels required by the hospital to maintain
one or more pharmacy outlets within the hospital
The stocks will be replenished by an automated process or manually triggered by a
competent authority
The system will automatically generate reorder documents for the procurement of
new stock
The system will also facilitate manual entry of requisitions from the various
wards/clinics/departments in the hospital
The system will support expiry and near-expiry of items. For expiry items, stock will be
maintained at batch level with expiry date for each batch; and any store transaction will
identify the batches being processed as part of the transaction to ensure that no
expired or near-expiry items are issued
The system will generate a list of near-expiry items that are due to expire 30 days from
the date and display as an alert to the user
The system will have facility to record transfers between stores
The system should provide facility so that ; The stock balance will be updated
immediately on confirming a transaction (receipt of stock into inventory, returns to
vendors, dispensing to patients) to reflect true on-hand status at any time
The system should provide facility so that ; There will be automatic validation and
warning on expiry of items
The system should provide facility so that ; There will be provision to remove expired
items from active stock that need to be replaced or destroyed
The system should provide facility so that ; There will be provision for recording physical
stock check figures and generating variance reports and automatic adjustments
The system should provide facility so that ; The reason in adjustments with be
mandatorily entered for audit purposes
The system should provide facility so that ; Stock transactions effect on financial
accounts will need to be reflected in the General Ledger based on the accounting
linkages
The system should provide facility so that ; There will be provision to close each
accounting month after all transactions have been recorded for that month
The system should provide facility so that ; Outgoing medicines and prescriptions will be
automatically deducted from its stock list
The system should provide facility so that ; For each item-store combination, the
minimum, maximum and re-order quantities will be maintained depending on the

Kangra at Tanda
Page 156 of 219

policies and procedures adopted for replenishment of stock at the sub-stores and
non-stock stores
The system should provide facility so that ; The inventory levels reach reorder points,
the system will automatically generate purchase orders for reordering by comparing
the stock-on-hand with the reorder level and the orders will be reconciled upon delivery
28.2 Drug Procurement Management
List of the drugs and medical supplies used in the wards should be maintained
Should be able to enter supplies needed bed-wise by entering/selecting:
Name of item
Quantity
Should be able to update consumption details
Should be able to consolidate & aggregate the prescription details for all patients in a
ward and raise indent based on that
Should be able to save the data updating the Drug & Distribution Management System
Should be able to print the indent sheets according to prescribed format
The system will have the ability to display the alert for the indent approving authority on
receipt of indent approval requests in the system
28.3

Drug Dispensing
The system will have the ability for Pharmacist to check for availability and quantity of
required drug for issue
The system will facilitate retrieving details of available drugs (batch number, expiry
date, location) in the pharmacy / drug store & reserve drugs for the indent based on
the item code and quantity mentioned in the approved indent
The system will have the ability to reserve / release an item or batch for a specific
indent and display reservation status
The system should provide facility so that ; If the drugs under the batch numbers
retrieved by system are found missing/ destroyed in the warehouse, The system
will facilitate marking the batch as Missing/ Destroyed & retrieve the next batch of drug
with least shelf life
The system will have the ability to capture the re-assortment details of the drugs to be
issued. The details may include
Name of Drug
Drug quantity
Batch number
Expiry date
The system will have the ability to support planning methodologies; re-order point,
safety point, lot sizing, lead times, min/max levels etc
The system will have the ability to provide information on Expected Delivery dates for
each location
The system will have the ability for stock transfer between health delivery units,
based on stock transfer note
The system will have the ability to automatically deplete the inventory of each drug
when it is issued
The system will have the ability to maintain detailed audit trails for the transactions
carried out in the system for issuing the drugs including date & time and details of user
conducting the transaction in the system
The system will be able to view the available medications category wise
The system will be able to Update the available medications to reflect their issuance
The system will be able to locate the UHID and details of patient for whom the
medications are issued
The system will be able to print medication issuance report
The system will be able to enter the issued medications against the recipient UHID
The system will have the ability to record the details of drugs received against the
approved indent including the following:
Date of Receipt

Kangra at Tanda
Page 157 of 219

Drug Name
Drug Quantities
Batch Number
Expiry date
The system will have the ability to interface with barcode readers and retrieve the bar
coded information from the received batches of drugs.
The system will have the ability to validate the receipt against the Indent & Dispatch
note
The system will have the ability to assign physical location (box, rack, bin, etc)
The system will have the ability to automatically update to the inventory of the drugs
in pharmacy in field units
The system will have the ability to generate Receipt Report in which item details like
quantity, Expiry date, Batch number, quantity accepted, quantity rejected, portion
of purchase order received etc are included
The system will have the ability to record the details of drugs procured through
local purchases against the approved indent including the following:
Date of Purchase
Drug Name
Drug Quantities
Batch Number
28.4 Inventory Management
The system will maintain balances and a transaction history for each stock line including
cost and suppliers
The system should provide facility so that ; Movements will be input manually and
automatically from the sales/purchase order processing systems and transfer requests
would automatically update stock balances
The system should provide facility so that ; When a stock line is created the standard
cost would be input
The system should provide facility so that ; An issues note would be optionally be
printed for all issues
The system should provide facility so that ; Summarized monthly stock movements
would be retained on the system for 1 year and be available for enquiries
The system would interface with the purchase order processing system so as to produce
purchase order recommendations
The system should provide facility so that ; The stocks will be replenished by an
automated process or manually triggered by a competent authority
The system will also facilitate manual entry of requisitions from the various
wards/clinics/departments in the hospital
The system will support expiry and near-expiry of items. For expiry items, stock will be
maintained at batch level with expiry date for each batch; and any store transaction will
identify the batches being processed as part of the transaction to ensure that no
expired or near-expiry items are issued
The system will have facility to record transfers between stores
The system should provide facility so that ; The stock balance will be updated
immediately on confirming a transaction (receipt of stock into inventory, returns to
vendors, dispensing to patients) to reflect true on-hand status at any time
The system should provide facility so that ; There will be automatic validation and
warning on expiry of items
The system should provide facility so that ; There will be provision to remove expired
items from active stock that need to be replaced or destroyed
The system should provide facility so that ; There will be provision for recording physical
stock check figures and generating variance reports and automatic adjustments
The system should provide facility so that ; There will be a facility to use hand-held
devices for stock checks where inventory information may be downloaded to the device
at the start of the stock taking, and then uploaded back into the main system at the end

Kangra at Tanda
Page 158 of 219

of the day
The system should provide facility so that ; The reason in adjustments will be
mandatorily entered for audit purposes
The system should provide facility so that ; Stock transactions effect on financial
accounts will need to be reflected in the General Ledger based on the accounting
linkages
The system should provide facility so that ; There will be provision to close each
accounting month after all transactions have been recorded for that month
The system should provide facility so that ; Outgoing medicines and prescriptions will be
automatically deducted from its stock list
The system should provide facility so that ; For each item-store combination, the
minimum, maximum and re-order quantities will be maintained depending on the
policies and procedures adopted for replenishment of stock at the sub-stores and
non-stock stores
The system should provide facility so that ; As the inventory levels reach reorder points,
the system will automatically generate purchase requisition for reordering by
comparing the stock-on-hand with the reorder level and the orders will be reconciled
upon delivery
Inventory Management module will be integrated with the Nursing Management, Order
Management, OT Management, Patient Billing and Financial Accounting modules.
The system should be able to maintain a Linen data base
The system should maintain the following registers and provide reports for the same
Linen stock register
Daily transaction register for wards
Daily transaction register for other areas
Dhobi pay register
28.5 Purchase Order Processing
The system will facilitate the matching of purchase orders, receiving reports
and Supplier/Contractor invoices
The system will produce exception reports of unmatched invoices
The system will facilitate the matching of purchase orders, receiving reports
and Supplier/Contractor invoices
The system will permit matching for both whole invoice and manual matching
The system will produce exception reports of unmatched invoices
Capability to raise Indents with the following information:
Requesting Department
Indent Date
Indent No.
Material Specifications
Material Code (in case existing)
Quantity required
Unit
Date by which required / Delivery Schedule
Approval of Department Head
The movement of indent to the purchase department and its approval by various
departments should be done through the system and final decision can be taken in hard
copy for records
Facility to maintain approval hierarchy
Ability to raise indents by more than one department
It should be possible to link all indents to Purchase Orders and vice-a-versa
It should be possible to raise a common Purchase Order for multiple indents
Enabling various levels of approvals before purchase request can be converted into an
order
Workflow-based requisition Approval which needs approval from different departments
like engineering division, finance department etc.

Kangra at Tanda
Page 159 of 219

Blocking indent if there is no sufficient budget against the cost center
Maintaining Supplier Quotation File (comparative position)
Comparing "Landed Cost" of various vendors
Maintaining and tracking Requisition History
Provision to generate requisitions automatically for items replenished frequently like
Consumables, based on re-order level
Provision to check the availability of free or reserved stock available at different storage
locations while creating requisitions
Provision to store terms and conditions of the Supplier for material supplies and services
Option for conversion of Requisition directly into PO and Tender into PO
Automatic conversion of purchase requisition to Purchase Orders as per user-defined
criteria (Single Source Supplier)
Facility to generate PO based on the information from the indent and the vendor
database / comparison sheet
Facility to have the option to either pick up standard terms of payment and delivery and
modify the terms to specific requirements while preparing a PO
Facility to print PO on pre-printed stationery
Facility to print draft PO for review before approval
Facility of online approval of PO
Facility to carry out bulk or lot approval of POs
Each purchasing department to have a separate PO number identification
POs should capture the following information :
PO number
PO Date
Item code and description
Unit and Quantity
Rate
Cash discount percentage
Net Amount
Delivery period (date) / Delivery schedule
Other terms regarding Charges (Tax, Packing and Forwarding, Freight, Insurance,
Dispatch instructions, Payment terms) as per company's purchase manual
Facility to link PO number directly to the indent number.
Facility to generate blanket PO with only the required quantity against a particular
requirement
Facility to generate standing POs ( i.e. POs in the nature of term contracts)
Automatic sequential Purchase Order numbering scheme
Maintaining various types of Purchase Orders including Standard PO, Contract, Sub-
Contract Order etc.
Provision to create Purchase Orders for Miscellaneous (Non-Inventoried) Items / job
work
Provision to configure default Order Type by Project/Service / Production Order
Provision to manage multiple Lead Time Components in purchasing cycle
Option to mandate multiple deliveries per item in a PO /
Maintaining Purchasing Unit of Measurement with conversion factors
Option to create Blanket Orders with value and quantity limits
PO / Blanket Orders and Sub-Contracts can contain one or more items
Tracking shipments by Order Number
Specifying special Purchasing Conditions for an item
Option to add 'Inspection Required' flag on selected items
Option to define separate Due Date per item or job in a single Order
Support for review of PO prior to the release
Tracking PO Status
Sending reminders for Due Deliveries / completion dates of jobs
Creating PO for each division and cost to be allocated accordingly
Option to automatically create and maintain Sub-Contracted PO upon creation of sub-

Kangra at Tanda
Page 160 of 219

contracted work orders
Option to modify order quantity in ongoing parallel Purchase Orders for service jobs.
Provision to define various types of taxes on purchase order
Provision to define 'other charges' like Freight, Insurance, Handling Charges on PO
Purchase order line should show both item price and landed cost
Provision to record and account of Import levies (duties, clearance etc.)
Provision for tracking changes to the purchase orders
Enabling short closure of PO
Creation of a purchase commitment in finance as soon as purchase order is approved
Calculation of landed cost taking into account freight, insurance, customs, clearing cost,
even though the actual invoice is not yet received
Registering Latest Purchase Price for an item
Option to designate Discount by Order and by Order-Line
Option to configure Price / Discount Grades (by quantity and by amount)
Maintaining Effective Dates for Prices and Discounts
Updation of Prices and Discounts (by a fixed amount or a percentage) globally
Placing PO in any currency
Creation of rate Contracts (general, service, by product-class and by product) utilizing
pre-defined Templates
Managing and monitoring of User-defined Contract Milestone Dates
Option to specify Delivery Date and Quantity along with Contracts
Option to create Price and Discount Agreements
Option to define Shipping and Handling Costs alongside a Contract
Option to associate and monitor Delivery Schedule with a Contract
Option to receive Acknowledgement from Vendor upon acceptance of purchase or
release order
Contract History Maintenance
Contract Documentation and Reporting
Contract linked with PO
Option for Centralized or Distributed Purchase Monitoring
Configuring PO Milestones (Internal Lead Time)
Retaining PO Data for audit purposes
Generating Stock Replenishment Orders
Maintaining detailed Purchase Statistics
Specifying and managing a purchase budget department wise / project wise
Procurement is to be linked to purchase budget
Tracking PO History
Maintaining Shipment Notification from vendor in the system
Option to maintain different vendors for material, freight, insurance in same PO.
Facility to verify vendor invoice before actual payment based on PO terms and
conditions and goods receipt
Option to create subsequent credit or debit note to vendor
Set-up a tolerance limit for invoice verification
Management of multiple currencies
Sending Reminder for Overdue Shipments to Vendors via Fax or e-Mail
Auto-Faxing a Purchase Order to the Vendor
Facility to call the PO reference number and pick vendor details and rate information
automatically
Track of purchase order placed against which materials are yet to be received.
Facility to receive part of the total consignment mentioned in the PO
Facility to generate Material Receipt Note (MRN) on pre-printed stationery and updation
of stock ledger
Facility to create a MRN including the following information:
MRN No. & Date (system generated)
PO reference
Vendor Code and name (automatically)

Kangra at Tanda
Page 161 of 219

Supplier Bill No./Delivery challan No. and Date
S No / Description of material / Units
Quantity ordered / received / rejected
Facility to receive goods in a measurement unit different from the measurement unit in
which the order was placed (e.g.; in weight rather quantity) with appropriate conversion
Facility to hold MRN booking in case the actual quantity of goods received is less / more
than a particular amount of value or a certain percentage in quantity
Facility to book MRN for specified items with a variation in both quantity and value of a
specified percentage or amount
Facility to print draft MRN before QC check
Facility to capture the QC check in case of items requiring the same.
Facility to capture quantity rejected by QC against the MRN
Facility to generate a Debit Note to be sent to the vendors for all rejections. The Debit
Note should be linked to the Rejection Note in the system.
Facility to book add-on costs (incidentals) for each line item on the MRN
Facility to use the MRN and authorize credit to vendor account on receipt of vendor
invoice after comparison of terms with PO
Facility to link multiple MRNs to a single vendor invoice and vice-a-versa ( i.e. multiple
invoices from a vendor to a single MRN)
On the validation of invoice details a purchase voucher (or sanction order) should be
generated by the system
Managing Receipt by Project / Location / Lot Number / Plant
Managing Receipt of consolidated POs on a single shipment
Sequential Receipt Numbering Scheme
Option for Rejection of Items
Provision to trigger a notification to quality upon registering the receipt of goods
Provision to block the usage of goods till certified by quality control
Generating Claims for non-conformance receipt and for return of goods
Option to book Invoice upon receipt
Cumulative tracking of Receipts / job completion certificates
Provision to update Purchase Statistics, Financial Accounting and Project Accounting as
per Invoice
Provision for Part-Rejection of received Goods
Interface with General Ledger to increase the Materials Account and Credit Accounts
Payable upon receipt
Enabling seamless integration of purchasing system with Inventory Management System
Purchasing Materials directly for a project
Processing emergency purchases without tendering process
Automatic Intimation to finance department for actual payment to suppliers
Enabling import process
Monitoring payment process based on payment terms established in the PO
Facility to automate incoming invoice management
System should give various option to determine source for any material automatically
System will provide an online collaboration platform with vendors
Vendors will be able to login through vendor portal and see open purchase orders
Vendor will be able to send order acknowledgement through vendor portal on real-time
basis
28.6 Store Management
Facility to define Item Codes under an item group
System should be able to capture minimum, maximum and re-order level for the
inventory.
Facility to transfer material from one location to another
Inventory will be evaluated on standard or moving average basis
Facility to generate Store ledger with the following details for each item:
opening balance (Quantity and value)

Kangra at Tanda
Page 162 of 219

receipts and issues
closing balance (Quantity and value)
Issue of Material from Store
Facility to generate a Demand Note on the system including the following:
Item Code and Name
Quantity and Unit
Purpose (Capital/Repair/Any other)
Project wise
System will capture item issue and online update of stock entries in the system.
Inquiry & Reporting option for various Inventory Transactions (by item-code, item-type,
Production Order, Cost Centre, date of transaction, etc.)
Inquiry & Reporting for Inventory Status (by item-code, type, etc.)
Inquiry & Reporting for Slow Moving and Obsolete Inventory
Tracking items by Item-Code
Identifying and segmenting Type of material movement
Generating bin instructions/labels for the storing of items in the warehouse / storage
areas including bar codes
Enabling vendor consignment stock
Provision for views of inventory balances, in-transit and on-order across all warehouses
and for individual warehouses.
Managing accounting for the return of stock to suppliers
Handling damaged broken and returned material in the warehouse
Making stock requirement predictions based on re-order level, safety stock etc
Flexible assignment of inventory processing by Items (General Usage / Reserved)
Conducting ABC analysis for Items
Provision to adjust or update for differences or conversions in Unit of Measurement
Maintaining Audit Trail of all transactions
Implementing Cycle Count Functionalities
Tracking used / unused material supplied to subcontractor
Managing Inventories of Internally-produced Items
Option to create various alerts like Shelf Life expiry etc
Tracking and controlling Vendor-Wise Inventory
Monitoring and displaying stock
Capturing Item Description in the Inventory Master File
Capturing associated Unit of Measurement in the Inventory Master File
Capturing Lead Times in the Inventory Master File
Provision to scrap material and track them
Option to run Reports / Inquiries on Inventory Status
Enabling Stocking Locations default, fixed, assigned, manual or system-assigned (with
provisions to change the Locations as needed)
Multiple Stocking Locations per Item
Option to store Item by batch or Serial Number and Location
Provision to input unique descriptions, cost information and other details with batches
Display of Resources and Inventory availability by Location
Support for Hard Allocation of Inventory to Project
Automatic de-allocation of Inventory if Items are returned / rejected
Support for User-defined Reservation Criteria for sequencing or creating reservations
Preventing other departments consuming the materials purchased for one department
Support for manual update of Inventory Quantities
28.7 Reports & Analysis
List of Indent with status
List of vendors
List of materials
List of materials vendor-wise
List of Purchase Orders with status

Kangra at Tanda
Page 163 of 219

List of Purchase Orders pending for approval
Monthly purchase value analysis subsidiary-wise
Vendor Evaluation report with marks for different criteria
List of Purchase Order vendor-wise
List of preferred vendors for a particular material
Stock overview of different materials location-wise
Stock Overview of all stocks under a office
Stock with subcontractors
Stock in Transit
List of SRVs
List of pending invoices
ABC analysis of stock
Dead stock or non-moving stock
Consumption report location-wise, area-wise or project-wise
List of obsolete items
Comparative analysis of location-wise inventory and production
Stock overview of scrap location-wise
Conducting Vendor Performance Analysis (on the basis of quality of item / services
offered, delivery / timely completion performance)
Maintaining Vendor Quality Ratings (on the basis of quality of item / services offered,
delivery / timely completion performance and cost /price)
28.8 Administration
The solution should automated government File Processing system.
The solution should enable file tracking
The solution should have capability of Document Management which will organize and
track documents through logical folders
The solution should include workflow capability to move files between approvers within
the organization & outside
The solution should have provision for noting with unique numbering, provides record of
reviews
The solution needs to be configurable for easy implementation rather than development
from scratch.
The solution needs to be available in Hindi.
It should enable new file creation
It should enable customized numbering of files
The solution should have provision for document Storage & Retrieval
The solution should enable file status and action management
The solution should enable department specific workflow.
The solution should able to integrate with digital signature or biometric device.
The file can be moved and shared in a secured manner among different departments
and external stakeholders.
The access should be role-based and on SSO basis
The solution should give provision to create different file types.
The configuration of workflow should be easy and enable drag and drop facility.
It should have the audit trial of file movement.
The solution should have the capability to print digital files
The solution should be integrated with other modules like procurement, finance, human
resource etc.
29. Human Resource Management
29.1 Organization Management
Ability to define organization hierarchy, organization structure of corporate, Regional,
Division, Sub division & Site office etc.
Ability to generate tree structure giving details of all role holders and reporting
employees (defining reporting and reviewing relationship)

Kangra at Tanda
Page 164 of 219

Ability to define various categories of employees across class I,II,III & IV
Ability to define name of functions, sub-functions and positions (should be able to take
into account the existing manning norms for the organization)
Ability to maintain reporting structure (hierarchy of positions)
Ability to support integration of positions with manpower planning to understand
staffing requirements
Ability to create new SBUs, functions & positions
Ability to maintain change in designations due to promotions, transfers (Integrate with
Promotion Module, Transfer Module)
Ability to define multiple organizational structures (positions) and multiple reporting
relationships and integrate with the respective employee data
Ability to restrict making changes in the OM to authorized persons only
Ability to seek confirmation after every change made in the structure, changes to be
made permanent only on authentication by the authorized person.
Ability to define administrative powers for organizational units position-wise
Ability to tightly integrate administrative power definitions to work flows and approvals
Ability to provide reports of total organization hierarchy
Ability to provide reports on list of vacant positions
Ability to provide reports on reporting relationships (Functional, administrative) in a
department.
Ability to generate reports on categories of employees across class I,II,III & IV
Ability to clearly define the hierarchy of Delegation of Power in the organization
Ability to define the policy for outsourcing of manpower
Ability to define all Rules, Procedures, Regulations for outsourced employees.
Ability to store and maintain employee personal data such as employee no., name,
addresses, phone numbers, emergency contact information and email addresses, Bank
Account Details, Passport details etc
Ability to maintain employee's gender, date of birth, blood group, citizenship, marital
status, religion, caste etc.
Ability to maintain an employees education, certifications, degrees and any
endorsements (Professional Membership)
Ability to maintain list of all educational Institutes/Colleges identified by
AICTE/UGC/recognized Universities and provision for updating of the same
Ability to maintain previous employment details like name of the organization, position
held (designation), start/end dates, reason for leaving, last salary drawn, references etc.
Ability to maintain names, date of birth and contact details of spouse, children,
dependents, parents, dependants, nominees under different schemes, etc.
Ability to maintain employee's recruitment category like physically handicapped/
sportsperson /ex-servicemen / specialist / SC / ST / OBC / compassionate
grounds/Others
Ability to update employee's recent photograph and photograph with dependant
Ability to maintain employee's medical details after joining
Ability to maintain employee's health problems, medical history and capture the details
(integrate with payroll for reimbursement amount and health problem details, including
low medical category)
Ability to store caste certification verification & police verification report and detailed
status
Ability to maintain the languages known with details of speak read and writes
separately. Clear indication for the mother tongue
Ability to integrate Organization management with employee master
Ability to maintain details of present designation, salary details, reporting hierarchy.
Ability to maintain history of trainings attended (prior to joining & after joining) like
name of the course, name of the Institution, month & year of training, duration of the
course in days/weeks etc.
Ability to maintain the awards for which nominated / received by the employee
including the name of the award, year of award, in which discipline/field and date of

Kangra at Tanda
Page 165 of 219

receipt of award.
Ability to maintain date of joining, probation period, date of confirmation in each
grade/post
Ability to maintain details of promotion from one grade / scale / discipline to another
including any reappointment through internal selections
Ability to maintain full transfer history of the employee including the current & new
location, nature of transfer (self-initiated / company initiated), date of joining and date
of relieving at different locations etc
Ability to maintain present place of posting including name of the department, cost
centre, present designation, grade etc.
Ability to maintain history of disciplinary actions taken / initiated against the employee
including date of charge, nature of charge etc.
Ability to maintain details of suspended employees (reasons of suspension, time
duration of suspension, restricted privileges etc.)
Ability to change employee job status (Active-Trainee, Probation, re-appointed,
Extended probation, Regular, Contractual, deputation, Suspended, absconding (FIR) &
Exit Resigned, VRS, Terminated)
Ability to date and time stamp all changes in the database enabling data availability on
'as on date/time' basis
Ability to update the data through work flow on real time and online basis with maker
checker concept implemented
Ability to link employee data with the position based standard responsibility
Ability to maintain concurrent jobs for employees with additional responsibilities/special
duties in addition to regular responsibilities (Internal/External)
Ability to link employees with the membership with various Committees (permanent or
temporary) and membership of any professional organization
Ability to update only authenticated data reflected in the employee master on prompt
Ability to maintain employee data with regards to claims, etc
Ability to maintain and view employee leave details
Ability to maintain employee data with respect to PF, Gratuity, etc. and the nominations
for the same
Ability to create organizational chart of all positions and reporting relationships.
Ability to provide restricted access to different classes of employee master data
Ability to maintain the group insurance related details for each employee, like insurance
number, nominee details, amount etc.
Ability to maintain Audit trail of all changes made to sensitive information
Ability to maintain performance appraisal rating of last all years and promotion details
Updating of all information in Employee Master data since recruitment (such as personal
details, addresses, transfers, deputation, change of location.
Ability to process House Building Loan under tie-up arrangement with scheduled
Bank(s).
Ability to issue Release Orders to release the loan money by the respective accounting
unit against sanction order.
Ability to provide details of lien against employees
Ability to provide details of employees applying for higher education
Ability to submit and declare of assets by employees
Ability to record whether an employee is an office bearer of a recognized union or
association with details thereof.
Ability to provide reports on all employee details as per department, class/cadre wise,
location in specified period.
Ability to provide reports on employee counts retired, resigned, suspended, dismissed
or left, per department, class/cadre-wise, superannuating in a specified period
Ability to provide reports on status of details of disciplinary proceedings, time, progress,
status
The system should have mapping of employee to his cadre
The system should allow grouping of employees on functional basis like Doctor, Nurses,

Kangra at Tanda
Page 166 of 219

Paramedical staff, Multipurpose Assistant, statistical etc.
The system should enable compilation of employee numbers by cadre / function /
designation band at any given time.
The system should allow to redefine various definition mentioned above in case
of restructuring
The system should generate unique Employee code
The system should allow editing of the employees master data fields by competent
authority
The system should be able to maintain and retrieve employee records for employee skill
sets, qualification, training attendance, seniority, etc.
The system should be able to define Employee Compensation Definitions including
Salary definition with Basic, HRA, DA & other allowances, Leave Encashment definitions,
Provident Fund details, etc.
The system should be able to identify employees by name, part of name, employee ID,
job position, organization
The system should be able to track the historical record of employees from the date of
joining to the current date.
The system should be able to show the vacancy position in the hospital with drill down
feature up to the departmental unit level
The system should be able to view the vacancy position in different views to meet the
recruitment authority requirements like sub department wise, function wise (Doctor,
Nurses, Paramedical staff, Multipurpose Assistant, statistical etc), cadre wise, etc.
The system should allow sub departments to design the resource requirement plan
The system should allow the department to post the resource requirement plan to
approving authority
The system should consolidate the resource requirement plan.
The system should allow scrutiny / modification of resource requirement plan.
The system should allow feedback from HoDs on finalized recruitment plan.
The system should allow competent authority to finalize the recruitment plan
The system should generate the office orders to respective authorities responsible for
recruitment to specific post
The system should generate notification for inviting the application / office order to
recruitment authority
The system should be able to receive online applications
The system should allow to upload the list of qualified candidates after each round of
screening
The system should show the list of qualified candidates
The system should allow to change the cadre/ designation/ pay scale/ reporting
structure of the employee after getting promoted or demoted
The system should be able to change the role of the employee
The system should be able to show the vacancy position in the state that can be filled
by promotion, with drill down feature up to the departmental unit level
The system should be able to record the retirement date of the employee and update
HR record accordingly
The system should be able to record suspension, termination & retirement of the
employee
The system should be able to freeze all the rights of the suspended, terminated &
retired employee
29.2 Staffing - Manpower Planning
Capability to automate manpower requirement/planning based on competencies, skills,
experience, qualification and other criteria
Capability to analyze the unit-wise, cadre wise, grade wise resources available and
required and do a gap analysis with specific time frame.
Facility to create new posts or modify existing posts through proper approval
Capability to issue alerts before any position falling vacant due to retirement/term of

Kangra at Tanda
Page 167 of 219

temporary or contractual employee getting over
Capability to generate a consolidated manpower plan (Institution-wise/Unit-wise) for
approval through work-flow
Capability to identify critical posts (by function)
Capability to integrate with the recruitment/promotion module for filling up of
vacancies
Facility to include the entire process of recruitment in the system including the budget
involved in it. It may also include other new areas
Facility to define positions for internal or external recruitment (define vacancies based
on sanctioned strength and existing employee strength for each
department/unit/section etc)
Facility to define the requirements for recruitment of deceased dependents
Facility to record the details of the applicants of deceased dependents
Facility to furnish the list of applicants of deceased dependents found eligible for being
called for interview/selection
Facility to carry out recruitment for different grade/rank of employees and Part time
employees
Support vacancy and post based roster system for recruitment
Facility to derive competencies automatically from the job or position competency
requirements into vacancy competency requirements
Facility for managing recruitment for special categories requiring relaxation in norms
Facility to draw recruitment schedule in accordance with the requirement plan
Facility for generating advertisement for recruitment for internal / external candidates
for publication on HRMS portal, Media and websites
Support provision for approval of advertisement from competent authority
Linkage to resumes received from the extranet (careers page on websites or homepages
on external job sites)
Support the resumes to be imported from those sites into the resume database
Facility to receive on-line responses
Facility to attach documents / credentials in soft form as a part of the application or at
any other time as decided by the institution
Facility to auto generate unique identity number for each new applicant
Facility to create workflow for approval of application through various levels
Facility to route recruitments through various levels of approvals and review. Audit trails
of the entire approval process should be available
Ability to re-induct a person into the organization after a gap in service
Facility for generation of call letters for written test/interview with allocation of Roll
numbers (same as unique identity numbers allocated during recruitment phase) and
venue. Should support manual intervention in changing venue/centre subsequently.
Facility to create various competencies and categories them into various competency
types viz., Ability, Skill, Knowledge, etc.
Facility to define the evaluation criteria and generation of results post-evaluation
Ability to track interview results / Applicant's progression
Ability to record payments made to the panel members/invigilators/candidates etc.
Capability to maintain details of the candidates resorting to unfair means
Provision to record comments of interviewers at various levels of interviews
Generation of system driven regret letters and/or offer / appointment letters through
both manual as well as electronic modes (with terms and conditions for appointment)
Ability to issue orders of appointment on contract basis
Ability to issue orders of re-engagement (or extension) of retired officers, on contract
basis with re-employment terms
Ability to issue order on completion of probation period
Facility to maintain checklist for verification and acknowledgement of various aspects
related to joining viz., medical reports, testimonials, other relevant certificates, etc.
Should allow for maintaining a checklist of details to be mentioned in each employee's
personnel file

Kangra at Tanda
Page 168 of 219

Facility to change employment status from probation to confirmed/not confirmed after
one year from the date of joining
Facility to integrate with the Performance reporting of the employee on probation
Facility to attach scanned copy of the police verification certificate and medical fitness
certificate of the employee hired on probation
Facility to generate reports on Recruitment cost incurred/employee and cost per
recruitment agency
Facility to generate report on the time taken by each agency to recruit for a position
Facility to generate reports on the Recruitment & appointment details for each
quarter/year
Facility to generate report on the number of employees confirmed per quarter/year.
Facility to generate reports on the Separation details
Facilitate E-Exit process for employees at the time of exit. For retirement, send reminder
of the retirement date to the employee one year in advance
Ability to maintain case details of the employees reinstated/reappointed after being
terminated
Ability to retrieve details of terminated employees in case he/she is reinstated or
reappointed
Ability to calculate back pay or other entitlements of reinstated/reappointed employees
29.3 Employee Transfer & Promotion Management
Ability to automate Transfer process.
Ability to generate transfer orders
Ability to record the transfer orders cancelled, approved or deferred
Ability to update new designation, change of cadre/class, salary details etc. in Transfer
Database
Ability to generate reports on count of employees transferred in a specified period.
Ability to generate reports on total pending, approved/rejected cases of transfer with
details
Ability to generate report for employees in difficult area/terrain beyond a specified time
Ability to implement Companys Career path for various cadres, streams, grades and
scales
Ability to carry out the entire promotion process through work flows.
Ability to generate single page bio-data report for each employee due for promotion.
Ability to issue order of promotion.
Ability to record request for transfer through employee self-service and indicate
appropriately at the time of transfer exercise
Ability to notify to Promotion Department on their email addresses about the
employees to be promoted.
Ability to record interview ratings of employee shortlisted for promotion
Ability to handle Back Dated promotions with respective promotion policy
Ability to approve promotion list by appropriate ordering / approving authority.
Ability to update new designation, change of cadre / class, salary details etc. in
Promotion Database
Ability to generate Promotion Orders
Ability to record the promotion orders cancelled, approved or deferred
Ability to give input to Payroll Administrator to update salary details on promotion as
per the Promotion Database.
Ability to draw a competency matrix in the system and define the
competencies/skills/roles/responsibilities required at each level/position for the
purpose of promotion.
Ability to intimate the outcome of various stages of promotion (interview, first shortlist
etc.) to the employees through ESS Module
Ability to redefine the promotion process on change of policy
Ability to generate a list of eligible candidates for promotion of different grades and
streams.

Kangra at Tanda
Page 169 of 219

Ability to generate list of pending cases with requirement of particulars
Ability to provide reports on total employees promoted during specific period, category
wise, unit wise, designation wise
Ability to generate seniority list of all officers and staff ( with particulars like dob, doj,
qualifications) on any date/time
The system should be able to view the vacancy position in different views to meet the
transfer authority requirements like sub department wise, function wise (Doctor,
Nurses, Paramedical staff, Multipurpose Assistant, statistical etc), cadre wise, etc.
The system should be able to show the list of employees with specific skill set to assist
the transfer authority in mobilizing them to specific geography in case of epidemic
The system should be able to show the transfer request posted by the employee
to competent transferring authority
The system should provisionally update the resource allocation after formal release of
the transfer order
The system should update the resource allocation after joining of employee at the
transferred location
The system should be able to show the list of employees who has not joined offices even
after release of transfer order
The system should be able to notify the reporting officers transfer proceedings
The system should be able to show the vacancy position in the hospital with drill down
feature up to the departmental unit level
29.4 Succession Planning
Ability to automate the process of Succession Planning
Ability to identify key positions (employees who are retiring in near future) to formulate
the vacancy list.
Ability to take clearance from Vigilance Cell (HoD) for each employee in the Talent
Database to be shortlisted for Talent Evaluation Process
Ability to provide list of employees shortlisted for Talent Evaluation Process
Ability to update Interview Assessment Sheet Format including the rating scale
Ability to update list of Interviewing Authority for each function
Ability to update interview ratings of employees in Talent Assessment Database under
Evaluation Criteria
Ability to update list of top successors for each positions in Vacancy and Talent Database
Ability to define Individual Development Plan (IDP) Database and form for IDP of
successors
Ability to send the IDP to HoD for finalize IDP of successors
Ability to update the status of IDP completion in IDP Database
Ability to update list of Successors of last years
Ability to record history of succession planning process of all years
Ability to provide reports on list of employees due for retirement in near future.
Ability to provide reports on number and details of Vacancies.
29.5 Duty Roster
The system should allow duty to be allotted to staff only in their respective departments
The system should allow contract and daily wage staffs to be allotted duty anywhere
within the hospital premises on a daily basis
The system should have the ability to allocate duties in more than one area per day/shift
The system should have the ability to change duty allocation
The system should have the ability to permit compensatory leave
The system should have the ability to define user defined shift timings
The system should have the ability to designate in special/reserved category
The system should be interfaced with the present biometric attendance system
29.6 Time & Leave Management
Ability to manage on-line application, tracking and approval of various kinds of leave
through workflow logic and self-service.

Kangra at Tanda
Page 170 of 219

Ability to update work schedule/shift pattern of employees
Ability to maintain working hours, weekly offs and national holidays
Ability to define and process overtime allowances cases beyond ceiling limit
Ability to define and process types of leaves: half pay leave, earned leave, casual leave,
study leave, maternity, paternity, child care - all types, special leave, Leave not due etc)
Ability to define admissible leave for employees of all classes
Ability to track attendance and map it with applied leave
Ability to record employee's punch in/punch out details (integrating with access
card/bio-metric machine)
Ability to manually update attendance & leave details of employees in case of
employees to whom access card is not applicable
Ability to correct attendance & leave details of employees
Ability to update half day attendances/leaves in the system
Ability of record keeping and maintenance of historical data
Ability to provide reports on punch in/punch out data
Ability to provide reports on late coming hours (summing up late hours to automatically
debit from employee leave)
Ability to provide reports on total number of admissible leave and actual leaves taken in
a period by an employee
29.7 Travel Management
Ability to automate the process of Travel Request
Ability to define & select calendar and time schedules for travel planning
Ability to define Country/state/city for travel planning
Ability to select type of Travel (Local/Domestic/International Travel)
Ability to select mode of travel (Rail/Air/Road)
Ability to recommend type of Train, Flight
Ability to add number, name, age, department, function of travelers
Ability to select the cost center while raising travel requests
Ability to define approving authority and reviewing authority for
checking/approving/declining travel requests
Ability to select approving & reviewing authority for approval of travel requests
Ability to provide any additional comments before submitting the travel request (lowest
fare / berth preference)
Ability to approve/decline/modify travel request of employees by approving authority
(Link with ESS)
Ability to check status of approval/decline of travel requests
Ability to resubmit travel requests if declined
Ability to notify Travel Desk of approved travel requests submitted
Ability to create request for booking of taxis for Local/domestic Travel
Ability to approve/cancel/modify requests for taxi bookings
Ability to create, change, display, review and release travel advances
Ability to provide expenditure reports for separate cost centres
Ability to provide reports on number of employees for whom travel request has been
approved/declines/modified
Ability to provide reports on all past travel requests with details on travel advance
cleared/per-diem/allowances claimed
Ability to raise request for expenses such as medical reimbursement/travel
reimbursement/stationery/local conveyance etc
29.8 Training & Development (T&D)
The system should be able to view the competencies of the employee in different views
like sub department wise, function wise ( Doctor, Nurses, Paramedical staff,
Multipurpose Assistant, statistical etc), etc.
The system should allow sub departments to design the training plan
The system should allow the department to post the training plan to approving authority
The system should consolidate the training plan and show training catalogue including

Kangra at Tanda
Page 171 of 219

all trainings
The system should allow scrutiny/modification/addition of trainings in training plan by
competent authority.
The system should allow feedback from HoDs on finalized training plan by the training
sponsor
The system should allow competent authority to finalize the training plan
The system should capture the trainings with all required attributes like objective,
target audience with qualification criteria, trainers, tentative cost etc.
The system should be able to show all the scheduled training to the employees
The system should allow enrolment to one or more training from employee
The system should also capture the new training request from the employees which
are not displayed by allowing him to add new training
The system should show all trainings to employee clearly differentiating trainings under
training calendar and requested by his colleagues
The system should show the mandatory trainings for employee with details like
schedule, place trainer etc.
The system should capture the feedback from all employees on training attended. This
should be mandatory and time bound functionality
Provision to define training short-term, long-term training needs and Provision to
capture ad-hoc courses offered by various entities.
Ability to design selection criteria for various in-house/ external trainings especially
higher studies
Grading training institutions by the training dept. professionals based on employee
performance post training
Ability to provide training feedback by the employee supervisor.
Ability to issue letter of permission for undergoing higher studies
Ability to issue permission for acting as examiner/faculty member/guest lecturer in
different technical/management institute
Ability to capture Training Needs of various classes of employees through PMS Form
Ability to capture Training needs of employees met/not met during the quarter/year
Ability to formulate and update annual Training Calendar with list of Training
Programmes, Batch size, target group etc.
Ability to provide input to Finance & Accounts Module for payment to
Trainers/Institutes
Ability to update list of Trainers/Institutes for various training programmes.
Ability to record participant's attendance in training programmes and employees
nominated but did not attend a training programme
Ability to notify HoD/employees about the nomination for training programme
Ability to define and print training nomination letters to be sent to employees for
invitation
Ability to define training feedback & effectiveness form
Ability to manually update training feedback provided by participants in the online
feedback form
Ability to analyze training feedback
Ability to seek nomination from employees/HoD for training programmes not included
in Training Calendar
Ability to capture Training facilities available within the organization
Ability to capture course content of all training programmes along with list of Target
group, batch size
Ability to support the process of Induction Training for new recruitees by integrating
with the recruitment module
Ability to maintain topic/subject wise database of internal & external faculty, number
and details of courses conducted by them quarterly, half-yearly, yearly and cumulative
Ability to maintain training budget (for each category of training) - cost of training
Ability to maintain data for internal training exam and certification obtained by staff
Ability to maintain data on external certifications obtained by staff

Kangra at Tanda
Page 172 of 219

Ability to have online registration, cancellation, reminder, and confirmation of training
classes.
Define the competency inventory for unique roles in the organization across all classes
Ability to add cost centers for self-nominated external training programmes
Ability to select cost centers while raising approval requests for nomination to external
training programmes.
Ability to raise Requisition / Purchase Orders (PO) for clearing professional fees of
Trainers/Institutes/Stationery/Photocopy of training course content/material etc.
Ability to monitor Planned Training against actual training conducted based on user
defined parameters such as number of trainings, budget, participants etc.
Ability to maintain training database with full training history of all employees
Ability to produce individual and departmental training reports.
Ability to provide report with the participant list and total training hours for each
employee during the year
Ability to provide reports on Training Needs not specified by employees in PMS Form
Ability to calculate total Training Cost in a year against the T&D Budget
Ability to provide reports on training programmes nominated for but not attended
during employment (reasons for not attending)
29.9 Performance Management System (PMS)
The system should be able to show the already designed KPIs to managers
The system should display the mandatory KPIs recommended by Management to all the
user of the system
The system should allow the user to design the KPIs to meet his contemporary
monitoring requirement
The system should allow to set the annual targets and long term targets against each KPI
The system should allow user to add or remove the KPIs from his customized view
The system should display the selected KPIs on respective user home page
The system should allow change in the definition of the KPIs
The system should generate the graphical view for showing change in the value of KPI on
selected time scale with reference to the target
The system should allow the user to set his own target for each KPIs with accessibility
limited to him only
Ability to automate the process of PMS
Ability to generate marks on attendance
Ability to capture PMS Policy and customize process to update/edit the policy
Ability to define the structure of appraisal process (each stage of PMS)
Ability to define the various stakeholders in PMS
Ability to define Performance Rating Scale
Ability to help employees select approving authority for PMS
Ability to define the performance appraisal form
Ability to notify/send reminders HoD, PMS coordinating officer & Director HR on PMS
process deadlines
Ability to initiate target setting by employees and his supervisor
Ability to approve target setting by employee's supervisor
Ability to initiate midyear appraisal by employees and record any changes in Targets
Ability to review mid-year performance of employees by employee's senior and record
his feedback and performance ratings
Ability to review year-end performance of employees by employee's senior and record
his feedback and performance rating
Ability to compute annual performance ratings of employees automatically based on
mid-year and year-end performance ratings
Ability to review completion of target setting, mid-year review and year-end review by
PMS Coordinating Officer
Ability to define self-assessment form
Ability to fill Training Needs in the appraisal form by employees

Kangra at Tanda
Page 173 of 219

Ability to approve Training Needs of employees
Ability to provide input to other Personnel Decisions such as Promotion Module,
Succession Planning Module, T&D Module, Performance Linked Incentive, Job Rotations
Design PMS database to capture annual performance ratings of employees of all classes
Ability to record annual performance ratings of employees in PMS Database
Ability to route the Appraisal form / Evaluation sheet through the respective levels for
each of the employees.
Ability to group employees based on categories of performance appraisal ratings
Ability to generate memo letters / mails / workflows for the employee in case of
unsatisfactory performance
Ability to generate report on employee ratings in the last three years
Ability to provide reports on count/list of total employees completing the target setting,
mid-year and year-end appraisal
Ability to provide reports on count/list of total employees for whom target setting, mid-
year review and year-end review has been completed/pending
Ability to provide reports on count/list of employees based on categories of
performance appraisal ratings
29.10 Employee Self Service (ESS)
The system should allow employee to access his personal & professional records
The system should be able to show the various performance indicators related to his
performance
The system should allow to manage the performance indicator by giving access to all
the features listed in KPI sub module
The system should be able to display the pay slip on demand
The system should allow employee to print the pay slip
The system should show various training programs scheduled across the department
The system should allow to perform all the training related task listed in training sub
module
The system should allow to file grievances and offer all the functionality listed in
grievance sub module
The system should allow to manage the dashboard view of critical activities
The system should be single point access for accessing all the functions and features of
the system
Facilitate employee for changes in permanent & correspondence addresses, details of
family members, emergency contact details, contact details, office location, nomination
for various schemes like PF /Gratuity, etc.
Ability to add /update bank information for expense reimbursement, PAN no, passport
details, driving license no. etc
Ability to allow employee to update online through ESS the non-critical personal data
(such as weight, height, etc.)
Ability to provide address proof letter to employer for various purposes
Integrate ESS with Employee Master
Ability to send the employee confirmations after changes are made online
Ability to mark attendance and fill time sheets
Ability to view list of weekly offs, holidays in an year
Ability to apply for leave under the appropriate category and state the reasons for it
Ability to Check the status of leave request
Ability to approve/cancel/modify leave requests by employees
Ability to view accrued leave balances.
Ability to approve or cancel leaves of subordinates
Ability to intimate the controlling officer when an employee goes on unauthorized
absence / returns back from unauthorized absence/ extends leave/ reports in the middle
of the sanctioned leave period
Ability to provide reports to subordinates & HR in ESS on attendance & leave details.
Ability to provide reports to HR and HoD on employees presently on leave in the

Kangra at Tanda
Page 174 of 219

department.
Ability to provide the Manager consolidated status of present/absent employees
working under him/her.
Ability to provide report on attendance details & leave quota/balances
Ability to provide reports on number of employees for whom leave has not been
approved/declined/modified
Ability to check position in the gradation list (Category wise, Grade wise, Class wise)
Ability to view vacancy list & status of vacancy (Filled/vacant/abolished)
Ability to post CVs of references as per the vacancy list
Ability to view department wise manpower strength by HoD
Ability to internally apply for a job and view the status of the application
Ability to record requests by employees for passport/visa /study and outside
employment and permission granted/rejected thereof
Ability to provide report on list of vacancies (filled/vacant/abolished)
Ability to submit / update declarations for Income Tax calculation
Ability to view compensation and benefit details by Employee
Ability to view the Performance Linked Incentives earned during a year
Ability to apply for Loans & Advances and Check the status of approval
Ability to approve loans and advances of employees by appropriate authority
Ability to Check Loan Balances
Ability to display and print pay slip information for each pay period, including gross pay,
taxes, other deductions and net pay, with pay period and year-to-date totals.
Ability to view Income tax computations
Ability to handle making online application for sanction of LTC/HTC/other entitlements
through ESS and approval through workflow.
Ability to apply for medical advance, HTC/LTC/TRANSFER TA/transfer grant/advance/re-
imbursements
Ability to enter and approve general claims and expenses through the system
Ability to track loan requests made by employees and send reminders, Feedback &
Grievances
Ability to view PF accumulation
Ability to provide report on past salary slips & income tax statements
Ability to provide report on expense requests approved/claimed/rejected/paid
Ability to view the training calendar and nominate oneself and subordinate for the same
Ability to approve/Reject the Training requests.
Ability to view history of past trainings attended
Ability to apply for higher education
Ability to record requests by employees for pursuing higher education and permissions
granted/rejected thereof
Ability to provide reports on training calendar of present/past years
Ability to provide reports on training programmes attended during employment.
Ability to provide reports on training programmes nominated for but not attended
during employment.
Ability to fill appraisal documents in the system during each stage of appraisal
Ability to view appraisal documents and provide rating and feedback, view status of
appraisal
Ability to fill Training and Development needs in the appraisal document
Ability to provide reports to HR&A on status of completion of appraisal process during
each stage of PMS
Ability to provide reports of employees based on performance appraisal initiated and
completed, appraisal ratings
Ability to request for VRS (integrate with Employee Master for status of disciplinary
proceedings and HBL)
Ability to make transfer requests by employees
Ability to maintain complete history of employee transfers since recruitment
Ability to record request for transfer through employee self-service and indicate

Kangra at Tanda
Page 175 of 219

appropriately at the time of transfer exercise. Record of such request wherever acceded
to be maintained.
Ability to provide promotion letter/increment letter through the system.
Ability to generate reports on the total number of employees applied for transfers,
number approved/rejected/pending
29.11 Payroll Management
The system should be Rules-Based Payroll Solution for calculation of the pay for various
cadres
The system should be able to Include compensation and benefit plans
The system should be paperless Payroll Processing
The system should be able to include revised compensation plans
The system should show all the information to check and reconcile payroll to competent
authorities
The system should allow integration with HR and Finance function
The system should be able to show complete payment history
The system should show the component view of pay structure
The system should allow to print pay slip on demand
The system should allow for tight integration with Financial Accounting systems.
Ability to centralize the entire payroll process
Audit trails for all system activities.
Support alert features about scheduled dates like receipt of payments.
Provide customizable workflow for all internal processes & approvals associated with
the payroll system.
Provision for TDS calculations (if any) & tracking of TDS payable to the Government
The system may provide for interface to interact/migrate with data available in the
existing system to the proposed ERP
Approval limits for expense reimbursement should be configured based upon the
hierarchy limits.
Provision to allocate cost of employee based on his/her associated cost centers
TDS, PF or any other such returns should be available online
Maintain information of the salary bank account.
Ability to allow for the creation of user defined components of Pay like Recurring and Ad
hoc Allowances, Recurring and Ad hoc Deductions , User Defined Allowances &
Deductions
Ability to allow for the computation of the following elements: Fixed Pay elements
applicable to all employees Like Basic, PF, Special Allowance, Conveyance Allowance
etc.,
Ability to allow restriction of administrative functions to a few select payroll users
Ability to have a data upload facility to upload historical payroll data
Ability to allow the maintenance of slab wise details for statutory elements like Income
Tax as well as user defined element
Provision to calculate reduction in salary based on attendance policy
Ability to allow the following calculation of onetime payment of allowance and / or
deduction: Incentive, arrear, ex-gratia, uniform, lease / conveyance maintenance,
Foundation day, etc, By Amount: enter amount to be deducted or payable, by Days:
enter number of Days for system to compute the amount based on Basic Pay or gross
Pay and/or any other component of Pay, By Percentage: enter percentage for system to
compute the amount based on basic pay or gross pay and/or any other component of
pay
Allow for input of start and end date for recurring payment / deduction (both specific,
and general)
Ability to automatically update Payroll database for changes in employee record without
interfering with payroll processing (e.g. Promotions in the middle of month)
Ability to allow Back dated calculations
Ability to allow provision to suspend Payroll runs or control final settlement processing

Kangra at Tanda
Page 176 of 219

on a case to case basis as well as group basis
Ability to have the provision to run separate bonus/ incentive runs
Ability to have a provision to process Arrear and backdated Payment calculations
Provision to recover advances in subsequent pay periods with a single transaction
Ability to maintain earnings history information (i.e., a record of all pay of all activity) for
each employee for a user-specified period of time.
Ability to support multiple banks or savings institutions per employee
Ability to calculate HRA Rebate
Ability to handle tax exemptions as per the Income Tax Rules
Ability to handle Gratuity Calculations
Ability to handle Provident fund rules like Calculate and deduct contributions according
to the respective Statutory Acts/ Company policy etc, Maintain individual GPF accounts
and generate individual account slip for every financial year
Ability to notify (flag) individuals of any outstanding balances when employee is
terminated (Integrate with ESS in case of E-Exit process)
Ability to record an employee's selection of benefit, retirement and deduction options.
Ability to automatically recover salary advances.
Ability to define multiple payment methods (Bank Transfer/Cheque Payment)
Ability to require approval before a specific payment is made to an employee.
Ability to maintain a salary range for each job family or job class/career band.
Ability to automatically adjust calculations for mid-pay period salary, advanced salary,
and employment actions.
Ability to convert the payroll to an excel or other software formats
Ability to assign work calendar (scheduled work days, scheduled holidays, etc) to one or
more employee groups.
Ability to default standard holiday data, as well as user-defined holiday data.
Ability to create and maintain work calendars over user-defined years.
Ability to provide input to Finance & Accounts Module for salary payment based on
attendance.
Ability to calculate arrears in case promotion is made with retrospective effect.
Ability to support salary fitment on promotion. The fitment made should automatically
reflect in payroll.
Ability to update salary details on promotion, Succession Planning
Ability to Support encashment of Leave, tours and travel and also on retirement with
consequent tax adjustments
Ability to Release of festival advance and other advances against salary.
Ability for Payment of medical reimbursement, allowances, recovery and taxation
thereon
Ability to Support Recovery of club/ union contributions
Ability for Provision of Housing loan or any other loan component to be adjusted
against the employee salary
Ability to Support payment of educational allowance, transfer allowances and any other
user defined allowances.
Ability to allow payroll to deduct the amount due from an employee.
Ability to Define tax rules to determine employees tax liability as per changes India
statutory legislation for actual tax liability of employee
Ability to provide investment declaration form in electronic format. The employee will
be required to fill and submit the form electronically so as to automatically updating of
salary record and tax calculation by the system
Ability to ensure support for major statutory reports / certificates of taxes in the user
defined format
Ability to establish deduction limits for each deduction based on various parameters
like: Employee; Job Classification, Company, Benefit plan, Salary
Ability to reverse deduction to be included in next pay check if incorrectly withheld /
Option with user
Ability to determine deduction amounts by: Amount of earnings, Percent of earnings,

Kangra at Tanda
Page 177 of 219

Number of hours
Ability to apply or stop various deductions based on employee status changes.
Ability to Provide for online ad-hoc calculation of employees pay slip amount
Ability to have the ability to evaluate different scenarios for change in pay-roll
structures.
Ability to display the status of the Payroll calculations
Ability to Post the amount of salary paid for each element of pay for an employee, based
on the relevant GL account code and employee cost centre information to General
Ledger. Financial postings include: Element, Amount, GL Account, Cost Centre
Ability to Post salary payment advice including multiple payment methods such as bank,
cash and cheque to General Ledger
Ability to generate pay slip with following detail:- Taxable and non - taxable
components in separate columns, Tax till date, Calculated, Recovered, Projected, Loan
balances and no. of installments deducted / left, Provident fund opening balance,
interest till date, closing balance etc.
Ability to support calculation of periodic interest and crediting the amount to the
accounts
Ability to perform PF application processing, loan sanctioning, loan disbursement,
modification of loan installments, loan short closure, recovery through payroll, final
settlement during closing/transfer for different type of PF loans
Ability to maintain nominee details and payment to nominee in case of death of an
employee.
Ability to provide PF Returns and other statutory forms.
System should generate all types of reports/registers related to PF management
Ability to allow multiple user-defined messages to be printed on Cheques.
Ability to perform gratuity calculation, provision & accounting employee-wise as per
user defined rules
Ability to perform forfeiture of Gratuity in case of dismissals etc.
Ability to generate gratuity payment cheques
Ability to maintain nominee details and payment to nominee in case of death of an
employee
Ability to have multiple pension schemes so that company's Pension scheme available in
public sector can be incorporated.
Ability to intimate the employees three months before their retirement about their PF
subscription, PF Loan, Gratuity and Pension claim forms etc.
Ability to handle employees joining and going out on deputation / LIEN along with
details like:- Leave salary contribution, Pension, PF, GIS etc, Economic rehabilitation
with nomination & other details
Ability to automate PLI scheme
Ability to capture the time to revisions/edit any changes in the PLI scheme
Ability to generate reports on list of employees based on pay scales
Ability to have provision for generating ad-hoc payroll reports & provision for generating
user defined reports
Ability to generate reports on list of employees for whom system notified error in
payroll run.
Ability to generate reports about percentage of salary increments by employee, by
division, by certain jobs family within all divisions.
Ability to produce reports on employee cost by employee/Organization unit/Job family,
etc.
30. Quality Management
30.1 General
Ability to manage quality information for materials, vendors / suppliers / contractors
etc.
Ability to integrate quality management with cost accounting and allocate costs to
quality processes to capture costs of quality management functions

Kangra at Tanda
Page 178 of 219

Ability for any concerned department from materials, operations, maintenance, finance
across multiple units and locations to view quality management information related to
their respective units
Ability to capture various accepted standards, manuals, templates, reporting
requirements and necessary data in the system and revise them with track of changes
when required
Ability to maintain online Quality Manual to be accessed by personnel across multiple
locations and units
Ability to integrate quality inspection results with performance management, rating
system of rate vendors/suppliers/contractors
30.2 Quality Planning
Ability to plan for resource requirements during annual budgeting exercise (personnel of
various skills, test equipment, lab facilities, outsourcing contracts etc.) for executing QM
functions
Ability to generate all documents (plans, checklists, instruction sheets for
test/inspection, result records, test certificates, reports, MIS etc.) required to carry on
quality management functions
Ability to prepare a Quality Plan which specifies target compositions, desired sizes and
other product specifications of different materials.
Ability to customize standard quality activities workflow as per requirement.
Ability to define various business scenarios related to quality management using
catalogues (by defects / deviations, follow-on actions, tasks, characteristics, attributes,
chemical / physical / mechanical / process properties etc.)
Ability to define additional customized catalogues to capture specific quality
management parameters
Ability to define various inspection / test / analysis characteristics to describe the criteria
for acceptance / rejection / down gradation etc.
Ability to define the inspection / test / analysis methods for each characteristic defined
to standardize and have uniformity of quality management process
Ability to define the inspection characteristics unique to each material being tested, and
also to configure number of measurements per sample.
Ability to define sampling strategy (sampling procedures / sampling schemes / rules of
sampling) at various stages / departments.
30.3 Quality Inspection
Ability to support planned as well as unplanned quality inspections
Ability to define detailed steps in each inspection and assign resources to such steps
with capability of monitoring the completion/ outcome of each step
Ability to capture standard time for inspection, no. of resources required for inspection
and to record actual inspection time by the quality inspectors and consumption of
resources issued to capture costs / variance for conducting quality inspections
Ability to record inspection / test / analysis results against defined inspection lots per
characteristic / attribute as defined in the quality management catalogues
Ability to record defects during quality inspections against standardized defect
categories / codes
Ability to handle in the system acceptance, usage or rejection decisions for the
inspection batch/lot from the results/defects recorded in quality inspections
Ability to conduct inspections at vendor's premises outside the company premise and
recording results of the same
Ability to let 3rd party inspection authorities authorized by customers to conduct
inspections.
Provision for automatic transfer of goods to quality inspection stock so that before
inspection goods will not be used.
Storing incoming materials temporarily for visual and other inspection before creating
SRV.
Provision to reject material and send back to vendor directly from quality module

Kangra at Tanda
Page 179 of 219

Provision to maintain qualitative and quantitative characteristics
30.4 Quality Control
Ability to plan for different types of Quality Certificates, Inspection Reports,
Measurement Sheets, Test Sheets from special test equipments.
Ability to print multiple / single / specified no. of copies of the certificate as per control
defined by the quality management team
Ability to retrieve / print specific test certificates from remote locations through internet
Ability to create daily worksheets / job sheets for individual inspectors / testers.
31. Test Equipment Management
31.1 Ability to manage all pertinent test equipment information and located in different facilities
across different geographies
31.2 Ability to plan / maintain schedules for maintenance and calibration of different test
equipment as per policy / AMC contracts with the OEMs and appropriate notification for the
same
31.3 Ability to conduct calibration of different test equipment and recording the measurements /
results of the same with details of date of calibration / observations / party details
31.4 Ability to maintain a history of calibrations done on different test equipment.
31.5 Ability to initiate and manage repair job contracts issued on 3rd parties who offer calibration
and equipment testing services with relevant integration with finance
31.6 Ability to generate job completion reports, service reports and other relevant MIS
31.7 Ability to conduct testing and calibration of test equipment on a un-planned / ad-hoc basis
over and above planned schedules
32. Financial Accounting
32.1 General
The system should have the ability to support single chart of accounts across
departments/units/programmes etc.
The system should have the flexibility to define complex organization structure
The system should have the ability to provide for numerical and alpha numeric chart of
accounts
The system should allow for account description to be given for each account code in
the Chart of Accounts
The system must permit additions and amendments to the chart of accounts structure
without corrupting existing data at any level in a simple and efficient way; i.e. without
the need to rebuild the chart of accounts.
The system must permit the deactivation of elements so that no postings are possible
(subject to user access controls)
The system must prevent active elements from being deleted; i.e. when there are
postings to the account.
The system should control user access to individual elements and combinations of
account codes, in terms of posting and enquiries/reporting etc.
The system should support various accounting standards and also different accounting
principles
Balanced Financial Statements should be available at various levels within the
organization
The system should support defining of closing activities and tracking of these activities
The system should have the ability to enter recurring entries and accruals.
The system should support electronic bank reconciliation with complete audit trail
32.2 Accounts Payable
The system should be able to handle online data entry for:

Kangra at Tanda
Page 180 of 219

Supplier/Rate Contractor Details
Voucher Entry
Payment Processing
Continuous online display of List and Total Accounts Payable
Supplier/Rate Contractor Details
The system will allow the setting up an "irregular suppliers" account for processing
transaction for rarely used suppliers or one-time suppliers/rate contractors
The system will produce a listing of supplier/rate contractors with no activities for a
specified period of time
The system will allow the automatic of flow of transactions from the
inventory/pharmacy management module
The system will automatically reflect the moment material purchase is made in the
inventory/pharmacy module
The system will have adequate controls to check on duplication of submission of claims
or bills from the inventory/pharmacy module
The system will automatically generate the Material Received Note (MRN) date-wise
under the purchases functionality
To perform accounting audit, the system will inform whether any bills are not
processed at inventory/pharmacy
The system will provide functionality for finance to check for the bills generated but not
presented or settled.
The system will allow the issue and printing of cheques only after proper authorisation
of the bills raised have been done
The system will allow automatic generation of financial statements in cash book and
ledger
The system will automatically record all expenses incurred with details once it is
captured in a transaction.
The system will automatically post in particular patient record at billing all cheques
issues as refund to patients
The system will check for duplicate supplier/rate contractor invoice numbers
The system will validate online the general ledger codes in the Accounts Payable
functionality and all invalid transactions will be rejected
The system will check that the total recorded against various items in the invoice equals
the total invoice sum
The system will automatically post a discount to the correct general ledger account for
discounts given
The system will permit authorisation of a group of invoices in a batch
The system will allow matching of items both invoice-wise and individual items within a
single invoice
On posting the system will automatically update the accounts payable and the
general ledger simultaneously
The system will handle accruals with automatic reversal in the next applicable period
The system will allow the specification of an end date for recurring payments
The system will allow the payment of more than one Cheques for a Supplier/Contractor
The system will allow stop payments of a specific invoice temporarily
The system will allow the payment of invoices as specified without regard to the
scheduled payment date.
The system should provide facility so that ; Interfacing with the general ledger
functionality will allow the Cheque number to be passed to the general ledger to assist
with bank reconciliations
If a posted payment is made void, then the system will allow the general ledger posting
to be automatically be reversed
The system will allow processing of more than one accounting period, which would
typically be previous and current periods
The system will generate a report before the payments are made that will list
payments made to each Supplier/Contractor

Kangra at Tanda
Page 181 of 219

The system will produce comprehensive cash requirements reports by period planned
as per the payment run date
The system will show amounts expected to be paid in all planned payment runs within
a user specified period
All cash requirements reports and enquiries will take into account the projected
payments in respect of goods received but not invoiced
32.3 Accounts Receivable
The system should allow online data entry of customers
The system should allow invoices, credit/debit notes and payments to be entered
The system should generate customer statements at the end of the period
The system should maintain customer balances on open item basis
The system should record adjustments to the Accounts Receivable module that will
include a reference number and reason
The system should track full exposure by customer (i.e. customer credit limit minus
outstanding receivables)
The system should permit authorised users to override customer credit limits
The system should permit credit note entries to update accounts receivable and
sales analysis
The system should allow the handling of internal adjustment (e.g. negative credit notes)
The system should allow partial billing of an invoice amount
The system should maintain daily Accounts Receivables billing control totals with
supporting details
The system should post cash receipts online
The system should display all open customer invoices during payment posting
The system should allow for partial payments to be made
The system should permit the write-off of a receivable amount at the time of
cash application
The system should allow the storing of partial payments and over-payments as
separate open items against the original invoice amount until the invoice is fully cleared
The system should allow reviewing on-line customer aging and other statistic data
such as last payment date, etc.
The system should display online the Billing Statements, including beginning open items,
new charges, credits and payments, ending open balance and aging recap, invoice
number, date and date due, customer name, patients name, and admission number
The system should display the Detailed Aging Trial Balance for each active customer
showing open invoice and AR activity (e.g. payments, debit and credit memos, write-off,
comments) and summary total balance across all customers
The system should maintain Accounts Receivable Invoice Register that includes list
of automated and manually entered invoices with control totals
32.4 Cashbook Management
The system will be capable of maintaining different cash books
The system should provide facility so that ; The cashbook will receive automatic
postings from purchase, sales ledgers and the payroll system, together with manual
batch posting of other payments and receipts
The system should provide facility so that ; The cashbook will be integrated with the
general ledger and the postings will be updated with specified general ledger accounts
and general ledger cash book balances
The system will facilitate bank reconciliation, using bank statements inputs either
manually or automatically
The system should provide facility so that ; The receipts and payments from sales and
purchase ledgers and the payroll will be posted as separate postings
The system should provide facility so that ; An audit trail of all cashbook transactions
will be maintained
32.5 General Ledger

Kangra at Tanda
Page 182 of 219

The system should provide the facility to have multiple, independent general ledgers
The system should allow information to be consolidated within and across general
ledgers for month-end reporting purposes
Each general ledger should be capable of supporting and fully integrating with sales
and purchase ledgers, payroll and cash book
Each subsidiary ledger should relate to a separate control account in the general ledger
Postings to subsidiary ledgers should result in automatic postings to the control
accounts in the general ledger
The system should help in identification of costs with various departments / units /
programmes
The system should be able to identify all the charcteristics or master data for the
different units and departments
Plan and budgets should be supported at unit / department level to track the
performance of the unit / department
The system should allow allocation and apportionment of costs from servicing
departments
Certain Key figures important for the units should also be captured within the system for
reporting purposes
Variance analysis can be done at the unit/department level to check for efficiencies /
inefficiencies
The system should allow capture of costs to a temporary programme or bucket so that
these are tracked separately
The system should allow to capture the costs incurred for construction or acquisition of
an asset before capitalization
32.6 Budget Control
The system should have the ability to capture the budget amounts for the defined
budget heads for each implementation location defined for the programme
The system should have the ability to import or export budget details from / to external
systems electronically ( using spread sheet)
The system should have the ability to navigate within the budget hierarchy (e.g. expand
/ collapse structure, drill down for details)
The system should have the ability to calculate and compare budget versus actual in
terms of amount variance and percentage variance
The system should support multiple iterations of budgets.
The system should associate each budget set with a unique identifier, for audit
purposes.
The system should provide budget cap
The system should have the ability to freeze/ unfreeze budgets.
The system should provide the access controls and data validation control when
uploading budgets.
The system should allow budget information to be exported in the following formats:
Spread-sheets
XML
CSV, ASCII text file etc.
The system should allow budgets to be copied from one period to another from plan
versions
The system should have the ability to revalue budget by percentage and fixed amounts
The system must roll closing balances from one period into the opening balances for the
subsequent period(s).
The system should record the history of changes and preserve the original budget; in all
cases where the budget is modified.
The audit trail should include the username, the date and time of the operation and
data before and after change concerned.
The system should have the ability to have multiple levels of budgeting and reporting.
The system should have the ability to roll-up budgets from the lowest level.

Kangra at Tanda
Page 183 of 219

The system should have the ability to generate budget data on multiple dimensions -
combinations of programme, implementation unit, duration etc
The system should have the ability to provide drilldown for actual versus budget
reporting.
The system should have the ability to reallocate budget items ensuring the reallocation
is maintained in history
The system should provide the flexibility to:
Maintain original budget version and revised budget version
Update the original budget by
Increasing the budget amounts
Reducing the budget amounts
Transferring budget amounts (transfer between locations, transfer
between heads of account etc.)
The system should have the ability to carry forward the budget amounts to the
following fiscal year
The system should have the ability to perform automatic budget availability checks
during transaction posting
The system should have the ability to define budget tolerance limits either as a
percentage or absolute value and trigger warning to all concerned users on exceeding
the limits fixed
The system should have the ability to navigate within the budget hierarchy.
The system should have the ability to specify the sanctioned/released amounts for the
implementation unit for month, quarter, year
The system should facilitate reconciliation of fund transfers from one account to
another
System should have the flexibility to create temporary budgets for non-routine activities
32.7 Expenditure Tracking
The system should have the ability to capture the individual voucher details
(voucher number, budget head, expense details, expenditure amount, date etc)
The system should have the audit trails to log the entire chain of activities performed by
the users across the locations and levels for all the programmes
The system should have the ability to drill down the expenditure data from top-down
The system should have the ability to generate individual location and group-wise
expenditure reports for the programmes
The system should have the ability to generate the budget versus actual comparison
reports for each location and at aggregate level
The system should have the ability to export the expenditure data to the well formatted
spread sheets, word for printing and distribution
The system must provide the functionality to open and close accounting periods to
control posting of transactions into current and/or previous/future periods
The system must allow prior year and audit adjustments to be made throughout the
current year. This must be subject to strict security / access control. All such
adjustments must be also applied to the current year where relevant
33. Technical Requirements
33.1 The architecture should be SOA (Service Oriented Architecture) where all the modules
and interfaces are mounted on the service bus.
The different layers of the solution architecture are explained below:
UI Layer: Users include all the Employees, Business Community (Suppliers, Licensee
etc), Data users (Researchers, insurance companies etc) and patients.
Access Channels and Presentation Layer: The services shall be accessed through
different channels. The portal would be the main access channel for most of the
services.
Security and Access Management Layer: Access management and security are the

Kangra at Tanda
Page 184 of 219

critical components of the solution architecture. Single-Sign-On (SSO) and Role
based access are achieved through the identity assertion, credential management
and directory services components.
Middleware Layer: Service interface components are middleware components
which enables the successful delivery of the requested services to the users. When
user puts any service request, these service interfaces invoke the respective
applications and data returned by this application are presented to the user in a
readable format. Service interfaces are the infrastructure components which can
easily combine and re-assemble services to changing requirements without
disruption.
Application Components: Application components are the actual implementation of
business requirements. It will serve all the functional requirements of the project
including service automation, workflows etc.
Data Access Layer: Applications and users use this layer for the actual data access.
It contains the data access logic.
33.2 The system must support scalability to provide continuous growth. A scalable system is one
that can handle increasing numbers of requests without adversely affecting the response
time and throughput of the system.
33.3 All the solution components must be configured in high availability mode to avoid any single
point of failure.
33.4 The entire system with all subsystems should be interoperable, in order to support seamless
information flow and integration. Operating systems and storage technologies from
several suppliers must interact well with each other. These systems should support the
open architecture solutions such as XML, LDAP, SOAP, etc. where information/data can be
ported to any system, whenever desired.
33.5 An audit trail is a record of actions taken by either the user or the system triggers. This
includes actions taken by users or Administrators, or actions initiated automatically by the
system as a result of system parameters. All information related to all the actions
(Create/read/Update/delete) with date and time, user details should be captured. Reports of
audit trails should be provided.
33.6 The application should have features such as Role based Access, define privilege for different
access, Active directory/LDAP Integration for end user ID identification, Enterprise wide single
sign-on user authentication process, automatic log-off after pre-defined time of inactivity,
two level security systems like RSA Token, etc are required.
33.7 The Vendor shall provide the solution for data warehousing functionality for all data (Master
and Transaction both) so that the data is easily available for querying and analysis.
33.8 The application should be completely web based and have a windows-oriented point and
click interface. It should make extensive use of below functionalities thus making it easy to
use by the users:
Icons
Pull-down menus
Buttons
Check boxes
Radio buttons
List boxes
Customized Screen Captions and layout
Amount of information visible on home screen
User defined color theme
33.9
The solution should support international health standards as mentioned below but not

Kangra at Tanda
Page 185 of 219

limited to:
Health Level 7 (HL7) for messaging and communicating with HL7 compliant systems
International Statistical Classification of Diseases and Related Health problems
Revision ICD 10
33.10 The system should be able to send SMS and or email alerts to patients, staff or
physicians, engineers for status of but not limited to appointments, Investigation /
Endoscopy information, medicine timings, Medical equipment malfunctioning etc.
System should be able to define subsets of patients, physicians, staff etc for sending
both predefined as well as customizable alerts/messages by different methods
SMS/emails.
The system should be able to send SMS to vendors for generation of purchase order, re-
order level alerts, etc.
33.11 Following Search functionality should be available at respective screens / modules for the
respective search options.
There should be configurable search options available with end user/administrator so
that user can search data based on specific fields of his choice instead of all fields. The
end user should be able to customize search and associated results format as per their
choice.
Support searching of patient record (e.g., results and transcribed reports) using key
words or phrases.
Physician is able to search patients treated by him.
33.12 The Solution's core functional application to provide configurable functionality that enable
site-specific process & rule definitions along with the ability to upgrade the base solution with
each new release.
33.13 The Solution should also be available with development environment to do customization as
per the requirements.
33.14 The Solution should have and satisfy all the functionalities and processes as natively
integrated applications on a single interoperable open platform and not the integration of
multiple products.
33.15 The Solution should support all Operating Systems - Microsoft Windows, UNIX, Linux and the
proposed integrated application should work on any database like Sybase ASE, MS SQL,
Oracle & DB2, etc.
33.16 The solution should be based on open architecture and compliant with Service Oriented
Architecture, with all the functions as natively integrated applications on a single
interoperable open platform.
33.17 The Solution should provide wide range of security features such as single sign-On (SSO),
Multiple Authentication, Authorization and Integrated User management
33.18 The solution should provide implementation, administration and operational tools seamlessly
integrated with the product.
33.19 The solution should be capable of the following:
Uni-code Compliant
Support N-tier and Internet architecture
Be natively built based on 64 bit operating system
33.20 The solution should have an application architecture which can be integrated with third party
/ legacy applications using the built-in integration tools
33.21 The solution should be able to generate report output directly in excel, PDF, text, XML, HTML
or such other file types.

Kangra at Tanda
Page 186 of 219

33.22 The solution should have Online Documentation, On-line help, Field-level help, Screen-level
help etc.
33.23 The solution should have single sign-on access across applications and should be intuitive,
with easy-to-use user interface that can be accessed via the web interface.
33.24 The solution should have ability to provide concise overview of parameters like configuration
changes, infrastructure usage, performance, required maintenance activities, potential
security issues, status of business flows and diagnostic test results.
33.25 The solution should provide performance statistics for the CPU/ Memory, database,
Application servers.
33.26 The solution should have built in software to manage application software backups and
restore with Source Control and the solution shall have built in software to manage
automated database backups and restore.
33.27 The solution should have the ability to provide Real-time Transaction update and masters
update.
33.28 The solution should include tools / mechanism for System, Database and performance
measurement activities.
33.29 The solution should have ability to:
Support configurable Password policies
Support TCP/IP, HTTPS, HTTP
Provide automatic time out for entry transaction
Configure the number of permissible application log-in attempts
Support role based access control
33.30 The solution should be web enabled with role based access control for all the internal and
external and stakeholders to use it from intranet and internet. Users and administrators
should be able to access the system with any leading web browsers like Internet Explorer,
Firefox, Chrome etc.
33.31 The solution should support multiple levels of integration including synchronous and
asynchronous message based integration with legacy and modern applications.
33.32 The solution should come with inbuilt tools for data migration, upgrades etc.
33.33 The solution should have provision for handling reporting through a built in data warehouse.
33.34 The solution should utilize modern workflow capabilities in streamlining interactions among
functional processes.
33.35 The workflow should be integral part of the solution.
33.36 The workflow should be able to send notifications when manual intervention is required in a
process.
33.37 The workflow should provide a drag and drop GUI based single/ common design tool to
define and alter business process across all modules of the ERP.
33.38 The solution should provide application development tools to support the continuous
development/refinement of application.
33.39 The system will interface with the HR module to get access to the employee details.
33.40 The system will display the list of users and allow each user to be assigned roles,
privileges as well as alter or revoke them.
33.41 The system will allow the system administrator to reset passwords, in which case the user will
be automatically notified using email of this fact and the user will be asked to log in to the

Kangra at Tanda
Page 187 of 219

system within a specified period after which a new password request will need to be made by
the user.
33.42 The system will allow the system administrator to maintain a list of privileges and assign, alter
or revoke rights that may be view, add/create, edit/alter/update, delete/remove/archive to
each form control of every user interface.
33.43 The system should provide facility to impose mandatory requirement of password format,
number of digits etc.
33.44 The system should provide facility so that Passwords will be changed every 90 days (or other
period).The systems will enforce password change with an automatic expiration and prevent
repeated or reused passwords.
33.45 The system should provide facility so that On allocation for the first time as well as reset of
password by the system administrator for lost passwords, the user will be forced to
change the password.
33.46 The system should provide facility so that Passwords must be stored in encrypted forms by
the system and these cannot be retrieved by the system administrator who may only reset
the password.
33.47 The Solution should provide integrated document management system.
33.48 Document management system should be able to store documents related to transactions.
33.49 Document Management system should allow viewing document without requiring any
external tool.
34. Enterprise Portal
34.1 The Institute desires to give their users uniform, role-based, and secure access to any kind of
applications, services, and information. With the enterprise portal, all members employees,
patients, faculty, students, and other stake holders should have a single, uniform point of
access to the applications, services, and information they need for their daily work.
34.2 The system should provide portal behaviour which is requested and expected from Web sites
(browser functionality, indexing by search engines, etc.)
34.3 The system should simplify the customization of the portal look and feel.
34.4 Portals should be able to accomplish scalability and availability through load balancing and
fail-over mechanisms.
34.5 Both hardware and software load balancing should be possible.
34.6 The system should have a portal development kit (PDK) to provide tools for rapid portal
development and deployment.
34.7 The portal run time features should include a portal server, user management engine,
connectors and client frameworks and the unification server.
34.8 The portal should support multiple databases.
34.9 The portal server should follow open standards
34.10 Portal should support task management through workflow automation.
34.11 Portal should support localization features for currency, time and date, depending on where
the portal is accessed from.
34.12 Portal should support optimization techniques like caching.
34.13 Portal should support Unicode.
34.14 Portal should support the embedding of modules or other modular development and
integration capabilities.

Kangra at Tanda
Page 188 of 219

34.15 The portal should have its own navigation tools like the navigation panel and the history bar.
34.16 Portal should support remote performance monitoring.
34.17 It should be possible to connect several systems to one portal environment and to use single
sign-on to log onto these systems.
34.18 Portal should provide Web-based administration of the portal.
34.19 Portal should support anonymous logons.
34.20 Broad set of preconfigured portal content dedicated to the needs of business users (worksets
of information, applications, services) that are Web deployed.
34.21 The system should support for a global or federated portal across different vendors.
35. End to End process Integration
35.1 A key component for IT infrastructure would be integration to make disparate applications
and business partners systems work together consistently to perform business processes,
exchanging information and executing transactions smoothly and operating as if they were a
single system. User should be able to orchestrate the process flow between applications
using message-based and standards-based methods for process integration.
35.2 The adapters that are offered for connectivity along with the product should be used out-of-
box.
35.3 The product should be able to connect to third-party products using standard protocols.
35.4 There should be a framework and tool provided to develop custom adapters in the product.
35.5 The whole middleware solution should be able to run on any database.
35.6 The system should be able to support both asynchronous and synchronous communication.
35.7 The system should be able to provide support for resolving or debugging business service
exceptions.
35.8 The system should provide for monitoring of for individual system components and for the
entire system landscape.
35.9 The system should support the following document formats XML formats, IDoc, EDIFACT,
VDA, RNIF, Flat File (both comma separated and fixed length), XCBL, and CIDX.
5.16 DATABASE MANAGEMENT SYSTEM
b. Installation:
1. COTS Database Management System having following capabilities

Kangra at Tanda
Page 189 of 219

1.1 Must have built-in security means to protect its content (and users) from dangers of
unauthorized users
1.2 Database should support OS clustering to avoid any single point of failure
1.3 Should support a sufficiently rich data manipulation language to allow data manipulations
and information generation
1.4 Detailed documentation shall be provided for Database Management specific to the project
and the applications deployed
1.5 GUI based tool shall be provided to manage, test and tune the database
1.6 The database should be provided with features which will allow securing / encrypting the
sensitive / classified data
1.7 Database licenses should not impose any restriction in case of any customization
requirements on the COTS application platform
1.8 The database should provide with features, which will prevent the DB administrator and
other users to delete / erase the audit trails
1.9 The Backend Server of the Solution should necessarily work on Linux OS.
5.17 PASSIVE COMPONENTS
a. Supply: Supply of the Components including peripherals, completely described in the BID, and
their installation, maintenance at on-site / off-site locations provided by the Institute. All the
material should be of one OEM make only.
b. Installation:
i. Fixing the racks, mounting of components according to the requirements of the Institute.
ii. Splicing of fibres and crimping of cables etc.
iii. User training to the IT staff of the Institute.
d. AMC and Upgrades: The technical maintenance of the Components will be the responsibility of
the Bidder. The charges for such AMC shall be borne by the Institute after the expiry of one year
standard warranty only.
Needed
1.
1.1

COPPER SCS
CAT 6 U/UTP cable, 305 Mtr/Box
Should comply with ANSI/TIA-568-C.2 Category 6 and ISO 11801 Class E channel
standards, ETL verified and same should be furnished with the bid submission
4 Pair Cable, 23 AWG Copper with integral cross -member pair separator for
uniform separation between each pair.
Cable jacket should be CMR rated flame retardant as per UL 1666 or as per IEC
60332-3. It should be certified for 4 connections by independent test labs like
ETL/Delta to meet Cat -6 Standards for parameters like NEXT, PSNEXT, ACR, PS
ACR, FEXT, ELFEXT & Return Loss. 3
rd
party report should be furnished with the
bid submission
Cables should be UL listed for CMR rating and UL certificate for the same should

150 Box

Kangra at Tanda
Page 190 of 219

be submitted with the bid
The cable should have 100 ohm impedance and data transmission frequencies
up to 550MHz or more
1.2 CAT 6 Patch Panels
The 1U 24 port patch panel shall have electrical performance guaranteed to
comply with Category 6 requirements of the standards ISO/IEC 11801:2002,
interoperable and backwards compatible with Cat.5e and Cat.5.
Material: Powder coated steel
Patch panels shall be modular in design and capable of supporting Cat 6
Unshielded and Cat 6A Shielded modules on same port. The same panel should
have the capability of terminating CAT6 & CAT6A Shielded Jacks
Each port should be individually terminated i.e. each Port should be individually
replaceable & provide consistent port-to-port performance.
I/O placement should be modular for better accessibility to the patch cord, High
Density and should have grounding bar or equivalent
The Panel should be UL listed & RoHS compliant.
The Panel should be supplied with Cable Management Bar for dressing at rear
170
1.3 CAT 6 Information Outlets
The cat 6 Information outlet shall have electrical performance guaranteed to
comply with Category 6 requirements of the standards ISO/IEC 11801,
interoperable and backwards compatible with Cat.5e and Cat.5.
The Category 6 Outlets should be PCB based to have a separate signal path to
minimize the crosstalk issues.
Should have IDC to hold conductor and can be terminated at 45/90/180 degrees
Should be heavy-metal free in acc. with EU directives of RoHS
The Cat 6 jack should be supplied with bend limiting boots to provide cylindrical
support to the cables to limit the bend radius at the point of termination and
securing the stress free IDC contacts.
Shall support applications such as Gigabit Ethernet (1000BASE-TX), 10 and
100BASE-TX, token ring, 155 Mbps ATM, 100 Mbps TP-PMD, ISDN, analog and
digital video, and analog and digital voice (VoIP).
Should be certified by third party like ETL or Delta or GHMT.
1500
1.4 CAT 6 Faceplate
Faceplate Material Should be of Poly Carbonate or ABS.
Should be as per UL 94 V0 and have individual shutter for protection against the
dust suitable for RJ45 connection and compatible with both cat 6 and cat 6 A
shielded jacks.
1500
1.5 CAT 6 U/UTP Patch Cords
1 Meter Length
3 Meter Length
Performance guaranteed with Cat.6, Class E (250 MHz) requirements: ISO/IEC
11801 with Cat 6 / Class E performance.
Patch Cords should have FRPVC or LSZH or Lead Free PVC jacket with conductor
diameter copper strand 24 AWG 7/32 conductors.
Patch cords should withstand with -20Deg C to +60 Deg C or better operating
temp.
Patch cord should support applications such as Gigabit Ethernet (1000BASE-TX),
10 and 100BASE-TX, token ring, 155 Mbps ATM, 100 Mbps TP-PMD, ISDN, analog

1500
1500

Kangra at Tanda
Page 191 of 219

and digital video, and analog and digital voice (VoIP).
Should support optional locking mechanism for security purpose wherein the
patch cords can be locked on all RJ45 ports and required Mechanical key to open
patch Cord.

1.6 Patch Guard RJ45 (patch cord lock)
Lockable plug-out protection, can be added at a later date (tool-free) onto the
boot or plug RJ45 patch cords, can only be released with the matching key.
Material: ABS or equivalent.
1500
2.
2.1
Fiber SCS
12 Core Single Mode Loose tube stranded Outside Plant Fiber Cable
The cable shall be armored with a corrugated steel tape, Loose-tube, Gel filled.
The single mode fiber shall be low water peak fiber which meets the ITU-T
G.652D requirements.
The Single Mode, 9/125 micron primary coated buffers OS2.
The cable should have a central strength member and have a tensile rating of
2700 Newton or better and also have the crush resistance of 3000 Newton or
better.
The cable shall be made with flame retardant low smoke zero halogen
compounds.
The cable jacket should be verified by 3
rd
parties for standards like IEC 60332-3
(flame retardancy) & IEC 61034-2 for smoke density.

10 KM
2.2 LC-LC Duplex Single mode patch cord
Patch cord with LSZH jacket, 1.8x3.6 mm, yellow, single mode G652.D 9/125 m
(OS2).
Fitted with both the ends on LC-Duplex PC connector color: blue.
Mounted both sides with LC-Duplex connectors in acc. with TIA/EIA-604-10.
Pre radiused ceramic ferrule with a PC polished end face geometry, connector
qualified in acc. to ROHS compliance Blue connector housing (single mode), blue
duplex clip, material UL 94 V-0, blue strain relief and dust cover.
Patch cord should have attenuation equal or smaller than 0.3 dB.
150
2.3 FOBOT - 24 Port LC Duplex Loaded Fiber Shelf with 24 SM Pigtails, 12 Duplex
Adapters, Labels, Splicing Sleeves & Splice Tray
Shelf shall be used for a combination of splicing and termination of fiber-optic
building cable or outside plant (OSP) cables.
Splicing and patching box, should contain internal fiber rings for ease in routing
the pigtails inside the fiber panel
Material should be of powder-coated sheet steel.
The loaded Splice kit shall be available to provide easy access and administration
of splice trays for fusion splices.
Shelf shall be available in 19 rack or cabinet mountable.
75
2.4 Network Racks
10 U
15U
All Accessories Like Cable Manger Vertical & Horizontal, Power Supply, Cooling
Fans, Front Glass Door (600 x500 Single Section).

50
100
3. Permanently Lubricated (PLB) HDPE Pipe of ISI Brand for laying Optical Fiber
Cable.
3 KM

Kangra at Tanda
Page 192 of 219

5.18 SURVEILLANCE SYSTEM
a. Supply: Supply of the Cameras and NVR including peripherals, completely described in the Bid,
and their installation and maintenance.
b. Installation:
i. Networking of the Cameras i.e. connecting them to the network provided by the Institute.
ii. Interface with the ancillary hardware / software systems proposed.
c. Uptime: The Bidder will ensure an uptime of 97% for the supplied systems.
e. AMC: The technical maintenance of the Cameras will be the responsibility of the Bidder. The
warranty only.
Needed
1. High Resolution Indoor IP Network Dome Cameras having following features
and specifications
32
(Thirty
two
only)
Video standards Dual streaming H.264 and MJPEG selectable
main profile

Sensor 1/3-inch progressive-scan CMOS or better
Sensor matrix PAL 2048 x 1536 or better
Max Resolution 2048 x 1536 or better @ 20FPS
Other Available resolutions 1920 X 1080 @ 25FPS
1280 X 720 @ 25FPS
800 X 600 @ 25FPS
Open Architecture ONVIF Profile S Conformant
Connectors RJ-45, 10BaseT/ 100BaseTX
Video S/N Ratio 50 dB
Sensitivity 0.03(B/Wcolor) Lux (F1.4, 50IRE) or better
Wide Dynamic Range Yes
Mechanical IR Cut Filter Yes (AUTO/MANUAL selectable), with different
set points on lux
White balance 2,500 to 8,000K
Shutter Speed 1/23 - 1/10,000 sec or equivalent/better
Varifocal Lens Upto 3 to 9 mm motorized remote zoom lens
Focus Autofocus
Iris control DC Iris
Unit configuration Via web browser or Configuration Manager

Kangra at Tanda
Page 193 of 219

Firmware Remote update
Protocols TCP/IP, UDP, ICMP, IPv4/IPv6, SNMP v2c/v3,
HTTP, HTTPS, SSL, SSH, SMTP, FTP, RTSP, UpnP,
DNS, NTP, RTP, RTCP
Local Storage Micro SDXC
Audio Dual Channel , G.711 A-law/G.711 U-law
Alarm 1 Input and 1 Output
Ethernet 100BaseTX, PoE, RJ45
PoE IEEE 802.3af compliant
Compliance ONVIF compliant
Analytics Camera Sabotage & Motion Detection
Input voltage PoE, IEEE 802.3 af
Operating Temperature -10C ~ 50C or better
Operating Humidity 15% ~ 85% (non-condensing) or better
Certificates & Approvals UL & CE & FCC
2. Video Recording & Management Software having following features and
specifications

Licences
are
needed
for all
the 32
Cameras
Architecture Software shall be an ONVIF compliant software
Set-up Centralized set-up from each authorized PC
Access via video management software or
integrated Web server and centralized
management architecture.

Storage Media All storage media possible (e.g. HDD / RAID
etc.), depending on operating system

Activation Continuous, Scheduled and Alarm-triggered
Recording Camera name adjustment
Configuration Bandwidth limit, Frame Rate and Video Quality
Recording Content Video data
Authentication Secured recordings / images with authenticated
playback through secured player

Search Parameters Time, Date and Event
Playback Playback via secured player over IP network
(LAN). Simultaneous recording, playback and
back-up, Sophisticated playback features

Expansion The system shall be expandable by addition of
cameras, video servers, storage
devices/capacity, NVR modules etc.

Features Viewing and recording for upto 32 cameras per
server

Kangra at Tanda
Page 194 of 219

VMD Motion Detection activated recording with
speed-up on motion

Event activated recording
Input / output event control, plus manual event
buttons and event list in recordings

Intelligent PTZ control with preset positions;
plus multiple pattern configurations

Remote access: Remote Video access through
client PC over LAN IP network

Individual user profiles, password protection,
logging of user actions by time, location and
cameras

OS Specs: XP Pro, 2003, XP Pro (64-bit), 2003
Server (64-bit); plus Windows 2008 Server,
Windows 7 etc.

Each cameras bit rate, frame rate and
resolution shall be set independently from
other cameras in the system and altering these
settings will not affect the recording display
settings of other cameras. This means that
settings shall be camera dependent and
independent of other cameras

Software should support HD resolution in full
frame recording for all channels simultaneously

Software should support the feature of system
health monitoring by continuously checking the
health status of the system and raising alarms
when any system failure is detected like
network overload, full storage, hard disk error,
power supply failure etc.

Should support digital zoom to both live view
and record view

Should support play or backward play historical
video as 8x/16x/32x or better frame by frame

5.19 SYSTEM INTEGRATION AND SERVICES
5.19.1 The Institute intends to automate its operations for its Healthcare and Education Services through
various Bidders providing hardware, software, network and other allied goods. All the Bidders are
required to provide services for their solutions for three years as per the Request for Proposal
Document. However, to ensure reliable uptime and timely and proper repair / services /
maintenance, the Institute is looking for a service provider, who can act as a single point contact for
these services through liaising among various service providers. The service provider shall also handle
the project management from the start.
5.19.2 The Bidder shall ensure that any complaint lodged by any Institute official or their authorized Agency
for problems related to hardware / software / LAN / WAN or any other item pertaining to the
execution / operation of the project, be rectified efficiently in time. For this purpose the responsibility
of liaising with various vendors / agencies / departments / statutory and regulatory authorities shall
lie with the Bidder including seeking permissions and approvals as may be needed.

Kangra at Tanda
Page 195 of 219

5.19.3 To ensure efficient and effective rollout of the project as well as to ensure smooth operations of the
complete system during the entire project life, the prospective Bidders will be required to work in
collaboration from the beginning of the project with any other Bidder / Agency which has been
entrusted with either full or part of the work under this RFP. A tripartite agreement to this effect shall
be signed among the Institute, the Bidder and each such Bidder / Agency.
5.19.4 The following activities need to be undertaken by the Bidder during project roll out:
Needed
1. Excavating trenches up to a depth of 1 meter in soft soil areas and back filling the
excavated trenches after laying the PLB pipe with protection
1 KM
2. Excavations of trenches upto a depth of 1 meter in hard soil/rocky area and
reinstatement work after completion of pipe laying
500
meter
3. Laying of cables and fiber in the underground trenches provided by the Institute 2 KM
4. Fixing of PVC Conduits and laying fiber / CAT 6 cable 10 KM
5. Fiber Termination / Splicing / Connectorisation per Core 500
6. Fixing / mounting of networking Racks 150
7. Fixing / mounting of Face Plates and IOs 1500
8. Testing and Certification of the Network Entire
fibre as
well as
copper
5.19.5 The responsibilities of respective Bidders have been enumerated elsewhere in this RFP. The
prospective Bidder shall ensure proper synchronization and completion of all the activities assigned
through this tender to other Bidders.
5.19.6 It will be the responsibility of the Bidder to keep the systems in working condition and ensure
compliance of service level agreement (SLA) and various uptime commitments for service
components as per the terms of this Tender.
5.19.7 The Bidder has to provide the details of single point contact viz. designation, address, telephone /
mobile / fax number / website / E-mail address etc. for lodging the complaint.
5.19.8 The Bidder shall ensure timely preventive maintenance of all the systems by their respective vendors,
liaising in this regard shall be the responsibility of the Bidder.
5.19.9 The Institute may continue the service contract with the existing Bidder at the same terms /
conditions and SLA. However, the Institute reserves the right to make amendments to the terms and
conditions of the contract and renegotiate the rates at the time of renewal of the contract.
5.19.10 It will not be obligatory for the Institute to enter into the service agreement if at any time in previous
year there is deficiency in service on part of existing Bidder.
5.19.11 Bidder will have to guarantee timely rendering of services expected. If the Bidder fails to meet the
obligations then the Bidder will have to pay @ 0.5% per hour of cost of the total purchase value for
this component.
5.19.12 The Bidder shall be responsible for resolving any technical disputes amongst various other successful
Bidders.
5.19.13 The Bidder shall be responsible for providing facility equivalent to at least 1 seater Call Centre
365x24x7 to enable logging of problems / complaints during the entire life of the project. Moreover,
the Bidder shall provide 365x24x7 helpline for the purpose. The Bidder will display the toll free
helpline numbers at all the locations of the Institute.

Kangra at Tanda
Page 196 of 219

5.19.14 The Bidder will maintain a logbook of all the problems or complaints and shall submit a copy of such
logbook along with remedial measures taken to the Institute every month.

Kangra at Tanda
Page 197 of 219

6
Bid Proposal Proformae
6.1 BID COVERING LETTER
To:
The Principal,
Kangra at Tanda. H.P.
176 001.
Dear Sir,
1 Terms & Conditions
1.1 I / We, the undersigned Bidder(s), having read and examined in detail the specifications and all
bidding documents in respect of this Request for Proposal do hereby propose to provide goods and
services as specified in the bidding document.
1.2 I / We, the undersigned Bidder(s) having submitted the qualifying data as required in your Request for
Proposal, do hereby bind ourselves to the conditions of your Request for Proposal. In case any further
information/documentary proof in this regard before evaluation of our bid is required, I / We agree to
furnish the same on demand to your satisfaction.
2 Rates & Validity
2.1 All the rates mentioned in our proposal are in accordance with the terms as specified in bidding
documents. All the rates and other terms and conditions of this proposal are valid for a period of 180
days from the date of opening of the bid.
2.2 I / We have studied the Clauses relating to Indian Income Tax Act and hereby declare that if any
Income Tax, surcharge on Income Tax and any other Corporate Tax is altered under the law, I / we
shall pay the same.
3 Deviations
I / We declare that all the goods and services shall be performed strictly in accordance with the
Technical specification, Time Schedule and other terms of the Request for Proposal Document except
the deviation as mentioned in the Technical Deviation Proforma. Further, I/We agree that additional
conditions, if any, found in the proposal documents, other than those stated in deviation proforma,
shall not be given effect to.
4 Bid Pricing
I / We further declare that the rates stated in our proposal are in accordance with your terms and
conditions in the bidding document.
5 Earnest Money
I / We have enclosed the earnest money as required under Section 4.21 of the Request for Proposal
Document. In case of default it is liable to be forfeited in accordance with the provisions enumerated
therein.

Kangra at Tanda
Page 198 of 219

6 Details of cost of RFP Document:
Value
Demand Draft / Cash Deposit Receipt
Number with Date

Name and Branch of the Bank
7 Performance Guarantee
I / We shall submit a Bank Guarantee as required under Section 4.26 of the Request for Proposal
Document.
8 Declaration
I / We hereby declare that my / our proposal is made in good faith, without collusion or fraud and the
information contained in the proposal is true and correct to the best of my / our knowledge and belief
and nothing has been concealed therefrom.
Thanking you,
Yours faithfully,

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 199 of 219

6.2 PROFORMA TECHNICAL BID
S No Description Response
1.
2.
3.

4.
5.

6.

7.

8.

Bidders Proposal Reference No & Date
Bidders Name and Address
Contact Person
Designation
Telephone Number
Fax Number
e-mail Address
Please attach a copy of company incorporation certificate.
Please attach list of your offices in India with addresses thereof:
a. Offices
b. Spare Part Depots
c. Service Centres
d. Development Centres
Please provide details if you have been blacklisted / debarred by
the Government of India or their undertakings, any State
Governments or their undertakings previously. If no, please
enclose an undertaking in this matter
Applicable in case of Schedules A & B
a. If the Bidder is not OEM, Please enclose due authorization
certificate from OEM? (if applicable)
b. Please enclose a list of similar installations done by you
along with their value. Please attach relevant experience
certificates also.
c. Please enclose copies of ISO 9000 certificates in case of the
Bidder as well as the OEM.
d. Please enclose copies of valid VAT / LST / CST / Service Tax
Registration certificates and Copy of PAN Card.
e. Please attach copies of audited Balance Sheets and P/L
Accounts for last three financial years.
f. Is the Bidder or the OEM involved in any Bankruptcy filing
for protection from it? If not, please enclose undertakings
from the Bidder as well as OEM in this matter.
Applicable in case of Schedules C & D
b. Please enclose copy of SEI CMMi level 5 certificate of the
OEM
c. Please enclose copies of valid VAT / LST / CST / Service Tax
Registration certificates and Copy of PAN Card
d. Please enclose copy of a purchase order older than 3 years
e. Please enclose a list of similar installations done by you
certificates also.
f. Please enclose copies of ISO 9000 certificates in case of the
Bidder as well as the OEM
g. Please attach copies of audited Balance Sheets and P/L
h. Is the Bidder or the OEM involved in any Bankruptcy filing

Annexure EG 1
Annexure EG 2

Annexure EG 3

Annexure ETAB 1

Annexure ETAB 2

Annexure ETAB 3

Annexure ETAB 4

Annexure ECAB 1

Annexure ECAB 2

Annexure ETCD 1

Annexure ETCD 2

Annexure ETCD 3

Annexure ETCD 4
Annexure ETCD 5

Annexure ETCD 6

Annexure ECCD 1

Annexure ECCD 2

Kangra at Tanda
Page 200 of 219

9.

10.

11.
Applicable in case of Schedule E
b. Please enclose copy of SEI CMMi level 5 certificate of the
OEM
c. Please enclose copies of valid VAT / LST / CST / Service Tax
d. Please enclose copy of a purchase order older than 3 years
e. Please enclose a list of similar installations done by you
certificates also.
f. Please enclose copies of ISO 9000 certificates in case of the
g. Please attach copies of audited Balance Sheets and P/L
h. Is the Bidder or the OEM involved in any Bankruptcy filing
Applicable in case of Schedules F & G
b. Please enclose copies of valid VAT / LST / CST / Service Tax
c. Please enclose copies of ISO 9000 certificates in case of the
d. Please attach copies of audited Balance Sheets and P/L
e. Is the Bidder or the OEM involved in any Bankruptcy filing
Please attach printed or typed specification / feature sheets of
all the equipment / components / software quoted by You.

Annexure ETE 1

Annexure ETE 2

Annexure ETE 3

Annexure ETE 4
Annexure ETE 5

Annexure ETE 6

Annexure ECE 1

Annexure ECE 2

Annexure ETFG 1

Annexure ETFG 2

Annexure ETFG 3

Annexure ECFG 1

Annexure ECFG 2

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 201 of 219

6.3 DEVIATIONS FROM THE DETAILED TECHNICAL SPECIFICATIONS
Following are the Deviations and Variations from the detailed specifications given in this Request for
Proposal Document. These deviations and variations are exhaustive. Except for these deviations and
variations, all the goods and services shall be provided as per the specifications mentioned in the
Request for Proposal Document.
S No Clause No Page No Statement of Deviations and Variations

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 202 of 219

6.4 DEVIATIONS FROM THE TERMS AND CONDITIONS
Following are the Deviations and Variations from the terms and conditions of this Request for
Proposal Document. These deviations and variations are exhaustive. Except for these deviations and
variations, all the terms and conditions are acceptable to us.
S No Clause No Page No Statement of Deviations and Variations

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 203 of 219

6.5 PRFORMA MANUFACTURERS / DEVELOPERS AUTHORIZATION
Ref. No________ Date: ____________
To:
The Principal,
Kangra at Tanda. H.P.
176 001.
Dear Sir,
Request for Proposal No. RPGMC/IT-01/13 Dated September 30
th
, 2013, for Automation of Hospital
and Medical College.
We_______________________________________ who are established and reputed Manufacturers /
Developers of ______________________________________ having Factory / Development Centre at
______________________________________________________________ do hereby authorize M/s
______________________________________[Name and Address of Vendor] to submit a bid and sign
the contract with you for the goods Manufactured / Products developed by us against the above
Request for Proposal No RPGMC/IT-01/13(A). We hereby extend our full Guarantee and Warranty as
per the clauses of contract based on the Terms and Conditions of the RFP for the goods and services
offered for supply by the above organization in response to your RFP.
Yours faithfully

Name of the Manufacturer / Developer

Authorized Signatory

Note:
This letter of authority should be on the letterhead of the manufacturer and should be signed by a
person competent and having the power of attorney to bind the manufacturer. It should be included
by the bidder in its bid.

Kangra at Tanda
Page 204 of 219

6.6 BILL OF MATERIAL CUM COMPLIANCE SHEET FOR HARDWARE
Following is the exhaustive bill of material with makes and part numbers. Further we abide ourselves
by the compliances indicated as per the desired specifications.
S No Description Make Part Number if
any
Quantity Compliance
(Yes/No)

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 205 of 219

6.7 BILL OF MATERIAL CUM COMPLIANCE SHEET FOR SOFTWARE
Following is the exhaustive bill of material with makes and part numbers. Further we abide ourselves
by the compliances indicated as per the desired specifications.
S No Description
Please copy all the functional requirements specified in this RFP
Response
S: Standard
W: Work around
C: Customization
T: Third Party
N: Not Possible

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 206 of 219

6.8 PROFORMA COMMERCIAL BID
6.7.1 We hereby quote our commercial offer as given below:
S No Particulars (a) Bid Currency Gross Base
Price (b)
Excise and/or
Custom Duty, if
applicable +
Taxes including
VAT as
applicable +
Octroi and other
levies, if
Applicable (c)
TOTAL Price to
be paid
including all
taxes, duties
and any other
levies
(Criterion for
Bid
Evaluation) (b)
+ (c)
1. Schedule A including
warranty for first year

2. AMC for Schedule A for
2 years after the

3. Schedule B including

4. AMC for Schedule B for
2 years after the

5. Schedule C including

6. AMC for Schedule C for
2 years after the

7. Schedule D including

8. AMC for Schedule D for
2 years after the

9. Schedule E including

10. AMC for Schedule E for
2 years after the

9. Schedule F including

10. AMC for Schedule F for
2 years after the

11. Schedule G for 3 years

Kangra at Tanda
Page 207 of 219

6.7.2 The Details of Earnest Money Deposit (If required):
Value ` 1,00,000/-
(Rs One Lakh only)
Demand Draft / Fixed Deposit
Receipt Number with Date

Name and Branch of the Bank

(Signatures)
Date:
Place:
Name:
Designation: Seal

Kangra at Tanda
Page 208 of 219

6.9 RATE SCHEDULE FOR DATA CENTRE, SERVERS AND STORAGE (SCHEDULE A)
S No Item Unit Rate
1.
2.
3.
Modular Data Centre
Blade Chassis
Blade Servers
Number
Number
Number

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 209 of 219

6.10 RATE SCHEDULE FOR CONVERGED DATA & VOICE NETWORK (SCHEDULE B)
S No Item Unit Rate
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

12.
13.
14.
15.
16.
Core Switch
Distribution Switch
Server Aggregation Switch
Edge Switch
PoE Edge Switch
Router
WLAN Controller
Indoor Access Point
Outdoor Access Point
Power Injector
Wireless Management Software with
Required Hardware
Internet UTM
Intranet UTM
Load Balancer
IP PABX
IP Telephone Type I
IP Telephone Type II
12 Core Single Mode Fiber Optic Cable
6 Core Single Mode Fiber Optic Cable
OS1 Duplex Fiber Patch Cord Single Mode 2
metre SC-SC LSZH
metre SC-LC LSZH
metre LC-LC LSZH
24 port, modular Jack Panel with Rear Cable
Tray
Cat 6, UTP Workstation LSZH Patch cord, 7
feet
Cat 6, UTP Patch Cords LSZH for Switch & Jack
Panel
15 U Racks
24 port Configurable Fibre Drawer
Mini GBIC
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number

Number
Number
Number
Number
Number
Number
Number
Meter
Meter
Number

Number

Number

Number

Number

Number

Number
Number
Number

Kangra at Tanda
Page 210 of 219

UTP Cat 6 Cable
UTP Laying in PVC Conduit and fixing
Fibre laying in 1 m deep trench in PVC pipes
Box
Meter
Meter

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 211 of 219

6.11 RATE SCHEDULE FOR AUTOMATION SOFTWARE, COLLABORATION SUITE, DATABASE
MANAGEMENT SYSTEM AND OTHER ANCILLARY SERVERS (SCHEDULE C)
S No Item Unit Rate
1.
2.
3.
Automation Software
Collaboration Suite
Lot
Lot
Lot

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 212 of 219

6.12 RATE SCHEDULE FOR PICTURE ARCHIVING AND COMMUNICATION SYSTEM, RADIOLOGY
INFORMATION SYSTEM (SCHEDULE D)
S No Item Unit Rate
1. Picture Archiving and Communication System
and Radiology Information System
Lot

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 213 of 219

6.13 RATE SCHEDULE FOR HEALTHCARE MANAGEMENT INFORMATION SYSTEM (SCHEDULE E)
S No Item Unit Rate
1. Healthcare Management Information System Lot

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 214 of 219

6.14 RATE SCHEDULE FOR DESKTOPS, TABLETS, PERIPHERALS AND SURVEILLANCE SYSTEM (SCHEDULE F)
S No Item Unit Rate
1.
2.
3.
4.
5.
6.
Desktops
Tablets
Printers cum Scanners
Laser Printers
Surveillance Cameras
Network Video Recording Software
Number
Number
Number
Number
Number
Lot

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 215 of 219

6.15 RATE SCHEDULE FOR SYSTEM INTEGRATION AND SERVICES (SCHEDULE G)
S No Item Unit Rate
1. System Integration and Services Year

(Signatures)

Date:
Place:

Name:
Designation:

Seal

Kangra at Tanda
Page 216 of 219

Annexures
A. BUILDING WISE DETAIL OF SWITCHES AND LOCATIONS
S.No. Name of Building /
Department / Centre
Grid No. of
Data/
Voice/
Video
Nodes
No. of Indoor
Access Points
Required
No. of 24-
Port PoE
Switches
Required
No. of
Locations to be
Connected
1 Library & Computer
Centre
Hospital and
Admin.
150 10 8 5
2 Auditorium Complex Hospital and
Admin.
15 6 2 2
3 Guest House Hospital and
Admin.
35 5 2 2
4 Lecture Complex Hospital and
Admin.
25 5 2 2
5 Parking
Complex/Shopping
Market
Hospital and
Admin.
10 2 1 1
6 Principal's Office Hospital and
Admin.
50 5 2 2
7 Autopsy Complex Hospital and
Admin.
15 4 1 1
8 Bank (Near Gate) Hospital and
Admin.
5 1 1 1
9 Security Gate - at the
Entrance
Hospital and
Admin.
5 1 1 1
10 New Blocks behind
Auditorium (under
construction)
Hospital and
Admin.
25 4 4 2
11 Para Clinic Block Hospital and
Admin.
120 10 15 6
12 Anatomy Block (under
construction)
Hospital and
Admin.
50 8 8 2
13 Mortuary Complex Hospital and
Admin.
5 0 1 1
14 IPH Complex Hospital and
Admin.
5 0 1 1
15 Raj Bahadur Jodhamal
Sanatorium Pulmonary
Diseases (Chest & TB)-
2 Nos. of Block
Hospital and
Admin.
25 8 1 1
16 Super Speciality (Under
Construction)
Hospital and
Admin.
200 20 12 12

Kangra at Tanda
Page 217 of 219

17 Main Hospital and
Academic Departments
Hospital and
Admin.
300 60 30 30
18 Principal's Residence Hostel and
Residential
10 2 1 1
19 Water Harvesting Hostel and
Residential
5 0 1 1
20 Type-V Residences Hostel and
Residential
50 14 7 7
21 Type-IV Residences Hostel and
Residential
50 14 7 7
22 PG Hostel Hostel and
Residential
20 10 6 4
23 Boys Hostels -2 Nos. Hostel and
Residential
20 20 8 4
24 Girls Hostel Hostel and
Residential
10 10 4 4
25 Nursing Hostel Hostel and
Residential
10 10 4 4
26 Internship Hostel Hostel and
Residential
10 10 4 4
27 Type-III Residences Hostel and
Residential
75 18 9 9
28 Type-I Residences Hostel and
Residential
75 8 8 8
29 Type-II Residences Hostel and
Residential
75 8 8 8
30 Type-IV Residences
(Opp. to Principal's
Office)
Hostel and
Residential
5 4 4 4
31 Type-III Residences
(Opp. to Principal's
Office)
Hostel and
Residential
25 4 4 4
32 Vivekananda Doctors
Residences (Two Room
Sets)
Hostel and
Residential
50 16 3 3
TOTAL 1530 297 170 144

Kangra at Tanda
Page 218 of 219

B. LOGICAL CONNECTIVITY AT THE CORE

Kangra at Tanda
Page 219 of 219

C. FIBRE LAYOUT IN THE CAMPUS

ICT Tender Final - Website - Before Prebid

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ICT Tender Final - Website - Before Prebid

Uploaded by

Copyright:

Available Formats

Page 1 of 219

Dr Rajendra Prasad Government Medical

You might also like