1 / 32

LLNL and LANL Portal Update Cathy Aaron, Lawrence Livermore National Laboratory Katherine Norskog, Los Alamos National L

LLNL and LANL Portal Update Cathy Aaron, Lawrence Livermore National Laboratory Katherine Norskog, Los Alamos National Laboratory Presented at InterLab 2003, November 6, 2003. UCRL-PRES-155700 and LA-UR-03-8124.

natara
Download Presentation

LLNL and LANL Portal Update Cathy Aaron, Lawrence Livermore National Laboratory Katherine Norskog, Los Alamos National L

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. LLNL and LANL Portal Update Cathy Aaron, Lawrence Livermore National LaboratoryKatherine Norskog, Los Alamos National Laboratory Presented at InterLab 2003, November 6, 2003 UCRL-PRES-155700 and LA-UR-03-8124

  2. This work was performed under the auspices of the U.S. Department of Energy by the University of California, Lawrence Livermore National Laboratory under Contract No. W-7405-Eng-48 UCRL-PRES-155700

  3. ‘02 Interlab what LANL said … UCRL-PRES-155700

  4. LANL FY03: Next Steps • Provide additional data to managers —performance indicators, comparative benchmarks • Provide data for the individual—your training, property, paystub, etc. • Move business applications to common authentication when possible • Develop: Eudora/Meeting Maker integration, Virtual workplaces (with directory) • Formalize the portlet development methodology, developer training, content rule set and content review process UCRL-PRES-155700 LLNL and LANL Portal Update 4

  5. What LANL did… UCRL-PRES-155700

  6. What LANL did… • Provide additional data to managers • Provide data for the individual—your training, property, paystub, etc. • Move business applications to common authentication when possible • Develop: Eudora/Meeting Maker integration, Virtual workplaces • Formalize the portlet development methodology, developer training, content rule set and content review process • Expand the audience for My LANL to facility managers • Formalize the governance structure for My LANL • Serve 1200 unique visitors per month who are visiting MyLANL about 3,000 to 5,000 times a month. UCRL-PRES-155700 LLNL and LANL Portal Update 6

  7. LANL web and content governance UCRL-PRES-155700 LLNL and LANL Portal Update 7

  8. My LANL, welcome UCRL-PRES-155700 LLNL and LANL Portal Update 8

  9. My LANL, personnel UCRL-PRES-155700 LLNL and LANL Portal Update 9

  10. My LANL, finance UCRL-PRES-155700 LLNL and LANL Portal Update 10

  11. My LANL, property and purchasing UCRL-PRES-155700 LLNL and LANL Portal Update 11

  12. ‘02 Interlab what LLNL said … UCRL-PRES-155700

  13. LLNL FY03: Next Steps • Migrate to Oracle Portal Release 2 • Analysis and delivery of additional communities of interest and organizational portals • Portlet development methodology, documentation, training, and workbench • User communication/education • Moving business applications to 9iAS infrastructure • Development projects: Eudora/Meeting Maker integration, institutional calendar, browser bookmark import, integrated inbox • Redesign of front page to align with institutional communication plan UCRL-PRES-155700 LLNL and LANL Portal Update 13

  14. What LLNL did… UCRL-PRES-155700

  15. LLNL FY03: Accomplishments • Provided support to Web publishers and MyLLNL end users (January – September 2003) • 5,649 average visitors per day using MyLLNL • 414 portal cases logged • 13,087 staging requests processed by ~150 content publishers • 97 staging requests required special handling • Developed the Institutional Web Resource Center portal • Developed and enhanced portlets • My Favorites/My Applications • Special Announcements enhancements • Customizable Weather • Event in box and API • Livelink Enterprise Workspace • Institutional Calendar • Alpha paging upgrades • People lookup enhancements • Portal administration tools enhancements • Upgrades to various portlets to implement enhanced db connection pooling, caching, and error handling • Participated in the Oracle Portal 9.0.4 beta program • Developed proposed Institutional Web governance model UCRL-PRES-155700 LLNL and LANL Portal Update 15

  16. LLNL Web and content governance • Goal for Institutional Web governance: • Effectively manage LLNL’s Institutional Web in support of the growing demand for web delivered content, applications, document management systems, and user collaborations across programmatic boundaries (workbenches). • The Institutional Web includes the “llnl.gov” external web presence, the “MyLLNL” intranet user interface built with portal technologies, and the institutional web content publishing and hosting services • The current LLNL Institutional Web governance structure includes defined roles and responsibilities for the oversight of… • Institutional content publication • People and operations • Practice community workbenches • Institutional communication • Process and organizational community workbenches • Infrastructure and operations UCRL-PRES-155700 LLNL and LANL Portal Update 16

  17. LLNL Web and content governance,continued UCRL-PRES-155700 LLNL and LANL Portal Update 17

  18. LLNL Web and content governance,continued • Roles and responsibilities for web and content governance - PROPOSED • The Administrative Information Systems Department (AIS) is responsible for Infrastructure and Operations, which includes oversight of the Institutional Web architecture, production support, and new development and integration • The Computation Directorate is responsible for central authentication/single sign-on • Various Technical Advisory Groups review policies for Infrastructure and Operations • The Director’s Office is responsible for oversight of institutional content, including policies and procedures for institutional web publication management, including • Operations data used for the Institutional Personalized User Interface • Practice communities’ alignment with institutional requirements and review of their respective workbenches • Content in the realm of institutional web communication, both internal and external • Individual business units are responsible for oversight, development, and maintenance of process community workbenches • Individual directorates are responsible for oversight, development, and maintenance of organizational community workbenches • Business units and directorates are encouraged to align their workbench development with institutional requirements UCRL-PRES-155700 LLNL and LANL Portal Update 18

  19. MyLLNL update UCRL-PRES-155700 LLNL and LANL Portal Update 19

  20. MyLLNL update UCRL-PRES-155700 LLNL and LANL Portal Update 20

  21. MyLLNL update UCRL-PRES-155700 LLNL and LANL Portal Update 21

  22. MyLLNL update, continued UCRL-PRES-155700 LLNL and LANL Portal Update 22

  23. MyLLNL update, continued UCRL-PRES-155700 LLNL and LANL Portal Update 23

  24. MyLLNL update, continued UCRL-PRES-155700 LLNL and LANL Portal Update 24

  25. MyLLNL update, continued UCRL-PRES-155700 LLNL and LANL Portal Update 25

  26. MyLLNL update, continued UCRL-PRES-155700 LLNL and LANL Portal Update 26

  27. MyLLNL update, continued UCRL-PRES-155700 LLNL and LANL Portal Update 27

  28. MyLLNL update, continued UCRL-PRES-155700 LLNL and LANL Portal Update 28

  29. What we’re going to do… UCRL-PRES-155700

  30. LLNL FY04: Next steps (funded) • Provide support for internal and external Web publishing • Perform search tool research, analysis, and search results improvements • Develop and implement Web publishing guidelines/standards • Analyze and improve access control, group and user management processes • Implement new content management processes and procedures • Develop and implement strategy for archiving content • Integrate content staging with Information Management processes • Standardize web and portal support operating procedures • Standardize institutional use of My In Box and Calendar UCRL-PRES-155700 LLNL and LANL Portal Update 30

  31. LLNL FY04: Next steps(require funding) • Oracle Portal 10g upgrade • Automation tools analysis and implementation • External Web upgrade • New and enhanced workbenches: • Project Management workbench • Manager/Supervisor workbench • Computer Security workbench • Resource Management and Administrative workbench updates • Data Warehouse portal interface • Security portal • Employee Handbook implementation UCRL-PRES-155700 LLNL and LANL Portal Update 31

  32. LANL FY04: Next steps • Expand the number of contributing developers through the “portlet build kit” created to increase ease of adoption • Continue to build managerial “to do” list by increasing the number of “alerts” to managers indicating actions needed (and their priority) while reducing related email • Enable a “customer-service center” deliverable, FAQs for managers • Enhance infrastructure • Build security portal • Build safety portal • Integration with Enterprise Project for deployment of new Oracle application content • Expansion of My LANL audience to include safety workers, business team leaders and security specialists UCRL-PRES-155700 LLNL and LANL Portal Update 32

More Related