1 / 26

Collaborative Management Environment CIO Technical Presentation

Collaborative Management Environment CIO Technical Presentation. Thomas E. Potok and Mark Elmore Collaborative Technologies Research Center Computer Science and Mathematics Division Oak Ridge National Laboratory. Collaborative Management Environment: Goals and Objectives.

kaiser
Download Presentation

Collaborative Management Environment CIO Technical Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Collaborative Management EnvironmentCIO Technical Presentation Thomas E. Potok and Mark Elmore Collaborative Technologies Research Center Computer Science and Mathematics Division Oak Ridge National Laboratory

  2. Collaborative Management Environment: Goals and Objectives • Create an environment to financially manage and analyze research funding • Minimal impact to the laboratories • Provide complete and consistent data to DOE • Gain an order of magnitude efficiency in the proposal submission process • Provide a safe and trusted environment for researchers and program managers • Reuse information from proposals to populate the R&D tracking database

  3. Current situation • Field Work Proposals (FWPs) submitted to DOE are in paper books • Weeks and thousands of dollars are spend in collating, copying, binding, and shipping these books • The books provide very limited query and search capability • This paper system makes management of research programs very difficult

  4. CME Pilot Goals • Plan to develop a pilot based on FWP data from three labs • ORNL • LANL • FNL • Gathering lab data • Different formats • Very limited resources from the labs • Initial software commitment problems • Lab feedback • We want the capability of CME, however…they have “been burned before…” • We will be unable to provide data in needed format due to lack of resource.

  5. Information Integration Alternatives • Distributed relational databases (Data Warehouse) • Too expensive for labs to setup and maintain • Object Request Brokers • Too expensive for labs • Too complex for our needs • Groupware (Lotus Notes) • Too expensive for the labs • Lack of flexibility in formats supported • HTML and internet • Difficult to store and manage structured data • XML provides a possibility

  6. Distributed Information through XML • Strengths - We are at the ground level of this technology • XML is the de-facto standard, accepted by Microsoft, Sun, IBM, and the software industry in general • XML allows simple storage of structured, distributed data • XML allows queries and data presentation • Weakness - We are at the ground level of this technology • XML is an evolving standard • The tools to support XML are limited, and weak • Supporting standards for data presentation are very limited

  7. Approach • Data model developed with LANL, FNL, ORNL, and OSTI • Reviewed by business systems experts as well as technical experts • Pioneered use of XML as a means of storing, querying, and presenting FWP information. • Simple data storage technology • Very low costs to the labs, integration work done by CME team • Very well received article at XML’98

  8. Sample FWP

  9. CME Data Mapping Example

  10. CME Pilot Data Model Sample

  11. CME Information Model

  12. Same XML Data Type Definition

  13. Sample XML file

  14. Keyword Search

  15. Gathering Data from the Labs Original Lab FWP Lab HTML Format Infoseek HTML Registry Keyword and Schema Search Lab XML Formats CME Title PI LANL Common SQL Format Date Common XML Format ORNL

  16. New CME Tools Developed Data Translation to XML Original Lab FWP Lab HTML Format Infoseek HTML Registry Keyword and Schema Search XML to SQL Generator Lab XML Formats CME Title PI LANL Common SQL Format Date Common XML Format ORNL XML To HTML Generator

  17. Future Vision Lab XSL Format Original Lab FWP Keyword and Schema Search Lab XML Formats CME LANL Title PI ORNL Common SQL Format Date Common XML Format

  18. Automatic Full CME System Oracle Database Manual Operational CME Data Model Logic Socket Phthia CME Client CME Server Data Socket Infoseek HTML Registry Data Socket Data Socket Nenad NT Web Browser CTRC DTDs HTML Data Netscape Web Server CTRC XML Data Lab FWP Report

  19. Key Pilot Milestones • 1998 ORNL and LANL data in CME Pilot • Distributed information using XML • Low-cost participation by ORNL and LANL, (only 2 person-days from the lab is required!) • Lab information presented in lab FWP format • Capable of adding a new lab in 1 month or less • Very strong interest in CME, limit lab resources • Fermi participation delayed • Berkeley is very interested • PPPL will participate in the future

  20. Extended Pilot Goals • Add three labs to the CME system • Strive for a wide representation over the DOE laboratory system • Add OSTI to the development team • Begin transition to production through training, and development of key database components • Begin merger of CME and R&D Tracking data models • Prototype CME and R&D Tracking interaction

  21. Pilot Findings • Not all labs have data in database format, • Full databases (ORNL, SNL) • Partial databases (LANL) • MS Word template (LBNL, PNNL, LANL) • Scanned images (PNNL) • General situation • First page of the FWP created from a word processing package by the PI, then printed. The source file is lost. • Financial data is manually entered into a financial database

  22. How to get ALL labs into CME? • Scan paper documents into CME • Benefit: All labs can participate • Drawbacks: • Another step and more cost is added to the process • Limited searching capability • Limited presentation capability • Require labs to present information in database report format • Benefit: Pilot can be moved into production immediately for some labs • Drawback: A heavy burden for a number of labs that may take years to support • Capture electronic information from PIs • Benefit: PI’s original information is captured • Drawback: • The structure of the information is lost • Central control of the data is lost

  23. Word Processor Support • Benefits • Richer description for the Program Manager • In the current paper based system, an FWP is limited to text only. • CME will allow a proposal to contain any of the following: • Equations, • Graphs, • Audio, • Video, • VR, • Any future web presentation technologies. • The FWPs are keyword searchable • The information resides at the labs under lab control • PI has full control over how an FWP looks

  24. Word Processor Support • Drawbacks • The FWPs are not field searchable, only keyword searchable • Labs and PIs need to slightly change their processes to: • Save the word processor files as HTML • Post the FWP page at the site • PI has full control over how an FWP looks

  25. Extended Pilot participant labs • Currently we are working closely with: • ORNL • LANL • Sandia • PNNL • Have contacts with: LBNL, Fermi, PPPL, and, SLAC • These labs represent a broad range of differing formats, and approaches to FWPs • The lab representatives are very supportive of the extended pilot approach! • Major issue are business related rather than technical

  26. Summary • Pilot demonstrated the gathering of FWP data from two labs • Extended Pilot to add three labs to the CME system • Supporting all lab FWP formats • Partnering with OSTI • Merging with R&D Tracking Database • Estimated annual savings to $1M • Poised for a successful deployment of CME

More Related