University of Bradford Online Learning Platform Integration

The procurement contact named on the official notice.

Objectives of the contract: • Define a clear and robust integration design that enables effective data exchange between the partner CRM solution and the University of Bradford's student systems. • Leverage the existing Azure Integration Architecture to ensure consistency with established patterns, standards, and governance. • Identify and design required inbound and outbound integration endpoints to support key business processes, including applications, enrolments, modules, and payments. • Establish appropriate orchestration, data transformation, and error-handling mechanisms using Azure integration services. • Address key integration considerations such as identity linkage, data mapping, and reporting requirements (including HESA-related needs). • Work collaboratively with University teams and partners to reduce delivery risk and accommodate evolving requirements. • Align to a scalable and extensible integration approach that supports future partners and additional data flows. • Scope includes but is not limited to: • Review of available partner integration artefacts and high-level requirements, including reference architectures and diagrams. • Definition of a target integration design leveraging the University of Bradford's Azure Integration Architecture. • Design and build of inbound and outbound integration endpoints to support agreed data flows between the partner CRM and University systems. • Configuration and development of required SITS interfaces, including use of StuTalk APIs and event-based data exchanges where applicable. • Implementation of data events to enable timely and reliable data synchronisation between systems. • Build and configuration of Azure integration components, including API Management, Logic Apps, Azure Functions, and Azure Data Factory pipelines. • Development of data mapping and transformation logic for key entities, including applications, users/contacts, course enrolments, modules, and payments. • Alignment of identifier management to link external partner records with internal student records. • Identification of non-functional requirements, including security, monitoring, logging, error handling, and retry mechanisms. • Collaboration with University teams and partners throughout design, build, and validation activities. • Support for integration testing and handover into operational support