SOUTHEAST MISSOURI STATE UNIVERSITY CONTENT MANAGEMENT SYSTEM SOFTWARE/MAINTENANCE REQUEST FOR PROPOSAL 4691 INTRODUCTORY AND BACKGROUND INFORMATION 1. This document constitutes a request for proposals from qualified vendors to provide the following goods and services for Southeast

creaturewoodsInternet and Web Development

Dec 8, 2013 (3 years and 8 months ago)

70 views


2

SOUTHEAST MISSOURI STATE UNIVERSITY

CONTENT MANAGEMENT SYSTEM SOFTWARE/MAINTENANCE

REQUEST FOR PROPOSAL 4691


INTRODUCTORY AND BACKGROUND INFORMATION


1.

This document constitutes a request for proposals from qualified
vendors to provide the following good
s and services for Southeast
Missouri State University.



1.1

Provide for the purchase
of a content management software system
(hereinafter referred to as “CMS”) for the University’s Web
presence

and assist with the installation
.


1.2

Provide training on the CMS sof
tware.


1.3

Provide for the technical support and maintenance of the above
mentioned software after the purchase.


2.

Southeast Missouri State University (hereinafter referred to as

“University” or “Southeast”) is a regional comprehensive university
loc
ated two hours south of St. Louis and two and a half hours north
of Memphis, Tennessee, on Interstate 55 in Cape Girardeau, Missouri.
Southeast enrolls approximately 9,500 students and has extended
learning centers in Kennett, Perryville, Malden, and Sike
ston,
Missouri. In addition, Southeast has an international presence with
approximately 300 students from countries around the world.


3.

Stamats Communications, Inc., a comprehensive research, marketing,

interactive media, and publications company which

serves educational
institutions, recently conducted a Web site audit of Southeast’s Web
presence. They recommended the University purchase a CMS product
that will assist in updating and maintaining the current Web site.
In addition, the University will
produce a new external Web site and
upon completion of that site, the plan is to merge and re
-
launch the
new site together with the current site.


3.1

Currently, there are more than 10,000 pages and forms on the

Southeast Web site with more than 100 conte
nt authors and

administrators.


4.

Any offeror with questions is strongly encouraged to contact

Sarah J. Steinnerd, Purchasing Manager, at (573) 651
-
2588. Every
attempt shall be made to ensure that the offeror receives a prompt
response. However, the o
fferor is strongly encouraged to submit all
questions no later than seven (7) calendar days prior to the RFP
closing date.


5.

The contract awarded as a result of this Request for Proposal will
allow for a one (1) year contract with the option of three (3)

additional one
-
year periods in accordance with all terms and
conditions as specified herein.


6.

Although an attempt has been made to provide accurate and

up
-
to
-
date information, the University does not warrant or represent
the background information pro
vided herein reflects all
relationships or existing conditions related to this Request for
Proposal.


3

SOUTHEAST MISSOURI STATE UNIVERSITY

CONTENT MANAGEMENT SYSTEM SOFTWARE/MAINTENANCE

REQUEST FOR PROPOSAL 4691


TECHNICAL SPECIFICATIONS/SCOPE OF WORK


The contractor must supply a content management software system that meets or
exceeds the following specifications.


1.

System Architecture


1.1

Must provide automated workflows that route content through an

approval process, but also allows for editin
g at each level.

1.2

Must demonstrate compatibility and ability to integrate with

existing Web infrastructure products, which includes Microsoft

Windows NT, 2000, and XP, Microsoft IIS and Microsoft SQL.

1.3

Provide a browser
-
based interface for system
administration.

1.4

Must be compatible with Web page layout tools such as

Dreamweaver and Frontpage and provide an integrated page

layout tool.

1.5

Must support the following protocols: HTTP, HTTPS and FTP.

1.6

Must be compatible with common browser ty
pes and versions.

1.7

System must be easy to install as compared to other systems

in the marketplace.

1.8

System must be easy to configure and maintain for those on

campus unfamiliar with CMS.

1.9

Must provide navigation features that place the content

in its

proper location on the site and ensure that links are updated

as necessary.

1.10

Must provide for adequate security levels and audit trails to

protect the integrity of the content.

