Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Project targeted to complete by 5/31/11

Wiki MarkupIncludes (as noted in Approved Change Order 001):
1.            Scalability/Linear testing [https://jira.cornell.edu/browse/UPORTALUPG-188]
2.      Fully Transition production support from the       Fully Transition production support from the E-Team to the A-Team (ISIS); which includes the following tasks:
a.       Internal Procedures\[1\]                                                i.      Updating/maintaining groups [       Internal Procedures[1]
                                               i.      Updating/maintaining groups https://jira.cornell.edu/browse/UPORTALUPG-263]                                               ii.      Adding group definitions to Announcements [
                                              ii.      Adding group definitions to Announcements https://jira.cornell.edu/browse/UPORTALUPG-247]
b.      Production Support Transition from Engineering team to       Production Support Transition from Engineering team to A-Team (A-Team Hand-Off Docs) [https://jira.cornell.edu/browse/UPORTALUPG-44] ; including:                                               i.      CAS provisioning under puppet [including:
                                              i.      CAS provisioning under puppet https://jira.cornell.edu/browse/UPORTALUPG-284]                                               ii.      "hardening" of uPortal production environment [
                                              ii.      “hardening” of uPortal production environment https://jira.cornell.edu/browse/UPORTALUPG-283] c.       Standard Operating Procedures (SOPs):                                                i.      Operating Procedures for Infrastructure [
c.       Standard Operating Procedures (SOPs):
                                               i.      Operating Procedures for Infrastructure https://jira.cornell.edu/browse/UPORTALUPG-56]                                               ii.      Engineering/Architecture Docs [
                                              ii.      Engineering/Architecture Docs https://jira.cornell.edu/browse/UPORTALUPG-41]                                               iii.      ISIS Disaster Recovery (DR) Docs [
                                              iii.      ISIS Disaster Recovery (DR) Docs https://jira.cornell.edu/browse/UPORTALUPG-42]                                               iv.      Configuration Management (CM) Docs [
                                              iv.      Configuration Management (CM) Docs https://jira.cornell.edu/browse/UPORTALUPG-43]                                                v.      Hosting Disaster Recovery (DR) Docs [
                                               v.      Hosting Disaster Recovery (DR) Docs https://jira.cornell.edu/browse/UPORTALUPG-52]                                               vi.      Hosting Release Management (new channels) Docs [
                                              vi.      Hosting Release Management (new channels) Docs https://jira.cornell.edu/browse/UPORTALUPG-55]
3.      Support of LaunchPad performance testing (if needed) [      Support of LaunchPad performance testing (if needed) https://jira.cornell.edu/browse/UPORTALUPG-270]
4.      Stabilization period (includes problem resolution)   Production Support for the myCornell framework will be handled as follows for the interim period (until transition from the E-Team to the A-Team is complete as noted above):   Ø  Tier 1 calls à Help Desk à Portal Administrator Ø  Tier 2 calls à Portal Administrator à A-Team à E-Team   A Service Support Team has been formed and includes members from the Help Desk.   Any issues/fixes will be batched up and prioritized with the Portal Administrator, Service Owner, Service Manager and the A-Team.   As additional Reference Groups are defined, the Portal Administrator will coordinate with the A-Team to have these applied to the PAG groups and/or Announcements as needed per Standard Maintenance requests.   LaunchPad "loose-ends": 1.      Performance testing and resolution (if needed) [      Stabilization period (includes problem resolution)
 
Production Support for the myCornell framework will be handled as follows for the interim period (until transition from the E-Team to the A-Team is complete as noted above):
 
Ø  Tier 1 calls à Help Desk à Portal Administrator
Ø  Tier 2 calls à Portal Administrator à A-Team à E-Team
 
A Service Support Team has been formed and includes members from the Help Desk.
 
Any issues/fixes will be batched up and prioritized with the Portal Administrator, Service Owner, Service Manager and the A-Team.
 
As additional Reference Groups are defined, the Portal Administrator will coordinate with the A-Team to have these applied to the PAG groups and/or Announcements as needed per Standard Maintenance requests.
 
LaunchPad “loose-ends”:
1.      Performance testing and resolution (if needed) https://jira.cornell.edu/browse/LAUNCHPADENHANCEMENTS-92]
2.      Stabilization period (includes problem resolution) 3.      User preferences needs fixing [      Stabilization period (includes problem resolution)
3.      User preferences needs fixing https://jira.cornell.edu/browse/UPORTALUPG-328]

 
Administrative "loose“loose-ends"ends”:
1.      Prepare support FAQs, Help URLs, etc.:
a.       FAQ and Feedback pages https://jira.cornell.edu/browse/UPORTALUPG-220
2.      New & Revised CIT Services documentation https://jira.cornell.edu/browse/UPORTALUPG-127
3.      Final uPortal/LaunchPad environment sign-off https://jira.cornell.edu/browse/UPORTALUPG-272

...