PaperThin Response - The University of Texas at Arlington

landyaddaInternet και Εφαρμογές Web

10 Νοε 2013 (πριν από 3 χρόνια και 9 μήνες)

136 εμφανίσεις


The University of Texas
-

Arlington


Page
1

of
35








PaperThin Response



University of Texas


Arlington


Request for Information for

a Content Management System


January 26, 2007


The University of Texas
-

Arlington


Page
2

of
35

Table of Contents


Introduction / Instructions

................................
................................
................................
...

3

Network Infrastructure

................................
................................
................................
........

4

Do you have a recommended security infrastructure?

................................
................................

4

Authentication / Authorization

................................
................................
................................
....

4

File System Access

................................
................................
................................
.....................

5

Server/OS Infrastructure

................................
................................
................................
.....

5

General

................................
................................
................................
................................
........

5

Hardware

................................
................................
................................
................................
.....

6

Software

................................
................................
................................
................................
......

7

App
lication Metrics

................................
................................
................................
............

8

Application Security

................................
................................
................................
...........

9

UI (Presentation)

................................
................................
................................
...............

10

Template creation

................................
................................
................................
......................

10

Browsers / WYSISWYG

................................
................................
................................
..........

12

Page Layout / Design

................................
................................
................................
................

13

Content

................................
................................
................................
..............................

13

Workflow

................................
................................
................................
..........................

18

Content Versioning

................................
................................
................................
...........

22

Adminis
tration

................................
................................
................................
..................

24

Deployment

................................
................................
................................
.......................

25

Integration with 3rd Party Content

................................
................................
...................

25

Support of File Types
................................
................................
................................
........

26

Support of Industry and Open Source Standards

................................
..............................

28

Accessibility Support

................................
................................
................................
........

28

Technical Details

................................
................................
................................
..............

28

Company Focus

................................
................................
................................
................

30

Cost

................................
................................
................................
................................
...

33


The University of Texas
-

Arlington


Page
3

of
35

Introd
uction / Instructions


The University of Texas at Arlington (The University) requests information from companies regarding a
Content Management System. This RFI is issued for the purpose of gathering information which may be used to
develop specifications
for a Request for Proposal (RFP) which may be issued by University to procure a
Content Management System. University offers
no

assurance or guarantee that such an RFP will in fact be
issued.


The University of Texas at Arlington is a comprehensive public

university located in the dynamic and growing
Dallas
-
Fort Worth metroplex. The University has a population of approximately 31,000 students, faculty, and
staff (~ 4,000 full
-
time and part
-
time employees). University offers 91 baccalaureates, 76 master an
d 35
doctoral degrees to approximately 25,000 students who come from 150 nations.


The University has recently implemented the Oracle/PeopleSoft Campus Solutions system for its Student
Information System. Faculty, staff, and students access this system (c
alled “MyMav”) using the
Oracle/PeopleSoft Enterprise Portal. Currently there is no standard web development or content management
tool used at the University.


The University will not provide compensation to any respondent to this RFI for any expenses in
curred by
respondent for response preparation. Respondent submits its response at its own risk and expense. All responses
to this RFI and any supporting documentation will become the property of University.


The University considers all information, docume
ntation and other materials requested to be submitted in
response to this RFI, to be of a non
-
confidential and/or non
-
proprietary nature and, therefore, may be subject to
public disclosure under the
Texas

Public Information Act
(
Texas Government Code
, Chap
ter 552.001, et seq.).
Respondent is hereby notified that University strictly adheres to all statutes, court decisions and opinions of the
Texas Attorney General with respect to disclosure of public information.


In response to this RFI, please provide inf
ormation regarding the following matters:


1.

Responses to each item in the attached document pertaining to how their solution meets the business
requirement. Any information that could be provided about how the requirement is met in your solution
would be a
ppreciated. Please allow your comments to remain highlighted.


2.

Any other pertinent information with regard to the use of your solution in the area of higher education.


The response should be entered into the attached document. Each question should be an
swered. An electronic
response on CD
-
ROM is requested, as well as two (2) paper copies of the response. The response should be
typed on 8½ x 11 inch paper with all pages sequentially numbered, and either stapled or bound together. Mail
responses to the fo
llowing address:


The University of Texas at Arlington

UTA Computing Center

Box 19601

200 East Loop 820

Fort Worth, TX 76112

Attention: Darlene Hopkins


If you have further questions regarding this RFI, please contact
Darlene Hopkins

at
817
-
272
-
1437

or
d
hopkins@uta.edu
.


All responses to this RFI should be received by University no later than January 12, 2007.



The University of Texas
-

Arlington


Page
4

of
35

Network Infrastructure

Do you have a recommended security infrastructure?

1.

Regarding Firewalls?

CommonSpot supports the ability to establish an ‘au
thoring’ server behind a
firewall and to be able to push content to a production environment in front of a
firewall using
protocols such as
FTP and HTTP.


2.

Regarding Proxy Servers?

CommonSpot supports the transport

of data from Authoring to Read
-
Only
Produc
tions servers via a proxy.


3.

Regarding SSL Accelerators?

All URL’s created within CommonSpot are relative which means that the
transport mechanism for the content of the page is independent of the protocol.


4.

Regarding DMZ?

CommonSpot servers work well withi
n a DMZ
.


5.

Regarding NAT?

Since most CommonSpot server information
can

be

managed with a hostname or
N
etbios, there will be no issue with the use of NAT
.


6.

Does your application work with Citrix’ Netscaler?

Most load balancing/caching tools work with
CommonS
pot;

in fact we have some
great success with customers who have m
ultiple Read
-
Only servers
.


Authentication / Authorization

1.

Describe the level of application support LDAP authentication?

CommonSpot provides
custom API’s that

allow you to authenticate direc
tly with
an LDAP server
. This is the preferred method of

a
uthentication among

most of
our higher education customers.


2.

Describe the level of application support LDAP authorization?

LDAP users and groups can be easily coordinated with CommonSpot users and
groups such that, a change in a user’s role within the LDAP server can directly
affect that user’s role

with
in

CommonSpot.

Similar to

custom authentication, the
authorization link is p
erformed

with an API call during our authentication
process.



The University of Texas
-

Arlington


Page
5

of
35

File Syste
m Access

1.

Describe the support for WebDAV.

At this time the only support
for

WebDAV would be with the management of
custom scripts and custom applications.


Server
/OS Infrastructure

General

1.

What information do you need to estimate hardware requirements (dis
k space,
memory, processor, OS)?

It is difficult to calculate hardware requirements to an exact number but we can
estimate server/hardware performance expectations based

on

the following
items




Number of Page Views per day/month



Number of expected “concurr
ent” authors



Percentage of Custom Applications that deliver dynamic content

2.

How does your application support load balancing / failover?

M
u
ltiple

production servers

can be deployed to support load
-
balancing and
failover.


3.

Is your application scalable for i
ncreased user demand?

CommonSpot can scale from a single server where all the authoring and
production of content is effectively managed on one (1) Web server, to an
environment with multiple stand
-
alone or clustered servers. For high traffic
or high avail
ability sites, CommonSpot supports two configuration options,
‘Replication’ and ‘Shared Database Clustering’, which provide the necessary
facilities to properly manage and scale one or more dynamic sites across
multiple servers.


4.

