Grid of Grids Information Management Kick off Meeting

1. Grid of Grids Information ManagementKick off Meeting AnabasJune 30 2006

2. ACKNOWLEDGMENTS • We are grateful to: • Bill McQuay, • Raymund Garcia • The Air Force Research Laboratory - AFRL IFSD • Indiana University CGL (Subcontractor Partner) • Ball Aerospace (Subcontractor Partner)

3. General Goal • Build Net Centric Core Enterprise Services in fashion compatible with GGF/OGF and Industry • Add key additional services including those for sensors and GIS • Support Systems of Systems by federating Grids of Grids supporting a heterogeneous software production model allowing DoD greater sustainability and choice of vendors • Build tool to allow easy construction of Grids of Grids

4. Gerstner and Commercialization of GoG Architecture • Reference [1]: Who Says Elephants Can't Dance, Louis Gerstner, Jr., 2002 is practically a primer on IBM's vision and strategy to re-gain its influence to setting IT industry agenda. • "The industry's disaggregation into thousands of niche players would make IT integration services a huge growth segment of the industry."  [1] • Grid of Grids builds the information management infrastructure for efficient integration of components. • "Over the next decade, customers would increasingly value companies that could provide solutions - solutions that integrated technology from various suppliers and more importantly, integrated technology into the processes of an enterprise."  and "The two companies that have enjoyed the highest market valuation in the IT industry in over much of the last decade have been component manufacturers -- Intel and Microsoft. There is no doubt that a strategy built around providing fundamental building blocks of the computing infrastructure has proven to be extremely successful in this industry."  [1] • Grid of Grids has huge commercial potential by offering both the integration infrastructure for component manufacturers and providing Network-Centric Enterprise Services as essential building blocks . • "The dazzlingly wired-world would also change the course of computing in profound ways. For one thing, it was virtually certain that world would be built on open industry standards. There would be no other way to fulfill the promise of ubiquitous connections among all the businesses users, devices, and systems that would participate in a truly networked world. If that standards-based world came to pass, it would represent a major shift in the prevailing competitive landscape." [1]  • Grid of Grids information management with its foundation on GGF/OGF open standards is a key to integration.

5. Technical Advisory Board • Build a group of some 6-10 knowledgeable people to guide project • Mainly from Industry including Boeing, Lockheed Martin, Ball Aerospace, Aerospace Corporation, Mitre, DISA, and the core technology companies (IBM, Microsoft) • Use to guide both technology and commercialization strategy • Meet F2F, email and telecons. • Brings significant external expertise to Grid of Grids team, and visibility of Grid of Grids to other world-renowned institutions.

6. SS Database SS SS SS SS SS SS SS Raw Data  Data  Information  Knowledge  Wisdom AnotherGrid Decisions AnotherGrid SS SS SS SS FS FS OS MD MD FS Portal Portal OS OS FS OS SOAP Messages OS FS FS FS AnotherService FS FS MD MD OS MD OS OS FS Other Service FS FS FS FS MD OS OS OS FS FS FS MD MD FS Filter Service OS AnotherGrid FS MetaData FS FS FS MD Sensor Service SS SS SS SS SS SS SS SS SS SS AnotherService

7. The Grid and Web Service Institutional Hierarchy 4: Application or Community of Interest (CoI)Specific Services such as “Map Services”, “Run BLAST” or “Simulate a Missile” XBMLXTCE VOTABLE CML CellML 3: Generally Useful Services and Features (OGSA and other GGF, W3C) Such as “Collaborate”, “Access a Database” or “Submit a Job” OGSA GS-*and some WS-* GGF/W3C/….XGSP (Collab) 2: System Services and Features (WS-* from OASIS/W3C/Industry) Handlers like WS-RM, Security, UDDI Registry WS-* fromOASIS/W3C/Industry 1: Container and Run Time (Hosting) Environment (Apache Axis, .NET etc.) Apache Axis.NET etc. Must set standards to get interoperability

8. The Ten areas covered by the 60 core WS-* Specifications

9. Activities in Global Grid Forum Working Groups

10. Net-Centric Core Enterprise Services

11. Produce the Needed Core Services • We can classify services in many ways and following 2 charts are one way; slightly changed from proposal as NCOW and our work changed a little. • Green is “in hand”; our team leaders • Orange is “in hand” with outside but available solutions • Red has problems – Security does not have industry consensus while current Scheduling work does not address DoD real-time service and network requirements

12. The Core Features/Service Areas I

13. The Core Feature/Service Areas II

14. Additional Services • Sensors have low level support listed as FS3; higher level integration using SensorML and Filters well understood. Some work in phase I • GIS Grid services pioneered by team and already shown in phase I • Mediation (Interoperability) Services needed to link Grids (defined as a collection of ≥ 1 Services) • Need to generalize existing solutions for Sensor Grids and for MQSeries-SOAP Mediation • View NaradaBrokering as a SOAP Intermediary

