# MODIFIABLE REQUEST FOR PROPOSALS (RFP) TEMPLATE
## Project Title: PowerBuilder to Oracle APEX Migration & Automated PBL Conversion
- **RFP Document Reference**: `VNA-RFP-001` (Companion to Solution Brief `VNA-SB-001`)
- **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://powerbuilder-to-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 **Sybase / Appeon PowerBuilder (.pbl, .srd, .srw, DataWindows, PowerScript)** environment to **Oracle APEX 24.2, Oracle REST Data Services (ORDS), PL/SQL Packages & AMP**.

Our primary business and technical objectives are:
- Enterprise operations still rely on mission-critical PowerBuilder 6.5 through 2022 desktop applications built 15 to 25 years ago. The original authors have retired, leaving hundreds of thousands of lines of undocumented PowerScript buried inside binary .pbl libraries.
- Every PowerBuilder DataWindow (.srd) mixes SQL joins, computed columns, conditional UI formatting, and transaction state directly inside the client binary. Deploying changes requires pushing thick-client installers or maintaining expensive Citrix / RDS terminal server farms.
- Manual rewrites fail because business analysts cannot document twenty years of edge-case PowerScript validation rules found in ItemChanged, RowFocusChanged, and UpdateStart events.

---

## 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`) | Sybase / Appeon PowerBuilder (.pbl, .srd, .srw, DataWindows, PowerScript) | Full retirement / modernization |
| Target Architecture (`Stack Y`) | Oracle APEX 24.2, Oracle REST Data Services (ORDS), PL/SQL Packages & AMP | Production-grade HA/DR & security |
| PowerBuilder Windows & UserObjects | `[Insert Count, e.g., 240 windows]` | 100% functional parity & optimization |
| DataWindow Objects & Reports (.srd) | `[Insert Count, e.g., 450 DataWindows]` | Automated AST & schema uplift |
| Query Fan-Out Rationalization (Cloned Reports -> 1 Core SQL + Runtime/Inference Filters) | `[Insert Count, e.g., 75 % 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 PBL & SRD/SRW AST Parser: Our reverse-engineering engine unpacks binary .pbl archives into ASCII source objects (.srw windows, .srd DataWindows, .sru user objects, .srm menus) and builds a complete Abstract Syntax Tree (AST) and dependency graph.
2. **[MODIFIABLE REQUIREMENT 2]**: DataWindow-to-APEX Component Compiler: Tabular, Grid, Freeform, and Master-Detail DataWindows are mapped directly to Oracle APEX 24.2 Interactive Grids, Interactive Reports, and Smart Filters. Computed fields and DropDownDataWindows (DDDW) become Shared List of Values (LOVs).
3. **[MODIFIABLE REQUIREMENT 3]**: PowerScript-to-PL/SQL Pushdown: Client-side PowerScript data manipulation and embedded SQL are refactored into compiled, unit-tested Oracle PL/SQL API packages with utPLSQL test harnesses, eliminating chatty client/server network round-trips.
4. **[MODIFIABLE REQUIREMENT 4]**: Enterprise Governance via AMP & SQLcl: All converted APEX workspaces are wired into our Application Management Platform (AMP) for centralized SSO (OIDC/SAML), role-based access control, unified auditing, and automated SQLcl Liquibase CI/CD pipelines.
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 | PowerBuilder DataWindow (.srd - Grid / Tabular) | APEX 24.2 Interactive Grid / Interactive Report | Automated SQL & Column Metadata Compiler | `[Mandatory / Optional]` |
| REQ-02 | Freeform DataWindow & Window Controls (.srw) | APEX Form Region + Universal Theme 42 Layout | Grid Coordinate Normalization to Responsive Flex/Grid | `[Mandatory / Optional]` |
| REQ-03 | DropDownDataWindow (DDDW) & Code Tables | APEX Shared Components List of Values (LOV) | Deduplicated Schema-Level LOV Generator | `[Mandatory / Optional]` |
| REQ-04 | PowerScript ItemChanged / Validate Events | APEX Dynamic Actions + PL/SQL Validation Packages | AST Rule Extraction & Server-Side Pushdown | `[Mandatory / Optional]` |
| REQ-05 | Non-Visual User Objects (NVO / .sru) | Oracle Database PL/SQL Packages + ORDS REST APIs | AST Transpilation + utPLSQL Automated Test Suite | `[Mandatory / Optional]` |
| REQ-06 | Composite / Nested Report DataWindows | APEX Office Print (AOP) / BI Publisher PDF Templates | Pixel-Perfect Layout & Bind Variable Mapping | `[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
- Oracle APEX 24.2 (Universal Theme 42, Interactive Grids, Dynamic Actions, Native Approvals & Workflow)
- Viscosity Application Management Platform (AMP) for multi-app SSO, RBAC, telemetry, and error logging
- Oracle REST Data Services (ORDS) for OAuth2 REST API exposure
- Oracle SQLcl Projects & Liquibase for Git-backed schema and APEX page diffs
- utPLSQL & Selenium for automated regression verification against legacy PowerBuilder outputs

---

## 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: How do you extract business logic trapped inside PowerBuilder ItemChanged and Clicked events?
- **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)**: Our parser decomposes .srw and .sru exports into an Abstract Syntax Tree, separating UI state changes from database validations and DML. UI state toggles become APEX Dynamic Actions, while validations and transactions are compiled into server-side PL/SQL packages.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 2: What if our PowerBuilder application runs on Sybase ASE, SQL Anywhere, or SQL Server instead of Oracle?
- **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)**: We convert both the database tier (Sybase T-SQL / Watcom-SQL to Oracle Database 23ai PL/SQL) and the PowerBuilder UI tier simultaneously, or connect APEX to your external database via ORDS REST Enabled SQL and database links during phased cutover.
- **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 4-page PDF Solution Brief includes the complete PowerBuilder-to-APEX AST Reference Architecture, the DataWindow-to-Interactive-Grid mapping matrix, a sample PBL complexity sizing worksheet, and a 12-week phased cutover blueprint.
- **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 `PowerBuilder to Oracle APEX Migration` 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-001` | Companion Portal: https://powerbuilder-to-apex.web.app/ | This site is designed by Viscosity.AI*