1.11

The CMS must publish to multiple formats including, but not


limited to, HTML (Web), printed, PDF, hand
-
held (WAP),

text
-
only, handheld PCs, etc., and should support the

possibility of additional formats as new standards evolve.

1.12

Must provide for site export (static portable image).

1.13

Must provide ability

to restore individual pages/components

from backup or versions.

1.14

Must provide ability to integrate with E
-
Commerce, ListServer,

and other interactive Web applications.

1.15

Must provide templates that can be customized.

1.16

Should contain ability t
o integrate with Microsoft Windows

2000/IIS security for user authentication and system controls.

1.17

Must support 128
-
bit encryption or higher.

1.18

Must provide a way to link content provider to specific pages

or applications (personalized menu).

1.1
9

System must have ability to scale easily and manage anywhere

from 10,000 to 1 million individual items.

1.20

System must have ability to process a posting of a simple

global change and a template change(s) to every page on the

site.

1.21

System must h
ave ability which allows Southeast to customize

the system to meet applicable needs and to integrate with other

backend systems.

1.22

Site must be hosted on campus servers and not on external

Web/Internet site.


4

1.23

System must provide basis for making
all Web pages ADA

compliant and accessible.

1.24

System must be accessible to University employees with

disabilities.


2.

Content Architecture


2.1

The CMS product must have the ability for non
-
technical staff

to create, edit, manage and finally pub
lish a variety of

content (such as text, graphics, video, etc.), whilst being

constrained by a centralized set of templates, rules, process

and workflows that ensure a coherent, validated Website

appearance.

2.2

Must have spell check for content editor
s.

2.3

Authoring must be style
-
based, with all major formatting

applied during publishing phase.

2.4

Must have ability to identify the original content author and

department as well as log and track content changes and

content approvals.

2.5

Must pr
ovide an automated method for routing content for

approval, allowing for either single user or multiple levels

of approval before content is promoted to production.

2.6

Provides ability to automatically push approved and scheduled

changes to the product
ion environment dynamically (as soon as

they are approved), as well as roll back changes to a given

version or point in time.

2.7

Supports automatic notification of approvals/rejections to

contributors and moderators (e.g. via e
-
mail).

2.8

Should be abl
e to support the promotion of content to multiple

load
-
balanced production servers (farms) in an automated

manner.

2.9

Provide for either assigned ownership and/or shared ownership

of individual pages or groups of pages.

2.10

Provide flexible updates to

the created pages once required

approvals are complete (e.g. daily, hourly, instant, scheduled

or requested).

2.11

System helps enforce policy and maintain standards by

constraining content providers to allowed behavior (e.g.

constrains the use of HTM
L functions such as “mailto:” and

forms).

2.12

In order to achieve high quality in every format, it is

critical that content be separated from presentation at the

time of authoring, thus allowing distinct

style
-
sheets/templates to be used for each outp
ut.


3.

Content Development and Operations


3.1

Must provide time
-
based management of content that allows

authors to specify when content should be published and when

it should be removed from the site.

3.2

Must provide e
-
mail reminders to notify users w
hen it is time

to approve, update or edit content.

3.3

Must provide a set of sample templates or sites to assist in

conversion and development.

3.4

Must allow for content and component inventory and re
-
use

where an item is changed only once and those ch
anges are


5

propagated throughout the site.

3.5

Provide the ability for a content creator to customize the

content within the template, e.g. uses of images, tables,

photographs, etc.

3.6

Support a secure and segregated development, testing, staging

and p
roduction of Web environments, and provide a mechanism

or framework for moving updated content through each

environment.

3.7

Provide a method for developers, reviewers, and approvers to

test, verify, and preview changes in a real
-
time fashion, in an

is
olated environment, incorporating those components needed

from the production environment

to get a complete view of the

impact of their changes.

3.8

Provide a facility to allow for concurrent development of

content or functions (e.g. locking, check
-
in/
checkout and

version control).

3.9

Provide for reviewer ability to merge page changes in

situations where multiple authors are submitting changes to a

common page.

3.10

Provide a tool that automates or simplifies the creation and

maintenance of Metatag
s and Metadata.

3.11

