Project Overview

Why a new SIS?

The current student information system in use at the 5Cs was implemented over 20 years ago. That product is built on outdated on-premises technology, has been highly customized, and is approaching end-of-life. This leaves the 5Cs in a precarious position where academic operations rely on a fragile technical infrastructure and a diminishing pool of experts capable of maintaining it. The Consortium needs to transition away from its present system and implement a contemporary and more robust SIS that can meet The Claremont Colleges’ unique needs for the next 20 years.  

Why Anthology?

The Claremont Colleges identified Anthology Student through an SIS market analysis and vendor selection process, with the support of Strata Information Group. Anthology presented a proof-of-concept of its Student product to 5C stakeholders that demonstrated the product’s functionality aligned with the Colleges’ critical needs including support for cross-registration, abundant integrations with third party systems, a contemporary cloud-based technical infrastructure, and flexible configuration capabilities. Through our rigorous vendor selection process, the Colleges obtained feedback from over 50 5C functional and technical subject matter experts, which confirmed Anthology’s ability to meet the Consortium’s needs. Reference calls with other Anthology clients also supported this assessment and inspired confidence in the vendor’s commitment to customer success.

Project Factsheet

(click to enlarge)

Project FAQs

(click to enlarge)

SIS Implementation Project Milestones (March 2024)

(click to enlarge)

Anthology SIS Project Guiding Principles

We will endeavor to align our business processes and integrations to make the best use of Anthology’s functionality wherever possible: too many customizations and multiple versions of integrations will create challenges with ongoing maintenance. Where customizations and divergent integrations are necessary, we must make a clear and compelling case for them (e.g., an academic policy requirement) and accept the downstream consequences of managing and maintaining them ourselves.

Design and configuration decisions should result in straightforward solutions that use the system’s fields and features as the vendor recommends. 

Before committing to a configuration, design, or business process decision, carefully consider that decision’s downstream consequences for other stakeholders (students, faculty, reporting, and cross-functional users)

We will respect each college’s needs and each other’s opinions as we drive toward consensus on configuration and design decisions. In the unlikely event that we cannot achieve consensus on a design decision, we will escalate decisions to the SIS-EC for prompt resolution. 

Change management is a collective responsibility. Project participants will contribute toward change management and communication efforts that are appropriate for their roles at their home colleges. 

Some desired features and functions will not be ready by our go-live date. We will distinguish those features we must have to go live from those we can wait to launch after go-live.

Project Timeline

Plan

Jun 2023 – Sept 2023

Design

Aug 2023 – Jan 2024

Build

Feb 2024 – Jan 2025

Test

May 2024 – Mar 2025

Deploy

Apr 2025 – Jun 2025

Transition

Jun 2025 – Aug 2025