diegoecab/oci-deal-accelerator
1
1
Fork 2
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

initial version

Browse Source
This commit is contained in:
Diego Cabrera
2026-03-18 18:03:44 -03:00
commit 9d269e902b
136 changed files with 28175 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
templates/adr-template.md Normal file
View File

@@ -0,0 +1,43 @@
# ADR-{NUMBER}: {TITLE}
**Status**: Accepted | Proposed | Superseded
**Date**: {DATE}
**Deciders**: {STAKEHOLDERS}
## Context
{Why this decision was needed. What problem are we solving? What constraints exist?}
## Decision
{What was chosen and how it will be implemented.}
## Alternatives Considered
### Option A: {NAME}
- **Pros**: {benefits}
- **Cons**: {drawbacks}
### Option B: {NAME}
- **Pros**: {benefits}
- **Cons**: {drawbacks}
## Rationale
{Why this option was selected over alternatives. Reference workload profile requirements, Well-Architected Framework checks, and commercial considerations.}
## Consequences
- **Positive**: {benefits gained}
- **Negative**: {trade-offs accepted}
- **Risks**: {what could go wrong and mitigations}
## Well-Architected Alignment
| Pillar | Impact | Notes |
|--------|--------|-------|
| Security & Compliance | {PASS/GAP} | {details} |
| Reliability & Resilience | {PASS/GAP} | {details} |
| Performance & Cost | {PASS/GAP} | {details} |
| Operational Efficiency | {PASS/GAP} | {details} |
| Distributed Cloud | {N/A/PASS/GAP} | {details} |

153
templates/business-case.yaml Normal file
View File

@@ -0,0 +1,153 @@
# Business Case Template — DEFINE Phase
# Generates the business justification for OCI adoption.
# Target audience: Customer's internal decision-makers (CxO, finance, procurement).
# Output: Slide deck (.pptx) + YAML spec for reuse.
business_case:
# --- Header ---
customer_name: ""
prepared_by: ""
date: ""
version: "1.0"
status: draft # draft | review | approved
confidentiality: "Oracle Confidential"
# --- Executive Summary (1 paragraph for CxO) ---
executive_summary: ""
# e.g., "Migrating 5 Oracle databases from on-prem to ADB-S reduces
# annual infrastructure costs by 47% ($1.2M/year), eliminates 4h/month
# of unplanned downtime, and positions Acme for PCI compliance by Q3."
# --- Business Drivers ---
drivers:
primary: "" # cost_reduction | modernization | performance | compliance | hw_eol | consolidation | competitive_pressure
secondary: [] # Additional drivers
urgency: "" # Why now? e.g., "Hardware EOL in 6 months"
cost_of_inaction:
financial: "" # "$X/year in maintenance + $Y risk exposure"
operational: "" # "4h monthly downtime, 3 FTEs on manual patching"
strategic: "" # "Competitor already on cloud, losing talent"
urgency_deadline: "" # Absolute date if applicable (e.g., "2026-09-30")
# --- Current State Summary ---
current_state:
infrastructure: "" # Brief: "3 Exadata racks on-prem, 5 years old"
pain_points: [] # ["Manual patching takes 2 weekends/quarter", "No DR tested in 18 months"]
annual_spend: 0 # Current total annual IT spend for in-scope workloads
team_size: 0 # FTEs dedicated to operations
# --- TCO Comparison ---
tco:
horizon_years: 3 # 3 or 5
current_state:
annual_infrastructure: 0 # HW depreciation, DC, power, cooling, network
annual_licensing: 0 # SW licenses + annual support
annual_operations: 0 # FTEs × average cost (DBAs, sysadmins, etc.)
annual_downtime_cost: 0 # Revenue loss + recovery effort
annual_compliance_cost: 0 # Audit prep, remediation, tooling
total_annual: 0
total_over_horizon: 0
proposed_oci:
migration_one_time: 0 # Migration effort (consulting, tools, overtime)
annual_cloud_consumption: 0 # OCI UCM or PAYG
annual_licensing: 0 # BYOL savings or License Included delta
annual_operations: 0 # Reduced FTEs (managed services effect)
annual_downtime_cost: 0 # Improved SLA
annual_compliance_cost: 0 # Automated compliance (Data Safe, etc.)
total_annual: 0
total_over_horizon: 0 # Includes migration one-time
savings:
annual: 0
over_horizon: 0
percentage: 0
assumptions:
- "730 hours/month for always-on workloads"
- "BYOL applied for existing EE licenses with active support"
- "Migration duration: X months"
notes: ""
# --- ROI Analysis ---
roi:
total_investment: 0 # Migration cost + Year 1 cloud premium
annual_net_benefit: 0 # Annual savings + quantified value
payback_months: 0
three_year_roi_pct: 0 # (total_benefit - total_investment) / total_investment × 100
five_year_roi_pct: 0 # Optional
# --- Value Drivers (quantified where possible) ---
value_drivers:
- category: cost_reduction
title: ""
description: ""
quantified: "" # "$X/year" or "X% reduction"
evidence: "" # Source: benchmark, customer data, field experience
- category: risk_reduction
title: ""
description: ""
quantified: ""
evidence: ""
- category: agility
title: ""
description: ""
quantified: ""
evidence: ""
- category: innovation
title: ""
description: ""
quantified: ""
evidence: ""
# --- Risk Assessment ---
risks:
migration_risks:
- risk: ""
probability: medium # low | medium | high
impact: high # low | medium | high
mitigation: ""
residual_risk: low
do_nothing_risks:
- risk: ""
probability: high
impact: ""
timeline: "" # When does this risk materialize?
# --- Competitive Context ---
competitive:
alternatives_considered: [] # ["AWS RDS", "Azure SQL MI", "Stay on-prem"]
why_oci: [] # Differentiators for THIS workload
honest_gaps: [] # Where competitors have an edge
oci_unique: [] # Features only OCI offers (ADB, Exadata, BYOL depth)
# --- Implementation Roadmap ---
roadmap:
total_duration: "" # e.g., "6 months"
phases:
- name: "Phase 1: Foundation"
duration: ""
deliverables: []
quick_wins: [] # Early visible value
- name: "Phase 2: Migration"
duration: ""
deliverables: []
- name: "Phase 3: Optimization"
duration: ""
deliverables: []
# --- Success Criteria (post go-live KPIs) ---
success_criteria:
- metric: ""
baseline: "" # Current value
target: "" # Expected value post-migration
measurement: "" # How to measure
timeline: "" # When to measure
# --- The Ask / Recommendation ---
recommendation:
summary: "" # 1-sentence: "We recommend X"
commitment_type: "" # UCM | PAYG | hybrid | PoC_first
commitment_amount: "" # "$X/year for Y years"
next_steps:
- action: ""
owner: "" # Oracle | Customer | Joint
deadline: ""
escalation_path: "" # If no decision by [date], what happens?

