What's Changing


Existing applications that send or receive student data will need to be changed to integrate with the new SIS.  The SIS Integration team will help application owners and developers understand and prepare for the way data formats, integration access, and security enforcement will change. Here are the primary issues you need to know about.

  • Standardized Data 
    The SIS Replacement project provides campus with an important opportunity to improve student, faculty, and staff experience by redesigning the ways data is shared.  An important step towards a more modern integrations environment is to decouple the data used within any application from that exchanged across the campus. This can be done by introducing a standard data format for each information entity, referred to as an “Enterprise Data Object” or “EDO.” Integrations with core SIS systems will rely on these EDOs as intermediary data formats.
  • Centralized Access 
    Applications that interact with SIS will be required to use the the Integration Hub, a collection of services provided by IST-API’s Enterprise Integration Services, as the intermediary for all integrations with core SIS systems.  The Integration Hub provides management, transformation, and security layers to each integration. The centralization of this functionality reduces the duplicative workload of every application and integration developer and makes every integration more robust.
  • Secured Integration
    Both coarse and fine-grained authorization of systems to access integrated data will be maintained and enforced within the Integration Hub. Authentication of the calling service will be handled by the API Management layer. Authorization will permit access to the content of the EDOs, with row and column filtering based on roles assigned to integrating systems, or even their attributes (such as college or major).