# MODIFIABLE REQUEST FOR PROPOSALS (RFP) TEMPLATE
## Project Title: Oracle Forms Modernization: Convert Oracle Forms & Reports (.fmb / .rdf) to APEX 24.2
- **RFP Document Reference**: `VNA-RFP-003` (Companion to Solution Brief `VNA-SB-003`)
- **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-forms-modernization.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 Forms & Reports 6i / 10g / 11g / 12c (.fmb, .mmb, .pll, .rdf)** environment to **Oracle APEX 24.2, ORDS, PL/SQL Packages, AOP & AMP**.

Our primary business and technical objectives are:
- Running Oracle Forms 6i, 10g, 11g, or 12c requires maintaining heavyweight Oracle WebLogic Server clusters, Forms Standalone Launcher (FSAL) client configurations, and legacy Java runtimes across thousands of workstations.
- Simply running a naive 1:1 screen converter produces unusable web pages because Oracle Forms is stateful (firing WHEN-VALIDATE-ITEM and POST-QUERY triggers synchronously over persistent database sessions), whereas modern web apps are stateless.
- Hundreds of business rules are hidden inside .fmb form-level triggers and .pll attached PL/SQL libraries rather than centralized in database packages.

---

## 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 Forms & Reports 6i / 10g / 11g / 12c (.fmb, .mmb, .pll, .rdf) | Full retirement / modernization |
| Target Architecture (`Stack Y`) | Oracle APEX 24.2, ORDS, PL/SQL Packages, AOP & AMP | Production-grade HA/DR & security |
| Oracle Forms Modules (.fmb / .pll) | `[Insert Count, e.g., 300 Forms]` | 100% functional parity & optimization |
| Oracle Reports (.rdf / BI Publisher) | `[Insert Count, e.g., 160 Reports]` | Automated AST & schema uplift |
| Report Query Fan-Out Rationalization (Core SQL Only; WHERE/Filters Built at Runtime/Inference) | `[Insert Count, e.g., 80 % fan-out reduction]` | `[Target Rationalization / SLA]` |
| 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]**: Automated FMB/MMB/PLL/RDF XML & AST Analyzer: Using our dedicated FMB Conversion Tool VM and frmf2xml parser, we convert binary .fmb, .mmb, .pll, and .rdf files into structured AST repositories, cataloging every trigger, program unit, LOV, alert, and canvas.
2. **[MODIFIABLE REQUIREMENT 2]**: Trigger Rationalization & Stateful-to-Stateless Refactoring: Chatty UI triggers (POST-QUERY, WHEN-NEW-FORM-INSTANCE, KEY-NEXT-ITEM) are refactored into set-based SQL views, APEX Computations, and Dynamic Actions. Business logic in Program Units and .pll files is promoted into versioned Database PL/SQL Packages.
3. **[MODIFIABLE REQUIREMENT 3]**: Canvas & Multi-Block Modernization: Master-detail Forms blocks and stacked canvases are consolidated into clean Universal Theme 42 APEX pages using Interactive Grids, Faceted Search, and Modal Dialogs that preserve keyboard-first data entry speed for power users.
4. **[MODIFIABLE REQUIREMENT 4]**: Oracle Reports (.rdf) to AOP / BI Publisher: Legacy .rdf reports and Lexical Parameters are converted to APEX Interactive Reports for self-service slicing and APEX Office Print (AOP) or BI Publisher for pixel-perfect PDF/Excel output.
5. **[MODIFIABLE REQUIREMENT 5]**: Query Fan-Out Rationalization & Runtime/Inference Filtering: Instead of migrating cloned reports and DataWindows 1-for-1, our AST SQL parser clusters queries by their canonical core JOIN graph, builds governed Oracle 23ai views only for those core queries, and generates dynamic WHERE clauses, faceted filters, and ad-hoc report variations at runtime and via AI inference (APEX 24.2 Smart Filters & Select AI).

### 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 | Forms Base-Table Data Block (.fmb) | APEX 24.2 Interactive Grid / Form Region | Automated Block-to-Region Mapping + Optimistic Locking | `[Mandatory / Optional]` |
| REQ-02 | Attached PL/SQL Libraries (.pll) & Program Units | Database PL/SQL Packages + APEX Application Processes | Automated Package Extraction & Global Variable Refactoring | `[Mandatory / Optional]` |
| REQ-03 | WHEN-VALIDATE-ITEM / WHEN-VALIDATE-RECORD | APEX Server-Side Validations + PL/SQL Package Calls | Stateless Validation Pushdown | `[Mandatory / Optional]` |
| REQ-04 | POST-QUERY Lookup Triggers | Set-Based SQL Joins / Shared LOVs (Zero N+1 Queries) | Query Optimizer Rewrite (10x-50x Faster Grid Loads) | `[Mandatory / Optional]` |
| REQ-05 | Menu Modules (.mmb) & Role Security | APEX Navigation Menu + AMP Authorization Schemes | Centralized RBAC & SSO Integration | `[Mandatory / Optional]` |
| REQ-06 | Oracle Reports (.rdf) & After-Report Triggers | APEX Interactive Reports + APEX Office Print (AOP) | SQL Extraction + Word/Excel/PDF Template Binding | `[Mandatory / Optional]` |
| REQ-07 | Cloned Reports / Queries Differing Only by WHERE Clause or Group-By (Query Fan-Out) | Canonical Core SQL View + APEX 24.2 Runtime / AI Inference Filters | AST Join-Graph Clustering (75-90% Report Count Reduction) | `[Mandatory / Optional]` |

### 3.3 Mandatory Platform & Tooling Standards
- Viscosity FMB/PLL/RDF AST Conversion Analyzer & Trigger Classifier
- Oracle APEX 24.2 + Oracle REST Data Services (ORDS) (Zero WebLogic license required)
- Viscosity AMP (Application Management Platform) for enterprise menu, SSO, and audit governance
- APEX Office Print (AOP) & Oracle Analytics Publisher for .rdf replacement
- Oracle SQLcl Liquibase & utPLSQL for automated CI/CD and regression testing

---

## 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: Do we still need Oracle WebLogic Server licenses after converting Oracle Forms to APEX?
- **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)**: No. Oracle APEX and Oracle REST Data Services (ORDS) are included at no extra license cost with your existing Oracle Database license and run on Apache Tomcat or standalone Jetty, allowing you to terminate WebLogic Forms & Reports licensing completely.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 2: Will our high-speed keyboard data-entry users lose productivity moving from Forms to a browser?
- **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)**: No. We configure APEX Interactive Grids with custom keyboard shortcuts, tab-order control, and inline modal LOVs so keyboard-centric accounting and operations clerks can enter rows without touching the mouse.
- **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 complete Trigger-to-APEX mapping table (covering all 45+ Oracle Forms triggers), the WebLogic license termination checklist, and our automated FMB XML assessment workflow.
- **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 Forms Modernization (Forms to APEX)` 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-003` | Companion Portal: https://oracle-forms-modernization.web.app/ | This site is designed by Viscosity.AI*