Microsoft Word - Web Content Managment System Specification _2_

Web Content Management System

RFP# 0809-7176

Learner Resources and Technology Solutions 143 Bostwick Avenue NE

Grand Rapids, MI 49503-3295

Grand Rapids Community College Web Content Management System

Request for Quote RFP #0809-7176

1.0 Reason for Request for Proposal

Grand Rapids Community College is seeking bids for a Web Content Management System to replace the existing internally developed system. The ideal system will support our existing users and technology infrastructure and provide improved tools for content creation, workflow, and web asset management.

It is recommended that vendors wishing to submit a proposal(s) for this RFQ read this document completely before submitting their response.

1.1. Instructions to Vendors

1.1.1. General Terms and Conditions Definitions:

• The terms "Vendor" and “Submitter” means the business firm submitting the proposal

• The terms "College" and “GRCC” mean the Grand Rapids Community College

• The term "Contractor" means the vendor receiving the award Any contracts resulting from this RFQ:

• shall be governed under, and the rights and obligations of the parties

hereto be determined in accordance with, the laws of the State of Michigan; and

• shall incorporate this document and the responses of the successful

vendor and such responses shall constitute material terms of the contracts; and

• is dependent upon approval by the College’s Board of Trustees.

1.1.2. Communications between the College and Submitters.

Any and all communication with Grand Rapids Community College shall be accomplished as designated below and through the Purchasing Department as designated in 1.1.3. Any vendors that deviate from this requirement will be subject to disqualification.

Web Content Management System – RFP #0809-7176

2



Vendors, who receive this and wish to respond, are requested to reply with their "intent to respond" by 5:00PM, Tuesday, June 24, 2008. A vendor’s intent to respond must be sent to Mansfield Matthewson either by e-mail at [email protected] or FAX at 616.234.3855. The “Intent to Respond” must include the name of a contact person, phone and fax numbers, and an e-mail address.

1.1.3. Vendor Questions

Any questions regarding interpretation or intent must be made in written form. E-mail questions to Mansfield Matthewson, Director of Purchasing, at [email protected] by 5:00PM, Thursday, June 26, 2008. Vendors who have indicated intent to respond will be e-mailed answers to all questions received by 5:00PM, Friday, June 27, 2008.

1.1.4. Method of Response

All vendors must respond with a written proposal that corresponds to the information requests of this RFQ. Vendors must follow the format of the RFQ using the section titles and numbers of each information request (e.g., 1.1.11 – Warranty). If a reference to an attached document is used as part of the response to an information request, the reference must be specific. For example: “See page “8”, paragraph three.” Note: Proposals that do not follow the format of this RFQ and do not provide their responses to information requested per specification of this format will not be considered.

1.1.5. Proposal Submission

The official sealed copy of your proposal must be received in the Purchasing Department of Grand Rapids Community College no later than 1:30PM, Tuesday, July 08, 2008. RFQ proposals must be clearly marked Web Content Management System – RFQ #0809-7176.

Mailed responses to:

Grand Rapids Community College Mansfield Matthewson Director of Purchasing 143 Bostwick NE Grand Rapids, MI 49503


3

mailto:[email protected]

mailto:[email protected]



Delivered Responses to:

Grand Rapids Community College Mansfield Matthewson Director of Purchasing 180 North Division NE

Room 303 Campus Park Plaza Grand Rapids, MI 49503

Telegrams and/or phone responses are not acceptable. THREE copies of the proposal shall be included. Additionally, ONE electronic media (CD) copy of the proposal shall be included. The College will accomplish distribution to proper personnel.

The College will not consider or examine late proposals. Amended proposals will not be considered unless they are received in the Purchasing Department on or before the above time and date. The official copy must contain the complete proposal and related materials. A duly constituted corporate official legally capable of binding the vendor must sign proposals.

1.1.6. Proprietary Information

Vendors must provide a corporate financial statement. Proposals will be opened publicly and will be made a matter of public record and as such may be reviewed by any interested party. Any proprietary information the vendor does not want made available for public inspection must be enclosed in an envelope clearly marked "Proprietary Information". Pricing and contracts cannot be considered proprietary information

1.1.7. Freedom of Information Act

