# MODIFIABLE REQUEST FOR PROPOSALS (RFP) TEMPLATE
## Project Title: FOEX Plugin Migration: Replace Discontinued FOEX (ExtJS) with Native Oracle APEX 24.2
- **RFP Document Reference**: `VNA-RFP-004` (Companion to Solution Brief `VNA-SB-004`)
- **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://foex-plugin-migration-apex.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 **FOEX Plugin Framework (Sencha ExtJS Wrapper on Legacy APEX 5.x / 18.x / 19.x / 20.x)** environment to **100% Native Oracle APEX 24.2 (Universal Theme 42, Native Grids, Dynamic Actions)**.

Our primary business and technical objectives are:
- The FOEX Plugin Framework wrapped Sencha ExtJS inside Oracle APEX to build desktop-like multi-pane grids in the APEX 4.x/5.x era. Following corporate acquisitions and product discontinuation, FOEX is a dead-end dependency.
- Every time an organization attempts to upgrade Oracle Database or Oracle APEX to 23.2 / 24.2, broken FOEX plugin metadata, deprecated ExtJS JavaScript APIs, and custom CSS overrides halt the upgrade.
- FOEX pages bypass standard APEX Universal Theme rendering, loading multi-megabyte ExtJS bundles and proprietary AJAX handlers that cannot use modern APEX features like Native Approvals, AI Assistant, or Template Components.

---

## 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`) | FOEX Plugin Framework (Sencha ExtJS Wrapper on Legacy APEX 5.x / 18.x / 19.x / 20.x) | Full retirement / modernization |
| Target Architecture (`Stack Y`) | 100% Native Oracle APEX 24.2 (Universal Theme 42, Native Grids, Dynamic Actions) | Production-grade HA/DR & security |
| APEX Pages Containing FOEX Plugins | `[Insert Count, e.g., 120 FOEX pages]` | 100% functional parity & optimization |
| FOEX Grids & Report Regions | `[Insert Count, e.g., 310 FOEX regions]` | Automated AST & schema uplift |
| Grid Query Fan-Out Rationalization (Core SQL Views + Runtime Smart Filters) | `[Insert Count, e.g., 70 % 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]**: APEX Export Metadata & FOEX Plugin Scanner: We parse your application export SQL/YAML via SQLcl to inventory every `PLUGIN_COM.FOEX.*` region, item, and dynamic action across all pages, scoring each page by ExtJS customization depth.
2. **[MODIFIABLE REQUIREMENT 2]**: Viewport & Splitter Replacement with Universal Theme 42: Complex FOEX Viewport, Tab, and Accordion containers are replaced with native Universal Theme 42 CSS Grid/Flexbox sub-regions, collapsible drawers, and modal dialogs.
3. **[MODIFIABLE REQUIREMENT 3]**: FOEX Grid & TreeGrid to Native Interactive Grid: FOEX Grids are converted to native APEX 24.2 Interactive Grids with custom `apex.region().call('getViews', 'grid')` configurations, preserving frozen columns, summary rows, and inline editing.
4. **[MODIFIABLE REQUIREMENT 4]**: Zero-Disruption Coexistence & Page-by-Page Cutover: Using APEX session-sharing and AMP navigation routing, we migrate high-complexity FOEX applications module-by-module without freezing ongoing business operations.
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 | FOEX Viewport / Border Layout / Panes | Universal Theme 42 Region Display Selector & CSS Grid | Responsive Native Layout Refactoring | `[Mandatory / Optional]` |
| REQ-02 | FOEX Grid / Editable Grid Plugin | Native APEX 24.2 Interactive Grid + Server Processes | Metadata Remapping & Native DML Wiring | `[Mandatory / Optional]` |
| REQ-03 | FOEX Form & Field Plugins (Combo, Lov, Date) | Native APEX Form Region, Popup LOV & Date Picker | Item Type Conversion + Validation Preservation | `[Mandatory / Optional]` |
| REQ-04 | FOEX Dynamic Actions (Server/Client ExtJS Events) | Native APEX Dynamic Actions + `apex.server.process` | Clean JavaScript & PL/SQL Callback Refactoring | `[Mandatory / Optional]` |
| REQ-05 | FOEX Master-Detail Linked Panes | Native APEX Master-Detail Interactive Grids | Declarative Parent-Child Region Binding | `[Mandatory / Optional]` |
| REQ-06 | 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
- Oracle APEX 24.2 Universal Theme 42 & Template Components
- Oracle SQLcl Liquibase for page-level YAML/SQL export analysis and diffing
- Viscosity AMP for seamless cross-application session sharing during phased FOEX retirement
- Playwright / Selenium automated UI regression suites

---

## 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: Can we migrate off FOEX incrementally without rewriting the entire application at once?
- **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)**: Yes. By configuring Shared Session Cookies between your existing FOEX app and a new Native APEX 24.2 companion app in the same workspace, users can navigate seamlessly between legacy and modernized pages while we convert module by module.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 2: Do we have to rewrite our underlying PL/SQL packages when removing FOEX?
- **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)**: Almost all core PL/SQL business logic remains intact. Only the thin FOEX JSON/AJAX wrapper calls are refactored to standard `apex_json` or native Interactive Grid DML handlers.
- **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 `COM.FOEX.*` plugin-to-Native-APEX mapping catalog, SQL queries to audit your workspace's FOEX footprint in 60 seconds, and a phased coexistence architecture.
- **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 `FOEX Plugin Migration to Native 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-004` | Companion Portal: https://foex-plugin-migration-apex.web.app/ | This site is designed by Viscosity.AI*