OPUS-College Student Information System Functional / Technical Functions & Ownership

New functions for OPUS-College On the central level (Academic Office / Registrar) Central Functional Manager of OPUS-College ; responsible for:  The user training for OPUS-College.  The (organization and supervision of) the initial testing of the system during the implementation period and the testing in the future of newly added functionality (modules).  The coordination of the de-central functional administrators. More specifically this task involves the organization of regular (i.e. Monthly) meetings between the central and de-central functionaries to discuss possible problems or requirements regarding OPUS- College.  ……..

On the central level (Academic Office / Registrar) - continued …….  The communication with the technical people concerning (possible problems in) the technical functioning of the system as well as the commissioning of newly requested functionality to be developed.  Guarding the agreed upon development process for new functionality (e.g. take care that the new functionality is delivered in time by the technical developers).  Reporting and contact person for the central OPUS- College management. New functions for OPUS-College

On the de-central level (Schools) De-central Functional Administrators of OPUS-College ; responsible for:  The on time filling of the OPUS-College system with data from the school in question.  The collecting of possible requests for new functionality within the School.  Representing the School in the OPUS-coordination and information meetings, organized by the Central Functional Manager.  Acting as OPUS-College contact person / coordinator for the Heads of the Departments.

New functions for OPUS-College On the de-central level (schools) - continued Contactperson for the de-central functional administrators (1 dean / asst. dean) responsible for:  Functioning as spokesperson for the De-central Functional Administrators  Functioning as contact person for the Technical Project Manager of OPUS.  Functioning as contact person for the Central Functional Manager of OPUS.

New functions for OPUS-College Technical functions One Server administrator: responsible for the optimal technical functioning of the machine and platform the system runs on. One System or application administrator, responsible for the installation and updates of the OPUS-College application, including the database management. Two System Developers, responsible for the development of new modules for OPUS-College. One Technical Project Manager or supervisor, responsible that all above mentioned tasks are executed correctly and in time.

New functions for OPUS-College Roles within OPUS system (authorization) Roles & Privileges indicate an organizational choice. This means that they can differ between universities. In this session we will try to establish consensus on roles and privileges.

New functions for OPUS-College Roles within OPUS system (authorization) Existing Roles: academic affairs office dean / asst. dean head of department teachers of subjects student

New functions for OPUS-College Roles within OPUS system (authorization) Identified new roles: Functional Admin = 1 person at the university Financial officer = bursar / asst. bursars / controllers Registrar / asst. registrar Librarian Internal Audit Dean of Students PR / Communication Alumni-student Issues: Are there more roles to be identified …? Do we need a role for the vc / dvc ?

New functions for OPUS-College Privileges within OPUS system (authorization) Most common privileges: View / Print Add / Edit Delete Some extra privileges: View History View Withheld... Issue: the privileges are now defined on a very high level, but they can be fine-tuned on tab / panel level and even on field- level. E.g. medical history of a student ! (Under privilege: View / Add / Edit students - personal data – details)