Oracle Calendar Policy Steering Committee
June 29, 2005
Minutes

• Overview of Oracle 10g Beta
  • Harry Nicholos gave a review/demo of Brickyard (Oracle) Calendar (Oracle 10g)
  • The time frame/schedule is to begin1st week in July to tear it down, repopulate it with peoples calendars, unity IDs and passwords.
  • Harry mentioned that with this version, we will have regularly scheduled outages (1/month - 4 hours each is a possibility)
  • During the repopulation phase, systems staff will review privacy block requirements and implement accordingly
  • Node Managers (as they currently exist) will no longer be necessary - nodes, per se, will not exist
  • Resource Managers will be necessary - these managers will coordinate, maintain and add resources from their areas
• Brickyard (Oracle) Calendar
• Brickyard (Oracle) Conferencing
• If faculty would like to implement use in their classes, that is OK. Email Twanda_Baker@ncsu.edu if you need educational assistance.
• Oracle WebConferencing will be next to roll out.
  
  
• Review of Calendar Steering Team charge (Bill Padgett)
  • Members of the Calendar Steering Team are invited to expand their roll to become the Oracle Collaboration Suite Steering Team. Members who do not want to remain on the committee in this capacity should send Laura_Grady@ncsu.edu or Harry_Nicholos@ncsu.edu an email. Likewise, if there are others whom you believe should be included on the Steering team, please send Laura or Harry an email.
    
    
• Implementation Plans (Laura Grady)
• Brickyard/Oracle Web Conferencing will be the next Collaboration Suite tool to roll out. Each member of the committee will be given an account for testing. Harry Nicholos will plan a 'web conference' and invite the members so that we can see the tool in action.
• The new Brickyard Calendar rollout
• Soft rollout
  • emphasis that we are testing the implementation/ scaling (ie: the software is reliable, stable and secure)
• ideas:
  • allow LITRE to assist in publicity
  • make an announcement in the Faculty Bulletin
  • get on the agenda, make a presentation at the Deans, Directors, Department Heads and/or IT Director's meetings (present to the Associate Deans first as a trial run)
  • provide information meetings / opportunities to educate Groupwise users who may not be aware all faculty & staff are not in groupwise.
  • announce the rollout on pay stubs
  • create a sysnews announcement
  • send an announcement to lists (extension, NAG, etc)
  • work with faculty in the introductory computing classes (e.g. ALS)
  • Email Announcement
  • Flyer in Bookstore
  • Banner on Library
  • Plywood Signs in the Brickyard
  • Technician Article/Ad
  • Posters in the Labs
• Training
  • to students we emphasis web access (but do allow client installs)
  • documentation is already done for the web version
  • documentation is mostly done for the client versions
  • provide training
    • online (do it yourself)
    • train the trainer
    • classes (already in place for faculty & staff : (http://www.ncsu.edu/it/education/schedule/corp_time.html)