Specifications include, but are not limited to: To support our envisioned future state, the system must support multiple simultaneous relationships or lifecycles for a single person. Examples of the relationships include: employee, parent of student, volunteer, and alum student and employee employee and alum current student and applicant for additional degrees volunteer and parent of student The system must be able to provision multiple accounts for a single person in other words a solution that supports one identity to multiple roles and accounts without customization. The system OSU is looking to implement should be cloud-based or Software as a Service. It should enable OSU to sever the direct tie between the creation of an identity record and our ERP/SIS.
