1. TOPIC FOR THE DISCUSSION SECTION AUTHOR ONE AUTHOR TWO AUTHOR THREE FIFE Workshop Template Service Name

2. Service Name describe what functionality the service is supposed to provide e.g. SAM delivers files while keeping track of projects, datasets, snapshots, etc. here are the requirements that we're answering with this solution requirement 1 requirement 2 requirement 3 6/4/13 SCD FIFE Workshop 2

3. Service Name how this service is going to make your life easier this is a sales pitch to the experiments about what makes this great e.g. with each use of the SAMWeb client you get a free piece of cheery pie. 6/4/13 SCD FIFE Workshop 3

4. Service Name high level description of what the service actually performs, diagrams if possible e.g. IFDH uses several different protocols to transfer data across the network to include gridftp, BestMan, cpn, etc BlueArc SAM/dcache storage element cpn gridftp ifdh FermiGrid OSG site job section 6/4/13 SCD FIFE Workshop 4

5. Service Name configuration options for the service how can an experiment have the service configured, what buy in does it require e.g. to utilize gridftp within ifdh an experiment will need to have a gridftp server configured spun up for it 6/4/13 SCD FIFE Workshop 5

6. Service Name current requests from experiments current issues (only if applicable) 6/4/13 SCD FIFE Workshop 6

7. Service Name plans for the future e.g. monitoring will soon upgrade the server to expand capabilities and include gratia additional functionality e.g. jobsub is going to introduce tarball submission to FermiGri timeline 6/4/13 SCD FIFE Workshop 7

8. Service Name Documentation project/service site (redmine, wiki, etc.) users guide issue tracking/feedback instructions 6/4/13 SCD FIFE Workshop 8