# MODIFIABLE REQUEST FOR PROPOSALS (RFP) TEMPLATE
## Project Title: Oracle to PostgreSQL & AlloyDB Migration vs. Oracle SE2 / ODA License Right-Sizing
- **RFP Document Reference**: `VNA-RFP-012` (Companion to Solution Brief `VNA-SB-012`)
- **Issuing Organization**: `[INSERT ORGANIZATION / COMPANY NAME]`
- **Issue Date**: `[2026-10-27]`
- **Proposal Due Date**: `[INSERT DATE, e.g., +30 Calendar Days]`
- **Reference Architecture Portal**: https://oracle-to-postgresql-migration.web.app/
- **Template Attribution**: This site is designed by Viscosity.AI

---

## SECTION 1: ISSUING ORGANIZATION PROFILE & PROCUREMENT SCHEDULE (MODIFIABLE)

> **Instructions for RFP Author**: Replace all bracketed placeholders (`[...]`) below with your organization's specific dates, contacts, and environment metrics before issuing to prospective bidders.

| Procurement Milestone | Target Date / Entry (Modifiable) |
|---|---|
| Issuing Organization Name | `[Insert Legal Entity Name]` |
| Primary Procurement / Technical Contact | `[Insert Name, Title, Email]` |
| RFP Issue Date | `[2026-10-27]` |
| Vendor Written Questions Due | `[Insert Date - Week 2]` |
| Organization Responses to Vendor Q&A | `[Insert Date - Week 3]` |
| Final Vendor Proposals & Pricing Due | `[Insert Date - Week 4]` |
| Technical Architecture Demos / Oral Presentations | `[Insert Date - Week 5]` |
| Target Contract Award & Phase 0 Kickoff | `[Insert Date - Week 6]` |

### 1.1 Executive Summary & Business Objectives
`[INSERT COMPANY NAME]` ("Organization") is soliciting competitive proposals from qualified enterprise architecture and engineering firms to modernize and transition our current **Oracle Database Views, Schemas & Departmental Workloads** environment to **PostgreSQL / AlloyDB / Cloud SQL OR Right-Sized Oracle SE2 / ODA**.

Our primary business and technical objectives are:
- Organizations often attempt 'all-or-nothing' Oracle-to-PostgreSQL migrations using generic cloud-vendor contractors who underestimate Oracle-specific features: Package state variables, Autonomous Transactions (`PRAGMA AUTONOMOUS_TRANSACTION`), Global Contexts (`SYS_CONTEXT`), Advanced Queuing (`DBMS_AQ`), and complex analytical view hierarchies.
- Meanwhile, many tier-2 and tier-3 databases sitting on expensive Enterprise Edition cores actually use zero EE-only features and could be legally right-sized to Oracle Standard Edition 2 (SE2) or consolidated on an Oracle Database Appliance (ODA) without rewriting a single line of code.
- When workloads *do* move to PostgreSQL / AlloyDB / AWS Aurora, poorly translated views (`CONNECT BY`, `DECODE`, `NVL`, outer join `(+)` syntax) suffer 10x performance degradation under PostgreSQL's MVCC vacuum model.

---

## SECTION 2: CURRENT ENVIRONMENT BASELINE INVENTORY (MODIFIABLE)

Bidders must size their technical delivery plan and fixed-fee milestone pricing against the baseline inventory table below:

| Inventory Dimension | Current Baseline Count / Footprint (Modifiable) | Target Modernization SLA / Objective |
|---|---|---|
| Legacy Source Stack (`Stack X`) | Oracle Database Views, Schemas & Departmental Workloads | Full retirement / modernization |
| Target Architecture (`Stack Y`) | PostgreSQL / AlloyDB / Cloud SQL OR Right-Sized Oracle SE2 / ODA | Production-grade HA/DR & security |
| Current Oracle Enterprise Processor Licenses | `[Insert Count, e.g., 32 EE licenses]` | 100% functional parity & optimization |
| PL/SQL Packages, Triggers & Complex Views | `[Insert Count, e.g., 850 PL/SQL objects]` | Automated AST & schema uplift |
| Target Cutover Downtime Window | `[e.g., < 15 Minutes / Near-Zero Downtime]` | Rehearsed parallel run + rollback plan |
| Security, Compliance & Identity | `[e.g., SSO/MFA via Entra ID / Okta, Row-Level VPD, Audit Logs]` | Zero critical/high CVEs at Go-Live |

---

## SECTION 3: MANDATORY TECHNICAL SCOPE OF WORK & DELIVERABLES (MODIFIABLE)

