# MODIFIABLE REQUEST FOR PROPOSALS (RFP) TEMPLATE
## Project Title: Public Sector & SLED Fast-Track Cooperative Procurement Hub for Oracle, APEX & Cloud
- **RFP Document Reference**: `VNA-RFP-041` (Companion to Solution Brief `VNA-SB-041`)
- **Issuing Organization**: `[INSERT ORGANIZATION / COMPANY NAME]`
- **Issue Date**: `[2026-10-30]`
- **Proposal Due Date**: `[INSERT DATE, e.g., +30 Calendar Days]`
- **Reference Architecture Portal**: https://sled-cooperative-procurement-oracle.pages.dev/
- **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-30]` |
| 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 **9-to-12 Month Formal RFP Delays Stalling Urgent County, Municipal, ISD & State IT Projects** environment to **Pre-Competed Cooperative Contract Vehicles (TX DIR DBITS / Choice Partners / Interlocal SOW)**.

Our primary business and technical objectives are:
- Critical business operations remain trapped in 9-to-12 Month Formal RFP Delays Stalling Urgent County, Municipal, ISD & State IT Projects, creating audit risk, manual reconciliation overhead, and rising support costs.
- Duplicate queries, cloned reports, and undocumented triggers make impact analysis slow and expensive across legacy screens, reports & interfaces in scope.
- Lack of automated binary-to-database metadata mapping causes traditional consulting shops to pad estimates with 40% manual discovery buffers.
- Leadership needs a predictable, fixed-fee phased timeline with verifiable test specifications and zero-downtime cutover guarantees.

---

## 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`) | 9-to-12 Month Formal RFP Delays Stalling Urgent County, Municipal, ISD & State IT Projects | Full retirement / modernization |
| Target Architecture (`Stack Y`) | Pre-Competed Cooperative Contract Vehicles (TX DIR DBITS / Choice Partners / Interlocal SOW) | Production-grade HA/DR & security |
| Target Modernization Modules / Workstreams | `[Insert Count, e.g., 4 workstreams]` | 100% functional parity & optimization |
| Legacy Screens, Reports & Interfaces in Scope | `[Insert Count, e.g., 160 scoped objects]` | Automated AST & schema uplift |
| Procurement & Legal Cycle Compression | `[Insert Count, e.g., 80 % faster award]` | `[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 Phase 0 AST & binary scan mapping 9-to-12 Month Formal RFP Delays Stalling Urgent County, Municipal, ISD & State IT Projects artifacts directly to live Oracle dictionary metadata and profiling production data.
2. **[MODIFIABLE REQUIREMENT 2]**: Target architecture built on Pre-Competed Cooperative Contract Vehicles (TX DIR DBITS / Choice Partners / Interlocal SOW), consolidating cloned queries into governed core SQL views with runtime Smart Filters.
3. **[MODIFIABLE REQUIREMENT 3]**: Automated generation of full Business Requirements Documents (BRD), Technical Approach Docs, Testing Specifications, and Verified Test Results.
4. **[MODIFIABLE REQUIREMENT 4]**: Zero-trust SSO/MFA (Entra ID / Okta) paired with database-enforced row-level security (VPD / RAS) and SQLcl Liquibase CI/CD pipelines.

### 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 | Source Tier: 9-to-12 Month Formal RFP Delays Stalling Urgent County, Municipal, ISD & State IT Projects | Pre-Competed Cooperative Contract Vehicles (TX DIR DBITS / Choice Partners / Interlocal SOW) | Automated AST & Metadata Uplift (85%-95%) | `[Mandatory / Optional]` |
| REQ-02 | Primary Footprint: Target Modernization Modules / Workstreams | Oracle APEX 24.2 Redwood UI + PL/SQL APIs | Binary-to-DB Metadata Mapping + Pilot Sprint | `[Mandatory / Optional]` |
| REQ-03 | Workload & Queries: Legacy Screens, Reports & Interfaces in Scope | Canonical Core SQL Views + Runtime Smart Filters | Query Fan-Out Clustering (75%-90% Reduction) | `[Mandatory / Optional]` |
| REQ-04 | Undocumented Legacy Business Rules & QA | Auto-Generated BRD, Approach Doc, Test Specs & Results | 100% Automated Documentation & utPLSQL / Playwright | `[Mandatory / Optional]` |

### 3.3 Mandatory Platform & Tooling Standards
- Oracle APEX 24.2 & Universal Theme (Redwood Light Flavors)
- Oracle Database 23ai / Autonomous Database (ATP / ADW)
- Viscosity Automated Binary (.fmb/.rdf) & AST Metadata Profiler
- Auto-Doc Engine (BRD, Approach Doc, Test Specs & Test Results)
- Oracle REST Data Services (ORDS) & APEX Office Print (AOP)
- SQLcl Liquibase CI/CD, utPLSQL & Playwright 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: What are the primary levers that control the cost of SLED Cooperative Procurement Hub (DIR / Co-Op)?
- **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)**: Cost is controlled by five levers: (1) collapsing cloned query fan-out across legacy screens, reports & interfaces in scope into canonical core SQL views, (2) percentage of business logic already in database packages vs. UI triggers, (3) production data quality profiled during Phase 0, (4) external integration/SSO count, and (5) cutover downtime requirements.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 2: How does your tool convert binaries (.fmb, .rdf, etc.), map database metadata, and generate documentation?
- **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 automated analyzer parses legacy binaries and source files, extracts every trigger, query, and UI control, cross-references them against live database dictionary metadata (ALL_TAB_COLUMNS, ALL_DEPENDENCIES), profiles actual column data distributions, and automatically generates the Business Requirements Document (BRD), Technical Approach Doc, Test Specifications, and Verified Test Results.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 3: What does a typical project timeline look like from kickoff to production cutover?
- **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)**: Projects follow four gated phases: Phase 0 (Weeks 1-2: Binary AST Scan, Data Profiling & Auto-Generated BRD), Phase 1 (Weeks 3-6: Core Schema Uplift & Working Pilot), Phase 2 (Weeks 7-12: Automated Conversion Sprints & Test Spec Execution), and Phase 3 (Weeks 13-16: Parallel Run, Zero-Downtime Cutover & 30-Day Hypercare).
- **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 `SLED Cooperative Procurement Hub (DIR / Co-Op)` 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-041` | Companion Portal: https://sled-cooperative-procurement-oracle.pages.dev/ | This site is designed by Viscosity.AI*