What performance metrics
does your application supply?

Currently
CommonSpot

do
es

not offer direct performance metrics out
-
of
-
the
-
box
.

H
owever
,

CommonSpot is

built on a J2EE architecture which provide
s

several
out
-
of
-
the
-
box and free 3rd Party tools for performance evaluation
.


5.

Do
es it collect and provide data required for fine
-
tuning web and app server
performance?

With the out
-
of
-
the
-
box J2EE metrics and
available
3rd Party tools you would
be
able to collect
all

of

the
data required for

fine
-
tun
ing

performance.




The University of Texas
-

Arlington


Page
6

of
35

6.

What type of con
tent (html content, file attachments, etc.) can be stored in a
database?

All of the content, except images and other native document files, is stored and
managed within CommonSpot’s content repository, a series of relational
databases.


This object
-
oriente
d framework provides tremendous advantages
,
including
:



Content can be stored independently from its formatting, enabling

better
control over its

display and
look and feel.



Content can be controlled, approved, versioned, scheduled, personalized
a
nd secured at a much finer level of granularity.





Multiple

users

can contribute to the creation and management of content
in a shared environment.

In general CommonSpot supports t
hree different database schemas:

sites,
users, and site
-
specific.


The ‘s
ites’ database manages information regarding
all of the sites running on the server, such as the Web document directory,
data
-
source names, etc.


The ‘user’ database manages users, their profile
information, passwords, as well as which group
/
s a user belon
gs to.


The
‘site
-
specific’ database houses all

of

the content for the site and subsites.




Please note that
CommonSpo
t

provides an intelligent caching system that
automatically and transparently caches static versions of dynamically created
pages when ap
propriate. This enables the rich adaptive assembly of pages
without having to compromise performance that is typically associated with
purely dynamic approaches. This approach offers the performance equal to
that of a static site.


As content is approved f
or publication, appropriate page level cache files are
generated for the specific browser type. The next time a request is made to the
page, the page is pulled from the page cache for the specific browser type. If
the page contains dynamic content, or when

the page is in ‘Author’ mode,
caching is done at the element level. This ability allows only the recently
changed or dynamic elements to be rendered from the database. The other
elements are pulled from the element cache.



7.

What type of content (html co
ntent, file attachments, etc.) can be stored in a file
system?

Content that is stored and managed in the file system includes uploaded files
(MSOffice documents, PDF, MP3, etc), images, and templates.



Hardware

1.

What operating system(s) does your applicati
on require?

CommonSpot is supported on Windows as well as Unix, Linux and
MacOS

platform
s.


The University of Texas
-

Arlington


Page
7

of
35


2.

Do you have vendor preference regarding hardware / operating system?

No.


3.

Are there issues or limitations with any supported platform?

No.


4.

What is the standard rec
ommendation for an Application Server?

The recommende
d hardware

specifications can be found at
:
http://www1.paperthin.com/products/Technical
-
Specifications.cfm


5.


What is the s
tandard recommendation for a Web Server?

The recommende
d hardware

specifications can be found at
:
http://www1.paperthin.com/products/Technical
-
Specifications.cfm


6.

What is the
standard recommendation for a Database Server?

PaperThin does
not offer hardware specifications for the database server but it
has been our experience that if the Database server is dedicated to the
CommonSpot Application server, that the above mentioned r
ecommendations will
suffice for most application activity.

Software

1.

Is your application 100% 3
-
tier (web application)?

No.


2.

Which modules / functionalities are not web based?

All
of
CommonSpot
’s

modules and functionality

are

W
eb
-
based.


3.

What is the standar
d recommendation for an Application Server?

The recommende
d specifications can be found at
:
http://www1.paperthin.com/products/Technical
-
Specifications.cfm


4.

What is the standa
rd recommendation for a Web Server?

The recommende
d specifications can be found at
:
http://www1.paperthin.com/products/Technical
-
Specifications.cfm


What is the standard recom
mendation for a Database Server?

The recommende
d specifications can be found at:
:
http://www1.paperthin.com/products/Technical
-
Specifications.cfm
.


5.

Which databases are support
ed for use with your application (include name and
version)?

SQL Server 2000, SQL Server 2005, Oracle 9i, Oracle 10g, and MYSQL 5.0


6.

What database vendor do you prefer?

We not have a preference, but most of our customers run SQL Server.



The University of Texas
-

Arlington


Page
8

of
35

7.

How much
custom
iza
tion is necessary for the system to be usable?

None.

CommonSpot offers a robust set of out
-
of
-
the
-
box features and functionality
that allow you to get a Website up and running quickly and without the need for
coding.


However should you wish to customize
and extend
CommonSpot
functionality,
CommonSpot
provides technical developers with a robust set of
well
-
documented
APIs, event hooks, callback and overrides
.

In addition, CommonSpot exposes
variable information for developers to leverage including session,

application,
request, template and others.


8.

Describe standard interfaces your application supplies.

CommonSpot provides a number of integration points, including over 75 API
calls, where developers can interface with its architecture using custom code to

control aspects such as authentication, content rendering, 3rd party application
integration, content migration, among others.


Application Metrics

1.

How many content contributors can the system support?

CommonSpot can support an unlimited number of content

contributors, users
involved in the creati
on
, updating, management and administration of Web
content.


2.

How many template designers can the system support?

CommonSpot can support any number of template designers. The ability to create
and manage templates

is a permission that can be assigned to an individual(s) or
group.


3.

How many user groups can the system support?

There is no limit to the number of user groups that CommonSpot can support.


4.

How many groups can one person belong to?

A person may belong to

any number of groups necessary. There is no limit.


5.

Describe the modularity of your application. Can substitutions be made for any
parts of it?

CommonSpot
’s

Single Site and Standard Edition
s

offer core content management
features and functionality. Severa
l
add
-
on modules
may be purchase
d

in addition
to the ‘core’ license that include: Custom Metadata
, Taxonomy, Simple Form
s

and Data Sheet Element, Content Personalization and Static Site Generation. The
CommonSpot Enterprise Edition license however includes

all the available ‘bells
and whistles’.




The University of Texas
-

Arlington


Page
9

of
35

Application Security

1.

How do you handle the assignment of privileges and roles, particularly in
complex scenarios? For example, one person has one set of privileges for one
department and an entirely different se
t of privileges in another.

CommonSpot provides a robust security framework that can be tailored to
meet the
precise
needs of your organization. This framework permits either a
distributed security model
, whereby administrators that know best the content,

users and the role they play can assign permissions,
or one that is centrally
controlled.


CommonSpot supports the assignment of permission
s

for
participating in the
creation, management and administrat
ion

of Web content for individual users
or groups
at six
(
6
) levels
: ‘root site’ (
www.university.edu
)
,

subsite
(
www.university.edu/admission
), page
(
www.university.edu/admission/visit_main.cfm
), content object (text block,
image, list of links on a page), form field (secure a field on registration,
contact us or survey form), as well as template (permission to create and edit
templates as well a
s security that inherits
from

pages that derive from the
template).

A single user or group can play many different roles from one
site
,

subsite

or
page

to the next
.
User defined or role
-
based p
ermissions
,

includ
e

designer, editor,
approver
and

administrat
or
. In addition, the ability to

create page
s, upload
documents

and

image
s
, register an external URL, create templates
, access menus,
and view