Respondents are advised that all materials submitted to Grand Rapids Community College for consideration in response to this solicitation will be considered the property of Grand Rapids Community College and will not as a matter of course be treated as confidential information. Grand Rapids Community College reserves the right to distribute or not to distribute materials and information submitted by Respondents as it sees fit and/or as required by applicable law.

If a Respondent wishes to supply any information, which it believes is exempt from disclosure under the Act, that Respondent should summarize such information in a separate envelope. Each page submitted should be clearly marked "Confidential," but otherwise be presented in the same manner as the Proposal. However, any such information is provided entirely


4



at the Respondent's own risk and Grand Rapids Community College assumes no liability for any loss or damage which may result from the College’s disclosure at any time of any information provided by the Respondent in connection with its proposal.

1.1.8. Delivery/Pickup

Shipping and handling of any items acquired by the College as a result of this RFQ must be quoted F.O.B. our dock and delivered to the following address.

Grand Rapids Community College Shipping/Receiving

151 Fountain NE Grand Rapids, MI 49503

1.1.9. Addenda to the Request for Quote

In the event it becomes necessary to revise any part of this RFQ, an addendum will be provided to all vendors who have indicated intent to respond as outlined in section 1.1.2.

1.1.10. Non-discrimination in Employment

1.1.10.1.1. Equal Opportunity

The Board of Trustees establishes the goal of minority and women contract awards at twelve percent (12%) of the budget allocated for purchase services.

1.1.10.1.2. Equal Opportunity Employer

The Grand Rapids Community College, as an Equal Opportunity Employer, complies with federal and state laws prohibiting discrimination, including Title VI and Title VII (with Amendments) of the 1964 Civil Rights Act, Title IX of the Educational Amendment of 1972, Section 504 of the Rehabilitation Act of 1974 as amended 38 USCO20-12. It is the policy of the Board of Trustees that no person, on the basis of race, sex, color, religion, national origin or ancestry, age, marital status, handicap, sexual orientation or veteran status, shall be discriminated against in employment, educational programs and activities, or admission. Inquiries or complaints should be addressed to the Personnel/Affirmative Action


5



Office, 143 Bostwick NE, and Grand Rapids 49503-3922, (616) 234-3972.

1.1.10.1.3. Fair Employment Practice Agreement

The enclosed Fair Employment Practice Agreement (Appendix “A”) must be submitted with the vendor’s proposal.

1.1.11. Warranty

Proposals must specify the exact period(s) of warranty coverage for all proposed equipment.

1.2. Evaluation

The College will determine the successful proposal. The Purchasing department is responsible for the entire process from release of the RFQ to the awarding of an agreement. A cross-functional team led by the Learner Resources & Technology Solutions unit, following the College's policies and procedures, will conduct the technical evaluation of all proposals. The RFP evaluation criteria listed below summarizes the elements that will be considered when evaluating submitted proposals. Criteria sub-elements listed are provided for illustration and may not represent all possible.

Evaluation Criteria WeightTechnical and Operational Capabilities

• Meets technical and operational requirements of RFP • Adaptability to increased load and incorporate new technology • Follows industry standards and best practice adherence • Product feature support, demonstrated stability and quality

assurance

30%

Complete Cost of System for 3 years

• Software • Warranty • Maintenance • Support • Installation • Training

30%


6



Ease of Implementation

• Simplicity of installation and operation • Flexibility of solution to align with changing site needs • Ease of upgrades and modifications • Number and range of users supported • Solution alignment with industry best practices • Vendor supplied training or consulting to ease implementation

20%

Vendor and Manufacturer Relations

• Pre and Post Sales Technical Knowledge and Support • Sales Staff Knowledge and Responsiveness • Ease of doing business • Future upgrade path and investment protection • Ability to deliver support and maintenance

o Technical support staff knowledge o Timeliness of follow-up to support calls

• Vendor/customer partnering o Vendor interest in building long term support relationship o Long term discount arrangements o Demonstration of applications in like installations and

environments

10%

Vendor RFP Process

• Timeliness of response • Response organization • Completeness of response

5%

Vendor Background

• Customer references (past, present, similar environ. & products) • History of experience • Demonstrated ability to deliver and install on time

5%


7



