Eastern Washington University
APPENDIX E: RFP Response Form
Instructions for Vendor Proposals:

Submit all information on the attached RFP Response Form.

If more that one solution is offered, issue a separate RFP Response Form for each
solution.

All responses to questions should be entered directly on the RFP Response Form.
To make the proposal review process easier, please use a different font type than
the questions (Arial) for your response. In addition the questions are in bold type
face, please DO NOT USE BOLD in your responses.

Proposals must be submitted according to the schedule listed within the RFP
document.

Upon completion, update the table of contents.

Follow the format instructions from the RFP Section 3.10

Several of the questions within this Response Form address VoIP issues. Please
answer these questions even if the proposed solution recommends staying with
digital sets. EWU will then understand the migration path that would be available
for a future VoIP implementation.
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
Table of Contents
I.
Title Page and Signatures ................................................... 1
II.
Contractor Information and Qualifications ..................... 3
A.
B.
C.
D.
E.
F.
G.
Contact Information .............................................................................................3
Vendor Background Information .........................................................................3
Manufacturer’s Background Information ............................................................4
User Group Identification ....................................................................................4
Key Team Member Resumes ...............................................................................4
Project Team Information / Certifications ...........................................................5
Vendor References ...............................................................................................6
III.
Form and Content of Proposals ......................................... 7
IV.
RFP and Proposal Terms and Conditions ........................ 8
V.
Terms and Conditions of Contract .................................... 9
A.
B.
Describe any Contract Responsibilities for the University ..................................9
Escalation Procedures ..........................................................................................9
VI.
Technical Requirements ................................................... 10
A.
B.
C.
D.
E.
F.
G.
Proposal / Solution Description .........................................................................10
Service and Support Questions ..........................................................................10
Telephone System Questions .............................................................................12
Telephone Station Feature Questions.................................................................15
ACD Questions ..................................................................................................17
Attendant Console ..............................................................................................19
Voice Messaging System Questions ..................................................................19
VII.
Pricing ................................................................................. 22
A.
B.
C.
D.
System Configurations .......................................................................................22
Itemized System Costs .......................................................................................24
Maintenance Cost ...............................................................................................25
Post Cutover Pricing ..........................................................................................26
VIII. Contracts / Agreements ..................................................... 27
IX.
Manufacturer’s Continuity Letters ................................. 28
X.
Vendor’s Financial Statement .......................................... 29
XI.
Product Information ......................................................... 30
XII.
Attachments........................................................................ 31
Page -2 -
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
I. Title Page and Signatures
The undersigned agrees to furnish the enclosed items at the price stated, subject to
the conditions and requirements of this proposal. The proposal must be signed by
someone with the authority to legally bind the Vendor.
Bidder Identification and Authorized Signature:
System Proposed:
Firm Name:
Address:
Signed By:
Printed Name:
Title:
Date:
Proposal shall remain in effect for ______ days (Minimum 120) from date submitted.
Please indicate person to be contacted by the EWU concerning this proposal:
Name:
Title:
Telephone:
Fax Number:
E-Mail:
Page -1 -
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
Certifications and Assurances
I/we make the following certifications and assurances as a required element of the
Proposal to which it is attached, understanding that the truthfulness of the facts affirmed
here and the continuing compliance with these requirements are conditions precedent to
the award or continuation of the related contract(s):
1. I/we declare that all answers and statements made in the Proposal are true and correct.
2. The prices and/or cost data have been determined independently, without consultation,
communication, or agreement with others for the purpose of restricting competition.
However, I/we may freely join with other persons or organizations for the purpose of
presenting a single proposal.
3. The attached Proposal is a firm offer for a period of 60 days following receipt, and it
may be accepted by EWU without further negotiation (except where obviously required
by lack of certainty in key terms) at any time within the 60-day period.
4. In preparing this Proposal, I/we have not been assisted by any current or former
employee of the state of Washington whose duties relate (or did relate) to this proposal or
prospective contract, and who was assisting in other than his or her official, public
capacity. (Any exceptions to these assurances are described in full detail on a separate
page and attached to this document.)
5. I/we understand that EWU will not reimburse me/us for any costs incurred in the
preparation of this Proposal. All proposals become the property of EWU, and I/we claim
no proprietary right to the ideas, writings, items, or samples, unless so stated in this
proposal.
6. Unless otherwise required by law, the prices and/or cost data which have been
submitted have not been knowingly disclosed by the Proposer and will not knowingly be
disclosed by him/her prior to opening, directly or indirectly to any other Proposer or to
any competitor.
7. I/we agree that submission of the attached Proposal constitutes acceptance of the
solicitation contents and the attached sample contract and general terms and conditions. If
there are any exceptions to these terms, I/we have described those exceptions in detail on
a page attached to this document.
8. No attempt has been made or will be made by the Proposer to induce any other person
or firm to submit or not to submit a proposal for the purpose of restricting competition.
___________________________________________
Signature of Proposer
___________________________________________
Title
Date
Request For Proposal, RFP 16/07 issued June 5, 2006
Eastern Washington University, Telephony Systems
Page -2 -
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
II. Contractor Information and Qualifications
The Vendor understands and agrees to the requirements of Section 2 of the RFP:
____
Agrees/Comply without exception
____
Agrees/Comply with following clarification:
____
Take exception, as noted below:
A. Contact Information
1.
Principals
2.
Contract Executive
3.
Account Executive
4.
Project Manager
5.
Sales Engineer
6.
Subcontractors:
B. Vendor Background Information
1.
Parent Company (if applicable):
2.
Organizational Type/Structure:
3.
State of incorporation:
4.
Federal Identification Number:
5.
Washington State Business License:
6.
Vendor Experience:
a.
Years company in business in Washington State:
b.
Years firm has represented the equipment manufacturer:
c.
Number of systems installed by the proposing office, same model:
d.
Other products/manufacturers represented:
e.
Additional background information (optional):
Page -3 -
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
C. Manufacturer’s Background Information
1.
2.
Phone System Manufacturer’s Background Information
a.
Manufacturers Name:
b.
Headquarters address:
c.
Original release date of this family of systems:
d.
Release date of this model of system:
e.
Release date of the proposed level/version of software:
f.
Number of systems installed nationwide, same model:
Voice Messaging System Manufacturer’s Background
Information:
a.
Manufacturers Name:
b.
Headquarters address:
c.
Original release date of this family of systems:
d.
Release date of this model of system:
e.
Release date of the proposed level/version of software:
f.
Number of systems installed nationwide, same model:
D. User Group Identification
E. Key Team Member Resumes
Insert behind this page professional resumes, not to exceed two pages
each for the Project Manager, the Sales Engineer, and the Lead
Maintenance Technician (for ongoing MAC work).
Page -4 -
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
F. Project Team Information / Certifications
Name
RFP Response Form
Location
Post-Project?
Role /Tasks
Experience
Page -5-
Certification(s)
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
G. Vendor References
Company Name
RFP Response Form
Address
Contact Name
Telephone
System Type System Size
Page -6-
Date of
Installation
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
III. Form and Content of Proposals
The Vendor understands and agrees to the requirements of Section 3 of the RFP:
____
Agrees/Comply without exception
____
Agrees/Comply with following clarification:
____
Take exception, as noted below
RFP Response Form
Page -7-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
IV. RFP and Proposal Terms and Conditions
The Vendor understands and agrees to the requirements of Section 4 of the RFP:
____
Agrees/Comply without exception
____
Agrees/Comply with following clarification:
____
Take exception, as noted below
RFP Response Form
Page -8-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
V. Terms and Conditions of Contract
The Vendor understands and agrees to the requirements of Section 5 of the RFP:
____
Agrees/Comply without exception
____
Agrees/Comply with following clarification:
____
Take exception, as noted below
A. Describe any Contract Responsibilities for the University
B. Escalation Procedures
Describe the escalation procedures for both the local Vendor and the
manufacturer(s) of the systems proposed. Include contact information
(names, titles, telephone numbers, and e-mail address), preferably in a
chart format showing the relationship between the individuals. Detail
the consideration(s) and remediation(s) provided to EWU if problems
are unresolved or any specifications are not met.
RFP Response Form
Page -9-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
VI. Technical Requirements
The Vendor understands and agrees to the requirements of Section 6 of the RFP:
____
Agrees/Comply without exception
____
Agrees/Comply with following clarification:
____
Take exception, as noted below:
A. Proposal / Solution Description
Briefly describe the high-level architectural design of your proposed
solution to meet the requirements of this RFP. Describe your approach
to the analog requirements; the voice messaging replacement, and the
proposed option for the Spokane Center.
B. Service and Support Questions
RFP Response Form
Page -10-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
1.
What is the Vendor’s contractual definition of a major alarm and
a minor alarm?
2.
State the Vendor’s guaranteed service response time for:
a.
Major Alarm:
b.
Minor Alarm:
c.
Standard M/A/C Service Request:
3.
Describe system’s external hardware and/or facilities that
provide remote alarm notification.
4.
Describe remote maintenance/troubleshooting operations
supported. Include descriptions of any 24 hour response
centers and how the system(s) automatically interact.
5.
Describe the type of support available from the manufacturer,
including escalation of technical issues, remote dial-in access,
auto alarm reporting and response, etc.
6.
Describe the System Environmental and Cutover Requirements.
7.
Describe the System Administrator Training (pricing to be
included in Section VII)
8.
9.
a.
Length of training:
b.
Location of training:
Describe the Recommended User Training
a.
Length of training:
b.
Options for Train the Trainer:
Professional and Technical Assistance from the Vendor
a.
Per hour cost for additional training, beyond the stated
requirements:
b.
Other training options (Computer based, imbedded tutorials, etc):
10. Describe Security Issues
a.
System Security Audits
b.
Password Management
RFP Response Form
Page -11-
Eastern Washington University
Telephony Systems Project
RFP Response Form
c.
Facility Key Management
d.
VPN / Access Security
e.
Firewall / Voice Traffic
RFP 16/07
April 17, 2006
C. Telephone System Questions
RFP Response Form
Page -12-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
1.
Briefly describe the proposed telephone system capabilities and
how the system meets the requirements stated in the RFP.
2.
System Maintenance and Management
3.
a.
What operating system does the software run on? What steps
have been taken to “harden” the OS from failures and security
risks, such as a virus or denial of service attack?
b.
Describe mechanisms or techniques used to ensure system
uptime, including components and levels of redundancy options
available.
c.
Describe how system maintenance functions, such as component
change-outs, trouble-shooting, and loading of new software
revisions are accomplished in the system (procedure overview,
reboot requirements, impact on users, etc.).
d.
Are software upgrades included at no charge during warranty?
Are they free if the client is covered under a maintenance
agreement?
e.
Can the system management tasks be accessed via the LAN?
f.
Can the system be accessed and managed via a standard browser
interface without additional client software loaded at the desktop?
g.
What capabilities do the individual users have to make changes to
their own sets? How do they accomplish this (touch-tone pad,
browser based, etc.)?
h.
Describe how the telephone system measures usage, quality and
performance.
i.
Please state whether the system’s common telephone equipment
components are SNMP compliant.
j.
Describe where the CDR records are stored; is there a requirement
for an external server? If so, is this included or the responsibility
of EWU to purchase?
k.
Are there multiple levels of administrative access for the telephone
system? If so describe.
l.
Attach to the proposal a referenced appendix showing a sample of
the standard traffic/usage reports available.
Trunking, Signaling and E911 Capabilities
RFP Response Form
Page -13-
Eastern Washington University
Telephony Systems Project
RFP Response Form
4.
RFP 16/07
April 17, 2006
a.
Please list the voice communications signaling (SS #7, MGCP,
Q.SIG, etc.) supported by the system.
b.
Will the system be able to provide outbound ANI identification via
the ISDN trunks? Can a different ANI be provided on outbound
calls to 911 other than the outbound ANI supplied on regular calls
(for example, a department number for normal calls, but the user’s
DID number on 911 calls)?
c.
Is the system compatible with CAMA trunks for 911 calls?
d.
Is the proposed E911 location solution integrated into the
switching system or a stand-alone device/server?
e.
How is E-911 supported for “SOHO” locations?
VoIP Capabilities
a.
Describe how the proposed system telephones share Ethernet
ports with data devices, such as PCs. Indicate whether switch
functions (hubs not acceptable) are internal to the telephone or are
provided via an add-on module. What is the maximum speed of the
downstream switch port (for the PC) of the telephone sets?
b.
Are there any options for encryption of the IP voice traffic? Is this
an extra cost item? Does it interfere with call recording / call
monitoring features?
c.
Briefly describe the QoS mechanisms used to ensure that voice
traffic will receive priority over data and other non-real-time
communications traffic.
d.
Describe how the proposed system guarantees against “oversubscription” on WAN links (link bandwidth exceeded by too many
calls and resultant degraded voice quality).
e.
What is the status or future plans within the proposed system for
implementation or support for each of the following?
f.
IPv6
g.
MPLS
h.
List the IP signaling protocols (SIP, H.323, H.248, etc.) the
proposed system supports.
i.
List the VOIP compression / encoding standards (G.711, G.723,
G.729a, etc.) supported by the system. List any right-to-use (RTU)
fees associated with using any of the specific codecs. Also, list
the configuration issues or any restrictions for using a concurrent
RFP Response Form
Page -14-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
mix of codecs (for example, using G.711 on some WAN segments
and G.729 on others).
j.
5.
Does the system allow for users to move their own IP set and
automatically update location identification information? How is
the ANI information updated? Is there a method of reporting user
self moves? Is there an option to prevent users from moving their
own sets?
Describe the music or message on hold (MOH) options, including
the ability to handle multiple sources (mix of recorded music and
messages, live broadcasts, etc) and define which groups (by the
class of service, location, etc.) hear specific selections. What is
the maximum capacity of sources and what hardware / software
and interfaces are required?
D. Telephone Station Feature Questions
RFP Response Form
Page -15-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
1.
Describe the make, model and capabilities of the telephone sets
proposed for the three types of sets described. Also describe
the IP speakerphone set options and the “soft phone” options.
2.
What shows on a display telephone in idle mode (such as time of
day, previous calls, etc)? Are any of these user changeable, or
administrator changeable, including time-of-day?
3.
What shows on the display when a call rings in when the phone
is on-hook?
4.
What will the user see on their display when a second call rings
in while the user is on another call? Will they see ANI on outside
calls? Will they see the name displayed on inside calls?
5.
What will the user see on the display when receiving a
transferred call? What do they see on their display after the call
transfer is complete?
6.
Does the system allow extension numbers to be used without
actual hardware ports assigned (virtual or phantom numbers)?
Are there any limitations to the number of software only
numbers, including right-to-use fees?
7.
Does the system provide a feature for ring-back (re-ring) of calls
on hold when the hold time exceeds a threshold? Is the feature
assignable by set, class of service, or system? Is the ring-back
interval set individually or as a system-wide timer?
8.
Can the user change the information that shows as a button
label? If so, describe how. Can they change any button label
information, or only certain types?
9.
Does the busy-lamp field (BLF) indication feature show the status
of the set or the status of an individual extension
10. Will the BLF buttons also work as a Direct Station Selection
(DSS) button?
11. When extensions are shared between multiple sets, is privacy
automatic? If yes, is privacy release available?
12. What is the maximum number of sets on which a shared line may
appear?
RFP Response Form
Page -16-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
13. If the group call pick-up feature is used to retrieve a call, will the
display show the extension number dialed by the caller (which
line is being picked-up)?
14. If the solution is capable of supporting VoIP, can QoS be fully
implemented with the soft-phones such that call quality can be
assured even when the PC is sending or receiving large data
files? Does the system require any special interface electronics
or unique NIC boards?
15. What is the size of the station specific speed call list?
16. Is there an online directory accessible from the phone set?
17. Do the telephones have the ability to display a system-wide
visual message broadcast to the display phones (for emergency
notices, bomb threat, etc)? Describe the process for creating a
message, and is there an audible notification on the telephone
set?
E. ACD Questions
RFP Response Form
Page -17-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
1.
Briefly describe the proposed ACD design and how it meets the
requirements stated in the RFP.
2.
How does the system provide pre-recorded announcements for
queue groups? Are they internal or external to the system? If
internal, what are the capacity limits per message and per system
or component? How many callers in queue can be
simultaneously connected to an announcement message?
3.
Can the voice mail system provide message only mailboxes that
can be used by the ACD system in place of ACD announcements,
without removing the caller from the queue?
4.
Can the callers be given auto-attendant style options while in
queue without taking the call out of queue or losing its priority?
5.
If a call is delivered by the ACD to an agent not at their desk (call
rings with no answer), will the system pull the call back into the
queue, with priority? What does the caller hear? Does the ACD
busy-out the agent (unavailable mode) or log the agent out of the
group?
6.
Can an ACD supervisor log users in and out of the group
remotely (from the supervisory PC)? Does a supervisor have the
ability to move agents between queues?
7.
Does the ACD system support an embedded pop-up screen for
the agent’s PC that can show queue status? Can it be triggered
by events (such as calls in queue or length of oldest call in
queue)? Are there any imbedded messaging capabilities (instant
messaging style) that would allow supervisors and agents to use
text messages while on calls? List any additional RTU cost for
any of the features mentioned.
8.
Does the system provide multiple music-on-hold or message-onhold capability to allow each ACD group to have customized onhold options for callers in queue? Describe how this is provided
and any additional hardware or software costs.
9.
Can remote IP telephones connected via virtual features such as
“soft-phones” participate in ACD distribution queues? Are there
any differences in features, measurements, or supervisor
visibility?
10. How does the system support queue over-flows or multiple level
queues?
RFP Response Form
Page -18-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
11. Attach to the proposal a referenced appendix showing a sample
of the standard ACD reports available.
F. Attendant Console
1.
Does the system have an option for both hard and soft consoles?
Briefly describe each.
2.
How many concurrent calls can be handled by a single console
position?
3.
If a call is forwarded to a console from an extension or voice mail
how is it identified?
4.
Is there malicious call trace capability from the console?
5.
Are there any restrictions as to where a console can transfer an
inbound call, especially an outside number?
6.
If a call needs to be forwarded to 911, or internal or external
numbers, can the console operator remain on the line until
answered by the remote final destination?
7.
Can the console perform call splitting, where the operator can
privately announce the call before completing the call transfer?
G. Voice Messaging System Questions
RFP Response Form
Page -19-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
1.
Briefly describe the voice mail systems and how they meet the
requirements of the RFP.
2.
What are the options to upgrade to a future implementation of
unified or integrated messaging at the desktop? Describe the
hardware, software and network components/requirements.
3.
Does the proposed voice messaging system integrate with fax
servers or provide fax server capability as part of the system?
4.
Does the system support voice activation of features and
functions (without DTMF input)?
5.
What extra capabilities are available to support mobile or remote
workers? For example, can a mobile employee use the system to
listen to e-mail, respond via voice message to e-mail, listen to
and make entries to their Outlook calendar, etc?
6.
Can the voice messaging system management tasks be
accessed via the LAN?
7.
Can the system be accessed and managed via a standard
browser interface without the installation of additional client
software at the desktop?
8.
Can the messaging and voice communications systems be
managed simultaneously through a single common interface that
integrates both databases? Does this feature reduce the normal
requirement to administer the two systems separately, requiring
some duplicate entries (such as user name)?
9.
What capabilities do the individual users have to make changes
to their own mailbox? How do they make such changes (method
of interface)?
10. How many extensions can be associated with a voice mail box?
11. How does the system provide group and system-wide broadcast
messages and what are the limits to the number of users in a
group or the number of senders to a group?
12. Is there a capability to perform “Bulk” add, delete, or modify
voice mail box’s configurations, or complete voice mail boxes?
13. Describe the capability for time of day control for auto-
attendants.
RFP Response Form
Page -20-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
14. Are there are multiple levels of administrative access for the
voice mail system? If so describe.
RFP Response Form
Page -21-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
VII. Pricing
A. System Configurations
(Refer to Section 7 of the RFP for definitions and instructions)
Main Campus
Request
Equipped
ISDN-PRI Spans
8
1.
CAMA Trunks
Actual
Equip
Request
Wired
10
Actual
Wired
Request
Capacity
12
2
2
4
Analog Stations – Dorm
1200
1280
1500
Analog Stations – Other
900
1000
1150
Station Set - Type 1
500
550
600
Station Set - Type 2
600
700
800
Station Set - Type 3
250
300
350
6
IP Speakerphone
6
Attendant Consoles
5
5
Softphones
12
20
Add-on Modules
15
ACD Users
100
120
150
ACD Supervisors
6
8
10
Announcements (minutes)
20
24
32
“Soft” Extensions
300
400
500
VM Ports
32
36
48
Storage Hours
250
275
320
Mailboxes
1500
1750
2400
VM Ports
24
24
24
Storage Hours
120
120
150
Mailboxes
2500
2800
3200
Actual
Capacity
Voice Mail System (Main)
Voice Mail System (Dorm)
RFP Response Form
Page -22-
Eastern Washington University
Telephony Systems Project
RFP Response Form
2.
RFP 16/07
April 17, 2006
Spokane Center
ISDN-PRI Spans
Request
Equip
1
Actual
Equip
Request
Wired
1
Actual
Wired
Request
Capacity
2
Analog CO Ports
2
4
8
Analog Stations
24
24
36
Station Set - Type 1
20
24
32
Station Set - Type 2
20
24
32
Station Set - Type 3
3
6
12
Attendant Consoles
0
0
1
Add-on Modules
2
ACD Users
12
16
20
ACD Supervisors
Announcements
(minutes)
“Soft” Extensions
2
2
3
6
8
12
20
24
32
VM Ports
8
8
8
Storage Hours
16
16
20
Mailboxes
80
100
120
Actual
Capacity
Voice Mail System
RFP Response Form
Page -23-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
B. Itemized System Costs
Item Description
TOTAL
RFP Response Form
Qty
Item
Cost
Extended
Cost
$
Page -24-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
C. Maintenance Cost
1.
Maintenance Coverage Description
2.
Subsequent Maintenance Costs
System Components
Desktop Components
Software
Voice Message System
$
$
$
$
per month
per month
per month
per month
TOTAL
$
per month
Indicate if rate is fixed or if rate is linked to a CPI-based increase.
3.
Optional On-Site Technician Contract
Monthly Rate for 4 hour/day
MAC & Maintenance Tech
(Committed to EWU every day)
Additional Technician Time
4.
$
per month
$
per hour
Additional Maintenance Costs
Crash Kit Components
Security Audit
Technology Review
$
$
$
(one-time)
per year
per year
Indicate if rate is fixed or if rate is linked to a CPI-based increase.
RFP Response Form
Page -25-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
D. Post Cutover Pricing
Provide below a list of all commonly ordered add-on equipment, software
packages, right-to-use charges, services, components, or additional
options.
The following prices become effective _____ days after date of last cutover.
The rate charged will be (check one):
_____ the individual amounts shown below for each item or
_____ will be charged at ______ per cent discount off of nationally
published price lists.
The above discount rate or the following prices are good until ___________.
(Specify date)
Item Description
TOTAL
RFP Response Form
Cost
$
Page -26-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
VIII. Contracts / Agreements
Submit a copy of any proposed purchase agreements, software license
agreements, or maintenance contracts in this section.
RFP Response Form
Page -27-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
IX. Manufacturer’s Continuity Letters
Place the manufacturer’s letter of continuity, as described in RFP
Section 2.4, in this section of the response.
RFP Response Form
Page -28-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
X. Vendor’s Financial Statement
Place the vendor’s financial statement, as described in RFP Section
2.5, in this section of the response.
RFP Response Form
Page -29-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
XI. Product Information
Use this section for brochures and pre-printed materials that describe
the individual systems or products. Include material on proposed new
telephone sets.
RFP Response Form
Page -30-
Eastern Washington University
Telephony Systems Project
RFP Response Form
RFP 16/07
April 17, 2006
XII. Attachments
Use this section for any other information, if applicable or necessary.
RFP Response Form
Page -31-