Triton Student System (TSS)

Starting March 2, 2026, the TSS Project Change Management and Training Teams will host weekly office hours. 

Office hour schedule: 

Mondays: 3–4 p.m. 

Wednesdays: 9–10 a.m. 

(Zoom link for office hours - opens in a new tab) 

Vision

• The TSS Project's strategic vision mirrors that of the overall SIS Project portfolio. View the SIS Project Vision.

Guiding Principles

• The TSS Project's guiding principles mirror those of the overall SIS Project portfolio. View the SIS Project Guiding Principles.

Shared Expectations

• The TSS Project's shared expectations mirror those of the overall SIS Project portfolio. View the SIS Project Shared Expectations.

**Need to Zoom in? Need additional viewing support? Please access these slides via the following link: TSS Project: Timeline. Descriptive and explanatory text has been added in the speaker notes of each slide.**

Below, find the detailed list of past, current and upcoming project milestones. Please note that upcoming milestones are subject to change.

• Pre-work: Process Mapping, Ideal State Development, RFPs/Vendor Selection (2019-2023)
  • Project Initiation (August 2019)
  • Process Landscape Approved by Stakeholders (December 2019)
  • Request for Proposal (RFP) #1 Released to Vendors (March 2020)
  • Current State Process Mapping (July - December 2020)
  • Conference Room Pilots with RFP #1 SIS Vendors (Nov 2020 - Jan 2021)
  • Ideal State Process Mapping Sessions with SMEs (February - May 2021)
  • Request for Proposal #2 Seeking a Vendor Partnership Released (October 2021)
  • Request for Proposal #3 Released (September 2022)
  • Conference Room Pilots with RFP #3 SIS Vendors (March - May 2023)
  • New Student Information System Vendor Selected (December 2023)

• Plan: Prepare (2023-2024)
  • Project Kickoff (March 2024)
  • Advisory Committee Meeting Kickoff (June 2024)

• Execute: Design, Build, Test & Train (2024-2026)
  • Process Design Workshops (May 2024 - March 2025)
  • System Testing (TBD)
  • System Training (TBD)
  • Initial Release Go Live (Summer 2026 Quarter)

• Close: Hypercare (2026)

Escalation Process

• TSS Implementation Team Members
• TSS Advisory Committee Members
• TSS Change Coalition Members (link coming soon!)

For more information about the team members, please view the TSS Project Overview Presentation. Learn more about the roles of this team in the SIS Project Teams article.

If you have difficulty accessing these links, please contact esr-student@ucsd.edu.

Articles shared below are listed from newest (top) to oldest (bottom). Please note that some content of older articles may be slightly out of date. To ensure you review the most accurate content, we recommend to review the most recent (newest) project information or articles. 

• TSS Scheduling Training: Coming Soon! (February 2026)
• Triton Student System (TSS): Demonstrations Recap (January 2026)
• Triton Student System (TSS): System Testing (October 2025)
• Prepare for Launch in Summer 2026: Triton Student System (TSS) (October 2025)
• Triton Student System (TSS): Impacts on Applications You Use (October 2025)
• TSS Process Group 4: Design Done, Build Begins (June 2025)
• Revised TSS Timeline: SU26 Release (May 2025)
• TSS Process Group 3: The Joy of Progress (March 2025)
• TSS Process Group 2: The Journey Continues (February 2025)
• Navigating New Systems: The Role of Training (January 2025)
• That's a Wrap on Process Group 1 (October 2024)
• They Advise, We Revise: TSS Project Advisory Committee Kickoff (August 2024)
• Sharing the Wealth: Learning about SLcM from the University of Kentucky (August 2024)
• New SIS, New Name: Introducing the Triton Student System (June 2024)
• Initial Release of the New SIS Explained (June 2024)
• Let's Get Down to Business: Process Design Workshops (May 2024)
• SLcM Training: Setting the Stage (April 2024)
• Project to Replace ISIS Moves Forward (March 2024)
• System to Replace ISIS Selected (December 2023)
• Backfill: Prioritizing Staff Expertise for the SIS Project (August 2023)
• Time to Upgrade: Why We Must Replace ISIS Now (June 2023)
• Preparing for Change Freezes (May 2023)
• Moving the SIS Project Forward After a Second No Award (September 2022)
• The Future State of SIS Reporting (March 2022)
• RFP for SIS Vendor Partnership Released (November 2021)
• Next Steps Toward a New SIS (February 2021)
• Information and Understanding Exchange (January 2021)
• SIS Moves Forward with Executive Support (July 2020)

If you'd like to learn more about the continuity planning & report remediation efforts, please see these articles:

• Retirement of Student QueryLink Reports & Updates (January 2026)
• Student QueryLink Reports Remediation Updates (November 2025)
• Second Round of Student Reports Now Available (August 2025)
• The First New Student Reports Are Here! (July 2025)
• Get Ready: New and Improved Student Reports Coming to the Business Analytics Hub (June 2025)
• A New Chapter for Report Remediation (March 2025)
• Planning for Continuity Planning (May 2024)
• Preparing Stakeholders for Reporting Changes (November 2023)
• SIS Project Preparation Work: Report Remediation (June 2022)
• Minimizing Disruptions and Supporting Report Access (December 2021)
• Reporting in Focus (July 2021)
• Focus on Reporting and “Pre-habilitation” Activities (May 2021)

OVERVIEW

What functions and processes will be available when the new student information goes live?

The initial release of TSS will prioritize the university’s critical functions and processes when we go live. Additional features will be introduced in follow-up releases as time and resources allow. For a system of this size and scope, a phased rollout is standard practice, with additional releases continuing to add more functionality.

Will we retain all the same functionality when we move to the new system?

The short answer is no. Because our current functionality is the result of many years of creating workarounds to support poor or missing functionality in ISIS, we are untangling functionality from processes. Some functionality may be approached differently in the future state. We will develop future state processes in conversations with stakeholders using the knowledge of our subject matter experts and aligned with our guiding principles. This future state process design will begin with the Process Design Workshops and continue in an iterative fashion throughout the build phase of the project.

What is “MVP”?

You may hear this initial release sometimes referred to by the software development industry-standard term of “Minimum Viable Product” or “MVP”.

CRITICAL FUNCTIONS

What are critical functions?

Critical functions and processes are those which we must be able to execute to maintain the ongoing operations of the university, such as those required to deliver transcripts and diplomas to students. The initial release of the new TSS must be stabilized before any future releases can be made.

What are the features included in the initial release and why were they prioritized? 

The project’s design team has already put a great deal of intentional thought into what will be in the initial release and has consulted with many functional subject matter experts from across the university, including Registrar, Division of Extended Studies (DES), Student Financial Solutions, Division of Graduate Education and Postdoctoral Affairs (GEPA), Financial Support Unit, Financial Aid and Scholarships, Business & Financial Services and others. 

What is included in the list of critical functions?

While these resources do not provide a comprehensive list, you can learn more about some of the critical processes and functions from the Process Design Workshops and Process Design Documents. A list of what functions have been identified as critical and therefore prioritized for the initial release will be made available for the university community to review.

How is it decided which functions and processes will be prioritized for the initial release?

In addition to the design team and the functional subject matter experts (SMEs) already consulted, the project’s advisory committee and governance committee will also have opportunities to review and provide feedback on the list of critical functions prioritized for the initial release. 

Who decides what is included in the initial release?

Final approval of the list, following review and feedback, lies with the Business Process Owner (Cindy Lyons), Service Owner (Jonathan Whitman), and Governance Chair (Christine Alvarado).

How will we be sure that all critical functions and processes are included in the initial release?

Even with the large amount of time and input that has already gone into determining what will be prioritized for the initial release, we are certain that we have not captured everything yet.

How do we know we've captured all the critical priorities for the initial release?

As we continue through the design and build phases of the project, we will continue to refine what will be included in the initial release and consult with stakeholders from across the university to review and provide input on what will be included.

PROVIDING FEEDBACK 

Who can provide input into the priority list for the initial release?

We rely on our university community with their own specialized knowledge to help us identify critical functionality that we may not have identified yet, so it can be prioritized for the initial release. Both the advisory and governance committees for the project will be engaged for their review and feedback.

How can someone outside of the project teams and committees review and provide input for the priority list?

Additionally, for those not directly involved in the project teams or committees, there will be opportunities for review and feedback throughout the project, including listening sessions, which will be announced via existing project communications channels.

MOVING TO THE NEW SYSTEM

What if something critical is missed and not included in the initial release? Once realized, how will this be handled by the team?

The project teams execute ongoing risk assessment and management and gather input from a wide-range of subject matter experts throughout the project to attempt to mitigate the risk of missing critical functionality for the initial release. However, given its immense complexity, even with continued review, feedback and refinement throughout the project, we may still miss something critical for the initial release. Identifying and closing these functionality gaps is a key aspect of the stabilization phase of the project, and the full attention and effort of both our business and technical implementation team members will be on closing any gaps during stabilization.

Will we retain all the same functionality when we move to the new system?

The short answer is no. Because our current functionality is the result of many years of creating workarounds to support poor or missing functionality in ISIS, we are untangling functionality from processes. Some functionality may be approached differently in the future state. We will develop future state processes in conversations with stakeholders using the knowledge of our subject matter experts and aligned with our guiding principles. This future state process design will begin with the Process Design Workshops and continue in an iterative fashion throughout the build phase of the project.

How can we be sure the team truly understands what functionally may change and how that might impact my work?