Evaluations from above will be tabulated to determine finalists. Up to five finalists will be chosen based on the evaluation of their proposals. The finalists will be required to provide a presentation in evaluation areas stated above and to respond to questions from the evaluation team. The presentation will be done in a format agreeable to the vendor and the College. The College will negotiate with the vendor(s) to reach an agreement that best meets the overall needs and desires of the College. The College reserves the right to reject any and all proposals, wholly or in part, and waive any minor irregularities in the RFQ process.

The evaluation period will be as follows (dates are approximate):

Date/Deadline Milestone

Day, June 17, 2008

RFP published and distributed to potential vendors.

Day, June 24, 2008

Vendors indicate receipt and intent to submit.

Day, June 26, 2008

Questions from Vendors are due to LRTS for clarification.

Day, June 27, 2008

LRTS responses due to Vendors questions.

Day, July 08, 2008

Vendor RFP’s are due, proposals opened

Day, July 09, 2008

Vendors notified that they have been selected for further consideration

Day, July 11, 2008

Vendor presentations to LRTS and staff

Day, July 14, 2008

Vendor selected

Day, July 21, 2008

Purchase agreement presented to College Board of Trustees


8



2.0 Background Grand Rapids Community College was founded in 1914 and today has 15,000 students enrolled in more than 1,600 liberal arts and occupational classes. In addition, 10,000 learners are served by our non-credit instructional programs. These students are served by 250 full-time faculty members and 350 part-time faculty members, assisted by a staff of 650. In addition to GRCC’s urban campus, there are two Technical Education Centers and an off-campus community learning facility. Grand Rapids Community College recognized a need to replace our existing web content management system to maintain the main public website that serves the informational needs for the prospective and current student population and the community at large. The current internally developed system contains the following assets that will need to be migrated to whatever system that we consider as part of our selection process:

• 3000+ Web pages records • 2000+ Images • 1000+ Documents (PDF, Word, Excel) • 1000+ Videos (Flash, Real, Windows Media)

In addition to migrating and maintaining our existing website content and structure, we have 600 existing web content management system user accounts maintained via an LDAP integration that will need to be maintained. There are 50 active system users that represent the majority of the content creation and editing processes on the current system. Any implementation of a Web Content Management System will ideally support our basic infrastructure requirements. These can be summarized as follows:

• Red Hat Linux Operating System • Apache Web Server • Oracle Database • LDAP Authentication

3.0 Requirements

3.1 Company Information Vendors must provide their company name, corporate head quarters and sales locations, Date founded and number of employees. 3.1.1 Account Responsibility


9



Vendors must provide the following: 3.1.1.1 Name, contact information (name, address, phone/fax,

email address), and organizational relationship of all personnel through the region level responsible for marketing, software, and System engineering/installation management support.

3.1.1.2 Name, contact information (name, address, phone/fax, email address), and reporting structure for all personnel who will be the service contact(s) for the College.

3.1.1.3 Vendor must provide information regarding vendor's fiscal

health and of the proposed computer manufacturer if vendor is not the manufacturer. Vendor should include number of years in PC business, quality assurance and testing programs, quantity of PC distributed annually, volume of market share and research and development. Refer to section 1.1.6 if this information is considered proprietary.

3.2 Product Information

Please provide the name of the product you are proposing, the version and release date. 3.2.1 Please give a brief history of your product.

3.2.2 Please detail an overview of your product’s roadmap and

development cycle.

3.2.3 What are the key strengths of your product?

3.2.4 How many web content management system implementations has your company completed?

3.2.4.1 How many in the Higher Education category?

3.3 Functional Requirements

The table below contains a list of functional requirements. There is a table provided in Appendix C each vendor must complete.

Implementation


10



Toolset or service for importing existing web content Pre-built components to speed implementation Architecture Apache Web Server Support Oracle Database Support Scalability Multi-site support Ease of integration with other web applications Development Standards Support Caching Clustering and/or load balancing support Security Encryption Support External Directory Service Support LDAP Integration Integration with existing security framework and guidelines Role based Security User based Security Group based Security Ability to control access to specific administrative functions based on role or user Content Creation Browser based content editing and creation without client software WYSIWYG Editor support, including ability to add images, styles and links Preview content in context prior to publishing Navigation management Support for standard client web browsers Section 508 Accessibility Support Support for publishing to multiple content types (html, pdf, word, etc.) Ability to remove invalid code from imported document formats like Microsoft Word Spelling and grammar check Internal and External Link verification Automatic Site Mapping Required attributes for user entered content Aggregate content objects from multiple sources Interface with third-party syndication engines


