1. User interfaces and engagement

2. What classes of users we are aiming at? Existing high-end computing users –Who we think are using the "wrong" technology Novice users (only used a desktop so far) Need to think about both HPC and HTC users and spectrum in between –Cycle-stealing community is a low-cost way of doing (especially) HTC Condor users are large user base for Campus Grids No easy split by subject area "apps on tap", "data on tap" or "CPU on tap"? –Some UIs will only handle some of these users

3. Existing HEC users Can't come up with a UI that restricts their existing use If they are using the wrong technology let's help them –Central job submission entry point –Automation with intelligent resource brokering

4. User engagement No single way to do this Approach from requirements-gathering point of view is very useful –bottom-up Find a quick win in an appropriate community –E.g. Portlet and Web Service for BLAST search Also top-down –Get Heads of School etc interested – depends on individuals Local SIG Searchable mailing lists often successful –Wikis, forums etc often less successful Take advantage of existing dissemination mechanisms Multiple touch-points Need experts (but not necessarily many) to hand-hold –And follow-up

5. User interfaces Common to require customization of interfaces for specific groups Building generic interface is very hard –Especially for a heterogeneous Grid –But can we do so as a community for simple requirements? Job monitoring in a portal could be very useful –Everyone wants this! API interface needed for workflows etc Whatever it is, it needs to be documented!