1 / 58

IT Briefing

IT Briefing. September 2006. IT Briefing Agenda 9/21/06. SWE Updates Manage IT Upgrade Blackboard Overview Web Approach NetCom Q&A. Karen Jenkins Karen Jenkins Sandra Butler Karen Jenkins Paul Petersen. October 19 Briefing 10:15 – 1:30 – MS to attend: 1 hour for Product Roadmap

edith
Télécharger la présentation

IT Briefing

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. IT Briefing September 2006

  2. IT Briefing Agenda 9/21/06 • SWE Updates • Manage IT Upgrade • Blackboard Overview • Web Approach • NetCom Q&A • Karen Jenkins • Karen Jenkins • Sandra Butler • Karen Jenkins • Paul Petersen • October 19 Briefing 10:15 – 1:30 – MS to attend: • 1 hour for Product Roadmap • 1 hour for Vista and Office 2007 MS to provide lunch. Please RSVP to: sebreana.williams@emory.edu

  3. Software Express • Microsoft access • Student employees no longer given access • Sponsored accounts & retirees • No longer given access • Examining all applications against our contracts and will make adjustments accordingly • Any issues?

  4. Manage IT Karen Jenkins Andrew Kincaid Al Shelton

  5. Remedy Modules Service Desk Change Management Action Request System Service Level Management Asset Management

  6. Architecture

  7. Remedy Upgrade – Heads up! • Major new release v7.0 • More ITIL compliance • Multi-tenancy • Additional categorization – from 3 levels to 6/7 (product & operational) • Cleaner look – left navigation & top navigation • Solutions/knowledgebase – added user flag • Definitive Software Library (DSL) • CMDB – with new tools to assist the build, graphical view • REMOVED the “teaser” apps

  8. Service Desk (Help Form) • New name for Help Desk module • Largest graphical change is top ITIL process bar • 2 types of Requests (ITIL compliance) • Incident • Problem • Task management added (use with incidents, problems, or change requests) • New canned reports • Enhanced problem management, new form • Work log renamed to Work Info (table based) • Other fields renamed (such as severity to impact) • Decision tree and scripts

  9. Change Management • Module now required to create any type of change request • More/tighter integration with Configuration Management, DSL, & CMDB • Closed loop change • Change calendar w/ business events • Set varying approval levels – even auto-approve – so process is not bogged down • Save high risk changes for CAB

  10. Other Applications • Service Level Management • Ability to compute overall SLA compliance with multiple weighted targets • Performance targets via SNMP interface (SMARTS) • Asset Management • Better integration with Configuration Management (aka Marimba) • DSL contains a product dictionary • Software license management

  11. Input & Schedule • First TechTalk tomorrow 2:00-3:30 NDB 225 Kennesaw • 10/13, 11/3, 11/24 • Will also updates at IT Briefing • Target installation => October • Go-live => TBD • Initial scope = migrate current functionality & data

  12. ? Questions Manage IT

  13. Blackboard @EmorySandra ButlerManager, Interactive Technologies TeamIT Briefing 09/21/06

  14. Adam Lipkin Marcy Alexander Tricia Goddard Kathy Hayes David Lower Julia Leon Marianne Schneider Open Slot Interactive Technologies Team

  15. Interactive Technologies • LearnLink • Blackboard • classes.emory.edu • classes@emory.edu • Insight • Wimba

  16. What is Blackboard (Bb)? • Academic Suite • Learning System • Community System • Content System • Building Blocks • Add-ins that extend capability and functionality

  17. Course and Content Authoring Assessment Engine Assignment Manager Online Gradebook Discussion Board Email Class Virtual Chat Group Management Course Reporting and Statistics Performance Dashboard/Review Status (recent upgrade) Bb Tools more available via Building Blocks and Course Cartridges

  18. History: Bb at Emory 1999: review Bb CourseInfo versus WebCT teaching & learning at anytime from anywhere 2000: University adopts Bb 5; upgrade to Course & Portal Manager depts, orgs, and clubs; customizable buttons; building blocks announcement (Bb Inc.) 2002: upgrade to Bb 5.5 Enterprise Bb app server & Oracle db server; move to 24/7 data center; custom script for enrollment; Emory’s GenLib developers release e-reserves interface for Bb; branding 2004: upgrade to Bb 6.1 LDAP enabled; PS feeds via Bb snapshot utility; dual servers in PROD and DEV

  19. History: Bb at Emory 2005: license Content System; SSL & load balanced; upgrade to Bb 6.2 file mgmt; content sharing; ePortfolios; passes to entire community and guests; Wimba Building Block trial 2006: Reorganize / AAIT / ATS / Interactive Technologies app system support transition; upgrade to Bb 6.3; RSPH migrates to University Bb servers; add’l training and outreach (ex. JIT sessions, custom training sites, etc.); increased non-academic and training usage; Wimba Building Block added 2007: Enhance integration w/other IT resources review overall structure: enhance processes; improve infrastructure

  20. Bb at Emory Stats 09/18/06 2:00pm • 3,255 courses • 1,772 active courses (08/06 – current) • 163 organizations • 104 active organizations (08/06 – current) • includes intranets, student forums and groups, faculty/staff groups and committees

  21. Bb at Emory Stats 09/18/06 2:00pm

  22. Bb Course Site

  23. Building Block: Wimba Voice Tools

  24. Bb & Insight integration made easy

  25. https://classes.emory.edu

  26. Proposed Web Approach September 2006

  27. Agenda • Current environment • Initial plan • Revised plan • Architecture goals • Draft architecture • Estimated timeline • Outstanding issues

  28. Gecko & Maple • Focused on the needs of the hard core developer community • Maple Issues: • Difficult to support & maintain due to multiple customizations (Apache, “ITD WebDrive”) • Security issues • Old hardware

  29. Initial Plan • Update hardware • Update software • But what are the most common needs of the community • Does this hit the mark … Stabilize, re-group, gather requirements

  30. Stabilize • Split SiteMinder / non-SiteMinder sites • Solved the performance issues identified in March ‘06 • Upgrade CF to 7.1 (Maple) • Containment capabilities improve stability • Majority of code in CF – allowed for early testing prior to new architecture • Identify high risk security issues • Plan in place to implement changes

  31. Community Requirements • Developers only need a couple of additional features: • MySQL, shell access on Dev, stability • Resource and/or skill set constrained users are the majority • Analysis indicates there are many static sites and others with basic/common minor dynamic components (~77%) • One size does not fit all …

  32. Revised Plan • Place focus on the majority and the current gaps • Build a tiered service offering • target different customers/needs • Build tool kit for common needs • Provide more applications • Improve documentation

  33. Web Approach • Standard Hosting • Users with limited resources needing to quickly and easily publish static websites • Advanced Hosting • Users with advanced developments skills creating dynamic sites and/or web applications • Enterprise Hosting • Users creating mission critical enterprise websites and/or enterprise web applications Tiered service offerings dependant upon user needs

  34. FUTURE STATE

  35. Hosting Options

  36. Hosting Options (cont.)

  37. Hosting Options (cont.)

  38. Hosting Options (cont.)

  39. Hosting Options (cont.)

  40. Hosting Options (cont.)

  41. Architecture--DRAFT--

  42. Architecture Goals • Low entry-barrier • Consolidate where possible • Improved isolation / management • Seamless scalability • Highly secure • High stability, availability, and performance

  43. Project Scope Phase 1 and beyond

  44. Project Scope • Design & implement new robust web infrastructure • Create mandatory tools • Administration/provisioning • File management • Necessary scripts for Standard • Improve existing documentation • Migrate current Maple sites • AAIT to move sites and test • AAIT to create required documentation • Site owners to test & validate

More Related