Description
This is a defining statement outlininga sequel project (‘Legacy RDS Transition and Decommission Awareness’) to the active project (‘RDS Lift and Shift’). Logically, this subsequentproject has been established to pick up where the current project completes. With the completion of the current RDS Lift and Shift project, the following items remain and communication to our customer is necessary:•Identify our customers who actively utilize the legacy RDS•Identify our customers who historically were granted accessto the legacy RDS (specifically those non-active customers, however likelyusers in the future)•Identify our customers who historically were granted access tothe legacy RDS (specifically those non-active customers, however unlikelyusers in the future)•Create a communication plan for each of the “customer groups” listed aboveoPossible “Reauthorization” to “new” RDSoCommunicate any action required of likelyuser•DefineDecommissioning of the legacy RDS•Establish date of DecommissioningoRetiringof “old”RDSoClearly communicate that accessibility is equal or better via the“new” RDSThere are differentiating factors that distinguish this ‘RDS Transition and Decommission Awareness’project from the active ‘RDS Lift and Shift’project.These differentiating factors make up the out-of-scopeitems not includedwithin “phase 1”, “phase 2”, “phase 3”, or“phase 4”of the ‘RDS Lift and Shift’ project. A “phase 5” which has been casuallymentioned, will now be separated from ‘RDS Lift and Shift’ and considered part of the ‘Legacy RDS Transition and Decommission Awareness’ project.Communications:(Background: It is recognized that relevant communication to our customer needs to be targeted, be clear and concise, provide appropriate announcementand required steps to transition our customer after completion of our separate “RDS Lift and Shift” project.)The following lists our customer, along with highlighted consideration to successful targeted communication that will define success:1.Active Usera.Intro –You are receiving this message because are an activeregistereduserb.Action requiredc.Is there a campaign manager to verify action taken?d.Who to connect with “if question”e.Reminder of retiring date2.Likely Usera.Intro –You are receiving this messagebecause are an active registered userb.Action requiredc.Is there a campaign manager to verify action taken?d.Who to connect with “if question”e.Reminder of retiring date3.Unlikely Usera.Intro –You are receiving this message because at some point “you mayhavebeen”a registered userb.Action optional(if you would like to register to be a user, moving forward)c.Is there a campaign manager to verify action taken?d.Who to connect with “if question”e.Reminder of retiring date
Cadence of Communication[Retirement Date]•1stNotice –90 days from Retirement•2ndNotice –60 days from Retirement•Final Notice –30 days from RetirementDiscovery, Assumptions, and Affirmations1.Do we need to be granular? (example: specific reports being connected to