Principal Architect

Enterprise Integration/APIM Strategy And Governance Model

Define Enterprise APIM strategy for Internal-to-Internal communication.

i. Define APIM strategy for Internal to internal (between COLO, GCP and Azure) communication.

ii. Define strategy on how all the APIs are discoverable through ULTA's enterprise developer portal, whether they are exposed internally or externally.

iii. Define Domains/Pods which will be created on Development Portal.

iv. Define and set up process to monitor.

Implement and Operationalize Intake.

i. Implement the intake request form in JIRA.

ii. Based on different criteria (Technology, Complexity, Enhancement/New Build, priority, start/end date etc.) of intake request, create automated dashboard to show forecast per technology. Also, show resource availability based on the available resources in the team and forecast.

iii. Define RACI for enterprise integration.

Define & socialize Patterns for Enterprise Integrations and APIM.

i. Define integration patterns for Integrations – TIBCO BW vs TIBCO CE.

ii. Define Integration/Orchestration patterns for APIM.

Define and implement Steady State and Dev Ops support process.

i. Define & implement measurement/dashboard KPI's/SLA's for monitoring APIs & system health.

ii. Transition all artifacts and knowledge to Dev Ops teams - engaging them throughout the process from design through delivery.

iii. Define and implement measurement/dashboarding of KPI's for developer productivity.