100
templates/customer-profile.yaml Normal file
View File

@@ -0,0 +1,100 @@
# ═══════════════════════════════════════════════════════════════
# ECAL Customer Profile Template
# ═══════════════════════════════════════════════════════════════
# Source: ECAL 3.1 - Ideate Step (Define Phase)
# Purpose: Strategic profiling of the customer beyond tech details
# Note: This is an INTERNAL document — not shared directly with customer
# ═══════════════════════════════════════════════════════════════
metadata:
customer: ""
account_team: ""
date: ""
version: "1.0"
status: "draft" # draft → reviewed → validated
# ───────────────────────────────────────────────────────────────
# 1. COMPANY OVERVIEW
# ───────────────────────────────────────────────────────────────
company:
name: ""
industry: ""
sub_industry: "" # e.g., "retail banking", "life sciences"
headquarters: ""
annual_revenue: ""
employees: ""
fiscal_year_end: ""
stock_ticker: "" # if public
recent_events: [] # M&A, IPO, restructuring, leadership change
# ───────────────────────────────────────────────────────────────
# 2. STRATEGIC GOALS & DRIVERS
# ───────────────────────────────────────────────────────────────
strategy:
published_goals: [] # from annual report, press releases, CEO keynotes
# Example:
# - "Double digital revenue by 2027"
# - "Reduce operating costs by 15% over 3 years"
# - "Expand to 3 new APAC markets"
technology_strategy: "" # cloud-first? multi-cloud? hybrid? on-prem?
digital_transformation: "" # where are they on the journey?
competitive_position: "" # leader, challenger, follower in their market?
competitor_threats: [] # cloud-native disruptors, adjacent players
# ───────────────────────────────────────────────────────────────
# 3. ORACLE FOOTPRINT
# ───────────────────────────────────────────────────────────────
oracle_footprint:
products_in_use: []
# Example:
# - { product: "Oracle Database EE", version: "19c", count: 350, licensing: "Processor" }
# - { product: "WebLogic", version: "14c", count: 12, licensing: "NUP" }
licensing:
type: "" # ULA, PULA, Processor, NUP, Named User
expiry: "" # when does ULA/PULA expire?
byol_eligible: ""
support_spend: "" # annual Oracle support spend
existing_oci_usage: "" # any OCI tenancy already? what's running?
existing_cloud_usage: [] # AWS, Azure, GCP — what workloads?
# ───────────────────────────────────────────────────────────────
# 4. INDUSTRY ANALYSIS
# ───────────────────────────────────────────────────────────────
industry_context:
market_trends: [] # relevant industry trends
regulatory_landscape: [] # regulations affecting IT decisions
peer_comparison: "" # how does this customer compare to industry peers?
# Example:
# market_trends:
# - "Open banking APIs mandated by 2025"
# - "DORA regulation requiring operational resilience testing"
# regulatory_landscape:
# - "EBA guidelines on ICT risk management"
# - "GDPR data residency requirements"
# ───────────────────────────────────────────────────────────────
# 5. RELATIONSHIP CONTEXT
# ───────────────────────────────────────────────────────────────
relationship:
account_manager: ""
current_engagement_status: "" # active deal, renewal, new, expansion
previous_engagements: [] # past ECAL/consulting engagements
customer_sentiment: "" # positive, neutral, at-risk
executive_sponsors:
oracle: "" # Oracle exec sponsor
customer: "" # Customer exec sponsor
key_contacts:
- { name: "", role: "", influence: "", relationship: "" }
# ───────────────────────────────────────────────────────────────
# 6. INITIAL HYPOTHESIS
# ───────────────────────────────────────────────────────────────
# Based on the profile, what Point of View could resonate?
hypotheses:
- hypothesis: ""
business_driver: "" # link to strategy.published_goals
pillar: "" # strategic / financial / business_ops / it_ops
confidence: "" # high / medium / low
evidence: "" # what supports this hypothesis?
risks: "" # what could invalidate it?

174
templates/discovery-questionnaire.yaml Normal file
View File

