AEP OE On-boarding: Use Cases

OE Onboarding

 

The standard rollout package contains the following:

  •  
  • Dedicated instance per OE following the oneMarketing Global Standards
  • Use case based rollout (no plain use of AEP)
  • AEP will be offered with agreed use cases and mandatory launch packages (use cases specific) within a to be agreed project rollout
  • Additional effort on OE side possible based on OE specific custom setups
  • Run / Support following oneMarketing standards (administrative and infrastructure-related activities are carried out by oneMarketing)
  •  AEP license cost will be covered via oneMarketing Core (TIE Model)
AEP Global Setup
AEP WorkPackages

Ownership: AzTech and OE
Scope: Close work in collaboration mode between the OE and AzTech, in order to establish below work items
Result: OE is ready for Work Package 2                                                                                             
  • AzTech shares the readiness checklist with the OE
  • OE point of contact can take over the checklist and coordinates its completeness internally within their organization
  • OE can reach out or ask for meetings to discuss open questions with AzTech
  • AzTech receives completed checklist from OE to proceed with onboarding of the OE into AEP world

Ownership: AzTech
Scope: Setup of AEP instance for the OE
Result: Ready with OEs sandbox and related modules for use case related work to begin.                                                                                                                                                                             
  • AEP Real Time Customer Data Platform (RT-CDP) Sandbox provisioning
  • Rights and roles setup and creation of relevant user groups and product profiles
  • Provisioning of relevant modules of AEP like Event Forwarding
  • Provisioning of AWS S3 data landing zone.

Ownership: AzTech + AEP Project Team + OE
Scope: Both AzTech and AEP Project Team to learn more from OE on their expectation and clarify important details of the use cases and other dependencies.
Result: Based on these discussions and alignments, all details are available to proceed with use case implementation.                                                                                                                                                             
  • Use case review and alignment
  • Identification of possible bottlenecks and mitigation plan for such scenarios
  • Identification of relevant data sources and destinations
  • Alignment and planning for relevant content and assets for use case related to Adobe Target or Ads or Email Content

Ownership: AEP Project Team
Scope: Develop and deploy the technical solution into OE´s sandbox
Result: Development work for use case rollout is completed and ready for User Acceptance Test (UAT) by OE                                                                                                                                                        
  • AEP Project team deploys the blueprint use cases to OE sandbox
  • Further customizations are developed and deployed as per OEs requirements
  • Internal validation and review for completeness check
  • Communication to AzTech and OE for User Acceptance Test (UAT) readiness

Ownership: OE 
Scope: The scope of this work package is for OEs team a review/UAT before making the use case go-live. 
Result: Onboarding and delivery completed                                                                                                                                                            
  • Post development review by the OE and their team
  • OE can conduct User Acceptance Test (UAT) and other tests to ensure completeness and quality
  • On successful completion of the review, OE can push these use-cases to production