The selected partner shall execute the project across four gated phases (**Phase 0: AST Discovery & Architecture Blueprint**, **Phase 1: Core Foundation & Data/Code Conversion**, **Phase 2: Integration, Runtime Filtering & UAT**, and **Phase 3: Parallel Run, Cutover & Hypercare**).

### 3.1 Core Architectural Requirements
1. **[MODIFIABLE REQUIREMENT 1]**: Phase 0 Workload & License Reality Audit: We scan `DBA_FEATURE_USAGE_STATISTICS`, PL/SQL package AST complexity, and SQL plan profiles across your fleet to segment databases into: (A) Clean candidates for PostgreSQL / AlloyDB conversion, and (B) High-complexity PL/SQL / APEX workloads where ODA Capacity-on-Demand or SE2 right-sizing delivers higher ROI.
2. **[MODIFIABLE REQUIREMENT 2]**: Automated View & SQL Dialect Refactoring: For workloads moving to PostgreSQL / AlloyDB, our AST engine rewrites Oracle legacy outer joins `(+)`, hierarchical `START WITH ... CONNECT BY` queries into ANSI recursive CTEs (`WITH RECURSIVE`), `MERGE` statements, and materialized views.
3. **[MODIFIABLE REQUIREMENT 3]**: PL/SQL Package Decomposition to Schema-Scoped PL/pgSQL: Oracle Packages are mapped to PostgreSQL schemas with session-scoped GUC variables replacing package globals and connection-pool-safe transaction handlers.
4. **[MODIFIABLE REQUIREMENT 4]**: Bi-Directional CDC & Read-Replica Offload: Using Oracle GoldenGate or SharePlex, we stream real-time changes from Oracle to PostgreSQL / AlloyDB / BigQuery to power external microservices without impacting core ERP transactions.

### 3.2 Component-Level Conversion & Deliverable Matrix
Bidders must confirm compliance with each component conversion requirement below:

| Req ID | Legacy Artifact / Baseline Workload | Required Target Architecture | Engineering Method & Acceptance Criteria | Priority (Modifiable) |
|---|---|---|---|---|
| REQ-01 | Oracle Hierarchical Queries (`CONNECT BY PRIOR`) | PostgreSQL / AlloyDB ANSI `WITH RECURSIVE` CTEs | Automated AST Query Rewrite & Cycle Detection | `[Mandatory / Optional]` |
| REQ-02 | Oracle PL/SQL Packages & Package Body State | PostgreSQL Schemas + `PL/pgSQL` Functions + Custom GUCs | State Decoupling & Procedural Transpilation | `[Mandatory / Optional]` |
| REQ-03 | Oracle `PRAGMA AUTONOMOUS_TRANSACTION` Audit Logs | PostgreSQL `dblink` / Background Worker or Outbox Pattern | Connection-Pool-Safe Asynchronous Logging | `[Mandatory / Optional]` |
| REQ-04 | High-Cost EE Databases Using Zero EE Features | Oracle Standard Edition 2 (SE2) or ODA Capacity-on-Demand | Zero-Rewrite License Reduction (60-80% TCO Drop) | `[Mandatory / Optional]` |

### 3.3 Mandatory Platform & Tooling Standards
- Viscosity Cross-Engine SQL/PLSQL AST Analyzer & `Ora2Pg` Enterprise Pipeline
- Oracle GoldenGate & Quest SharePlex for heterogeneous Oracle-to-Postgres CDC
- Google AlloyDB for PostgreSQL, Cloud SQL, and AWS Aurora PostgreSQL
- Oracle Database Appliance (ODA X11) & Oracle Standard Edition 2 (SE2) for zero-rewrite license optimization

---

## SECTION 4: VENDOR TECHNICAL Q&A QUESTIONNAIRE & SCORING RUBRIC

Bidders must provide direct, concise written responses to each question below. The Issuing Organization's evaluation committee will grade responses using the embedded benchmark criteria.