@@ -0,0 +1,174 @@
# ═══════════════════════════════════════════════════════════════
# ECAL Discovery Questionnaire
# ═══════════════════════════════════════════════════════════════
# Source: ECAL 3.1 - Current Step (Design Phase)
# Purpose: Structured collection of customer IT landscape info
# Usage: Send to customer pre-workshop or fill collaboratively
# ═══════════════════════════════════════════════════════════════
metadata:
customer: ""
engagement: ""
date: ""
completed_by: ""
version: "1.0"
# ───────────────────────────────────────────────────────────────
# 1. BUSINESS CONTEXT
# ───────────────────────────────────────────────────────────────
business_context:
industry: ""
annual_revenue: ""
employees: ""
geographies: [] # regions/countries with IT presence
business_drivers: # what is motivating this initiative?
strategic: [] # cloud strategy, digital transformation, M&A
financial: [] # cost reduction, CAPEX→OPEX, license optimization
operational: [] # efficiency, time-to-market, agility
compliance: [] # regulatory, audit, data sovereignty
urgency:
deadline: "" # hard deadline if any
trigger: "" # contract renewal, EOL, compliance, competitive
key_stakeholders:
sponsor: "" # executive sponsor name/role
technical_lead: "" # customer technical DRI
decision_makers: [] # who signs off
# ───────────────────────────────────────────────────────────────
# 2. CURRENT STATE — APPLICATIONS & SYSTEMS
# ───────────────────────────────────────────────────────────────
applications:
# Repeat this block for each application in scope
- name: ""
description: ""
business_criticality: "" # Critical / High / Medium / Low
current_platform: "" # e.g., "On-prem VMware", "AWS EC2", "bare metal"
database:
type: "" # Oracle, PostgreSQL, MySQL, SQL Server, etc.
version: ""
size_gb: ""
instance_count: ""
ha_current: "" # RAC, Data Guard, none, etc.
dr_current: "" # cross-site DG, backup only, none
compute:
type: "" # VM, bare metal, container
cpu_cores: ""
memory_gb: ""
os: ""
storage:
type: "" # SAN, NAS, local, S3
capacity_gb: ""
iops_required: ""
integrations:
- target: "" # what does it integrate with?
method: "" # API, DB link, file transfer, messaging
frequency: "" # real-time, batch daily, batch weekly
data_volume: "" # GB/day or records/day
users:
concurrent: ""
total: ""
locations: [] # where are users located?
sla:
uptime_requirement: "" # e.g., 99.9%, 99.99%
rto: "" # recovery time objective
rpo: "" # recovery point objective
compliance:
frameworks: [] # PCI-DSS, HIPAA, GDPR, SOX, banking regs
data_classification: "" # public, internal, confidential, restricted
data_residency: "" # must stay in specific country/region?
migration_preference: "" # lift-and-shift, re-platform, re-architect, retain
notes: ""
# ───────────────────────────────────────────────────────────────
# 3. CURRENT STATE — INFRASTRUCTURE
# ───────────────────────────────────────────────────────────────
infrastructure:
data_centers:
- location: ""
type: "" # owned, colo, cloud
provider: "" # if cloud: AWS, Azure, GCP, OCI
role: "" # primary, DR, dev/test
networking:
wan_type: "" # MPLS, SD-WAN, internet VPN
bandwidth_to_cloud: "" # if already connected
latency_requirements: "" # between sites, to users
dns_provider: ""
load_balancing: "" # F5, Citrix, cloud-native
identity:
idp: "" # Active Directory, Okta, Azure AD, Oracle IAM
sso: "" # yes/no, which protocol (SAML, OIDC)
mfa: "" # yes/no, which product
security:
firewall: "" # product/vendor
waf: "" # yes/no, product
siem: "" # product (Splunk, QRadar, etc.)
encryption_at_rest: "" # yes/no, method
encryption_in_transit: "" # yes/no, method
key_management: "" # HSM, KMS, manual
monitoring:
tools: [] # e.g., [Datadog, Nagios, OEM, CloudWatch]
alerting: "" # PagerDuty, email, custom
log_aggregation: "" # ELK, Splunk, OCI Logging
# ───────────────────────────────────────────────────────────────
# 4. CURRENT STATE — PEOPLE & PROCESS
# ───────────────────────────────────────────────────────────────
people_and_process:
team:
total_it_staff: ""
dba_count: ""
cloud_engineers: ""
devops_engineers: ""
security_staff: ""
cloud_experience: "" # none, basic, intermediate, advanced
oracle_experience: "" # none, basic, intermediate, advanced
certifications: [] # OCI, AWS, Azure, etc.
operations:
change_management: "" # CAB, lightweight approval, none
deployment_process: "" # manual, CI/CD, IaC
iac_tools: [] # Terraform, Ansible, CloudFormation, ARM
ci_cd_tools: [] # Jenkins, GitLab CI, GitHub Actions, OCI DevOps
patching_cadence: "" # monthly, quarterly, ad-hoc
backup_testing: "" # frequency of restore tests
incident_process: "" # NOC, on-call, outsourced
itsm_tool: "" # ServiceNow, Jira, BMC
managed_services:
current_provider: "" # self-managed, outsourced to whom?
preference: "" # self-managed, co-managed, fully managed
budget_for_managed: "" # yes/no, approximate
# ───────────────────────────────────────────────────────────────
# 5. CONSTRAINTS & ASSUMPTIONS
# ───────────────────────────────────────────────────────────────
constraints:
budget:
capex_available: ""
opex_monthly_target: ""
existing_oracle_licenses: "" # ULA, PULA, NUP, Processor
byol_eligible: "" # yes/no, which products
timeline:
project_start: ""
hard_deadline: ""
phased_approach_ok: "" # yes/no
technical:
- "" # e.g., "Must keep Oracle RAC", "Cannot change app code"
regulatory:
- "" # e.g., "Data must stay in EU", "FCA audit requirements"
organizational:
- "" # e.g., "Change freeze Dec-Jan", "Union approval needed"
# ───────────────────────────────────────────────────────────────
# 6. PRIORITIZATION (fill after workshop)
# ───────────────────────────────────────────────────────────────
prioritization:
# Score each application 1-5 on these criteria
# Then sort by weighted score to determine migration order
criteria:
- { name: "Business Criticality", weight: 0.25 }
- { name: "Functional Fit (cloud-ready)", weight: 0.20 }
- { name: "Transformation Potential", weight: 0.20 }
- { name: "Technology Fit (OCI alignment)", weight: 0.20 }
- { name: "Risk Profile (migration risk)", weight: 0.15 } # inverted: lower risk = higher score
scores: []
# Example:
# - { app: "Core ERP", criticality: 5, functional_fit: 3, transformation: 4, tech_fit: 4, risk: 2, weighted: 3.7 }

192
templates/go-live-checklist.yaml Normal file
View File

