Meet the IRP Student Team – Security, Access, Data & Reporting 

The Integrated Renewal Program – Student (IRP Student) refers to the renewal of the UBC Student Information System (SIS) that the University is undertaking. The renewed system will support UBC students in achieving their academic goals and create a better experience for all users through a new set of tools and new ways of working.  

IRP Student has eight core teams – Student Solution, Ecosystem Delivery, Transformation & Change Management, Security, Access, Data and Reporting, Technical Delivery, Solution Architecture, Quality Assurance, and Program Management Office. This series aims to explain each team, their objectives, and their role within the IRP Student program in terms you, our UBC community, will understand. 

The Security, Access, Data, and Reporting (SADR) team defines the processes to ensure UBC delivers a high-quality, responsive, and secure student information system to support the University’s mission to deliver a quality learning experience. 

The ultimate goal of each enterprise project implementation is to provide accurate data in a secure environment to provide business leaders with timely information, so they can make accurate decisions. IRP Student is no different in this case, therefore our mission is to ensure UBC's new Student Information Ecosystem not only follows our organization standards, but also is grounded in trusted data that is delivered on a modern and unified analytics platform. 

- Sharon Rashtian, Associate Director, SADR

The SADR team works closely with other IRP Student teams to provide a consistent framework for delivering the following: 

Security & Access: 

The Security and Access component within SADR focuses on provisioning access to Workday Student. They also ensure access and security authentication for all users. This team conducts regular security and infrastructure reviews to ensure ecosystem security. They work closely with Cybersecurity and PrISM (Privacy and Information Security Management) to ensure security, data privacy, and compliance.  

Data Conversion: 

For any large-scale system implementation, such as IRP Student, timely and accurate conversion of data is critical to the project’s success. As part of the IRP Student program, the Data Conversion team within SADR is responsible for: 

• Converting and migrating legacy SIS data into future solutions, which include Workday Student and point solutions. Point solutions are newly created systems that are required when Workday Student or an existing application does not meet UBC’s needs. 
• Monitoring, validating, and fixing student data quality issues, to ensure Workday Student and the point solutions are housing trusted University data. 
• Applying Data Governance principles and processes to the data delivery process. 

The Data Conversion team works closely with functional teams, vendors, quality assurance, solution architecture, Enterprise Data Governance, and others to validate data, identify risks and issues related to legacy data elements, and address them through the data conversion process. 

Reporting: 

The Reporting team is responsible for the end-to-end delivery of reports and other data-centric outputs within the IRP Student program. These include: 

• Operational reports: used to support functional business processes 
• Data Validation reports: used to ensure initial student data was consistently migrated 
• Regulatory reports: mandatory reports to satisfy internal or external regulatory needs 
• Strategic and managerial reports: used to support strategic and management needs 
• Datasets to be used by other existing UBC reporting solutions 

For more information about IRP Student teams, read the other entries in this content series on the IRP Student website. 

*Reflecting on our experience so far in working with Workday and seeing how our design is shaping up, we realize that we have to embrace change and be confident in our ability to adapt. Workday Student, along with IRP Student’s functional requirements, are evolving quickly and this could mean that we may have to adapt our approach throughout the project timeline.