HERUG Development requests Proposal Bob van der Werf Chair HERUG

Communications One person needs to be identified per institution to be the “HERUG representative” A listserver of all HERUG representatives is set-up for official communications A HERUG newsgroup is set-up for discussion purposes Web voting procedure

Overall process Log request items SAP input / feedback Additions to items Board approval Annual HERUG Annual voting

Logging requests Institutions add their items onto a form Title Description Business motivation Contact person with e-mail Name of HERUG representative

SAP input / feedback Group similar items together Remove redundancy Add comments per item Feasible, not feasible, under development If feasible, estimate of delivery time if item received most votes

Additions to items Pilot sites Institutions who are prepared to be pilot sites add their names to the request Spec sites Individuals who will assist in adding specifications later add their names

Board approval Items not specific to HER area are ruled out Items for which no pilot site exists to be ruled out Items for which only one institution will assist with drawing specifications to be ruled out

Annual HERUG meeting One morning is devoted early on in the agenda to discussing development requests SAP explains their comments The board explains their approval free discussion

Annual Voting 50 votes per institution entered by the HERUG representative The board approves the voting The results are published on the web The chair sends results to SAP / logs on the OSS as user group

Overall process future years Log request items SAP input / feedback Additions to items Board approval Annual HERUG Annual voting 6 weeks prior 4 weeks prior 2 weeks prior at HERUG 1 month post

Overall process this year Log request items SAP input / feedback Additions to items Board approval Annual voting 4 weeks after 6 weeks after 7 weeks after 8 weeks after 9 weeks after