@@ -0,0 +1,192 @@
# Go-Live Checklist Template — DELIVER/Operate Phase
# Pre-go-live verification items. Check ALL before cutover.
go_live_checklist:
customer_name: ""
project_name: ""
target_go_live_date: ""
architect: ""
# --- Infrastructure Readiness ---
infrastructure:
- item: "All OCI resources provisioned per architecture design"
status: "" # done, in_progress, blocked, not_applicable
owner: ""
notes: ""
- item: "Network connectivity verified (FastConnect/VPN throughput and latency)"
status: ""
owner: ""
notes: ""
- item: "DNS cutover plan documented and tested"
status: ""
owner: ""
notes: ""
- item: "SSL/TLS certificates provisioned and configured"
status: ""
owner: ""
notes: ""
- item: "Non-production environments operational"
status: ""
owner: ""
notes: ""
# --- Security Readiness ---
security:
- item: "IAM policies configured per least-privilege design"
status: ""
owner: ""
notes: ""
- item: "Network security (NSGs, WAF, Bastion) configured and tested"
status: ""
owner: ""
notes: ""
- item: "Encryption at rest and in transit verified"
status: ""
owner: ""
notes: ""
- item: "Cloud Guard enabled with appropriate recipes"
status: ""
owner: ""
notes: ""
- item: "Audit logging enabled and retention configured"
status: ""
owner: ""
notes: ""
- item: "Compliance controls verified (PCI/HIPAA/SOC2 if applicable)"
status: ""
owner: ""
notes: ""
# --- Data Readiness ---
data:
- item: "Data migration completed and validated"
status: ""
owner: ""
notes: ""
- item: "Data integrity checks passed (row counts, checksums)"
status: ""
owner: ""
notes: ""
- item: "Replication lag within acceptable RPO"
status: ""
owner: ""
notes: ""
- item: "Backup and recovery tested (full restore to point-in-time)"
status: ""
owner: ""
notes: ""
# --- Application Readiness ---
application:
- item: "Application functional testing passed in OCI environment"
status: ""
owner: ""
notes: ""
- item: "Performance testing completed (meets P95 latency targets)"
status: ""
owner: ""
notes: ""
- item: "Connection strings and endpoints updated"
status: ""
owner: ""
notes: ""
- item: "Rollback procedure documented and tested"
status: ""
owner: ""
notes: ""
# --- Monitoring & Operations Readiness ---
operations:
- item: "Monitoring dashboards configured and validated"
status: ""
owner: ""
notes: ""
- item: "Alerting rules active and notification channels verified"
status: ""
owner: ""
notes: ""
- item: "Runbooks documented for common failure scenarios"
status: ""
owner: ""
notes: ""
- item: "On-call rotation established"
status: ""
owner: ""
notes: ""
- item: "Ops team trained on OCI console and tools"
status: ""
owner: ""
notes: ""
# --- HA/DR Readiness ---
ha_dr:
- item: "HA failover tested (automatic recovery verified)"
status: ""
owner: ""
notes: ""
- item: "DR switchover tested (meets RTO/RPO targets)"
status: ""
owner: ""
notes: ""
- item: "Auto-scaling tested under load"
status: ""
owner: ""
notes: ""
# --- Cutover Plan ---
cutover:
- item: "Cutover window communicated to all stakeholders"
status: ""
owner: ""
notes: ""
- item: "Cutover runbook reviewed and rehearsed"
status: ""
owner: ""
notes: ""
- item: "Rollback criteria defined (when to roll back)"
status: ""
owner: ""
notes: ""
- item: "War room / communication channel established for go-live"
status: ""
owner: ""
notes: ""
# --- Sign-off ---
sign_off:
- role: "Solutions Architect"
name: ""
approved: false
date: ""
- role: "Customer Technical Lead"
name: ""
approved: false
date: ""
- role: "Customer Business Sponsor"
name: ""
approved: false
date: ""

104
templates/handover-document.yaml Normal file
View File

@@ -0,0 +1,104 @@
# Handover Document Template — DELIVER/Adopt Phase
# Single-source summary for implementation team handover
handover:
# --- Header ---
customer_name: ""
project_name: ""
date: ""
architect: ""
implementation_partner: "" # Oracle Consulting, partner name, customer self-implement
# --- Value Story Summary ---
business_driver: ""
desired_outcome: ""
success_criteria_reference: "" # pointer to success-criteria artifact
# --- Scope ---
scope:
in_scope:
- ""
out_of_scope:
- ""
mvp_scope:
- "" # What ships in Phase 1
# --- Architecture Summary ---
architecture:
diagram_reference: "" # path to .drawio file
key_decisions:
- decision: ""
rationale: ""
adr_reference: "" # e.g., "ADR-001"
services_used:
- service: ""
purpose: ""
configuration: "" # e.g., "ADB-S, 4 base OCPU, auto-scaling to 12"
# --- Environment Strategy ---
environments:
- name: "Production"
region: ""
sizing: "" # e.g., "Full sizing per proposal"
- name: "UAT/Staging"
region: ""
sizing: "" # e.g., "50% of production"
- name: "Development"
region: ""
sizing: "" # e.g., "25% of production"
# --- Migration Plan Summary ---
migration:
strategy: "" # e.g., "Phased migration over 8 weeks"
phases:
- phase: 1
description: ""
duration: ""
components: []
dependencies: []
- phase: 2
description: ""
duration: ""
components: []
dependencies: []
tooling: [] # e.g., [DMS, GoldenGate, Data Pump]
rollback_plan: ""
# --- Open Items ---
open_items:
- item: ""
owner: ""
due_date: ""
impact_if_unresolved: "" # e.g., "Cannot proceed with Phase 2"
# --- Assumptions to Verify ---
assumptions:
- assumption: "" # e.g., "AWR data represents typical workload"
status: "" # confirmed, pending, at_risk
verification_method: ""
# --- Risk Register Reference ---
top_risks:
- risk: ""
severity: "" # critical, high, medium
mitigation: ""
owner: ""
# --- Contacts ---
contacts:
oracle:
- role: ""
name: ""
availability: "" # e.g., "Available for questions during implementation"
customer:
- role: ""
name: ""
partner:
- role: ""
name: ""
# --- Governance ---
governance:
steering_cadence: "" # e.g., "Bi-weekly"
escalation_path: ""
change_control: "" # e.g., "Changes via JIRA, approved by steering committee"

79
templates/joint-engagement-plan.yaml Normal file
View File