Allows for full content searching of all managed components,

including data bases or provide integration with a third

party
-
product that provides this ability.

3.12

Provide for automated link verification within the site.

3.13

Provid
es ability to auto
-
generate “Tables of Contents” or

“Site Maps”.

3.14

Provide ability to auto
-
generate navigational structures for

the site.

3.15

Provide facilities and methodologies that allow for a

conversion from the existing site structure to the ne
w product

set.

3.16

Must allow for the archiving of an entire site, and provide a

facility to restore the archived site from a specific version.

3.17

Provide ability to easily generate “printer
-
friendly” versions

of content pages.

3.18

Provide interface
s for streaming media (e.g. Quicktime,

Realtime).

3.19

Allow parameters to be passed from an HTML page to a Web

application.

3.20

Support both upload and download capabilities.

3.21

Support and/or facilitate Multiple Languages.

3.22

Support connectivity
with existing legacy data sources.

3.23

Allow content to be shown in a specific sort order, (i.e.

reverse chronological by input date until expiration date).

3.24

Accessibility


support screen reader technologies.

3.25

System must allow for dynamic chang
es to the structure of

information on the site (architecture).

3.26

System must allow for re
-
categorization of existing data.

3.27

System must allow for application
-
like collections of related

information to be developed within the system (e.g. FAQs).

3.
28

System must allow users to bookmark a specific URL in order to

return to specific information on the site.

3.29

System should support automatic URL redirection of alternate

domain names to a specific location within the site.

3.30

System must provide
automated HTML cleanup.


6

3.31

System must allow for the parallel use of managed and

non
-
managed content (e.g. static Web pages housed in

directories outside of the CMS).

3.32

Support multiple site “views” reusing same information with

emphasis varying ba
sed upon the role of the site visitor.

3.33

Provide a viewable library of available resources such as

graphics and icons that are labeled with a description, file

format, file size, and standard clauses such as “Requires Adobe

Acrobat Reader.”

3.34

Must

have ability for remote content contributors to access

CMS.

3.35

Must have ability to drag and drop, or cut, copy and paste

from any Windows
-
based application.

3.36

Product must allow customized URLs (Web addresses), instead of

a combination of letter
s and numbers that would not make sense

to the end user.


4.


Site Reporting


4.1

CMS must allow comprehensive usage statistics to be gathered,

including most popular pages, least accessed pages, daily

usage, search engine usage, etc.

4.2

Provide an ad
-
hoc report that identifies links referring to a

specified page or content block (area). For example, if the

need arises to remove a Web page, editors need to know the

number of pages that are linked to the removal page as removal

will have an impact o
n other linked pages.

4.3

System must provide ad
-
hoc approval status reports.


5.


General Requirements




5.1

Must provide a user interface that allows non
-
technical staff

to learn to use the system without large amounts of training.

5.2

Must support

the following types of content: HTML, XML, SMTP,

Excel Spreadsheets, Active X Controls, JavaScript, DHTML, CGI,

Cascading Style Sheets, Word Documents, Real Player, ASP, JSP,

Java Applets (.class), Graphics (.jpg, .gif, .tif, .png),

Audio/Movie (.wav
, .mvr), Text (.txt), Icons (.ico), Photoshop

data file (.psd), PowerPoint (.ppt), and Perl.


6.

Installation: The contractor must provide the University with all
necessary support and technical assistance required to install the
delivered software.



6.1

If the University requires on
-
site installation of the software,

the contractor shall be reimbursed as per the prices contained

on the Pricing Page of this document.


7.

Training: The contractor must provide all training required for
successful su
pport and operation of the system.



7.1

The contractor must provide comprehensive training within thirty
days of installation. The contractor shall be reimbursed
separately for such
.



7

8
.

Warranty: The contractor must provide a one
-
year warranty to include
software upgrades, revisions, etc. The warranty shall commence
upon
written University acceptance of the software system.




8.1

In addition to the warranty, the contractor must provide

telephone support for technical issues.


9.

CMS software maintenance: The contractor shall provide annual

maintenance upon expiration of the aforementioned warranty. At a

minimum, the m
aintenance shall include
telephone
support, software

upgrades, revisions, etc.