11



Support for content syndication (RSS) Blog support Allow personalization by end users Workflow Built in web site statistics reporting for pages/content items viewed, number of users per time period, etc Version control for content Rollback content to earlier version Check in and Check out by users (can be overridden by admin) Content can be validated for accessibility and standards as part of workflow Custom workflow rules for organizational web standards Automatic publishing of content occurring on a scheduled publication date Automatic removal of content occurring on a scheduled expiration date Workflow Creation Utility Toolset to review older published content (6+ months old) for updates Content archiving, including related assets Easy to understand error messages History of published jobs for re-publishing and audit trail Granular publishing that can post individual assets instead of entire site Dashboard for administrators to view status of ongoing publishing processes Track user, date and time of content modifications Global search and replace Email notification of workflow tasks Proactive Error Prevention Templates Template creation with standard design tools Support for multiple device types (WAP, XML, Print) Template API Browser based template creation and editing Browser based style creation and editing Program logic (e.g. “If…Then” statements) within a template for advanced control of output Metadata Allow users to add metadata to content and assets Automatic creation of descriptive metadata Tools for user-defined metadata schema


12



Present metadata to visitors of the site Auto-extract metadata from imported content (author, creation date, color depth, compression, dimensions, resolution) Support for relationships between content assets Search Search results ranked by relevance Search Engine Friendly/Human readable URLs Full text search with keywords Filtering of search results to facilitate more advanced queries Ability to index both by crawling and by file indexing Ability to integrate with third party search engines Ability to hide content and assets from search Ability for users to limit search to specific document types and media formats Search for documents created within a specific date range Caching of results to speed duplicate queries Ability to save searches so they can be re-run at a later date Ability to define subsets of the content to be searched Permissions-based security for filtered search results Ability to define and control exclusions to indexing/searching Asset Management Image asset management Ability to crop, rotate and resize images Manage ALT tags for images on the web site Version control of digital assets Support any file format in the digital asset management system Repository to collect and store documents, images and other objects Naming conventions for images and assets Usage tracking of images and assets

4.0 Information Requests

Vendors must respond to the following information requests.

4.1 License

4.1.1 How is your product licensed (per user, per CPU, or per server)?

4.1.2 What is included in this license? Please detail any features such as maintenance and implementation or additional installations.


13



4.1.3 Please detail any discounts available for higher education customers.

4.1.4 What is the duration of the license and the annual renewal cost?

4.1.5 Are major product upgrades or revisions included in the license?

4.1.6 Does the license include the product source code or development tools?

4.1.7 Are there any client, server or third party licenses required for a fully-functioning implementation of your product? If so, please detail the costs for each.

4.1.8 Are there any other potential costs incurred during an implementation of your product?

4.2 Maintenance and Support

4.2.1 What kind of maintenance and support packages do you offer? Please include detail for online, email, and phone support, as well as hours of availability for each type.

4.2.2 Where is the support team based?

4.2.3 What is the average support response time?

4.2.4 What is the process for reporting bugs?

4.2.5 What is the communication policy for patches, hot fixes, and upgrades?

4.2.6 Is there installation support for patches, hot fixes, and upgrades?

4.3 Implementation Services

4.3.1 What implementation services do you offer?

4.3.2 What do these implementation services cost if they are not covered under the license agreement?

4.3.3 What is a typical implementation timeline for your product?

4.4 Training

4.4.1 What training programs are available for administrators and developers for your product?

4.4.1.1 What are the available training formats (Online, Classroom, On Site)?


14



4.4.2 What training programs are available for end users or content creators for your product?

4.4.2.1 What are the available training formats?

4.4.3 Is documentation for your product available?

4.4.3.1 What are the available documentation formats?

4.5 System Architecture

4.5.1 Please provide a detailed overview of your products system architecture, including hardware requirements.

4.5.2 Does your program require a separate application server(s)?

4.5.3 What standards does your program support?

4.5.4 What programming language is your product developed in?

4.5.5 What scripting languages does your product support?

4.5.6 Please detail your product’s support for business continuity and failover and list any associated costs. If possible, provide a system diagram for a Dual Data Center environment.