@@ -0,0 +1,79 @@
# Joint Engagement Plan Template — DEFINE Phase
# Scopes the DESIGN phase: timebox, resources, milestones, success criteria
engagement_plan:
# --- Header ---
customer_name: ""
project_name: ""
date: ""
architect: ""
engagement_tier: "" # small, standard, complex
# --- Value Story Reference ---
value_story_summary: "" # 1-2 sentence recap of the hypothesis
business_driver: ""
# --- Scope ---
scope:
in_scope:
- "" # e.g., "3 Oracle OLTP databases (PROD, UAT, DR)"
out_of_scope:
- "" # e.g., "Reporting data warehouse (Phase 2)"
assumptions:
- "" # e.g., "AWR reports will be provided within 1 week"
# --- Timeline ---
timeline:
design_start: "" # e.g., "2026-03-20"
design_end: "" # e.g., "2026-04-17"
proposal_date: "" # When the solution proposal will be presented
decision_date: "" # When the customer commits (or iterates)
# --- Milestones ---
milestones:
- name: "Current State Review"
date: ""
deliverable: "Validated Workload Profile"
attendees: []
- name: "Architecture Workshop"
date: ""
deliverable: "Draft architecture diagram + key decisions"
attendees: []
- name: "Solution Proposal"
date: ""
deliverable: "Complete proposal deck + cost estimate"
attendees: []
# --- Resources ---
resources:
oracle_team:
- role: "Solutions Architect"
name: ""
commitment: "" # e.g., "40% for 4 weeks"
- role: "" # e.g., "Database Specialist", "Security Architect"
name: ""
commitment: ""
customer_team:
- role: "" # e.g., "Technical Lead", "DBA", "Security"
name: ""
commitment: "" # e.g., "Available for workshops + async questions"
# --- Success Criteria for DESIGN Phase ---
design_success_criteria:
- "Architecture validated against Well-Architected Framework"
- "Cost estimate within customer's budget range"
- "Migration plan achievable within stated timeline"
- "" # Add engagement-specific criteria
# --- Risks to the Engagement ---
engagement_risks:
- risk: "" # e.g., "Customer may not provide AWR data in time"
impact: "" # high, medium, low
mitigation: "" # e.g., "Use sizing estimates with safety margin, flag assumptions"
# --- Artifacts to Produce ---
# Auto-populated based on engagement_tier — see docs/engagement-tiers.md
planned_artifacts: []

53
templates/lessons-learned.yaml Normal file
View File

@@ -0,0 +1,53 @@
# Lessons Learned Template — DELIVER/Improve Phase
# Captures what worked, what didn't, and improvements for future engagements
lessons_learned:
customer_name: ""
project_name: ""
date: ""
architect: ""
engagement_tier: "" # small, standard, complex
# --- What Worked Well ---
# Practices, tools, or decisions to repeat in future engagements
successes:
- area: "" # e.g., "Architecture Design"
description: "" # e.g., "ADB-S auto-scaling eliminated capacity planning complexity"
reusable: true # Should this be captured in KB?
kb_update: "" # e.g., "Add to kb/field-knowledge/ as positive finding"
# --- What Didn't Work ---
# Issues encountered and their root cause
issues:
- area: "" # e.g., "Migration"
description: "" # e.g., "GoldenGate initial load took 3x longer than estimated"
root_cause: "" # e.g., "Network bandwidth between on-prem and OCI was only 100 Mbps"
resolution: "" # e.g., "Used Data Pump for initial load, GoldenGate for CDC only"
kb_update: "" # e.g., "Update kb/field-findings/ with bandwidth sizing guidance"
# --- Process Improvements ---
# Suggestions for the ECAL/skill process itself
process_improvements:
- phase: "" # define, design, deliver
suggestion: "" # e.g., "Add network bandwidth assessment to discovery checklist"
priority: "" # high, medium, low
# --- Template/Tool Improvements ---
tool_improvements:
- artifact: "" # e.g., "workload-profile.yaml"
suggestion: "" # e.g., "Add field for current network bandwidth between sites"
# --- Customer Feedback ---
customer_feedback:
overall_satisfaction: "" # excellent, good, acceptable, needs_improvement
positive: [] # e.g., ["Fast turnaround", "Clear cost breakdown"]
negative: [] # e.g., ["Wanted more detail on security controls"]
would_engage_again: "" # yes, maybe, no
# --- Customer Success Story ---
# If applicable, capture for internal sharing
success_story:
publishable: false
headline: "" # e.g., "Financial Services company reduces DB costs 60% with ADB-S"
summary: "" # 2-3 sentence summary
metrics: [] # e.g., ["60% cost reduction", "99.995% availability", "Zero downtime migration"]

109
templates/operations-model.yaml Normal file
View File

@@ -0,0 +1,109 @@
# Operations Model Template — DESIGN Phase
# Defines how the solution will be operated day-to-day after go-live
operations_model:
# --- Header ---
customer_name: ""
project_name: ""
date: ""
architect: ""
# --- Operational Responsibility ---
# Who operates what?
responsibility_model:
type: "" # self_managed, co_managed, fully_managed
oracle_managed: [] # e.g., ["ADB-S infrastructure", "Exadata patching"]
customer_managed: [] # e.g., ["Application deployment", "Schema changes", "User management"]
partner_managed: [] # e.g., ["24x7 NOC monitoring"]
# --- Monitoring & Alerting ---
monitoring:
platform: "" # OCI Monitoring, OCI Logging Analytics, Datadog, Grafana, etc.
dashboards:
- name: "" # e.g., "Infrastructure Health"
scope: "" # e.g., "Compute, networking, storage metrics"
- name: ""
scope: ""
alerting:
channels: [] # e.g., [email, PagerDuty, Slack, OCI Notifications]
critical_alerts:
- condition: "" # e.g., "CPU > 90% for 5 min"
action: "" # e.g., "Page on-call DBA"
- condition: ""
action: ""
log_retention: "" # e.g., "90 days hot, 1 year archive"
# --- Patching & Maintenance ---
patching:
os_patching:
frequency: "" # e.g., "Monthly, third Saturday"
method: "" # e.g., "OS Management Service, rolling updates"
downtime: "" # e.g., "Zero downtime (rolling)"
database_patching:
frequency: "" # e.g., "Quarterly RU"
method: "" # e.g., "ADB-S auto-patching with maintenance window"
downtime: "" # e.g., "< 2 min with auto-patching"
application_patching:
frequency: ""
method: ""
# --- Backup & Recovery ---
backup:
strategy:
- component: "" # e.g., "ADB-S"
method: "" # e.g., "Automatic daily backup to Object Storage"
retention: "" # e.g., "60 days"
rpo: "" # e.g., "< 1 hour (continuous archive log backup)"
- component: ""
method: ""
retention: ""
rpo: ""
recovery_testing:
frequency: "" # e.g., "Quarterly"
last_test: ""
next_test: ""
# --- Incident Response ---
incident_response:
severity_levels:
- level: "P1 — Critical"
definition: "" # e.g., "Production down, data loss risk"
response_time: "" # e.g., "15 minutes"
escalation: "" # e.g., "On-call DBA → SA → Oracle Support"
- level: "P2 — High"
definition: ""
response_time: ""
escalation: ""
- level: "P3 — Medium"
definition: ""
response_time: ""
escalation: ""
runbooks:
- scenario: "" # e.g., "ADB-S failover"
location: "" # e.g., "Confluence/wiki link"
- scenario: ""
location: ""
# --- Capacity Management ---
capacity:
review_cadence: "" # e.g., "Monthly"
scaling_triggers:
- metric: "" # e.g., "CPU utilization"
threshold: "" # e.g., "> 70% sustained for 1 hour"
action: "" # e.g., "Auto-scale OCPUs (ADB-S) or add instance (OKE HPA)"
growth_forecast: "" # e.g., "15% annual data growth, 10% compute growth"
# --- Security Operations ---
security_ops:
vulnerability_scanning: "" # e.g., "Cloud Guard + quarterly pen test"
access_review_cadence: "" # e.g., "Quarterly IAM review"
key_rotation: "" # e.g., "Annual for Vault master keys"
compliance_audit_schedule: "" # e.g., "Annual SOC2 Type II"
# --- Cost Management ---
cost_management:
budget_alerts:
- threshold: "" # e.g., "80% of monthly budget"
action: "" # e.g., "Email to finance + architect"
optimization_cadence: "" # e.g., "Monthly review of unused resources"
reserved_capacity_review: "" # e.g., "Annual review of reserved vs. PAYG"