10.

The contractor must provide telephone support as identified

above. Such telephone support must be available Monday through Friday
from 9:00 a.m. through 4
:00 p.m. central time, excluding University
holidays.



10.1

The contractor should provide a toll free number for use

by the University.






8

SOUTHEAST MISSOURI STATE UNIVERSITY

CONTENT MANAGEMENT SYSTEM SOFTWARE/MAINTENANCE

REQUEST FOR PROPOSAL
4691


GENERAL CONTRACTUAL REQUIREMENTS


This portion of the RFP pertains to the offeror selected for final contract
award (“contractor”).


1.

The contract shall not bind, nor purport to bind, the University for
any contractual commitment in excess of the origin
al contract period,
which shall be from the date of award through one year after the
University’s written acceptance of the CMS software. The University
shall have the right, at its sole option, to extend the contract for
three (3) one
-
year periods, or an
y portion thereof. In the event that
the University exercises such right, all terms, conditions, and
specifications of the original contract, as amended, shall remain the
same and apply during the extension period.



1.1

If an extension option is exercise
d, the contractor shall agree
that the price(s) stated on the Pricing Page shall not be
increased in excess of the maximum percentage of increase for
the applicable option.


1.2

The percentage of increase for each extension option shall be
computed against

and added to the price(s) stated on the Pricing
Page for the
original

contract period. If the Pricing Page does
not include such percentages or if applicable spaces are not
completed by the contractor, the price(s) during extension
periods shall be the s
ame as during the original contract
period.


1.3

The University may not automatically exercise an extension
option based upon the maximum percentage of increase and
reserves the right to request justification from the contractor
supporting the requested in
crease.


2.

All prices and percentages shall be as indicated on the Pricing Page
of this document, or as specifically provided for by this document.
The University shall not pay nor be liable for any other costs. The
contractor shall not be allowed any

additional compensation for any
matter of which the contractor might have fully informed itself of
prior to the closing date of the Request for Proposal.



2.1

Payment for all
goods

required herein shall be made after the

successful completion of the res
pective contractual

requirements and written acceptance by the University.


2.2

Payment for all
services

required herein shall be made at
commencement of maintenance.


2.3

In the event the scope of work is revised by the University,
additional compensat
ion shall be considered and negotiated at
that time.


3.

The contractor shall fully coordinate its activities in the
performance of the contract with those of the University.


4.

The contractor agrees and understands that the contract shall not be
constr
ued as an exclusive arrangement and further agrees that the

9

University may secure identical and/or similar services from other
sources.


5.

The contractor shall indemnify, defend and hold harmless the Board of
Regents of the University, as well as the Univ
ersity’s officers,
agents, and employees, from and against all claims, loss or expenses
from any cause of action arising from or incidental to the
contractor's performance of the contractual requirements herein. The
contractor agrees to reimburse the Univ
ersity for any such loss,
damage or claim, including its attorneys fees. The contractor agrees
to have in effect, throughout the duration of the contract, liability
insurance coverage of the contractor for its acts, failure to act, or
negligence, arising o
ut of or caused by the activity which is the
subject of the contract, in the sum of not less than three hundred
thousand dollars ($300,000) per each person and not less than two
million dollars ($2,000,000) per occurrence. Evidence of insurance
coverage m
ust be submitted to the University upon request.


6.

The contractor shall not be responsible for any injury or damage
occurring as a result of any negligent act or omission committed by
the University, including its Board of Regents, agencies, employees,
a
nd assigns.


7.

The contractor represents itself to be an independent contractor
offering such services to the general public and shall not represent
itself or its employees to be employed by the University. The sole
relationship between the University an
d the contractor is as
established by this contract. The contractor acknowledges
responsibility for filing all returns and paying all taxes, FICA,
employee fringe benefits, workers compensation, employee insurance,
minimum wage requirements, overtime, etc
., associated with the
performance of the contractual requirements herein, and agrees to
indemnify, save, and hold the University, its officers, agents, and
employees, harmless from and against, any and all losses, costs,
attorney fees, and damage of any k
ind related to such matters. Upon
request, the contractor will provide to the University evidence of
compliance with these requirements.



10