5.0 Presentations

5.1 Vendors whose proposals are determined by the evaluation team to meet or exceed the requirements of this RFQ may be requested to provide a presentation to provide an overview of their proposal(s) and respond to questions from the evaluation team. The presentation will be done in a format agreeable to the vendor and the College.

6.0 Quality and Performance Standards 6.1 Successful bidder shall include a description of their quality program including

complaint resolution and corrective action procedures. 6.2 Successful bidder shall describe metrics that are tracked, the frequency at

which they are tracked and guaranteed level of performance. Submission of quality and performance history is also encouraged.

6.3 All bids must include five references (aligned with proposed configuration), including two higher education institutions (if possible) and three additional references. Local West Michigan references are preferred. References should include company name, contact name, address, phone, fax and email address and contact information for the specific person who is knowledgeable about the


15



vendor’s record and performance. References may be contacted for consultation and/or site visits at our discretion.

7.0 Cancellation/Non-Performance Evaluations

7.1 The College reserves the right to terminate this agreement within thirty (30)

days of written notice and prior to any Contract termination date, if either service, equipment or Contract performance and conduct, as judged by College, does not meet acceptable standards.

8.0 Pricing

8.1 Vendors must provide with their proposal a total project cost over a three

year period for an installation of the College’s size and scope. Please include detailed costs for the software license, implementation services, maintenance and support.

8.2 Vendors must provide detailed pricing for their proposals making certain to itemize the costs for each piece of equipment and each type of service proposed.

8.3 Any items or services that would result in additional charges must be clearly presented and explained

8.4 If the vendor believes the configuration is incomplete, they should add models/features with their associated costs and provide rationale for their recommendation.

8.5 Vendors must indicate what items have warranties and what the duration of the warranties are. If no warranty in offered, the vendor must indicate what the maintenance costs, per year, will be. Any quotas or limits of service must be clearly identified and remedies or additional costs explained.

8.6 All prices and rates are guaranteed to be firm for the first year. Please indicate pricing and/or discount percentage commitments for subsequent years (i.e. specific prices/discounts for years two and three; percentage increase maximums, or other defined methods). GRCC reserves the right to exercise the option to extend or close any awarded contract at the expiration of year one.

8.7 Any shipping costs to be incurred by the College must be quoted FOB our dock. Shipping costs must be provided by item and sub-totaled by system.

8.8 In addition to what has been specified, Suppliers are encouraged to provide “expressive bid” alternate pricing by suggesting alternate specifications, technology, terms and conditions, service conditions, etc. that could result in flexibility and cost savings for Grand Rapids Community College and for the


16




17

Vendor. Vendors must insure that their alternate proposal meets or exceeds requirements and specifications as detailed throughout this RFP.

8.9 Payment terms will be net 30 days upon delivery of products and following completion of any services and receipt of invoice.

9.0 Contracts

9.1 Vendors must attach any purchase agreements and support agreements

necessary to be completed for any equipment and software purchased as a result of this Request for Quote.

10.0 Taxes

10.1 Grand Rapids Community College is exempt from Michigan Sales Tax and

will furnish a tax exempt certificate upon request. Disclaimer: If any changes are made to this solicitation document by any party other than Grand Rapids Community College, the original document in Grand Rapids Community College’s files takes precedence.

Appendix A

Fair Employment Practices Agreement Completion of this Form is Necessary to do Business

with the Grand Rapids Community College

This rider is attached to and made a part of the bidding form agreement between the Grand Rapids Community College and

Name of Company During the performance of this contract, the above named firm agrees as follows: 1. Will not discriminate against any employee or applicant for employment because of race, color, religion,

sexual orientation, gender, age, national origin, height, weight, marital status, disability, or status as a veteran (“protected classes”) unless necessary as a bona fide occupational qualification. Said company will take action to ensure that applicants are employed without regard to their membership in a protected class, as defined above. Such action shall include but not be limited to the following: employment, upgrading, demotion or transfer, recruitment or recruitment advertising, layoff, recall, or termination, rates of pay or other forms of compensation, and a selection for training, including apprenticeship. He/She agrees to post in conspicuous places, available to employees and applicants for employment, notices to be provided by the contracting officer setting forth the provisions of this nondiscrimination clause.