173
templates/scorecard.yaml Normal file
View File

@@ -0,0 +1,173 @@
# OCI Well-Architected Scorecard — Output Template
# Generated automatically by the Deal Accelerator after architecture composition
well_architected_scorecard:
# Overall assessment
overall_status: "" # PASS | PASS_WITH_RECOMMENDATIONS | GAPS_IDENTIFIED
generated_date: ""
architecture_name: ""
customer: ""
# Summary metrics
summary:
total_checks: 0
total_passed: 0
total_gaps: 0
high_severity_gaps: 0
medium_severity_gaps: 0
low_severity_gaps: 0
# Per-pillar results
pillars:
security_compliance:
status: "" # PASS | PASS_WITH_RECOMMENDATIONS | GAPS_IDENTIFIED | NOT_APPLICABLE
checks_passed: 0
checks_total: 0
categories:
identity_access:
passed: 0
total: 0
gaps: []
resource_isolation:
passed: 0
total: 0
gaps: []
database_security:
passed: 0
total: 0
gaps: []
data_protection:
passed: 0
total: 0
gaps: []
network_security:
passed: 0
total: 0
gaps: []
monitoring_audit:
passed: 0
total: 0
gaps: []
reliability_resilience:
status: ""
checks_passed: 0
checks_total: 0
categories:
scalability:
passed: 0
total: 0
gaps: []
fault_tolerant_networking:
passed: 0
total: 0
gaps: []
data_backup:
passed: 0
total: 0
gaps: []
data_replication:
passed: 0
total: 0
gaps: []
disaster_recovery:
passed: 0
total: 0
gaps: []
performance_cost:
status: ""
checks_passed: 0
checks_total: 0
categories:
compute_sizing:
passed: 0
total: 0
gaps: []
storage_strategy:
passed: 0
total: 0
gaps: []
network_tuning:
passed: 0
total: 0
gaps: []
cost_management:
passed: 0
total: 0
gaps: []
operational_efficiency:
status: ""
checks_passed: 0
checks_total: 0
categories:
deployment_strategy:
passed: 0
total: 0
gaps: []
workload_monitoring:
passed: 0
total: 0
gaps: []
os_management:
passed: 0
total: 0
gaps: []
operations_support:
passed: 0
total: 0
gaps: []
distributed_cloud:
status: "" # Often NOT_APPLICABLE
reason: "" # e.g., "Single public cloud deployment"
checks_passed: 0
checks_total: 0
categories:
dc_deployment_strategy:
passed: 0
total: 0
gaps: []
dc_integration:
passed: 0
total: 0
gaps: []
dc_compliance:
passed: 0
total: 0
gaps: []
dc_operations:
passed: 0
total: 0
gaps: []
# Gap detail format
# Each gap entry follows this structure:
# - check_id: "SEC-IAM-001"
# area: "Identity & Access"
# finding: "Description of what's missing"
# severity: "HIGH | MEDIUM | LOW"
# recommendation: "What to do about it"
# wa_reference: "URL or doc reference"
# Prioritized action items (generated from gaps, sorted by severity)
action_items:
high_priority: []
# - check_id: ""
# pillar: ""
# finding: ""
# recommendation: ""
# effort: "" # quick_win, moderate, significant
medium_priority: []
low_priority: []
# References
references:
framework: "https://docs.oracle.com/en/solutions/oci-best-practices/index.html"
security: "https://docs.oracle.com/en/solutions/oci-best-practices/effective-strategies-security-and-compliance1.html"
reliability: "https://docs.oracle.com/en/solutions/oci-best-practices/reliable-and-resilient-cloud-topology-practices1.html"
performance: "https://docs.oracle.com/en/solutions/oci-best-practices/index.html"
operations: "https://docs.oracle.com/en/solutions/oci-best-practices/best-practices-operating-cloud-deployments-efficiency.html"
distributed: "https://docs.oracle.com/en/solutions/oci-best-practices/effective-strategies-distributed-cloud-implementation1.html"

90
templates/strategy-map.yaml Normal file
View File

