The MMC Architecture Workshop

1. The MMC Architecture Workshop Welcome and Introduction Oak Ridge October 21,1997 Michael Wright

2. Welcome • Thank you all for taking the time to come to Oak Ridge for this workshop! • Let’s work together to maximize what we accomplish today and tomorrow.

3. Why are we here? • Many of us have been involved in related work for some time and have been successful. • This work has brought us together and allowed us to create the MMC. • It is now time to use our knowledge to produce a new unified system that paves the way for the future.

4. Workshop Goals • To develop the architecture for the MMC in sufficient detail in order to: • Define the context of each element within the entire architecture. • List the functional requirements for each area. • Allocate responsibilities for execution of each task and set time lines. • Develop the mechanisms to proceed in a collaborative manner.

5. Workshop Deliverables • A functional description and requirements document for the MMC. • An integration plan for working together to create a functioning collaboratory. • Definition of tasks • Allocation of tasks to working groups • Establish timeline and critical path • Methods of communication • A plan for the next steps

6. Some Questions to Keep in Mind • Can the existing hardware (at our sites) be configured to use this architecture? • Can the APIs we need be extensible? Most detectors have a unique interface. • What is the role of integrators such as Gatan/Digital Micrograph? We don't want to usurp them. • What is the role of remote control apps like Timbuktu? • NT-based vs open architecture? • Decide on a hardware API set? • Determine the time schedule for inputs from industry and test tools from MMC.

7. Some Other MMC Issues • MMC is not just about remote control! • How can diagnostic tools be integrated? • How do we interact with DOE 2000, NGI,.... • Global file systems for data storage. • Educational outreach. • It is about collaboration. The whole must be bigger than the sum of its parts.

8. Workshop Agenda • The workshop agenda is intended to facilitate progress. If it gets in the way, let’s change it!

9. Agenda - Day 1 • 8:00 - 8:30 Registration and coffee • 8:30 - 9:00 Welcome and outline of Workshop - Michael Wright • 9:00 - 9:30 What can't we do today? - Edgar Voelkl • 9:30 - 10:00 Strawman architecture vision - Bryan Allen • 10:00 - 10:30 Break • 10:30 - 12:00 Examination of aspects of collaborative environments. • 12:00 - 1:00 Lunch • 1:00 - 2:30 Aspects continued... • 2:30 - 3:30 Determination of the components of the architecture and the functional requirements of each component. What are the boxes? • 3:30 - 5:00 What are the functional requirements of each box? • 6:00 Dinner together

10. Agenda - Day 2 • 8:30 - 10:00 Continuation of functional requirements. New ideas are sure to come up overnight. • 10:00 - 10:30 Break • 10:30 - 12:00 Determination of tasks, deliverables, and critical path. • 12:00 - 1:00 Lunch • 1:00 - 2:00 Allocation of tasks. • 2:00 - 2:30 How do we work collaboratively on this project? • 2:30 - 3:00 What are the next steps? • 3:00 Adjourn • Post-workshop activities: • Working group discussions. • Tours of the ORNL facilities.

11. Examination of aspects of collaborative environments • Security - James Rome • Software bus - Bahram Parvin • Microscope control - Industry • Detector systems - Hans de Ruijter • Imaging and analysis - John Hunt • Beam line control - Cam Hubbard • Remote Scientific Visualization and Operation Using Scanning Probe Microscopes - Anshuman Razdan • Video Conferencing - Kathi Alexander • User interfaces - Nestor Zaluzec • Reservations and resource control - Bryan Allen • Data archive and off-line analysis - Edgar Voelkl • Training - Jim Mabon

12. Workshop Philosophy • We are here to talk about architecture. • We want the best possible solution within the constraints of time, budget, platforms, and available and evolving technology. • Things are changing rapidly, we are trying predict the future and be flexible and adaptable. • We must be compatible with what we have in all our labs today. No religious wars over platforms!

13. The DOE2000 Program • A very brief reminder of why DOE funded the DOE2000 program and what they want to accomplish.

14. DOE2000 Vision • The vision of DOE2000 is to accelerate the ability of the Department of Energy to accomplish its mission through advanced computing and collaboration technologies. • DOE2000 ushers in a new era of scientific collaboration that transcends geographic, discipline, and organizational boundaries.

15. DOE2000 Goals • Improved ability to solve DOE's complex scientific problems. • Increased R&D productivity and efficiency. • Enhanced access to DOE resources by R&D partners.

16. DOE2000 Strategies • Build a National Collaboratory • Build an Advanced Computational Testing and Simulation (ACTS) toolkit • Provide an authentication and security infrastructure • Foster partnerships • Use off-the-shelf solutions whenever possible • Conduct R&D when necessary to meet objectives

17. DOE2000 Program Components • Advanced Computational Testing and Simulation • National Collaboratories • Collaboratory Pilot Projects

18. DOE2000 National Collaboratory • Put unique or expensive DOE research facilities on the internet for remote collaboration, experimentation, production, or measurement. • Provide collaborative tools: videoconferencing, shared electronic notebooks, shared whiteboards, shared document creation, shared data-viewing and analysis tools. • Provide tools for sharing and integrating DOE scientific information.

