Specifications include, but are not limited to: It is important to note that most components (with the exception of Azure AD Connect) would be replaced with the proposed solution. Details of each component are provided below: 1. SalesForce: SalesForce is currently being used to track prospective student information. This is currently being fed directly into Banner and being consumed by Banner. 2. Banner SIS: Banner Student provides a nightly file that is processed by components 5,6 and 7 which then flows downstream to USD-LDAP and USD.LOCAL Active Directory Domain. When a new student record is detected a new USD credential is provisioned for the new student record. It is important to note that this system is run by the Regents Information Systems at the state level and is out of control of the University. Banner SIS is the system of record (authoritative source) for all USD students. This is a commercially provided application. 3. Banner HR: Banner HR is the Human Capital Management system. Faculty and Staff records are tracked in the system. A nightly feed file is generated and processed by components 5,6 and 7. There are also some other constituent types that are also entered in Banner HR such as vendors, affiliates, and other constituent types. This system is also run by the Regents Information Systems at the state level and is out of the control of the University. Banner HR is the system of record (authoritative source) for all Faculty and Staff. This is a commercially provided application. 4. Med Database: This component is the system of record for all Medical School Clinical Faculty, Residents, Affiliates and Fellows that need a USD credential. There is a database view that is queried by components 5,6 and 7 which then flows downstream to USDLDAP and USD.LOCAL Active Directory Domain. Affiliations are also provided with the records. This includes which Medical School campus the user is affiliated with. This is considered the system of record for all Medical School Faculty and Affiliates requiring a USD credential. The Med Database is comprised of a Microsoft SQL server. 5. Account Request Application: This component is a Microsoft SQL Server Database which is the backend for component 10 (Accounts Management Application, a Cold Fusion Web Form). This is considered the system of record for accounts that do not originate from any of the other authoritative sources of information. This can include service accounts, test accounts, and others; however, this application is the primary method for creating accounts for faculty/staff.
