The Vendor is required to provide a vendor-supported, web-based, fully accessible electronic catalog management system (eCatalog system).
- The University seeks to:
• Modernize catalog management and publication processes
• Improve workflow efficiencies and editorial governance
• Enhance accessibility, searchability, and usability
• Strengthen integration with curriculum planning systems
• Maintain continuity of publishable catalog versions
• Adopt a platform compatible with long term academic information management strategies
- Provide a full catalog management solution including:
1. Implementation and Configuration
• Assist in the configuration and implementation of the software solution used to store catalog content, including courses, programs, policies, services, and other academic information.
• Support setup that enables administrative users to create, update, manage, and publish catalog content.
• Ensure the solution displays catalog information through a searchable, accessible, and user-friendly web interface.
2. Project Management
• Provide a comprehensive project plan outlining milestones, tasks, timelines, roles, and dependencies for implementation.
• Deliver ongoing project management services, including coordination, monitoring progress, risk tracking, and issue resolution throughout the implementation period.
3. Data Migration and Catalog Conversion
• Convert existing published catalogs into the new system’s format or otherwise ensure they are properly archived and accessible from the existing solution.
• Validate migrated content for completeness, correct formatting, and accessibility compliance.
4. Training and Knowledge Transfer
• Train institutional staff, including catalog administrators and content editors, on how to use the system, manage content, and publish catalogs.
• Provide training materials and/or documentation to support long-term internal training needs.
5. Catalog Publication Timeline
• Ensure the solution and associated workflows are fully implemented in time to support publication of updated catalogs for the next academic year no later than mid-May 2026.
6. Ongoing Support Services
• Provide ongoing functional and technical support, including troubleshooting, system maintenance, updates, and enhancements as needed to ensure continuous, reliable operation of the catalog solution.
7. Catalog Interface, Accessibility, and Publishing
• Provide a searchable, accessible web interface for the academic catalog meeting WCAG 2.1 AA or higher.
• Support a minimum of three catalog types: undergraduate, graduate, and medical.
• Support multiple published versions of each catalog type (e.g., current, future, archived).
• Support custom university branding, including colors, fonts, logos, and styling.
• Allow for periodic brand updates aligned with institutional brand refreshes.
8. Content Management and Course Data
• Support automated or bulk updating of course information, including options such as flat-file imports, service-based imports, APIs, or similar mechanisms.
• Provide tiered user-access levels that allow segmentation by content type, academic division, department, or other configurable criteria.
• Ensure users only access and modify content within their assigned areas.
• Include auditing functionality to track all changes made within the system.
• Allow central administrators to review edits, compare versions, and identify modifications prior to publishing.
9. Exporting, Accessibility, and External Sharing
• Allow catalog content to be exported to Word, PDF, or similar formats for external sharing.
• Exported content must remain fully accessible, retaining structure, headings, links, and tagging compliant with accessibility guidelines.
10. Reporting and Monitoring
• Offer general reporting features to identify content that is updated, outdated, unpublished, or pending review.
• Provide system-level reports helpful to catalog administrators and academic units.
11. Suite Integration / Ecosystem Fit: The catalog system must be part of a broader suite of curriculum related services, such as:
• Curriculum approval and workflow
• Curriculum governance
• Class schedule planning
• Academic scheduling and timetable management
12. Integration and Security
• Provide APIs or comparable integration technology to enable loading, sharing, or displaying catalog data on external websites or systems.
• Support Single Sign-On (SSO) using industry-standard protocols (e.g., SAML, OAuth, OpenID Connect).
- Contract Period/Term: 2 years
- Questions/Inquires Deadline: January 26, 2026