19. DOE2000 Collaboratory Research & Development Projects • Collaborative Integration Framework • Electronic Logbooks • Collaborative Session Management • Shared Virtual Spaces • Scalable Security Architecture • ESnet Quality of Service • Floor Control

20. DOE2000 Collaboratory Pilot Projects • The Diesel Combustion Collaboratory • Science Area: Diesel engine emissions control • Partners: SNL, LBNL, LLNL, Univ. of Wisc. • Industrial Partners: Cummins Engine Co., Caterpillar Inc., Detroit Diesel • The Materials MicroCharacterization Collaboratory (MMC) • Science Area: Microstructure of technologically advanced materials, with focus on interface characterization for wide user community • Partners:ORNL, LBNL, ANL, NIST, Univ. of Illinois • Industrial Partners: Gatan, Inc.; R. J. Lee; EMiSPEC Systems, Inc., Philips Electronic Instruments; Hitachi Scientific Instruments; Japan Electron Optics Laboratories - USA

21. The MMC • A very brief reminder of why DOE funded the MMC project and what we hold them we would accomplish.

22. MMC Goals • To extend, improve and mold the electronic laboratory environments already in place at each of these Centers into a single cohesive virtual laboratory, accessible from anywhere on the Internet. • To use the extended capabilities of the virtual Collaboratory to address materials sciences research problems related to interfaces and surfaces in economically important materials of interest to DOE programs. • To develop a functional, interactive electronic collaboratory having the necessary tools for operation by the microanalysis community; leading to a truly new paradigm in scientific research.

23. MMC Vision of the Future • This Materials Microcharacterization Collaboratory focuses on the scientists as users in an interactive electronic laboratory. Its goal is to create an electronic environment equipped with state-of-the-art research capabilities, (consisting of both expertise and instrumentation) which revolves around a common theme of microcharacterization in materials research.

24. MMC Vision of the Future, cont’d • By placing creative scientists having varying yet complementary expertise together in a new environment which allows convenient, rapid and dynamic interactions to flow unencumbered by the limits of time and distance, we expect to not only foster, but enhance, the ability of these individuals to conceive and execute scientific research.

25. MMC Vision of the Future, cont’d • It is essential to remember that, at the end of the day, it is not the instrumentation which produces the science but rather the individuals who formulate and execute experiments designed and carried out using the "tools" which they have at their disposal.

26. MMC Facilities

27. MMC Facilities

28. MMC Goals - Year 1 • Setup video conferencing • Get more facilities online (quick and dirty) • Begin site survey to determine MMC-wide solutions • Perform demos at major meetings • Implement individualized security solutions • Upgrade instrument systems to computer control • Share MMC requirements with R&D projects

29. MMC Goals - Year 2 • Routinely use video conferencing & e-notebooks • Define and implement MMC-wide solutions • Test cross-platform solutions at selected sites • Multisite demos at major meetings • Learn from extensive use of MMC • Implement cross-platform security solutions • Enable data sharing and analysis • Evaluate effectiveness of MMC architecture

30. MMC Goals - Year 3 • Deploy and refine MMC-wide solutions • Disseminate MMC technology • Publish materials science research • Expand educational outreach • Finalize next generation instrument specifications • Evaluate effectiveness of MMC • Utilize NGI technology for data analysis • Write final report

31. MMC Deliverables - Year 1 • Q3/97 Do a multisite video conference and document process for user access • Q4/97 Demonstrate remote operation on a low level, basic functionality at each site • Q4/97 Provide protection from Internet attack at each site

32. MMC Deliverables - Year 2 • Q1/98 Issue client certificates for strong authentication • Q1/98 Complete site survey to determine MMC-wide solutions • Q1/98 Complete interface specification between augmented DOE 2000 software bus and GUI • Q2/98 Do multisite materials science experiment • Q2/98 Complete interface specification between instruments and augmented DOE 2000 software bus • Q3/98 Provide advanced functionality of microscope for remote use • Q4/98 Present user with consistent GUI • Q4/98 Implement authorization certificates for fine-grained access control • Q4/98 MMC organize a symposium at MM98 with industrial collaborators

33. MMC Deliverables - Year 3 • Q1/99 Use MMC in classroom • Q2/99 Full deployment of MMC security features • Q3/99 Intelligent data compression and agents • Q3/99 Complete evaluation of effectiveness of MMC • Q3/99 “High speed” data transfer, analysis and data storage across sites • Q4/99 Write final report

34. MMC Metrics:Usage, Success & Dissemination • Instrument on-line hours (% and total) • VC on-line hours • E-notebook use and deployment • multisite instrument on-line hours • MatSci successes- problems solved • MMC joint publications • Technology transfer • Website hits - documents, software, tools • On-line outreach and teaching hours • Requests for joining/replicating MMC • Public relations venues for DOE2000 success

35. And in conclusion, ... • With all that said, let’s get to work!