2. Will, in all solicitations or advertisements for employees placed by or on behalf of the company, state

that all qualified applicants will receive consideration for employment without regard to race, color, religion, sexual orientation, gender, age, national origin, height, weight, marital status, disability, or status as a veteran unless necessary as a bona fide occupational qualification.

3. Will, as applicable, provide a written notice of the companies’ commitments under the Fair Employment

Practices Agreement to each labor union representative or worker(s) with which he/she has a collective bargaining agreement or other contract understanding. He/She further agrees to post a copy of the notice in conspicuous places available to employees and applicants for employment.

4. Will furnish all information and reports as requested by Grand Rapids Community College, including

pertinent books, records, and accounts to ascertain compliance with Grand Rapids Community College nondiscrimination policies.

5. In the event of noncompliance with the nondiscrimination clauses of this contract or with any of the said

policies, this contract may be canceled, terminated, or suspended in whole or in part, and the said company may be declared ineligible for further contracts in accordance with procedures established by the Grand Rapids Community College and such other sanctions may be imposed and remedies involved as provided by rule, regulation, order or statement of policy of the College or as otherwise provided by law.

6. The following provisions are required by the Elliot-Larson Civil Rights Act: The company and, where

applicable, sub-contractors shall not discriminate against any employee or applicant for employment, to be employed in the performance of this contract, with respect to his/her hire tenure, terms, conditions or privileges of employment, because of his/her f race, color, religion, sexual orientation, gender, age, national origin, height, weight, marital status, disability, or status as a veteran unless necessary as a bona fide occupational qualification

7. MINORITY OWNERSHIP

Ownership Interest: Public Act 428 of 1980 requires that the minority business owner or woman business owner own more than 50% of the shares or interest in the business and share in more than 50% of the net profit or loss of

the shares or interest in the business which accrues to shareholders who are members of a minority or a woman owned business.

CONTROL AND OPERATION

P.A. 428 of 1980 requires the minority or woman to exercise the power to make policy decisions and be involved in the day-to-day management of the business. Please check the following applicable criteria: ___Minority-Owned ___Female-Owned Company Name: ______________________________________Phone:________________ Address: _________________________________________________________ Type of Business__________________________________________________ ___Independent Firm, or Owned/Controlled by: _________________________ Corporate Address of Parent Firm___________________________________ Personnel as of (Payroll Date)__/__/__ JOB CATEGORIES ALL PERSONS NON WHITE PERSONS NON WHITE M/F/TOTALS M/F TOTALS Officials & Managers / / / Professionals / / / Technicians / / / Sales Persons / / / Crafts Persons / / / Operatives / / / Service Workers / / / Laborers (Unskilled) / / / Apprentices / / / All Others / / / Total Employees / / /

PLEASE NOTE: GOVERNMENTAL REGULATIONS PERMIT THE GATHERING OF THIS DATA.

NAME OF PERSON PROVIDING DATA (PLEASE PRINT):___________________________________ PHONE: _____________________________ DATE: _____________________________ TITLE: ______________________________ SIGNATURE: ______________________________

Appendix B

MBE/WBE PARTICIPATION

In addition to the information required in the Fair Employment Practices Agreement Form, this form shall be executed by the Bidder and submitted with the Bid.

A. Definitions

1. “Minority” shall mean a person of Black, Hispanic, Asian,

American Indian and Aleut descent shall be considered as such only if they are certified by the Bureau of Indian Affairs as having a minimum of twenty-five (25%) percent American Indian or Aleut ancestry.

2. “Minority” Business Enterprise”, or MBE, shall mean a Minority Business Enterprises, which: (I) It shall be at least 51% owned by one or more minorities; or, in the case of a publicly owned business, at least 51% of its stock shall be owned by one or more minorities; (II) It shall be managed by, and its daily business operations shall be controlled by one or more such individuals.

3. “Women Business Enterprise”, or WBE, shall mean a Women’s Business Enterprises, which: (I) It shall be at least 51% owned by one or more women; or in the case of a publicly owned business, at least 51% of its stock shall be owned by one or more women: (II) It shall be managed by, and its daily business operations shall be controlled by one or more such individuals.