@@ -0,0 +1,90 @@
# ═══════════════════════════════════════════════════════════════
# ECAL Strategy Map Template
# ═══════════════════════════════════════════════════════════════
# Source: ECAL 3.1 - Ideate Step (Define Phase)
# Purpose: Map customer goals → strategies → capabilities → enablers
# Note: Internal document; key info goes into customer-facing PoV/Value Story
# "Arguably one of the most important ECAL artifacts" — ECAL 3.1
# ═══════════════════════════════════════════════════════════════
metadata:
customer: ""
date: ""
version: "1.0"
status: "draft"
# ───────────────────────────────────────────────────────────────
# LAYER 1: BUSINESS GOALS
# What the customer wants to achieve (from annual reports, CxO statements)
# ───────────────────────────────────────────────────────────────
goals:
- id: "G1"
goal: ""
# Example: "Reduce operating costs by 15% over 3 years"
source: "" # annual report, CEO keynote, customer statement
timeframe: ""
measurable_target: ""
# ───────────────────────────────────────────────────────────────
# LAYER 2: STRATEGIES
# How the customer plans to achieve each goal
# ───────────────────────────────────────────────────────────────
strategies:
- id: "S1"
strategy: ""
# Example: "Consolidate data center footprint from 4 to 1"
supports_goal: "G1" # link to goal
owner: "" # who owns this strategy in the customer org?
# ───────────────────────────────────────────────────────────────
# LAYER 3: CAPABILITIES NEEDED
# What capabilities are required to execute each strategy
# ───────────────────────────────────────────────────────────────
capabilities:
- id: "C1"
capability: ""
# Example: "Cloud-based database platform with managed operations"
supports_strategy: "S1"
current_state: "" # how is this capability met today?
gap: "" # what's missing?
# ───────────────────────────────────────────────────────────────
# LAYER 4: ENABLERS (Oracle Products / Solutions)
# What Oracle can provide to fill the capability gaps
# ───────────────────────────────────────────────────────────────
enablers:
- id: "E1"
enabler: ""
# Example: "Autonomous Database on Exadata Cloud@Customer"
provides_capability: "C1"
oci_services: [] # specific OCI services
value_proposition: "" # why this enabler for this capability?
competitive_advantage: "" # why Oracle vs. alternatives?
# ───────────────────────────────────────────────────────────────
# LINKAGE SUMMARY
# Quick view: Goal → Strategy → Capability → Enabler
# ───────────────────────────────────────────────────────────────
linkage:
- goal: "G1"
strategy: "S1"
capability: "C1"
enabler: "E1"
point_of_view: "" # one-sentence PoV derived from this chain
# Example: "By consolidating 3500 databases onto ADB on ExaCC,
# [Customer] achieves 40% OpEx reduction while meeting
# EBA data residency requirements"
# ───────────────────────────────────────────────────────────────
# SMART EVALUATION OF EACH POINT OF VIEW
# ───────────────────────────────────────────────────────────────
pov_evaluation:
- pov_id: 1
linkage_ref: "G1→S1→C1→E1"
specific: "" # clearly defined scope?
measurable: "" # quantifiable outcome?
attainable: "" # technically feasible? (check feature matrix)
relevant: "" # tied to customer's stated goals?
time_based: "" # achievable timeline?
overall_score: "" # strong / moderate / weak
proceed: "" # yes / iterate / abandon

61
templates/success-criteria.yaml Normal file
View File

@@ -0,0 +1,61 @@
# Success Criteria Template — DELIVER/Operate Phase
# Quantitative metrics tied to the Value Story, measured post go-live
success_criteria:
customer_name: ""
project_name: ""
date: ""
architect: ""
value_story_reference: "" # Link back to the original value hypothesis
# --- Metrics ---
# Each metric should be SMART and traceable to the Value Story
metrics:
- name: "" # e.g., "Database Response Time"
category: "" # performance, availability, cost, operations, business
target: "" # e.g., "P95 < 15ms"
baseline: "" # e.g., "P95 = 45ms (current on-prem)"
measurement_method: "" # e.g., "OCI Monitoring — DB Performance Hub"
measurement_cadence: "" # e.g., "Daily automated, weekly review"
owner: "" # Who tracks this metric
- name: "" # e.g., "Monthly Infrastructure Cost"
category: ""
target: "" # e.g., "< $25,000/month"
baseline: "" # e.g., "$40,000/month (current Exadata lease + support)"
measurement_method: "" # e.g., "OCI Cost Analysis"
measurement_cadence: ""
owner: ""
- name: "" # e.g., "Unplanned Downtime"
category: ""
target: "" # e.g., "Zero in first 90 days"
baseline: "" # e.g., "4 hours/month average"
measurement_method: ""
measurement_cadence: ""
owner: ""
# --- Review Schedule ---
reviews:
- milestone: "30-day review"
date: ""
focus: "Stability, performance baselines, early issues"
attendees: []
- milestone: "60-day review"
date: ""
focus: "Cost tracking, operational maturity, optimization opportunities"
attendees: []
- milestone: "90-day review"
date: ""
focus: "Value realization assessment, next phase planning"
attendees: []
# --- Value Realization ---
value_realization:
hypothesis_validated: "" # yes, partially, no
actual_vs_target: "" # Summary of metrics performance
unexpected_benefits: [] # e.g., ["DBA team freed up for development work"]
unexpected_challenges: [] # e.g., ["Application connection pooling needed tuning"]
next_hypothesis: "" # What to tackle next? Returns to DEFINE phase

54
templates/value-story.yaml Normal file
View File

@@ -0,0 +1,54 @@
# Value Story Template — DEFINE Phase
# Captures the value hypothesis linking business drivers to OCI outcomes
value_story:
# --- Customer Context ---
customer_name: ""
industry: ""
engagement_date: ""
architect: ""
# --- Business Driver ---
# What is pushing the customer to act NOW?
business_driver:
primary: "" # cost_reduction, modernization, performance, compliance, hardware_eol, contract_expiry, consolidation, competitive_pressure
urgency: "" # Why now? e.g., "Hardware EOL in 6 months", "PCI audit in Q3"
quantified_impact: "" # e.g., "$2M/year in legacy maintenance", "4h monthly downtime"
# --- Current Pain ---
# What specific problem does the customer experience?
current_pain:
summary: "" # 1-2 sentences describing the problem in customer's terms
affected_stakeholders: [] # e.g., [CTO, DBA team, end users, compliance officer]
business_cost: "" # Quantified cost of inaction: dollars, hours, risk
# --- Value Hypothesis ---
# "If we [action], the customer achieves [outcome]"
hypothesis:
action: "" # e.g., "Migrate 3 Oracle databases from on-prem Exadata to ADB-S"
outcome: "" # e.g., "60% reduction in DB admin effort, 99.995% availability, PCI compliance"
evidence: "" # What supports this? e.g., "ADB-S automates patching, backups, tuning"
# --- SMART Validation ---
smart:
specific: "" # What exactly will be done?
measurable: "" # How will success be measured?
attainable: "" # Is this technically feasible? (reference feature matrix, field findings)
relevant: "" # How does this connect to the business driver?
time_based: "" # When will this be delivered?
# --- Competitive Context ---
competitive:
incumbent: "" # aws, azure, gcp, on_prem, none
why_oci: [] # e.g., ["BYOL cost advantage", "ADB-S unique capabilities", "FastConnect latency"]
honest_gaps: [] # e.g., ["Smaller marketplace", "Fewer regions in LATAM"]
# --- Confidence Assessment ---
confidence:
data_quality: "" # high (AWR/metrics available), medium (estimates), low (guesses)
assumptions: [] # List key assumptions made
gaps_to_fill: [] # What information is still missing?
# --- Next Step ---
recommendation: "" # proceed_to_design, iterate_hypothesis, insufficient_data
next_action: "" # e.g., "Schedule design workshop", "Request AWR reports"