15. Grid of Grids Building Tool • This will provide a graphical interface to build grids from existing libraries of Services and Grids • Meta-data (provenance) needs to be specified • Grids (services) need to be linked • This will be built by extending an existing workflow engine which is aimed at a more tightly couple version of the builder problem • We will consider HPSearch (CGL), Taverna (Open source from UK OMII), BPEL with user interface (OMII or IU LEAD project) • Semantic Grid provenance “add-ons” • We have experience with all these approaches

16. Applications • Indiana University will apply to Earthquake Science and Emergency Response • Ball Aerospace will apply to Matrix • Anabas will work with Technical Advisory Board to identify commercialization plan and possible prototype applications in first 12 months • Anabas will implement appropriately in last half of project

17. Out of Scope for Phase II • Many areas are still evolving significantly • Mediation/Interoperation • Security • Scheduling of non-compute Resources • Data/Information Federation • Semantic Grid and management • We will not test scalability on large number of services, sensors and component Grids • Integrating legacy systems not addressed • Grid of Grids building tool is “new idea” – can expect will benefit from further work

18. Research Tasks • The R&D Effort is divided into five major tasks: • Task 1: Implementation of Collaboration Grid Middleware • Task 2: Enhanced NCOW Core Enterprise Services (NCES) • with Enterprise Control Services and Metadata Services • Task 3: Design and implementation of Grid of Grids mediation • algorithms and NCOW services • Task 4: Design and Implementation of Net-Centric • Collaboration Grid Builder Tool • Task 5: Technology Demonstration

19. Task Organization • Requirements • Analysis • Design • Implement • Test & Measure • Repeat

20. Task Assignments Task Anabas Ball CGL Requirements Collaboration Grid Middleware (NCGGCM) (P) (S) (S) NCOW, GiG (P) (S) CES+ (11 service layers) (P) (S) (S) GWSA (P) (S) (S) Grid of Grids (GoG) (P) (S) (S) Mediation Algorithms (P) (S) (S) K2 service (S) (P) NCOW services (e.g., JBI publish, etc.) (S) (P) Net-Centric Collaboration Grid Builder Tool (P) (S) (S) CES+ (P) (S) (S) Wizards for each service (P) (S) (S) Collaboration and Messaging (P) (S) (S) GIS, Sensor and additional services (P) (S) (S) GIS and sensor (P) (S) (S) K2 service (S) (P) NCOW services (e.g., JBI publish, etc.) (S) (P) C2IEDM service (S) (P) Demonstration/Commercial Products (C) (C) (S) Crisis Management for Earthquake (C) (S) (C) Customer provided suggestions for DoD product (C) (C)

21. Task Assignments Task Anabas Ball CGL Research and Concept Analysis Collaboration Grid Middleware (NCGGCM) (P) (S) (S) Grid of Grids (GoG) (P) (S) (S) Net-Centric Collaboration Grid Builder Tool (P) (S) (S) GIS, Sensor and additional services (P) (S) (S) Demonstration/Commercial Products (P) (S) (S)

22. Task Assignments Task Anabas Ball CGL Design Collaboration Grid Middleware (NCGGCM) (P) (S) (S) Grid of Grids (GoG) (P) (S) (S) Mediation Algorithms (P) (S) (S) K2 service (S) (P) NCOW services (e.g., JBI publish, etc.) (S) (P) Net-Centric Collaboration Grid Builder Tool (P) (S) (S) GIS, Sensor and additional services (P) (S) (S) GIS and sensor (P) (S) (S) K2 service (S) (P) NCOW services (e.g., JBI publish, etc.) (S) (P) C2IEDM Services (S) (P) Demonstration/Commercial Products (P) (S)

23. Task Assignments Task Anabas Ball CGL Implement Collaboration Grid Middleware (NCGGCM) (P) (S) (S) Grid of Grids (GoG) (P) (S) (S) Mediation Algorithms (P) (S) (S) K2 service (S) (P) NCOW services (e.g., JBI publish, etc.) (S) (P) Net-Centric Collaboration Grid Builder Tool (P) (S) (S) GIS, Sensor and additional services (P) (S) (S) GIS and sensor (P) (S) (S) K2 service (S) (P) NCOW services (e.g., JBI publish, etc.) (S) (P) C2IEDM service (S) (P) Demonstration/Commercial Products (P) (S)

24. Task Assignments Task Anabas Ball CGL Testing & Evaluation Collaboration Grid Middleware (NCGGCM) (P) (S) (S) Grid of Grids (GoG) (P) (S) (S) Mediation Algorithms (P) (S) (S) K2 service (S) (P) NCOW services (e.g., JBI publish, etc.) (S) (P) Net-Centric Collaboration Grid Builder Tool (P) (S) (S) GIS, Sensor and additional services (P) (S) (S) GIS and sensor (P) (S) (S) K2 service (S) (P) NCOW services (e.g., JBI publish, etc.) (S) (P) C2IEDM service (S) (P) Demonstration/Commercial Products (P) (S)

25. Task Assignments Task Anabas Ball CGL Refine and Refactor Collaboration Grid Middleware (P) (S) (S) Grid of Grids (GoG) (P) (S) (S) Net-Centric Collaboration Grid Builder Tool (P) (S) (S) GIS, Sensor and additional services (P) (S) (S) Demonstration/Commercial Products (P) (S)

26. Milestones & Timelines