the CommonSpot user interface
are permissions that can be assigned to
either a single user
or group
.


2.
How do y
ou nest security roles and permission lists (a permission list contains
several roles, a one to many relationship)?

Permissions at the most granular level override those at a higher level. Thus
,

page level security overrides subsite security and element (c
ontent object) level
security overrides that of the page. For example
,

a user may have the ability to
edit content on all pages contained
with
in the Alumni site with the exception of
the

main landing page for the Alumni site. Permissions for the page over
ride
those for the subsite.


It is
also
possible for a user to belong to multiple groups and for those groups to
have different permissions entirely. The user

s permissions are the sum total of all
the groups they are a member, plus any individual user pe
rmissions that may have
been assigned.


3.
How many levels of security nesting do you have, how fine
-
grained is the

security model?


As mentioned above, permissions can be assigned for a user or group at the site,

subsite

(folder), template, page, con
tent object, and field level.



The University of Texas
-

Arlington


Page
10

of
35

4.
Can a subset of security be delegated to a site manager (a site manager can

designate content authors, reviewers, publishers)?

Yes, CommonSpot provides

the ability to delegate
administration
rights/
permissions
to a
site manager
.

The site manager can then
assig
n
permissions

(i.e.

e
dit, design and approval rights)
to other users or groups

within
the system.



5.
What can a site manager not do?

CommonSpot does not have inherently a ‘site manager’ role that includes cert
ain
permissions, but you can create this user and assign permissions as necessary.



6.
Is your security model LDAP compatible?

Yes.


7.
What features enhance the security of your application?

C
ommonSpot has a unique application framework which forces ca
lls to most
content management dialogs and administrative screens through a single
interface. Within that interface
, CommonSpot

can secure against attacks such as
SQL Injection.


8. I
f your application is capable of deploying a separate package of content

to a web
server, does it support secure protocols to accomplish this (list supported
protocols: SSH, WebDAV, SFTP, etc.)?

Yes, us
ing hooks into CommonSpot
,

additional proto
cols
,

such as those listed

above
,

can be programmatically supported
.


UI (Presentat
ion)

Template creation

1.

How are templates created?


CommonSpot provides a flexible template architecture to meet the needs of our
look and feel, navigation and page layout requirements that includes a ‘base’
template, navigation and content templates.



Ba
se

templates are the foundation of any CommonSpot site.


It is in the
base

template that the general site structure, design and function are established.


They are the “blueprint” of your site.


Unlike all other templates in
CommonSpot, which are edited in

your browser through the CommonSpot
interface,
base

templates are developed entirely in code.


A typical
CommonSpot site requires only one
base

template with every other page and
templ
ate ultimately deriving from th
is

base

template
. H
owever
,

CommonSpot
ca
n support an unlimited number of
base

templates
,

if desired. The
base

template may contain a standard navigational bar, a hierarchical menu,
company logo, stock ticker and/or any other recurring object.


The University of Texas
-

Arlington


Page
11

of
35

Navigation templates represent the first layer of te
mplates between the
base

and the content of your site.


These can be thought of as defining the “outside
the white space” of your site.


While the
base

template defines the structure of
your design, the navigational templates provide a consistent mechanism

for
presenting navigational constructs, common menu tool bars and other
common look and feel components.


Typically the navigational templates
might include defined menu tool bars, side bars, copyright notices and the
base layout of the page, leaving one
or more empty rectangular regions that
are filled in by content templates.




Content/layout templates are the templates that form the upper layers of a
page’s template hierarchy.


These templates typically do not include
navigational interfaces but instea
d provide a definition for how the pages’
real content looks.


Content templates can be very rigidly or loosely defined,
thus enabling very tight control over what the end user can and cannot edit.

CommonSpot provides a number of ready
-
made templates that
can
incorporate the “look and feel” of the Web site and offer typical formatting
and layout options. These basic
templates or
forms can be filled
-
in

directly
with content and published as Web pages, or they can be modified as needed.
Any user who has templ
ate
-
creation rights (which are granted by the site
administrator) can easily modify templates

(with exception
of

the
base

template)
to satisfy

their
precise needs. The result is a corporate
-
wide
development process in which the people who best understand t
he content
develop the templates.




2.

What skill set is needed to create templates in the system?

Creating a ‘
base
’ template typic
ally requires HMTL skills and is

usually
developed

by a designer or d
eveloper
. Navigation and content templates can

simply

be c
reated by creating a page, adding the content objects (
rich text

editor,
image, list of links, etc) and any recurring content to the page, and then saving it
as a template.


3.

What features make template creation/editing easy?


Base
’ templates can be creat
ed using
any HTML editing tools like Dreamweaver,
Front Page, Homesite, etc.


End users can create content

templates using
CommonSpot
’s

intuitive
,

wizard
-
driven interface, the same interface that
is

access
ed

to create new pages.


4.

How are templates integ
rated into the workflow of the system?

All pages created
with
in CommonSpot are created from a template
. CommonSpot
allows for the creation of multiple templates to meet the needs of a site or
departments particular look and feel, navigation and page layou
t requirements.



The University of Texas
-

Arlington


Page
12

of
35

W
hen
creating a new page

users

are presented with a
library of templates based
up
on their permissions. For example
,

a user in
the
Public Relations

department

may only have access to the Press Release template
,

while
a

W
eb administrator i
n
Admissions
may have

access to a variety of templates featuring different styles
and page layout
s
.
Once

a

template

is selected,

the user

simply click
s

where
directed and a series of wizards guide them through the submission of content. In
real
-
time, the c
ontent is integrated into the predefined structure of the template.



5.

What template technologies are supported?

Most all HTML editing tools can be used
to create ‘
base
’ template
s

as well as

standard Web technology

such as

CFM
, DTML, JavaScript
, PHP, etc.


6.

How complex can templates be with respect to nesting and reuse?


CommonSpot
supports a ‘template hierarchy’ where
by

templates derive from
other templates forming a hierarchy of derivation. Think of CommonSpot
templates as transparencies, which are layere
d on top of each other to form the
page. It is not uncommon for pages within CommonSpot to be built upon two or
three layers of templates.


Templates remain dynamically linked to all pages created from them. This
functionality is very powerful in that i
t allows a site designer to build a series of
templates with common components to be shared across multiple pages, and
manage them all in one place. In a typical HTML Web
-
authoring environment, a
change to a copyright notice appearing across multiple pages

requires that every
page affected be re
-
authored. In CommonSpot, such elements can be specified in
a template and thus all pages derived from that template are automatically updated
when the template is modified. By simply modifying a few templates, a lar
ge
-
scale design change can be implemented easily and effectively without changing
the underlying content. Changes in the
base

template automatically propagate to
any inherited template or page. And CommonSpot templates can be used
endlessly to create pages
.


7.

Are third
-
party Templates & Library items supported? List supported products
and versions (Macromedia Dreamweaver, etc.).

Please see the responses provide
d

for the several requirements above.


Browsers / WYSISWYG

1.

Which browsers and

versions do you su
pport?

Users can edit, approve
,

and administer content via
the
CommonSpot interface
using Internet Explorer, Mozilla, Firefox
,

or Netscape 7.2.


Pages created using CommonSpot are viewable from all standard browser types
including, but not limited to, Ne
tscape Navigator, Internet Explorer, Mozilla,
Safari, Opera
,