SOUTHEAST MISSOURI STATE UNIVERSITY

CONTENT MANAGEMENT SYSTEM SOFTWARE/MAINTENANCE

REQUEST FOR PROPOSAL
4
6
9
1


OFFERO
R’S INFORMATION


This portion of the RFP pertains to any interested party which wishes to be
provided an opportunity to submit a proposal.


1.

Proposals must be completed, signed, and returned (with all

necessary attachments) to the Purchasing Department
by the

closing date and time specified on the RFP cover sheet. In

addition to the original proposal, the offeror should include

three (3) complete copies of the proposal for distribution to the

appropriate evaluation personnel. The University only re
quests

copies of any pages completed by the offeror and any additional

pages added by the offeror. Copies of the original Request for

Proposal package or any attachments thereto are not needed.


1.1

In addition to the paperwork requested above, the
offeror is
strongly encouraged to submit a complete response via PDF on
disk (3.5” floppy or ZIP). If needed for the PDF response,
please submit a request to
ssteinnerd@semo.edu

for an electronic
copy of this do
cument.


2.

Any offeror with questions should contact Sarah J. Steinnerd,

Purchasing Manager. All offerors and/or anyone else acting on their
behalf must direct all of their questions or comments regarding the
RFP, evaluation, etc., to the Purchasing D
epartment. Offerors may not
contact other University employees regarding any of these matters
while the RFP and evaluation are in process. Inappropriate contacts
are grounds for suspension and/or exclusion from this procurement or
future procurements.



2.1

It is preferred that all questions be faxed to the

Purchasing Department at (573) 651
-
5099 or sent via e
-
mail to
t
h
e

a
d
d
r
e
s
s

s
h
o
w
n

a
b
o
v
e
.






3.

Evaluation Process: Any award accomplished as a result of this

Request for Proposal shall be based on the b
est proposal(s) received
in accordance with the following evaluation criteria. Failure to
provide adequate information for evaluation of the criteria listed
below will at least result in minimal subjective consideration and
may result in rejection of the
offeror’s proposal package.




3.1

Cost....................................................50%


3.2

Experience and Reliability of Offeror's Organization....10%


3.3

Proposed CMS Software...................................25%


3.4

Contractor Support/Ma
intenance..........................15%


4.

COST: Cost shall be evaluated based upon the firm, fixed price(s)
indicated by the offeror on the Pricing Page. Percentages quoted for
extension options shall also be considered in the evaluation of cost.



4.1

The offeror shall not be entitled to any other form of payment
or reimbursement not specifically provided for by this document.


11


5.

EXPERIENCE AND RELIABILITY OF OFFEROR’S ORGANIZATION: Ex
perience and
reliability of the offeror’s organization will be
considered in the
evaluation process. Therefore, the offeror is advised to submit any
information which documents successful and reliable experience in
past performances, especially those performances related to
activities similar to the requirements of t
his RFP.



5.1

The offeror should submit at least three (3)
references from the
higher education marketplace. At least two of the references
should include sources who have
acquired the same type of
software from the offeror. Each reference should includ
e
organization name, contact person with respective email address,
title, telephone number, and address. The offeror may utilize
Attachment 1 to provide this information. In addition, the
offeror is encouraged to submit a complete
list of all colleges
an
d universities which have selected the offeror’s CMS product.


5.2

The offeror should submit at least three (3) current customers

who have purchased a software maintenance agreement from the

offeror. Preferably, each customer provided should be using

t
he CMS software as offered by this Request for Proposal. If

such is not available, the University requests three (3)

current customers who have purchased any software maintenance

agreement from the offeror. Each reference should include

organization
name, contact person with respective email

address, title, telephone number, and address. The offeror may

utilize Attachment 2 to provide this information.


5.3

The offeror is advised to submit any information which documents
successful and reliable exp
erience in past performances similar
in nature to the requirements specified in this document.
Specifically, the offeror is encouraged to submit the following:



5.3.1 History of the bidder’s company, including years in
business; number of clients and
in what industries;
partnerships; third
-
party endorsements; and general vision of
the company and where the company is headed in the future with
this product.



5.3.2 The specific background and experience of staff who will
be directly involved in the pro
ject.



