1.       

P

Category

Description

Actions and Status

1

1

Enterprise Participation & Leadership

Ø        Recruit Enterprise participants, leaders and ADs

Ø        NOMCOM coordination

Ø        Gwen to send Enterprise list (https://forge.gridforum.org/sf/go/doc13914?nav=1) to NOMCOM

Ø        Gwen to get status on regular basis.

Ø        Gwen to close with John on merging lists

Ø        Gwen to post distributed document to Grid Forge.

Ø        Enterprise  will review and extract names to add to Enterprise  master list

1.        

1

GGF18 Follow-up

Ø        Letter to participants and disposition of req

Ø        Bob and Ravi to draft letter of “here is what we heard from you in terms of your top 3 req” https://forge.gridforum.org/sf/docman/do/listDocuments/projects.enterprise/docman.root.enterprise_requirements_rollup

Ø        Mark to sign letter in order to use it as a recruiting tool.

Ø        Get TSC to disposition the req and buy-in on process.  Gwen to get disposition from TSC when appropriate.

Ø        Output of Results

o        Capture of raw data, into a format that can be collated, analyzed, and made ready to be rolled-up and presented

o        Bob to receive EDA/Pharma panel feedback on notes.  Confirmed notes to be posted

Ø        Engaging participants to derive continued participation (OGF19 and forward)

2.        

1

OGF19

Ø        Enterprise track

Ø        Gwen to get enterprise program (https://forge.gridforum.org/sf/docman/do/editDocument/projects.enterprise/docman.root.enterprise_program_management/doc13964) integrated with master program.

Ø        Gwen to get session owners to submit formalt session request.

Ø        Need to status all Enterprise sessions. https://forge.gridforum.org/sf/go/doc14021?nav=1

Ø        Bob and Ravi to establish lightweight requirements format. When captured we produce a standard form.  Communication requesting status sent to Bob and Ravi.

Ø        Robert to elaborate on Enterprise Grid Best Practices proposal (submitted by Nick Werstiuk, Platform)

Gwen to get and distribute the “All Hands Standards Meeting” agenda and participant list to determine workarounds resulting from conflicts.

3.        

1

OGF Virtualization Working Group

Ø        With Alexander and Francisco

Ø        Craig to ensure this is on track.

Ø        Confirm that charter has been submitted to GFSG

4.        

1

OGF20

Ø        Dave Berry Lead for Enterprise Track (Grid Computing Now)

Ø        Bob and Craig to insert themselves into the planning.  Ensure that requirements sessions, vendor adoption and BKM sessions are in program.

Ø        Communication requesting status sent to Dave Berry

5.        

1

Collaboration Tools

Ø        Google calendar and MS LiveMeetingLive Meeting

Ø        Gwen to investigate and to provide requirements to Steve.

Ø        Requirements provided, currently investigating MS Live Meeting Competitors, WebEx and Confcall.com.

Ø        Next steps include update to MSC and trial by MSC to determine cost/benefit justification.

1.       1

*Vendor Adoption

Ø 

Ø 

6.        

1

Amsterdam Enterprise F2F Agenda

Ø         

Ø        Determine agenda/results.

7.        

1

*Requirements Process

Ø         

Ø        Bob to close with Ravi on process.  Include Craig from vendor perspective.

Ø        Close with TSC on process.

Ø        How do we drive into standards process?

8.        

1

Vendor Adoption

Ø         

Ø        Craig to insert himself into discussion started at SC06.

Ø        Craig to generate letter to vendors communicating that OGF Spec XYZ meets existing user requirements.  Craig to close with John to use this as a marketing promotion tool.

Ø        Craig to identify and recruit key vendors to OGF19 + events

9.        

2

OGC OGF Liaison

Ø        Craig: Promote OGC OGF Liaison

Ø        Gwen to Sheppard thru Joel to provide help contacting and Grimshaw.

10.    

2

Participation in Non-OGF Events

Ø        Participation in non-OGF events
Determine what the events are and define OGF level of participation

Ø        Bob Cohen to provide detail to Pharma events

11.    

3

*Regional

Ø        Determine what this means for Enterprise

Ø         

12.    

3

*Interoperability

Ø        Close with Andrew to determine what this means for Enterprise
o May tie into Vendor Adoption Project

Ø        Gwen to close with Andrew on his intention for the Interoperability project and how this may relate to MSC project on Vendor Adoption.  Waiting for response from Joel on communication with Andrew.

13.    

*

TSC ARs

Ø        AR for TSC: https://forge.gridforum.org/sf/go/artf5590?nav=1
Analysis of the common themes and gaps from the OGF 18 rollup session

Ø        Dave needs input on criteria for choosing use cases. 

14.    

*

*Success Metrics and Proof Points

Ø        List to Mark of success metrics by 10/6

Ø        Fogel to initiate

15.    

*

*Event Strategy

Ø        o Enterprise objectives

Ø        Robert to provide new input and Gwen to make certain that the ESC/OGF19PC gets the input included in documentation

16.    

*

EGR-RG Expanded Charter

Ø        Embrace all groups: Life Sci group, EGA, EGR…
o Combine EGR-RG with EGA, etc.
o Need to do review with Geoffrey on which groups go where

Ø        Gwen to close with Ravi on updating charter, per Robert document.  Expanded role needs to include diagram and output is a roadmap of what is being worked on and a gap analysis.

17.    

*

*Best-Known-Method Workshops

Ø        Develop day-long workshop plan for OGF19, OGF20, etc. to hold a series of day-long workshops on Grid best-known methods in areas such as: Web 2.0/Grid, Data, Security, Applications, etc. Content and conclusions from each day-long workshop would then be “packaged” and made available to the community via the OGF website
o Review plans with GFSG at Amsterdam f2f

Ø        o R. Fogel, G. Fox, G. Nichols-White by 11/06 @SC06 workshop
Need all functions in OGF
Web 2.0 sessions need to include a "how-to focus
Alan, Ravi, Vincent, input and plans on requirements gathering sessions