and FireFox.



The University of Texas
-

Arlington


Page
13

of
35

2.

Do you support WYSIWYG content creation?

Yes, CommonSpot provides a WYSIWYG editor for content creation.


3.

List required browser for WYSIWYG content creation.

Users can edit, approve
,

and administer content via

the

CommonSpot interface
using Internet Explorer, Mozilla, Firefox or Netscape 7.2.


4.

List required fat client for WYSIWYG content creation.

CommonSpot is a complete browser
-
based application and requires no software
to be in
stalled on the client.


5.

List required 3
rd

party application for WYSIWYG content creation.

No

3
rd

party application

is required, as it is provided with the CommonSpot
content management
software.


6.

List optional 3
rd

party application for WYSIWYG content cre
ation.

No

3
rd

party application

is required, as it is provided with the CommonSpot
content management
software.


7.

If you don’t support WYSIWYG content creation, how closely does content
creation resemble the final web page?

CommonSpot supports WYSIWYG cont
ent creation.


P
age Layout / Design


1.

Does your application support multiple tab layout (example:
www.costco.com
)?

Yes. CommonSpot supports multiple tab layout. As a matter of fact, CommonSpot
imposes no restrictions o
n the design of the site and its navigation elements.


2.

Can existing code (html, Javascript) be included in the page layout?

Yes.


3.

Can it process pages designed by 3
rd

party product (Dreamweaver, etc.)? List the
products and versions.

No. CommonSpot can o
nly process pages created using its own interface and
tools.



Content

1.

Do you
separate content from presentation?

CommonSpot leverages the efficiency and flexibility of a modular system by
separating form (formatting, layout, and style properties) from con
tent.
Instead of storing Web pages as static chunks of HTML code, CommonSpot
stor
es

the content and its properties in either separate tables within the content

The University of Texas
-

Arlington


Page
14

of
35

repository or as XML representations within the repository. This unique
approach enables any nu
mber of authors participating in the creation and
management process to re
-
use elements endlessly, in a myriad of
combinations, to create Web pages tailored to the precise needs of every
department.


2.

How do you enforce that separation?

By managing content
separate from its presentation CommonSpot is able to
present different and secured wizard interfaces for each aspect. These
interfaces can be secured individually thus allowing the
presentation settings
(i.e. layout and styles
) to
be restricted from the e
nd user and only controlled
by the template owner.


The end
-
user simply submits the content which is
automatically generated at the page level, enforcing the presentation of the
content on the page.


3.

How is existing content entered into the system?

Existin
g content may

be migrated

into CommonSpot
through its
Content
Creation API
,

an effective method for populating pages, images
,

and external
documents through a programmatic fashion.


The Content Creation API
allows developers to drive content creation throu
gh a series of Web
S
ervice
s

calls to custom API methods.


The API has calls for creating pages, deleting
pages,


creating subsites, adding images, uploading documents, creating
external URLs, populating Rich Text Block Elements and Populating Global
and Cu
stom Elements.


Existing HTML
or richly formatted text
may also be entered by copying and
pasting directly into

the WYSIWYG editor,
thereby

p
reserv
ing

the formatting if so
desired. Upon execution of the paste command, CommonSpot presents to the user
0ptio
ns on how the pasted content will be converted to HTML code.
The

options
available to the user

are

determined by the actual content that is being pasted, as
well
as the settings page and site
-
wide settings defined. The options that are
available include:





Paste formatted

-

This option is available when formatting is detected in
the pasted content. Options are provided to remove class and/or style
attributes from pasted HTML tags, and to remove HTML <font> tags.



Paste and replace non
-
standard fonts

-

This
option is available when non
-
standard fonts are detected in the pasted content. An option is provided to
remove class attributes from pasted HTML tags. When using this option,
select the desired replacement font from the drop
-
down list.



Paste without for
matting

-

This option is available when formatting is
detected in the pasted content. Options are provided to remove class
and/or style attributes from pasted HTML tags.


The University of Texas
-

Arlington


Page
15

of
35



Paste plain

-

This option removes all HTML mark
-
up from the pasted
content, inserting
only plain text.



4.

What other authoring tools may be used in conjunction with the system (list
product and version)?

Users may wish to continue to create HTML content using their favorite
HTML editing tools. Users can paste HTML code sample directly into t
he
WYSIWYG editor. Any included ‘<’ and ‘>’ characters are converted to
HTML entities ‘&lt;’ and ‘&gt;’ respectively so that the content will not be
interpreted and thus rendered as HTML. The WYSIWYG editor supports an
HTML

View of the content rendered to

allow for in
-
line editing of the HTML
directly. This view can be turned off or hidden as necessary.



5.

What sort of support for those authoring tools is provided?

Please see the response provided above.


6.

What features make content creation / editing easy?

CommonSpot provides simple authoring tools that support the various skill
levels of those contributing to the site. Intuitive user interface components,
role
-
based menus, and interactive wizards guide occasional and non
-
technical users though creating, up
dating and personalizing content,
establishing security and managing the approval workflow.



CommonSpot was designed with business users in mind. CommonSpot is
intuitive and easy to use, as all authoring, editing, scheduling, approving and
publishing of

content happens within the context of the page. All the
functionality for creating and publishing content (as well as managing user
access and security) happens within the browser. No client software besides
the browser is required, nor is it necessary t
o navigate to a separate
application or URL.


CommonSpot was designed specifically to allow non
-
technical users to create
and publish content in a secure and controlled environment. There are
several features that make it very easy for non
-
technical use
rs to manage
content within CommonSpot. They include the following:




In
-
context editing
-

Content contributors manage all content directly
within the context of their site. There’s no need to navigate to external
applications, they simply can navigate to
the page/content they wish to
edit and (given the proper permissions) can edit the content directly in
context.




Role
-
based access


CommonSpot presents user interface components,
menus, interactive dialog wizards
, and
functionality based on

a user’s

sp
ecified
role


designer, author, editor, style, approver or administrator.

The University of Texas
-

Arlington


Page
16

of
35

Options that are not applicable are hidden from the user, greatly
simplifying use.


‘Edit’ mode indicators are exp
osed based on a user

s role and
the security
defined at the site, s
ubsite, page, element or template level, allowing users
to update or revise content only for which they have rights to do so.




Context Sensitive Wizards


A ‘click here’ interface and dialog wizards help
guide the user through the process of contributi
ng content. Each element has
a context sensitive wizard for creating/uploading content and managing the
layout or display of the content.


Out
-
of
-
the
-
box, CommonSpot provides over
5
0+ easy to use wizard driven
elements (plus administrators/site designers c
an create th
eir

own content
objects

for use by system users
). Several of these elements use common
wizards or components, making it easy for a non
-
technical user. Once a user
learns how to interact with a component in one element, they are familiar with
them through all
5
0+ elements.


Many of the wizards were purposely designed to look like standard Microsoft
Office interfaces, in order to leverage user’s familiarity with functionality and
help users be effective immediately. Examples of such common comp
onents
include common link handling wizards, common image wizards, and a
common, easy to use WYSIWYG editor (Rich Text Editor).



The University of Texas
-

Arlington


Page
17

of
35





7.

How much training is required for non
-
technical contributors able to
contribute?

