Draft Program

 WEDNESDAY

             ITANA                                

N/A

THURSDAY

Advanced CAMP

7:30-8:30

Breakfast

8:30-9:00

Introductions and Goals of the Workshop

Provide set of issues to report on
per Chas examples below

9:00-10:00

Bamboo/SEASR: New Examples

Where do we add Cloud Computing discussion:- 20 minutes presentation and remaining time for discussion of what are people doing with it. Check out the presentation that Leif sent.
SEASR is coming per Ken - don't know who yet.

10:00-10:15

Break

10:15-11:30

Kuali/Fedora Projects and Users
Compare and contrast three projects and user stories

11:30-1:00

Lunch

1:00-2:15

Cloud Computing and OGSA

2:15-2:30

Break

2:30-3:45

Panel: Are there lessons learned from ESB that can be applied to loosely coupled environments? To project centric environments? 

How can campus architects learn about this? How do we get project and campus folks to talk?
How can we diagnose this complexity?

Workflow and services - Dennis Gagnon - Ken to contact
    ISI - Ewa Deelman 

3:45-4:00

Break

4:00-5:00

Discussion Groups: Services, Data Models, Governance
Groups will consider each of these in turn given the examples so far and develop a set of requirements for each.

Orchestration/Information discovery: How do you go about finding information of interest and cross linking your results? Introduce Tool from caBIG??? But where does infrastructure stop and governance begin? Or is it a design pattern instead of an infrastructure component?

5:30-7:00

Reception

(Available until 6pm)

 FRIDAY

N/A

7:30-8:30

Breakfast

N/A

8:30-9:30

Privacy and Policy Panel: Expose privacy and policy issues that loosely coupled environments create.

Blakely, EGEE, Lori Crantor (CMU),

N/A

9:30-10:30

Findings from

N/A

10:30-11:00

Break

N/A

11:00-Noon

Wrap-up and Findings

N/A

Report back with findings.

- vision of project
- motivation (business and technical)
- brief narrative
- initial timeline
- how they began to define requirements
        - business/operational
        - technical
- defining governance model
- describe their technology
        - architecture
        - why they made specific decisions
- status thus far
        - progress to date (real timeline)
        - problems
        - risks
                - core competencies of staff?
                        - development/operational
                - continued funding?
                - technology?
                        - development
                        - operations
                - governance?
                - etc?