Web-Based Curriculum and Catalog Software

University requires a web-based platform for managing academic catalogs and automating the curriculum approval process, with integration to Banner SIS and single sign-on functionality.

Purchase a web-based/hosted integrated software solution for catalog and curriculum management.
Manage course curriculum approval process through automated workflow.
Provide ongoing software support and updates.
Ensure compatibility with Banner Student Information System.
Ability to import pre-existing data while maintaining integrity and functionality.
Award will be made to one Offeror.
Contract includes one-time product purchase, one year maintenance with four one-year renewals, and professional services for implementation.
Specify a proposed implementation timeline including data conversion, functional work, hours, and go-live date.
Submit proposals electronically through Clemson University online bidding system.
Submit two separate documents: Technical Proposal (no pricing) and Financial Proposal.
Technical Proposal must address all requirements in Section III (Scope of Work/Specifications) and Appendix A (Technical Specifications).
Describe security features and sign-on authentication process.
Describe how the solution integrates with existing systems, including curriculum management and catalog management, and Banner.
Describe implementation approach, team members, and estimated time.
Describe how initial implementation establishes baseline curriculum and catalog, including data import and attachment of historical documents.
Provide a detailed timeline for catalog and curriculum management modules to meet aggressive deadlines (e.g., catalog publication by May 2017).
State total number of implementations completed in the last 12 months with estimated and actual times.
Describe training and reference resources available to users.
Describe ongoing technical support and software update procedures (frequency, costs, limitations).
System must be available 24/7 with exception of scheduled maintenance.
Describe tools for editing content.
Provide administrators ability to control style guidelines and limit editor formatting changes.
Provide administrators ability to auto-correct information.
Display multiple catalog types and years, including archived versions, with real-time modification capability.
Describe user-navigation features and search functionality.
Permit users to maintain a portfolio of content of interest.
Support referencing course information inline within programs.
Provide ability to print any page from online catalog without navigational elements.
Editing roles must be permission-based for colleges/departments.
Include a notification system to alert Catalog Editor of submitted changes.
Allow users to search for proposals and originators to access drafted versions.
Provide ability to create working agendas for committee meetings.
Allow course or program curricular changes to be proposed, approved, and held for a later catalog.
Provide ability to track changes to outcomes and objectives for courses and programs.
Allow users outside the system to participate in review process or view pending processes with security features.
Proposals in progress must reflect personnel changes immediately without user intervention.
Provide a repository for approved proposals or methodology to export them.
Allow Word or Acrobat documents to be added to proposal records.
Allow approvers to make comments on proposals (viewable by all or private).
Allow proposal routing to be altered for specialized approval tracks.
Provide organization's history, experience, year business started, total employees, and headquarters location.
Provide information regarding failed projects and litigation.
Provide a list of a minimum of three references from college/university accounts.
Provide a complete customer list.
Provide information on key staff, resumes, and areas of responsibility.
Provide satisfactory evidence of all required insurance coverage and licenses.
Financial Proposal must list all anticipated costs for the total potential term (initial year plus four option years).
Pricing must be based on unlimited users annually for catalog and curriculum management software.
Pricing must include a minimum of three environments (Test, Beta, Production).
Pricing must be inclusive of all travel, meals, lodging, and other expenses.
Offeror's Financial Proposal must be submitted as a separate file from the Technical Proposal.
Solution must be fully functional as two standalone systems (catalog and curriculum management).
Solution must be entirely web-based and vendor hosted.
Access to public e-catalog, administrative software, and curriculum management from Windows, Mac, or Linux workstations, any location with Internet, using standards-based browsers.
Solution must provide role-based access to features.
Solution must apply Clemson University 'brand' to public-facing web content, with no additional cost for updates.
Solution must allow removal and addition of user roles directly within the interface without IT or vendor involvement.
Solution must comply with SACSCOC requirements and ADA/Section 504 accessibility standards.
Solution must provide backup and disaster recovery options.
Awarded contractor must provide test plans for core functionality and integration testing.
Solution must allow changes to be embargoed pending approval and implementation by the Catalog Editor.
Solution must publish electronic catalogs on demand directly within the system without IT or vendor involvement.
Solution must treat course information relationally in the database (single edit updates all references).
Solution must share content between catalogs (departments, programs, courses, policies, faculty).
System must publish catalog into print format on demand with auto-generated Table of Contents and Index.
System must include auto-generated HTML electronic catalog interface, HTML-5 smartphone compatible, and compatibility with tablets/mobile devices.
System must generate web-based degree plans on demand, with checkboxes, dynamic updates, and print mechanism.
Support a collaborative edit-approval system with concurrent access for unlimited administrative staff (administrators and editors).
System must support global, limited editorial, and read-only access.
Solution must support and track relationship of content items to their owning entity.
Content access control must support granting editorial access to entire department content or single course.
Solution must provide current and historic audit trail showing creation/modification date/time, approvals, comments, versions, and editors, segregated by catalog year.
E-catalog portal must be integrated with Web analysis software for site statistics and reports, with Google analytics support.
Solution must have ability to import information from other data structured on campus systems.
Solution must provide ability for users to submit changes, additions, and deletions to courses and programs in one single system.
Solution must automatically identify affected departments/courses/prerequisites/programs/web pages and generate an impact report.
Solution should auto-populate information when a change is proposed to an existing course or program.
Solution must provide user configurable forms, allowing administrative users to make changes without IT or vendor involvement.
Solution must provide for an unlimited number of forms at no additional cost.
Solution must provide ability to print proposals on demand including field information, change tracking, and decisions.
Solution must provide ability to save proposals and return to edit without submitting.
Solution must provide ability to add comments to a request, with timestamps and author identification.
Solution must provide ability to add an unlimited number of attachments to a proposal.
Solution must have a workflow management tool with configurable steps, permission levels, view-only access, and accept/reject changes.
Solution must provide for configurable datasets, smart fields, conditional triggers, and validated field options within workflow.
Solution must track if/when a proposal has been modified, what information was modified, how long it spent on each step, and approval/rejection date.
Solution must provide ability to send proposals 'back' in the process if tabled, configurable step-by-step.
Solution must include ability for users to determine when notifications are received (e.g., daily digest).
Solution must provide automated notifications to users for tasks, status changes, or comments.
Solution must provide for customizable signature options, including paper uploading and electronic signature pin.
Proposed solution must be capable of migrating University's current catalog data.
Vendor personnel must protect access privileges and maintain confidentiality of University data.
Solutions must comply with FERPA, Clery Act, ADA, Rehabilitation Act Section 504 & 508, COPPA, HIPAA, and Clemson's Privacy Policy.
Offerors shall provide a detailed implementation plan with timeline, milestones, completion, and university resource requirements.
Selected vendor must supply initial technical training sufficient for Clemson personnel to fully understand, test, validate, use, operate, and instruct others.
Solution shall utilize currently supported versions of application frameworks (Java, PHP, etc.).
Offeror should describe compatibility or interoperability with desktop productivity tools (Microsoft Office, etc.).
Offeror should describe the Application Programming Interface (API) if available.
Offeror should describe the Application Server environment required.
Software installed/licensed to Clemson must not have dependency on Oracle Java unless licensing/maintenance costs are included (preference for OpenJDK).
Recommended architectural designs shall be resilient and able to run with minimum downtime in a cloud environment.
No Flash technology.
Solution shall be compatible with Oracle or MS SQL database technologies.
Offeror should provide technical documentation for database configuration, installation, backup, and maintenance scripts.
Solution shall be compatible with CU's Web Server hosting requirements for Linux-based (Oracle Enterprise Linux 6.x/7.x+) and Windows-based (Windows Server 2012 R2+) systems.
Solution shall be IPV6 compliant.
Contractor agrees to an independent third-party audit (SOC report) at least once a year, with results shared with the Institution.
Solution shall support one of the following for end user authentication: Shibboleth (preferred), Active Directory, Secure LDAP, CAS.
SHA-1 user/password hashing (stored passwords must be encrypted).
API for provisioning should support one of the following: REST (preferred), SOAP, NetIQ IDM driver, other HTTP based protocols.
If CU Hosted, SaltStack 'states' should be provided or consulting hours to develop them.
No license management solution based on a physical object (USB key/dongle) is acceptable.
Vendor Hosted Solutions: operate in virtual server or container environment.
Vendor Hosted Solutions: describe minimum and recommended server configurations (OS, CPU, Memory, Disk Space, firewall exceptions).
Vendor Hosted Solutions: describe any 3rd party software required.
Vendor Hosted Solutions: adhere to standard supported operating systems of Clemson University.
Vendor Hosted Solutions: data may only be used as directed by Clemson University.
Vendor Hosted Solutions: provide mechanism for Clemson University to control user and system level access (Shibboleth for user level).
Vendor Hosted Solutions: provide mechanism for Clemson University to monitor system status.
Vendor Hosted Solutions: not store Clemson University data in a facility outside the United States.
Vendor Hosted Solutions: provide mechanism for Clemson University to receive data files for Data Warehouse (scheduled, automated, controlled).
Vendor Hosted Solutions: provide mechanism for Clemson University to review and export security data (login history, record modifications, user location).
Customer (CU) will require an annual review of SOC1 (SSAE16) reports.
CCIT Business Continuity/Disaster Recovery Team will require an annual review of vendor disaster recovery plan or SOC2 report.
CCIT Business Continuity/Disaster Recovery Team will require an exit strategy that can be tested annually (database backup recoverable at CU datacenter).
Primary and secondary hosting sites must be located a minimum of 150 miles apart from Clemson, SC.

