Further Information
Agenda and minutes
- Agenda and minutes from 2009 (only accessible from within the UWA network)
Mailing list
- To be added to the Stakeholder Reference Group mailing list, please email us requesting inclusion.
The eRM Stakeholder Reference Group has four clear aims.
These are to:- allow stakeholders to have ownership of the InfoEd system
- consider recommendations from the eRM Functional Working Parties regarding the impact of the eRM on business processes, and approve solutions or provide recommended solutions for review by the Project Board and/or the Project Steering Committee as appropriate
- provide a forum for process owners to discuss changes to business processes, make decisions on changes to these processes and/or recommend policy changes to the eRM Project Board and Project Steering Committee as appropriate
- provide links to UWA staff outside the Project Team by sharing the information discussed at the eRM SRG with the staff who are functionally responsible.
Meetings
Meetings are held from 4.00 to 5.00 pm.
Definite meetings
- Monday 14 December 2009
Optional meetings
- Monday 23 November 2009
Terms of reference
The eRM Stakeholder Reference Groups' terms of reference are as follows:
-
Liaise with the relevant UWA members of the project team to obtain independent feedback on progress and to obtain an understanding of issues likely to come before the project board for decision.
- Consider issues arising from working parties and recommend business process changes, strategies for configuration and/or policies as required.
- Adjudicate on questions of functionality and configuration where conflicts arise and instructs their representative (the Senior User/s) of the views of the business process owners to be presented to the project board and/or project steering committee as appropriate.
- Advise the project board whether the University’s requirements have been fully met within the constraints of the business case and the contract, and in relation to the fitness of the product for the purpose.
- Obtain the views and opinions of staff functionally responsible for business processes, and present these views during discussions.
- Approve (sign-off), via the nominated members of the group responsible for that module of functionality, the functionality of the product.
University information
CRICOS Code: 00126G
