# MODIFIABLE REQUEST FOR PROPOSALS (RFP) TEMPLATE
## Project Title: Oracle Fusion Cloud Payables AP Automation, Departmental Intake & Payee 360 Matching
- **RFP Document Reference**: `VNA-RFP-019` (Companion to Solution Brief `VNA-SB-019`)
- **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-fusion-payables-ap-automation.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 **Manual Departmental Payment Forms, Paper Vouchers & Disconnected Fusion ERP** environment to **Oracle APEX 24.2 AP Intake Hub, Payee 360 Fuzzy Match & Fusion Payables FBDI/REST**.

Our primary business and technical objectives are:
- Giving 500+ occasional departmental clerks full Oracle Fusion Cloud ERP Self-Service or Payables licenses is cost-prohibitive and exposes complex ERP screens to non-accountants.
- Central Accounts Payable teams spend 60% of their week re-keying emailed PDFs/spreadsheets, chasing missing W-9s, fixing rejected GL Chart of Accounts segments, and cleaning up duplicate one-time payees (`JOHN SMITH` vs. `SMITH, JOHN JR`).
- Direct, unbuffered scripts pushing data into Fusion ERP fail silently when supplier sites are inactive or accounting periods are closed.

---

## 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`) | Manual Departmental Payment Forms, Paper Vouchers & Disconnected Fusion ERP | Full retirement / modernization |
| Target Architecture (`Stack Y`) | Oracle APEX 24.2 AP Intake Hub, Payee 360 Fuzzy Match & Fusion Payables FBDI/REST | Production-grade HA/DR & security |
| Monthly Non-PO & Departmental Invoices | `[Insert Count, e.g., 6000 invoices/mo]` | 100% functional parity & optimization |
| Departmental Requestors & Approvers | `[Insert Count, e.g., 250 users]` | 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]**: Departmental Self-Service Intake Portal (Oracle APEX 24.2): Distributed departments submit single or bulk Excel/PDF payment requests through a clean, guided APEX wizard secured with Microsoft Entra ID / Okta SSO via Viscosity AMP, consuming zero additional Fusion ERP named-user seats.
2. **[MODIFIABLE REQUIREMENT 2]**: Payee 360 Fuzzy Matching & TIN/Address Verification: Before a request ever reaches Fusion Supplier Master, our Oracle 23ai similarity and phonetic matching engine (`UTL_MATCH` / Vector Search + USPS address normalization) scores incoming payees against active Fusion Suppliers to block duplicate vendor creation.
3. **[MODIFIABLE REQUIREMENT 3]**: Financial Data Hub 'Shock Absorber' Architecture: Sitting on Oracle Autonomous Database between departmental systems and Fusion Cloud ERP, the hub pre-validates Fund/Department/Account GL combinations, enforces multi-tier departmental approvals, and attaches supporting PDFs.
4. **[MODIFIABLE REQUIREMENT 4]**: Automated Fusion REST API & FBDI Orchestration: Approved batches are automatically formatted and transmitted to Oracle Fusion Payables via REST APIs or File-Based Data Import (FBDI) with real-time payment status / check-number sync back to the requesting department.

### 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 | Paper / PDF / Email Departmental Payment Requests | Guided Oracle APEX 24.2 Intake Wizard + Bulk Excel Parser | Role-Based Departmental Self-Service | `[Mandatory / Optional]` |
| REQ-02 | Duplicate One-Time Vendors in Supplier Master | Payee 360 Fuzzy Name, TIN & Address Matching Engine | Pre-Submission Deduplication & Site Linking | `[Mandatory / Optional]` |
| REQ-03 | Rejected Fusion Payables Import Batches | Pre-Validated GL Segment & Period Check in Data Hub | Synchronized Fusion COA & Supplier Cache | `[Mandatory / Optional]` |
| REQ-04 | Manual Email Approval Chains | APEX 24.2 Multi-Stage Approval Matrix + Audit Trail | Automated Threshold Routing & Escalation | `[Mandatory / Optional]` |

### 3.3 Mandatory Platform & Tooling Standards
- Oracle APEX 24.2 (Native Approvals, `APEX_DATA_PARSER`, Interactive Grids)
- Oracle Autonomous Database 23ai & Oracle REST Data Services (ORDS)
- Oracle Fusion Cloud Financials REST APIs & File-Based Data Import (FBDI)
- OCI Document Understanding / Document AI for automated invoice header/line OCR
- Viscosity AMP for department-level data isolation and SSO

---

## 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: Does building an APEX AP Intake portal require buying Oracle Fusion ERP licenses for every departmental submitter?
- **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. Departmental submitters authenticate into the Oracle APEX portal running on Oracle Autonomous Database. Only the consolidated, pre-validated vouchers are posted into Fusion Payables via service integration, saving hundreds of thousands of dollars in SaaS user licensing.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 2: How does the Financial Data Hub stay in sync with Fusion's Chart of Accounts and Supplier Master?
- **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)**: Scheduled ORDS/REST synchronization jobs pull active Supplier Sites, GL Code Combinations, and Payment Statuses from Fusion Cloud into the Autonomous Database cache every few minutes.
- **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 Logical & Physical Financial Data Hub Architecture diagram, the Payee 360 fuzzy-matching scoring algorithm, and a 5-year licensing TCO comparison of APEX Intake vs. VBCS/Fusion Named Users.
- **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 Fusion Payables AP Automation & Intake Hub` 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-019` | Companion Portal: https://oracle-fusion-payables-ap-automation.web.app/ | This site is designed by Viscosity.AI*