We spent over a year inventorying and analyzing how current work is conducted with input from subject matter experts across the university. As we implement new systems, especially the new TSS, which will replace ISIS, we will rely on this baseline to help us understand and communicate changes. We will also continue to involve subject matter experts throughout the project and especially in advising our decisions.

STABILIZATION

What is stabilization?

Identifying and closing functionality gaps and addressing any bugs identified after go-live are key aspects of the stabilization phase of the project. The full attention and effort of both our business and technical implementation team members will be addressing gaps and bugs during stabilization.

What is the team focused on during the stabilization phase of the project?

The initial release of the new TSS will not be considered stabilized until we have closed all identified critical functionality gaps. Once the initial release has been stabilized, then the team will focus on the future releases.

Will the new TSS and ISIS run in parallel?

We will not turn off ISIS until we are certain that the new TSS is functioning as expected and we can maintain the ongoing operations of the university.

Will we be creating duplicate entries in ISIS and TSS post go-live of TSS?

While we plan to have ISIS and TSS running in parallel for some period of time, we do not expect that we will be creating transactions in both systems post-go-live of the new TSS. Should there be an urgent need to return to using ISIS after going live with TSS, we will have a clearly defined rollback plan to follow. Due to the disruption and manual work that would be required to return to using ISIS, the decision to rollback would only be made if absolutely necessary.

When will ISIS be shut off?

The decision to shut down ISIS entirely will follow a robust and structured process that will include key functional and technical stakeholders. Exactly when ISIS will be shut down and the framework that will be followed in doing so will be communicated to the wider university community via existing project communications channels as those details become available.

NON-CRITICAL FUNCTIONS

What features are excluded from the initial release?

Non-critical functions and processes will be deprioritized for the initial release and only included in the initial release if time and resources allow.

What is the plan for future inclusion of functions excluded from the initial release?

Following the stabilization of the initial release, there will be subsequent releases, which will include the functions not included in the initial release.

Will there be workarounds for functionality not included in the initial release?

The Design Team will provide thought partnership to units on addressing limitations and developing workarounds for those functions and processes not included in the initial release. The TSS Project advisory committee will also assist in addressing limitations and developing temporary workarounds.

Who will participate in the creation of workarounds?

It is not known at this time what workarounds may be needed for the initial release. As we know more, we will share that information with the university community via existing project communications channels.

• TSS Project Overview Presentation
• TSS Project One-Pager (General)
• TSS Project One-Pager (People Leaders)
• Report Remediation One-Pager (Resources for Self-Remediation)

• Review the TSS Project FAQs on Collab. If you have difficulty accessing this link, please contact esr-student@ucsd.edu.
• Learn more about Report Development and your role in the process.

The procurement process for the SIS Project is ongoing. Below are key milestones in the procurement process.

Request for Proposal and Conference Room Pilots

A Request for Proposal (RFP) was issued in Spring 2020, inviting vendors to bid to provide UC San Diego with their student information system solution. It contained questions designed to capture what we need to know to assess the capability of their software, contract terms and conditions, around 200 detailed questions, and Conference Room Pilot (CRP) scripts with detailed business scenarios.

Understanding and insight from business process landscape and mapping sessions were used to create these materials. For the SIS Project and other ESR projects, the ability of each vendor to execute crucial processes and meet the needs of our students is critical, as is total cost.

Vendors sent us their RFP responses, which were scored by the SIS Project and procurement teams. Next were the virtual CRP sessions, held November 2020 through January 2021, when finalists spent two weeks each showing exactly how their software would meet our needs. Subject matter experts (SMEs) from across the university participated and scored with the project team and technical experts on how well the software handled our real-life scenarios.

• Learn more about the Conference Room Pilot (CRP) sessions.
• Read a recap of the CRP sessions.

First Request for Proposal Closed without Award

After a rigorous and inclusive one-year process of proposal, review, consideration, and discussion, the initial RFP for a new student information system was closed without award.

• Read the full announcement regarding the closing of the RFP without an award.

RFP for Vendor Partner Released

On October 18, 2021, a second RFP was released, seeking a vendor to partner with UC San Diego to create a student information system able to meet the needs of the university at the time.

• Learn more about the release of the RFP for a vendor partner.

Second RFP Closed without Award

After more than six months of proposal, review, consideration and discussion, the RFP for a student information system development partnership has been closed without award.

• Read the announcement regarding the closing of the second RFP without award.
• See additional information about the closing of the second RFP.

Contract Awarded

After four years, three RFPs and much consideration and discussion, the contract for a new student information system has been awarded to invenioLSI, SAP’s North American distributor for their Student Lifecycle Management (SLcM) product.

• Read the announcement regarding the awarding of the contract for a new SIS.
• Review additional information about the system selection.