5.3.3 In
-
house capabilities to respond to the contract
requirements and description of any portion of the project
which may be outsourced.


6.

PROPOSED CMS SOFTWARE:
The offeror must fully describe all proposed

software including, but not limite
d to, those requirements as
described in the Technical Specifications/Scope of Work section. It
is highly desirable that the proposed CMS software be completely
described, with each item or response correlated in sequence to the
appropriate paragraph numb
er. It is the offeror’s responsibility to
make sure such is adequately described. It should not be assumed
that members of the evaluation committee have specific knowledge of
the products proposed, but that each member of the committee does
have sufficie
nt technical background to conduct an evaluation when
presented with complete information.
The offeror should specifically
address the following:



6.1

The offeror should describe in detail the proposed software.


12


6.2

The offeror should describe the hardware configuration

recommended for applicable workstations (such as the computer,
printer, modem, etc.) to execute the proposed software
satisfactorily. The offeror should also d
escribe server
configurations to host the software. In addition, the offeror
should
specify any pre
-
existing hardware or software that the
CMS must interface with, or run on including, but not limited
to, specific operating systems, databases or Web serve
rs.

6.3

The offeror should provide the load levels that the CMS

supports, and the additional resources (hardware and software)

required for increased usage.


6.4

The offeror should outline and describe in detail all training
manuals/materials and any oth
er trouble
-
shooting documentation
which will be provided to the University.

6.5

The offeror should provide information as to the age of the

current version of the CMS package.

6.6

The offeror should provide information regarding how and when

new releases
/updates are issued.


7.

CONTRACTOR SUPPORT/MAINTENANCE: The offeror should present a

written narrative which clearly and concisely states the method by
which the offeror proposes to satisfy the requirements of the
Technical Specifications/Scope of Work
section. At a minimum, the
offeror should specifically address all of the items listed below.



7.1

The offeror should describe in detail the training which will

be provided to University personnel.

In addition,
the offeror should describe the training process to
be used with University staff including course
descriptions, the target audience for each course,
and course sequences and prerequisites. The offeror
should also describe the

training plan, which should
include the following variety of methods as a
minimum.

7
.
1
.
1
formal, hands
-
on classroom training or workshops

7.1.2
train

the trainer

7.1.3
on
-
line systems training

7.1.4
on
-
line help functionality

7.1.5
participation by Univer
sity staff in contractor’s user

groups and on
-
line forums


7.2

The offeror should describe the
warranty

in detail.

7.3

The offeror should outline any skills and/or knowledge required

from within the University to customize and maintain the CMS.


7.4

The offeror should indicate whether a toll free telephone

number will be provided for use by the University

for technical

support. In addition, the offeror should specify whether a

specific individual will be assigned to the University as a

single point of contact.

7.5

The
offeror
should outline preferred support arrangements,

including service level agreem
ents and upgrade processes.

7.6

The offeror should specify whether or not the company supplies

Hotline support and applicable charges associated with use of

the hotline.

7.7

The offeror should provide support hours (eastern, central,

etc. time).

7.8

The

offeror should provide average response time to questions.


13

7.9

The offeror should describe what enhancements are scheduled

for upcoming releases.


8.

If requested, the offeror must demonstrate the proposed software on
the University's campus, at no cost
to the University. The
demonstration should be constructed both to clarify and verify the
offeror's response. The date of the demonstration shall be mutually
determined between the offeror and the University. However, the
offeror must accomplish the dem
onstration within 14 calendar days
upon
receipt of the
University

s request
.


9
.

If the offeror requires the University execute

some type of
licensing agreement in addition to this Request for Proposal, the
offeror
must

submit an exact replica of such with the original
proposal. However, such agreements must not amend, contradict, or
delete any terms, conditions, and/or requireme
nts set forth in or
referenced in this RFP and any amendment or attachment thereto.
Failure to submit such agreements with the original proposal but
require the execution of such at a later date may result in the
rejection of the offeror's proposal.


1
0
.

Business Information:
As a state entity, the University is
required

to report minority
-
business and women
-
business enterprise
information to the

Office of Administration, Division of Purchasing.
Therefore, the offeror is requested to complete and return
Attachment
3

