The Education group meeting was hosted by Claire Lorrain at University of Winchester on 6th September 2012 and as usual everyone gained a lot of value from sharing their experiences. It was good to see some new faces. Claire Lorrain gave a presentation of the Winchester process library, and outlined the involvement of students as a means to achieving a central buy-in, which had been expressed as a problem for many customers. The University of Bedfordshire has kindly offered to host the next meeting which has now been scheduled for 20th February at their Luton site.
The main User Group meeting was hosted by Fugro GEOS at their Wallingford offices on 18th October 2012. The minutes of this meeting will be available for all customers to read via the secure User Group page shortly. However in summary:
Q Tucker from Fugro GEOS provided an overview of their business and the various challenges they face within the Quality, Health and Safety areas.
It was noted that the next Focus Day (5th December) will be covering discussions regarding using Triaster on mobile devices and integration with SharePoint, which have been hot topics within the User Group meetings of late. Anyone interested in these areas of functionality development should attend the Focus Day if possible.
The next meeting is being hosted by Openfield at their Grantham offices on 21st March 2013. This will include the AGM at which the constitution will be reviewed and User Group officers elected. The constitution requires that there must be at least ten members present to constitute a quorum and agree changes. Constitution changes and User Group officers must be proposed in advance, so please send any suggestions to firstname.lastname@example.org. Note that some suggested changes have already been put forward and are being considered.
If you would like to attend any of the events mentioned above please register at www.triaster.co.uk/events. Space is limited, so do book on as soon as possible.
Feature requests should be e-mailed with a description of required functionality and perceived benefit to: email@example.com