Most higher education customers prefer
to train their non
-
technical contributors
using internal resources and are successful in getting them up to speed on the
product within half day to full day of training at the most. CommonSpot provides
a wizard driven interface that is intuitive and easy t
o use.


8.

How does it handle existing dynamic content (PHP, CFM, ASP, JSP)?

The engine that drive
s

CommonSpot features and functionality is Adobe
’s

Macromedia

ColdFusion, thus ColdFusion modules can be easily integrate
d

into
the
CommonSpot framework (page)

using an out
-
of
-
the
-
box ‘Custom
Script’ element (content object). To include
CFM code,
a developer simply
needs to implement a ColdFusion module and upload that module into the
appropriate site’s ‘customcf’ directory.
The
‘Custom script’
points to the
a
ppropriate module and is rendered.
Alternatively, the relative path to an
existing ColdFusion module located somewhere else on the server can be
specified when the Custom Script element is added to a page.


Applications built in
languages

such as

ASP, PHP

or

JSP can be integrated
seamlessly using CommonSpot’s Custom Script Element with Static Content
Generation. Under static content generation, the code is ‘wrappered’ to process
on the page outside the ColdFusion environment.


9.

To what extent are Flash file
s supported?

CommonSpot supports native Flash files

through a predefined Flash element
or content object.




The University of Texas
-

Arlington


Page
18

of
35

Workflow

1.

Does the user build workflows in a GUI environment?

Yes.



2.

Does the application support "task
-
based" workflows (approval/progress through
t
he workflow not only by level or role, but also by task completed)?

A workflow approval process can be assigned at a multitude of levels
including:



All pages within a site or subsite



Page



Section
s

of a page or content objects. For example
,

a

home page
may
contain

a
“W
elcome


text block that is approved by Public Relations and
a “
Featured Headlines


list that is managed by news bureau.



Template
-

Approval workflow may

be assigned to a ‘content’ template
thus requiring all ed
its to
be approved. In addition
, a
workflow can be
embedded in a template so that all pages that derive from the template
inherit its workflow.



3.

Does the application support "nested" workflows?
C

CommonSpot supports a ‘pipelined’ workflow where in a mult
i
-
step process those
first in the ap
proval process are notified of pending approval and then once
approved, those in the second step are notified of the approval.


It is possible to establish a
n

approval group and to require one or all members of
the group to approve the content.



4.

How many

levels of nesting will it support?

CommonSpot imposes no limit on the number of workflows you can create and the
steps (levels) in the process.



5.

Are there any limits to the nesting?


CommonSpot imposes no limit on the number of workflows you can create a
nd the
steps (levels) in the process.


6.

Does the application support "rules
-
based" workflow (based on content or type of
content)?

Please refer to

the

response provided for item
2

above.


10.

How is workflow designed and managed?

Administrators define the workf
low approval via a WYSIWYG interface. Each
approval level created represents a step in the workflow.


Administrators
define the level (naming convention) and their responsibility and then define
what step in the workflow to represent (first, second, final)
.



The University of Texas
-

Arlington


Page
19

of
35



Approval levels can be configured to permit bypassing of approvals at
selected earlier level
s in the workflow.


In a two
-
step approval process with
‘preliminary’ and ‘final’ approvers, the ‘final’ approval level can be
configured to permit final approvers to bypass the ‘preliminary’ approval
step.


In a more advanced configuration, a ‘supervisor’

level could be set up
to allow supervisors to bypass ‘editorial review’ but not ‘legal review’.


The
only limitation is that earlier or lower levels in the approval process cannot
bypass later or higher levels


‘preliminary approver’, for example, cannot

be
configured to bypass ‘final approver’.


In addition to the multi
-
level workflow capabilities, CommonSpot also
provides collaborative authoring of content and an ‘Email Review’ feature.
Collaborative
authoring

via CommonSpot’s ‘Edit mode’ allows
a

use
r to
pickup the editing/approval of content started by another user. The ‘Email
Review’ feature allows a
user

to send
via email,
an HTML
preview of the

content that is ‘work
-
in
-
progress’ or ‘pending approval’. This valuable

feature allows a user to obtai
n

feedback in a quick and easy f
ashion

from
others within the organization
who

m
ay

not either be apart of the formal
approval process or
who
are not
users

within the system.




The University of Texas
-

Arlington


Page
20

of
35


7.

Does workflow have to be set up in some global way, or can different areas ha
ve
different workflow?

Different
areas/
sections (subsites or folders) may have different workflows.


8.

Does the application give the user flexibility to define the workflow to capture
existing content management processes?

Absolutely


9.

Does the application al
low the user to schedule content for automatic deployment
based on date and time?

Yes.
CommonSpot allows a user to schedule content for publishing based on a
date and time.

CommonSpot will appropriately restrict access to those
pages/documents that have n
ot yet been published. All of the navigational
components will dynamically adjust their output to only reflect current content.




10.

Does the application support automatic expiration of content based on date and
time?

CommonSpot supports the ability to se
t an expiration date on all pages and
uploaded documents. The expiration date is specified as standard metadata,
and CommonSpot will appropriately restrict access to those pages/documents
that have not yet be
en

published or have expired. All of the naviga
tional
components will dynamically adjust their output to only reflect current
content.


CommonSpot also supports
a
‘Content Freshness Reminder’ which can serve
as a tickler to

remind

the author

of the page

that the content may require
some maintenance. T
he author has the ability to set a freshness reminder,

The University of Texas
-

Arlington


Page
21

of
35

either to remind him/her of a specific date, a specified number of days before
content expiration or after content last changed, that some maintenance with
the content may be necessary. Content Expirat
ion can be set during the page
creation process, or after a page has been created.
Users

are informed of the
reminder via e
-
mail
or their

‘Pending Actions’.


11.

Does the application support automatic content expiration notification to
owners/publishers and th
ose republishing the asset?

Yes
,. And
CommonSpot provides several means of notification
,

including email
notification as well as personal reports.


12.

Are there any limits in your software such as the number of notifications per
event, etc?

No.


13.

Is the date/
time of notification flexible?

No.


14.

What are the limits/constraints to automatic content expiration in your software?

None.


15.

Does the application support email notification triggered by completed steps in
the workflow?
If this feature is available, what a
re the constraints?

Yes
.

CommonSpot support
s

email notification triggered by completed steps in the
workflow, as well as notification through personalized reports. There are no
known constraints.


16.

What provisions are there for workflow process tracking and

reporting (for the
benefit of administrators, owners)?

CommonSpot provides a number of canned reports that

administrators

can access
to manage and track workflow. In addition
,

CommonSpot provides a configurable
transaction logging facility that allows
ad
ministrators

to define which events to
log, and determine the duration for maintaining the log data.


17.

To what extent does the application support annotation/highlighting of content
changes to mark them for review and edit?

CommonSpot’s
offers a
Visual Diff
erence tool
for content review and editing that
displays

in a color
-
coded format additions and deletions

to content either at the
page or element (content object
)

level. The tool indicates

deletions with a red
strikethrough font, while insertions

have a ye
llow background color
or content
review or editing.


The Compare tab displays a "Side
-
by
-
Side" comparison of the two versions,
allowing you to see and scroll through both versions simultaneously. The
Visual Difference functionality is accessible both from
the publishing icons

The University of Texas
-