131
templates/workload-profile.yaml Normal file
View File

@@ -0,0 +1,131 @@
# OCI Deal Accelerator — Workload Profile Template
# Fill this out during the Discovery phase to drive architecture composition and WA validation
workload_profile:
# --- Business Context ---
business_context:
customer_name: ""
industry: "" # e.g., financial_services, healthcare, retail, manufacturing, public_sector
engagement_type: "" # migration, greenfield, expansion, modernization
timeline: "" # e.g., "6 months", "Q3 2026"
budget_range: "" # e.g., "$50K-100K/month"
competitive_situation: "" # aws_incumbent, azure_incumbent, on_prem_only, multi_cloud
oracle_relationship: "" # existing_ula, existing_licenses, new_customer
# --- Compliance & Regulatory ---
compliance:
regulatory_frameworks: [] # PCI-DSS, HIPAA, SOC2, GDPR, FedRAMP, etc.
data_residency_required: false
data_residency_regions: [] # e.g., [us-ashburn-1, eu-frankfurt-1]
sovereign_requirements: false
audit_requirements: "" # e.g., "annual SOC2 audit", "quarterly PCI scan"
# --- Application Portfolio ---
applications:
- name: ""
type: "" # database, web_app, api, batch, streaming, analytics
current_platform: "" # on_prem, aws, azure, gcp
technology_stack: [] # e.g., [java, spring_boot, oracle_db_19c]
criticality: "" # mission_critical, business_critical, standard, dev_test
users: "" # e.g., "5000 concurrent", "internal only"
data_volume: "" # e.g., "2TB", "500GB growing 10%/year"
# --- Performance Requirements ---
performance:
compute_iops: "" # e.g., "50K IOPS sustained"
storage_iops: ""
network_throughput: "" # e.g., "10 Gbps"
latency_requirements: "" # e.g., "< 5ms database response"
peak_patterns: "" # steady, daily_peaks, seasonal, unpredictable
# --- Resilience Requirements ---
resilience:
rto: "" # e.g., "1 hour", "15 minutes"
rpo: "" # e.g., "0 (zero data loss)", "1 hour"
availability_target: "" # e.g., "99.95%", "99.99%"
dr_required: false
dr_type: "" # active_active, active_passive, pilot_light, backup_restore
backup_retention: "" # e.g., "30 days", "7 years for compliance"
# --- Connectivity ---
connectivity:
type: "" # fastconnect, vpn, internet, hybrid
bandwidth: "" # e.g., "10 Gbps"
on_prem_integration: false
multi_cloud_integration: false
existing_network: "" # e.g., "MPLS to 3 data centers"
# --- Operational Maturity ---
operations:
iac_experience: "" # none, basic, advanced
cloud_experience: "" # none, basic_aws, advanced_multi_cloud
team_size: "" # e.g., "3 cloud engineers"
existing_tools: [] # e.g., [terraform, ansible, jenkins, datadog]
managed_services_preference: "" # self_managed, managed, fully_managed
# --- People (ECAL Current State: who operates the solution?) ---
people:
team_size: "" # e.g., "5 IT staff"
roles: [] # e.g., [dba, cloud_engineer, devops, security]
skill_gaps: [] # e.g., [kubernetes, terraform, oci_console]
managed_services_preference: "" # self_managed, co_managed, fully_managed
change_readiness: "" # resistant, cautious, open, eager
# --- Process (ECAL Current State: how do they operate today?) ---
process:
deployment_process: "" # manual, scripted, ci_cd_basic, ci_cd_advanced, gitops
change_management: "" # none, informal, cab_based, automated
incident_response: "" # none, ad_hoc, on_call_rotation, noc_24x7, outsourced
backup_testing_frequency: "" # never, annually, quarterly, monthly
# --- Decision Drivers ---
decision_drivers:
technical:
- "" # e.g., "Need Oracle RAC equivalent in cloud"
commercial:
- "" # e.g., "Existing ULA covers DB licenses"
political:
primary_audience: "" # cloud_architect, security_architect, enterprise_architect, cto, finance
decision_maker: ""
influencers: []
concerns: [] # e.g., ["vendor lock-in", "migration risk", "cost predictability"]
# --- Derived Flags (auto-populated by validation engine) ---
flags:
has_databases: false
has_autonomous_database: false
has_production_databases: false
has_compute_instances: false
has_production_compute: false
has_block_volumes: false
has_object_storage: false
has_critical_data_in_object_storage: false
has_critical_object_storage: false
has_large_object_storage: false
has_load_balancers: false
has_internet_facing_services: false
has_fastconnect: false
has_drg: false
has_variable_workloads: false
has_critical_workloads: false
has_critical_data: false
has_application_workloads: false
has_production_applications: false
has_production_workloads: false
has_auto_scaling: false
has_oracle_licensed_services: false
has_stable_production_workloads: false
has_dev_test_environments: false
has_multiple_environments: false
has_sensitive_workloads: false
multi_tenant: false
multi_environment: false
enterprise_customer: false
hub_spoke_topology: false
requires_dr: false
multi_region: false
hybrid_cloud: false
multicloud: false
has_data_residency_requirements: false
has_sovereign_requirements: false
distributed_cloud_applicable: false