4. “Women/Minority, Business Enterprise: or W/MBE, shall mean an enterprise which: (I) It shall be at least 51% owned by one or more women and minorities; or in the case of a publicly owned business, at least 51% of its stock shall be owned by one or more such individuals: (II) It shall be managed by, and its daily business operations shall be controlled by one or more such individuals’ contract. W/MBE shall be classified as MBE’s if minorities own a greater share than women; the Manager shall classify W/MBE’s as WBE’s if women own a greater share than minorities.

5. “Subcontractor” shall mean an entity, which is or will be a direct contract or with the Bidder or Bidders Subcontractors and which shall provide services, materials, or supplies under agreements with the Bidder or other Subcontractors.

6. “Joint Venture” shall mean a business arrangement between two or more firms for the purpose of jointly working on construction project.

Name & Address

MBE*

WBE*

Type of Work- Subcontractor,

Material Supplier, Joint

Venture, etc

Approximate Dollar Amount of MBE/WBE Participation

Appendix C

In the Y/N column, answer affirmatively only if this functionality is available “out-of-the-box”. If the feature is available at an additional cost, please include this figure in the Extra column. If this feature is planned for a future product release, include the year or version number in the Future column. If the If this functionality is supported by an add-on component or with a reasonable amount of additional programming, please detail this in the Custom column. There is also a column for your Comments.

Grand Rapids Community College Web Content Management - Functional Requirements

Y/N Extra Future Custom Comments

Implementation Toolset or service for importing existing web content Pre-built components to speed implementation Architecture Apache Web Server Support Oracle Database Support Scalability Multi-site support Ease of integration with other web applications Development Standards Support Caching Clustering and/or load balancing support Security Encryption Support External Directory Service Support LDAP Integration Integration with existing security framework and guidelines Role based Security User based Security Group based Security Ability to control access to specific administrative functions based on role or user


Content Creation Browser based content editing and creation without client software WYSIWYG Editor support, including ability to add images, styles and links Preview content in context prior to publishing Navigation management Support for standard client web browsers Section 508 Accessibility Support Support for publishing to multiple content types (html, pdf, word, etc.) Ability to remove invalid code from imported document formats like Microsoft Word Spelling and grammar check Internal and External Link verification Automatic Site Mapping Required attributes for user entered content Aggregate content objects from multiple sources Interface with third-party syndication engines Support for content syndication (RSS) Blog support Allow personalization by end users Workflow Built in web site statistics reporting for pages/content items viewed, number of users per time period, etc Version control for content Rollback content to earlier version


Check in and Check out by users (can be overridden by admin) Content can be validated for accessibility and standards as part of workflow Custom workflow rules for organizational web standards Automatic publishing of content occurring on a scheduled publication date Automatic removal of content occurring on a scheduled expiration date Workflow Creation Utility Toolset to review older published content (6+ months old) for updates Content archiving, including related assets Easy to understand error messages History of published jobs for re-publishing and audit trail Granular publishing that can post individual assets instead of entire site Dashboard for administrators to view status of ongoing publishing processes Track user, date and time of content modifications Global search and replace Email notification of workflow tasks Proactive Error Prevention Templates Template creation with standard design tools Support for multiple device types (WAP, XML, Print) Template API


Browser based template creation and editing Browser based style creation and editing Program logic (e.g. “If…Then” statements) within a template for advanced control of output Metadata Allow users to add metadata to content and assets Automatic creation of descriptive metadata Tools for user-defined metadata schema Present metadata to visitors of the site Auto-extract metadata from imported content (author, creation date, color depth, compression, dimensions, resolution) Support for relationships between content assets Search Search results ranked by relevance Search Engine Friendly/Human readable URLs Full text search with keywords Filtering of search results to facilitate more advanced queries Ability to index both by crawling and by file indexing Ability to integrate with third party search engines Ability to hide content and assets from search Ability for users to limit search to specific document types and media formats Search for documents created within a specific date range Caching of results to speed duplicate queries Ability to save searches so they can be re-run at a later date


Ability to define subsets of the content to be searched Permissions-based security for filtered search results Ability to define and control exclusions to indexing/searching Asset Management Image asset management Ability to crop, rotate and resize images Manage ALT tags for images on the web site Version control of digital assets Support any file format in the digital asset management system Repository to collect and store documents, images and other objects Naming conventions for images and assets Usage tracking of images and assets