### Vendor Question 1: Why hire an Oracle-specialized engineering firm to help with an Oracle-to-PostgreSQL migration?
- **Bidder Response Requirement**: Provide a concrete architectural explanation, reference toolset, and verifiable production proof. Generic marketing statements will be scored zero.
- **Evaluation Benchmark (What High-Scoring Responses Must Demonstrate)**: PostgreSQL specialists rarely understand the subtle semantics of Oracle PL/SQL packages, optimizer hints, `SYS_CONTEXT`, and date/number implicit conversions. Because our architects know Oracle internals deeply, we spot and solve the 15% of Oracle idioms that break standard `Ora2Pg` migrations.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 2: When should we keep a workload on Oracle instead of converting to PostgreSQL?
- **Bidder Response Requirement**: Provide a concrete architectural explanation, reference toolset, and verifiable production proof. Generic marketing statements will be scored zero.
- **Evaluation Benchmark (What High-Scoring Responses Must Demonstrate)**: If a database contains 50,000+ lines of tight PL/SQL business logic or powers an Oracle APEX application, rewriting it in Postgres + React costs 5x to 10x more than consolidating it onto an Oracle Database Appliance (ODA) with Capacity-on-Demand licensing.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 3: What is included in the downloadable PDF Solution Brief?
- **Bidder Response Requirement**: Provide a concrete architectural explanation, reference toolset, and verifiable production proof. Generic marketing statements will be scored zero.
- **Evaluation Benchmark (What High-Scoring Responses Must Demonstrate)**: The PDF Solution Brief includes the Oracle-vs-PostgreSQL Internals Translation Matrix, the `DBA_FEATURE_USAGE_STATISTICS` right-sizing script, and a TCO model comparing Rewrite-to-Postgres vs. ODA Consolidation.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 4: How do you prevent report and query fan-out bloat, and how do you guarantee zero vendor lock-in?
- **Bidder Response Requirement**: Detail your methodology for clustering redundant legacy queries/reports into canonical core SQL views with runtime or AI-inference filtering, and specify customer code/data ownership upon project completion.
- **Evaluation Benchmark (What High-Scoring Responses Must Demonstrate)**: Bidder must demonstrate deterministic AST SQL clustering (collapsing 75%-90% of cloned reports into core database views with runtime predicates), 100% customer ownership of all DDL, PL/SQL, application source code, and Terraform scripts, and zero proprietary runtime lock-in.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 5: Describe your automated regression testing, parallel run, and zero-downtime cutover methodology.
- **Bidder Response Requirement**: Specify how data parity, business-rule equivalence, and rollback safety are verified prior to production cutover.
- **Evaluation Benchmark (What High-Scoring Responses Must Demonstrate)**: Bidder must provide automated row-count and cryptographic hash reconciliation, automated unit/UI test suites (e.g., utPLSQL, Playwright), and a rehearsed cutover runbook with sub-minute rollback capability.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

---

## SECTION 5: COMMERCIAL PRICING & LICENSING MATRIX (MODIFIABLE)

Bidders must complete the fixed-price milestone table below and disclose all recurring software or cloud consumption assumptions.

| Milestone / Cost Category | Deliverable & Acceptance Gate | Fixed Fee / Annual Cost (USD) | Estimated Duration (Weeks) |
|---|---|---|---|
| **Phase 0: Discovery & AST Code/Schema X-Ray** | Verified inventory, dead-code manifest, core SQL fan-out map, and final blueprint | `$[Insert]` | `[2 - 3 Weeks]` |
| **Phase 1: Target Environment & Automated Uplift** | Provisioned target stack, schema migration, and core business logic conversion | `$[Insert]` | `[4 - 8 Weeks]` |
| **Phase 2: UI, Integrations, Reporting & UAT** | Completed application/portal screens, runtime reports, AOP templates, and UAT sign-off | `$[Insert]` | `[3 - 6 Weeks]` |
| **Phase 3: Production Cutover & Hypercare** | Rehearsed cutover, reconciliation sign-off, documentation, and 30-day hypercare | `$[Insert]` | `[2 - 3 Weeks]` |
| **Optional: Annual Managed Services / Support** | 24x7 monitoring, patching, DBA performance tuning, and quarterly enhancements | `$[Insert / yr]` | `[12 Months]` |

---

## SECTION 6: PROPOSAL EVALUATION SCORECARD (MODIFIABLE)

| Evaluation Criterion | Weight (%) | Description |
|---|---|---|
| **1. Technical Architecture & Automation Tooling** | `35%` | Depth of AST automation, query fan-out rationalization, database/cloud architecture, and zero lock-in. |
| **2. Verifiable Production Experience & References** | `25%` | Proven track record delivering identical `Oracle to PostgreSQL / AlloyDB vs. SE2 Right-Sizing` engagements with measurable outcomes. |
| **3. Cutover Safety, Testing & Compliance** | `20%` | Rigor of data reconciliation, automated regression testing, security/compliance controls, and rollback safety. |
| **4. Commercial Value & Total Cost of Ownership (TCO)** | `20%` | Transparent fixed-fee milestone pricing and 3-to-5 year software/cloud licensing savings. |
| **TOTAL** | **`100%`** | |

---
*Template Reference: `VNA-RFP-012` | Companion Portal: https://oracle-to-postgresql-migration.web.app/ | This site is designed by Viscosity.AI*