Arlington


Page
22

of
35

and from within version history.


Content Versioning

1.

Does the application support asset locking for version and edit control (to prevent
altering past documents)?

Yes. CommonSpo
t allows you to ‘lock’ an asset

(web page, uploaded docume
nt,
image, etc.) so it can not be altered.


2.

Does the application support automatic versioning? Specifically, what sort of
meta
-
information does the application retain for versioning (version numbers,
date/time, etc.)


CommonSpot tracks a page’s history a
nd its evolution, providing the ability to
version element data/content as well as uploaded documents, images, video and
audio files, etc. There is no limit to the number of versions kept, as CommonSpot
manages versioning based on number of days.

CommonSp
ot records version
history for all content changes, including publish and approval comments,
timestamps, and author/approver IDs.





3.

What provision is there in the application to compare 2 versions of the same
content? If it exists in the application, p
lease give a screenshot.

CommonSpot’s
offers a
Visual Difference tool
for content review and editing that
displays

in a color
-
coded format additions and deletions

to content either at the
page or element (content object level. The tool indicates

deletions

with a red
strikethrough font, while insertions

have a yellow background color
or content
review or editing.


The University of Texas
-

Arlington


Page
23

of
35



The Compare tab displays a "Side by Side" comparison of the two versions,
allowing you to see and scroll through both versions simultaneously.
The
Visual Difference functionality is accessible both from the publishing icons
and from within version history.






The University of Texas
-

Arlington


Page
24

of
35

4.

Does the application have the capability to 'roll back' to any previous version? If
so, to what level (a page, a navigation tree, entire

site)?

Yes, CommonSpot supports the ability to ‘roll back’ to any previous version of the
content for all web pages and uploaded assets (uploaded files).



Administration

1.

Describe your applications capability for logging and reporting usage (click
count,

etc.) of individual assets (include screen shot(s) if possible)?

CommonSpot does not provide any web analytics that track clicks through usage.
We recommend integrating with tools such as Web Trends to obtain this
information.


2.

Describe your application'
s capability for reporting asset (content) inventory and
disk usage (include screen shot(s) if possible).

In order to better support emerging regulations regarding audit trails, and to
enable tracking of contributor actions and events,
CommonSpot provides

a
c
onfigurable transaction logging facility.


Via a simple interface a
dministrator
s

can determine which events to log, and
determine the duration for maintaining the log data. By expanding the
different event types in the list, the Administrator can sele
ct at a granular
level which events are to be logged. Transaction log data can be easily
exported to Excel for further analysis.





The University of Texas
-

Arlington


Page
25

of
35

3.

Does the application simplify administration for super
-
users and site
administrators?

CommonSpot provides a wizard driven
interface for the administration of users
and groups, sites and its properties including security permissions.



4.

How does your application validate internal and external links?

CommonSpot provides a number of ways to manage and keep track of links
through
out the site, including link validation

of both internal and external links
,
referring pages and facilities to
easily repair broken links.


5.

What features in your application would encourage the use of consistent naming
conventions for files and directories
?

CommonSpot allows you to specify the ‘
Page Title Prefix’

to ensure consistent
titles for each page

and upload file
within the site.


If a string is specified it will
be pre
-
pended to the title specified by the author
, such as
‘PaperThin


Company’
or ‘P
aperThin


Products’


Deployment

1.

Does your application serve content directly to the web or is it necessary to
deploy the content (packaged) to an application server? Can your application do
both?

Yes,

CommonSpot can support the publishing of static HTML
content to the web
or to an application server.


2.

Is your application capable of deploying content on a schedule? Can content be
set to be deployed at a specific time?

Yes, CommonSpot provides mechanisms to be able to schedule the deployment of
content a
t a specific time as well as ‘on demand’.



3.

Will your application allow us to serve or deploy the same content to multiple
environments (TEST, DEV, QA, PRODUCTION)?

Content can be deployed to any number of production servers after being
qualified through
a

workflow
approval on the staging server
.


4.

Will your application permit deployment of the same content item (not a clone or
duplicate) to multiple sites or multiple locations on the same site? What are the
constraints/limitations to this capability?

Yes,

CommonSpot provides the ability to reuse and repurpose content to multiple
sites (subsites or folders) or multiple locations on the same site. There are no
constraints or limitations to this capability.

Integration with 3rd Party Content

1.

Can your applica
tion produce RSS (specify supported version)?

Yes, any version of RSS is supported
.


The University of Texas
-

Arlington


Page
26

of
35


2.

Can your application consume RSS (specify supported version)?

Yes, it can consume any version of RSS
.


3.

Can your application produce web services (specify supported version
)?

Yes, web services are supported
.


4.

Can your application consume web services (specify supported version)?

Yes, web services can be consumed
.


5.

Can your application produce Portlets as specified by Sun’s JSR 168 (specify
supported version)?

Yes, Portlets c
an be produced
.


6.

Can your application consume Portlets as specified by Sun’s JSR 168 (specify
supported version)?

Yes, Portlets can be consumed
.


Support of File Types

1.

How are PDF files created and handled by the system (specify supported
version)?

PDFs ca
n be uploaded, versioned and archived into the system, as well as be
secured for limited access by specified groups
.


2.

To what extent is streaming media supported (specify supported version)?

CommonSpot provides support for streaming media via a out
-
of
-
the
-
box element
or content object. The element provides a wizard for uploading the file and
managing it display.



3.

To what extent are MS Office Documents supported?


CommonSpot offers a wizard interface for end
-
users to upload any file,
Word,
PowerPoint, and E
xcel included
, and to assist end
-
users in creating and
managing hypertext links to those uploaded files.

Administrators can define the file formats wish to support and the size of the
file upload, as well as what users or groups have the rights to upload
files.


CommonSpot also provides several predefined elements or content objects for
displaying and managing
MS Office documents. One such element renders an
uploaded Word document as HTML.


CommonSpot automatically converts

the
Word document to
HTML and r
enders the converted HTML as an element.


4.

To what extent are PDF Documents supported?

CommonSpot offers a wizard interface for end
-
users to upload any file,
PDF

The University of Texas
-

Arlington


Page
27

of
35

included, and to assist end
-
users in creating and managing hypertext links to
those

files.

Com
monSpot also provides a PDF
element that

renders in place

the PDF
document
withi
n the context of the page. So what is the
difference between the
PDF element and creating a hypertext link to a PDF
document? The
PDF
element renders the PDF document within th
e content area of the
CommonSpot Web page

and as full access to
all the navigational and menu
elements.

To open the PDF document full screen, the viewer simply clicks on
the text “Click here to launch the PDF document full screen
” directly below
the elemen
t.

If you were to link to a PDF document instead, the Adobe
Acrobat Reader application is launched and a separate window is opened
presenting the document. The viewer is presented with the PDF document
outside of the CommonSpot Web page.






5.

What other d
ocument types are supported?

CommonSpot supports by default the following file formats, a list of which is
provided below. CommonSpot allows administrators to modify the list (delete)
and add other file format types if not provided.


Adobe Acrobat Forms Do
cument (*.fdf)

AVI (*.avi)

Cascading Style Sheet (*.css)

ColdFusion Component (*.cfc)

ColdFusion Module (*.cfm)

CommonSpot .head Module (*.head)

Flash Movie (*.swf)

GIF (*.gif)

HMTL (*.html)

HTML (*.htm)

JavaScript Module (*.js)

JPEG (*.jpg)

JPEG (*.jpe)

J
PEG (*jpeg)

Microsoft Excel (*.xls)

Microsoft PowerPoint

(*.ppt)


Microsoft PowerPoint

(*.ppv)


Microsoft Word

(*.dot)


Microsoft Word

(*.doc)


MP3

(*.mp3)


MPEG

(*.mpg)


MPEG

(*.mpeg)


PDF

(*.pdf)


PNG Image

(*.png)


Quick Time Movie

(*.qt)


QuickTime

(*.
mov)



The University of Texas
-

Arlington


Page
28

of
35

Real Audio

(*.ram)


Real Audio

(*.rm)


Real Audio

(*.ra)


Real Audio Plugin

(*.rpm)


Real Audio Plugin

(*.rpm)


Rich Text Format

(*.rtf)


Windows Media Audio/Video

(*.wmv)


Windows Media Audio/Video

(*.asf)


Windows Media Audio/Video

(*.asx)


Windows

Media Audio/Video

(*.wma)


ZIP archive

(*.zip)


Support of Industry and Open Source Standards

1.

Describe the compliance of the application with Sun’s J2EE 1.4 specification?

CommonSpot runs on top of Adobe’s ColdFusion application server which can be
instal
led as a WAR or EAR file on top

of a J2EE application server, and by

default ColdFusion runs on

a
JRun
J2EE application server.


2.

To what extent is your application compliant with W3C standards?

CommonSpot renders W3C complaint HTML
.


3.

Which open standards d
o you support?

In general, CommonSpot provides a
flexible architecture which allows the
presentation of content in many standards based formats.


4.

Do you support SOA?


Currently our application does not have a Service Oriented Architecture.


Accessibility S
upport

1.

To what extent is your application compliant with Section 508 of the
Rehabilitation Act (
http://www.section508.gov/
)?

CommonSpot offer many tools that help to assure that Web content created is
compliant w
ith Section 508.



2.

What capabilities does your application have with respect to validating
compliance with Section 508?

CommonSpot do
es not validate 508 compliance, however it does offer tools
and
settings to help adhere to it.


Technical
Details

1.

How are
html comments handled?

HMTL comments can be added to the HMTL template or within the HTML view
of the WYSIWYG editor.


The University of Texas
-

Arlington


Page
29

of
35


2.

Is there support for PeopleSoft Enterprise Portal 8.9?

Yes, CommonSpot can integrate with PeopleSoft by either using content from its
por
tal or providing content to the portal.


3.

Describe your compatibility with existing search tools.

CommonSpot ships with an OEM version of Verity for full text and keyword
searching. CommonSpot
is compatible with
today’s
search

tools including
Google Mini,
G
oogle
Search Appliance

and Endeca amongst others.


4.

What features facilitate search engines (i.e. Google) in finding and indexing the
content?

There are several factors in the code/page that can influence the page’s ranking
with search engines. They include
:




The

page URL

and k
eywords that exist
within the
page URL
.

CommonSpot
support an addressable URL for all Web pages created avoiding
the use of
long query parameters to identify the page.

Addressable URLs are important
because s
earch engines give importan
ce to keywords that exist in the URLs
and

pages that contain the desired keyword in the URL have a

competitive
advantage over others.





Meta
-
tags, which are declared in the top of the HTML/XHTML page code
include tags such as title, keyword and descriptio
n. CommonSpot

user
prompt
s users when creating a new page for

meta
-
tag information

that is
designed for each page individually.
CommonSpot supports title tags <title>
which are usually the first item viewed by the search engine and the visitor.
To rank hi
gh in the search the page title must be the keyword, or at least,
must contain the keyword. CommonSpot supports m
eta
-
tag description
which
is used as the description for the page provided in the search results. To
encourage users to click and visit your p
age listed in the search results, it is
important to create text that stimulates and encourages action and includes
important keywords.




CommonSpot allows administrators to define a list of key words that users
can associate with their content. Web pages
are ranked according to the
keywords that people search, therefore the ability to define list of key words
and phrases that people will use to find your content is important. The
assignment of keywords can be a enforced thus optimizing your website SEO.




C
ommonSpot supports as well subtitle tags <h1>, <h2>, <h3>, which are
used for brief description of different blocks of content on the page. In
addition CommonSpot supports Alt tags for images since search engines
register text and links and not graphical
content. Should user choose to use a
table for laying out content; CommonSpot will prompt for summary text for

The University of Texas
-

Arlington


Page
30

of
35

all columns and rows.




CommonSpot supports Cascading Style Sheets (CSS) which can assist in
making a Website SEO friendly. Font tags and tables
make HTML code
cumbersome, and thus reduce the accuracy of the results. If you use external
CSS files to determine the design attributes, the HTML code will be clean
and will create better search engine rankings.




CommonSpot offers out
-
of
-
the
-
box support f
or Taxonomy which can
facilitate information search.


5.

What sort of URLs does your application create for the managed content?

All URLs are addressable and specifiable and are not dynamically created by the
content management system.


6.

What metadata standar
ds are supported by your project?

CommonSpot’s provides an extensive metadata layer that can be customized to
meet what ever standards necessary including Dublin Core and IPSV.


7.

What output devices are supported by your application?


CommonSpo
t content c
an be rendered for output to any device.


8.

How open is the API for your application?

CommonSpot provides an architecture that is customizable and extensible.


9.

Describe the support you provide for XML.

CommonSpot pages and content elements (portion of page
s) can be served up via
XML
, and developers have the
opportunity to work directly with th
e

XML and
apply XSL transforms at both the page and content element level.


10.

How are modifications made to the CMS system, if they become necessary?

CommonSpot’s inter
face for developers is currently through the CFML scripting
language and the ability
for developers
to
control the look and feel of the site,
seamlessly integrate with and customize CommonSpot is
accomplished through
an extens
ive set (over three dozen) API
s, event hooks, callback and overrides.



Company Focus

1.

Do you specialize in particular areas of ECM, or in comprehensive ECM?

CommonSpot is defined as a Web content management system.


2.

Do you focus on the mid
-
sized organizations (including the departments

of large
organizations), or on enterprise deployments in large organizations?

CommonSpot can scale from a departmental content management solution to one
for the entire enterprise. Please find a list of customer that
exemplifies

both
scenarios.


The University of Texas
-

Arlington


Page
31

of
35


Departmen
t Deployment
s

-

WP Carey School of Business at Arizona State University

Owen Graduate School of Management at Vanderbilt University

Stanford Graduate Sc
hool of Business
-

Intranet Only


Enterprise Deployments





C
ornell University

University of Wisconsin

Kent State

East Carolina University

Oregon Health & Science University


3.

D
escribe
you
r

experience with Higher Education customers?

PaperThin began working with colleges and universities such as University of
Alaska at Anchorage, Santa Clara University, W.
P Carey School of Business at
Arizona State University and Babson College in 2001 on their use of
CommonSpot to publish content with greater speed and ease, making staff more
productive, operations more efficient, and content more relevant and up
-
to
-
date.
Today over three dozen colleges and universities rely on CommonSpot to manage
their internet and intranet sites. A list of colleges and universities can be found on
our Website at
www.pap
erthin.com/customers/customer
-
list.cfm
. We remain
committed to higher education and two years ago established a higher
education
practice supported full time by two sales executives.


4.

Do you focus on particular vertical markets, such as higher education?

How
would you assess your breadth and depth of involvement in that market?

Yes, PaperThin is focused on the higher education market and has
been
working with colleges and universities and their use of CommonSpot
to
manage their public facing websites for

over five years. We believe we
understand well the challenges that higher education institutes faced today

in
the use of the Web as a primary communication tool with prospective students
and parents, enrolled students, faculty and staff.

The features and

functionality offered by CommonSpot reflect this understanding, along with
our continued development efforts. We see higher education as pushing
constantly the edge of the internet envelope and we are pleased to be able to
partner with our customers to de
liver the capabilities they demand.


5.

Do you focus on particular applications?

No.


6.

Tell us about your strategic architecture.

CommonSpot’s architecture scales to handle the most demanding Internet,
intranet or extranet sites. CommonSpot utilizes the hig
h performance and
scalability features of ColdFusion. The application server runs as a multi
-
threaded service. Advanced features such as just
-
in
-
time page compilation

The University of Texas
-

Arlington


Page
32

of
35

and database connection caching make CommonSpot an effective platform for
delivering miss
ion
-
critical Web applications. Support for deployment of multi
-
server clusters with dynamic load balancing and automatic server fail over is
provided through CommonSpot Slave Servers. For customers who wish to
replicate content from one to many servers,
CommonSpot internally manages
the task of replicating all database and file system content to the target server
on a real
-
time, scheduled or on
-
demand basis.


7.

How many of your customers have you built out with a similar list of
requirements?

PaperThin h
as over three hundred customers with a majority of those customers
having similar requirements to those outlined in this RFP. Approximately fifteen
percent of our customers are colleges or universities.



8.

How many of your customers utilize more than 75% of

their purchased licenses?

Most all.


9.

When your application is displacing other systems at a customer site, whose do
you typically displace? What do you see and the best migration plan from those
systems to yours?

Mostly we are replacing processes tha
t

involve static html editing. On occasion
we are replacing a
homegrow
n

content management solution

that was either
developed internally or by the web design firm that last designed their website.
These tools are mostly WYSIWYG and they are looking this tim
e around for a
fuller

featured and robust solution, one that provides for redundancy and load
-
balancing as well. There have been several scenarios of late where we have
replaced
Adobe Contribute.



10.

Do you provide tools for user training and adoption of sys
tems?

PaperThin provides documentation for end
-
users, administrators, designer and
developers as well as a wealth of recorded webinar sessions that address
important concepts as well as specific features and functionality that can be
downloaded, at no addi
tional cost, from our Support site.



11.

Would you be willing to build a pilot program to help validate your system
capabilities?

Yes. PaperThin offers evaluation software which can be downloaded and installed
on our own servers in your environment. With an u
nderstanding of your
expectations for the evaluation or pilot program, we are willing to commit
resources to ensure your success.




The University of Texas
-

Arlington


Page
33

of
35

12.

How much would you charge if your professional services organization were to
convert
http://www.uta.edu/publications/utamagazine/winter_2006/

to the CMS?
Itemize cost.

At this time we do not know enough about the site to be able to provide you with
an estimate to convert the site to CommonSpot. There ar
e many factors that need
to be taken into consideration.


Cost

1.

What is the licensing model for your application (number of users, processors,
etc.)?

PaperThin provides several opt
ions for purchasing CommonSpot.


A Singe Site license is sold on a per serv
er basis and provides support one (1)
domain or ‘root’ Web site. It ships with support for five (5) content contributors,
but additional content contributors can be purchased for a maximum of thirty.


The Standard Edition license is sold on a per server b
asis and support an
unlimited number of domains or ‘root’ Web sites (intranet, internet, and extranet).
It ships with ten (10) content contributors
. A
dditional content contribut
ors can be
purchased including an unlimited contributor option.


These license
s ship with CommonSpot’s rich presentation, authoring and
publishing, template and page management, content scheduling and
versioning, search and indexing, multi
-
language support, knowledge sharing
and discovery and security features.. Several features are

offered as add
-
on
options and are priced and sold separately.



Custom Metadata Support



Taxonomy



Simple Form and Data Sheet Elements



Content Personalization




Static Site Generation


For organizations that want to take advantage of all of CommonSpot’s
featu
res and functionality, have more than fifty content contributors, and need
to scale across multiple servers because of high traffic or security
requirements,
PaperThin offers an
Enterprise Edition
. The
Enterprise Edition
includes:



CommonSpot Content Serve
r License



Read
-
Only Production Server License



Development Licenses



All Add
-
on Features Options (see list above)



Unlimited Content Contributors



The University of Texas
-

Arlington


Page
34

of
35

In addition to the software licenses, PaperThin offers an option to purchase a
one
-
year subscription service t
hat provides access to all enhancements and
updates distributed through point releases and major upgrades at no
additional cost. The one
-
year subscription is an annual fee and it must be
purchased at the same time the server license is purchased. The cos
t for
subscription is 20% of the cost of the server license. Content Contributors
licensing costs are not factored into the cost for subscription.


CommonSpot Single Site License starts at $7,150 and Standard Edition
License at $16,500, not including addi
tional contributors and add
-
on
modules. The CommonSpot Enterprise Edition is
$68,000. Prices include a
fifteen percent (15%) Education Discount.


2.

What are typical implementation and training costs?

Training and implementation costs vary from customer to c
ustomer and can
depend on any number of factors:



N
umber
of
people to be trained
.



Attend regularly scheduled public training or training is delivered on
-
site



Technical resources available to build out ‘master’ template, customize or
integrate application i
f necessary



Complexity of the site and degree which require best practice consulting.


PaperThin
’s

‘Road to Success’ package is a
n

effective solution for building
and launching your sites

using CommonSpot
. This implementation and
training package pairs so
lid lecture
-
based training with on
-
site
implementation support, best practices and pre
-
launch consulting services for
mission
-
critical sites.


A developer will attend PaperThin’s three
-
day public CommonSpot
Fundamentals class to learn the fundamentals and
best practices for
developing sites in CommonSpot. Then, an experienced PaperThin engineer
will come on
-
site, and work side by side with your development team, to help
get you started with building your site in CommonSpot. We will review and
make recomme
ndations regarding template design, security, workflow,
personalization, and more. Most importantly, we’ll provide your developers
and administrators the training necessary to continue with the site
development after the on
-
site training is complete. As
you develop your site,
you’ll have access to our engineers via telephone consulting to address ad hoc
questions, and ensure you are staying on track. Finally, prior to your site
launch, we’ll perform a comprehensive performance review to ensure your
site
is ready for prime time. We encourage customers with complex or
mission
-
critical sites to consider this solution suite in order to get the most
from CommonSpot. This package includes:



One student to attend CommonSpot Developer Fundamentals



Three (3) day
s of CommonSpot Jump Start Implementation Support


The University of Texas
-

Arlington


Page
35

of
35



One student to attend CommonSpot Developer Advanced



Six hours of On
-
the
-
Spot Consulting phone
-
based consultation



Twenty (20) hours of CommonSpot Performance Review


The cost of the ‘Road to Success’ pack
age is $14,350.