$500,000 – $2,000,000

The contract is estimated to start on January 1st, 2027, and end on December 31st, 2032. The implementation of the catalog management system is expected to begin in early 2017 to publish a catalog in May 2017, with the curriculum management system implementation to follow shortly thereafter (historical context).

Clemson University

Organization overview and procurement intelligence available on paid plans.

The organization seeks a vendor to provide a web-based, hosted software solution designed to create, manage, update, and maintain both undergraduate and graduate catalogs. This solution should also facilitate the course curriculum approval process via a fully automated workflow. Ongoing support and updates are required to ensure continued compatibility with the Banner Student Information System.

The project involves leading the procurement and implementation of a new web-based platform for the production, maintenance, and archiving of university catalogs, as well as comprehensive curriculum management. The solution must offer a user-friendly interface for catalog management, a workflow engine for curriculum approval that integrates with current and future Banner system versions, and support for single sign-on through the iRoar portal for authorized users.

Key features include the ability to generate print-friendly catalog pages, tools for editing content, options to track changes to outcomes and objectives at the course and program level, and robust security and workflow capabilities.

Web-Based Curriculum and Catalog Software

Overview

Fit Score

SUMMARY

KEY REQUIREMENTS

BUDGET

CONTRACT DURATION

TIMELINE

Issuing Agency

DESCRIPTION

Similar RFPs