with the proposal. Completion of Attachment
3

does not
affect contract award.


1
1
.

Terms and Conditions, Request for Proposal (revised 07/01), are

hereby attached and incorporated.
Offeror’s terms and conditions
which conflict with this Request for Proposal document
and/or the
attached Terms and Conditions
could result in rejection of the
proposal.







14

SOUTHEAST MISSOURI STATE UNIVERSITY

CONTENT MANAGEMENT
SYSTEM

SOFTWARE
/MAINTENANCE

REQUEST FOR PROPOSAL
4
6
9
1


PRICING PAGE


T
h
e

o
f
f
e
r
o
r

m
u
s
t

c
o
m
p
l
e
t
e
,

s
i
g
n
,

a
n
d

r
e
t
u
r
n

t
h
i
s

P
r
i
c
i
n
g

P
a
g
e

i
n

a
d
d
i
t
i
o
n

t
o

a
l
l

o
t
h
e
r

i
n
f
o
r
m
a
t
i
o
n

r
e
q
u
e
s
t
e
d

e
l
s
e
w
h
e
r
e
.




1.

Content Manageme
nt Software System



The offeror must indicate a firm, fixed price for each of the

items indicated below. The price must include all applicable charges,
such as the initial purchase

and
warranty. All prices

submitted shall
remain in effect for the initial contract period as defined by
paragraph
1
, page
8
.



1.1

The offeror must provide a firm, fixed price for the purchase of
the CMS software as specified by the technical specifications portion
of this doc
ument. The offeror must indicate the total number of
concurrent user licenses provided with the initial software purchase
(if applicable).




$__________
___

firm, fixed price



_
____________
_

n
u
m
b
e
r

o
f

c
o
n
c
u
r
r
e
n
t

u
s
e
r

l
i
c
e
n
s
e
s






1.2

The offeror must provide a firm, fixed price for each additional
con
current user license (“per
-
seat”). In addition, the offeror is
strongly encouraged to provide additional prices if licenses are
purchased in quantities greater than one.




$____________
_

firm, fixed price per each license




1.3

In the event the U
niversity exercises its option to

renew the contract, the offeror must state below the maximum
percentage of increase for each renewal option that will be applicable
for item
1.2. Statements such as "consumer price index" or "cost of
living incre
ase" are not acceptable. Before completing this section,
the offeror is strongly encouraged to review page
8
, paragraph
1
.
Failure to complete this section may result in the rejection of the
offeror's proposal.




_______%

Maximum percentage of increase






First twelve
-
month renewal period



_______%

Maximum percentage of increase





Second
twelve
-
month renewal period



_______%

Maximum percentage of increase





Third
twelve
-
month renewal period


15



1.4

Installation
:
The offeror must
provide a
firm
, fixed
price to

a
ccomplish
on
-
s
ite
insta
llation

of th
e softw
are, i
f requested by the
University.
T
he

price indicated below must include
all
ap
plicable
expenses
.




$__________
___

firm, fixed price




1.5

Training: The offeror should fully describe all available

training (both on
-
campus and off
-
campus) and should provide
individual costs for all training
opportunities.
S
ee

also page
12
,
paragraph
7.1
, for additional details.



2.

CMS
S
oftware
M
aintenance



2.1

The offeror must provide a firm, fixed price to provide
technical support and maintenance of the aforementioned CMS software.
The price will become effective
upon expiration of the initial
warranty.




$____________

firm, fixed price per year




2.2

In the event the University exercises its option to

renew the contract for maintenance, the offeror must state below the
maximum percentage of increase for

each renewal option. Statements
such as "consumer price index" or "cost of living increase" are not
acceptable. Before completing this section, the offeror is strongly
encouraged to review page
8
, paragraph
1
. Failure to complete this
section may resul
t in the rejection of the offeror's proposal.




_______%

Maximum percentage of increase





First twelve
-
month renewal period



_______%

Maximum percentage of increase





Second
twelve
-
month renewal period



The offeror hereby affirms that the above
is stated in accordance with all
terms and conditions of Request for Proposal
4
6
9
1
.




__________________________________________________

Company Name



__________________________________________________

Signature/Date