# MODIFIABLE REQUEST FOR PROPOSALS (RFP) TEMPLATE
## Project Title: IBM Maximo Lift-and-Shift to OCI & Maximo Application Suite (MAS 9) Upgrade on OpenShift
- **RFP Document Reference**: `VNA-RFP-014` (Companion to Solution Brief `VNA-SB-014`)
- **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://ibm-maximo-mas9-upgrade-oci.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 **On-Premises IBM Maximo 7.6.x (WebSphere ND VMs, Oracle / DB2 / SQL Server) & High-Cost Legacy Hosting** environment to **Two-Lane OCI Architecture: Lane 1 (Maximo 7.6 Lift-and-Shift on OCI VMs + Oracle 19c/23ai) or Lane 2 (MAS 9 on Red Hat OpenShift + OCI + APEX Companion Portals)**.

Our primary business and technical objectives are:
- Urgent Data Center Exit vs. Complex MAS 9 Re-Architecture: Many organizations need to get Maximo 7.6.1 off aging on-premises servers or expensive colocation contracts immediately without waiting 9+ months for a full MAS 9 business-process overhaul.
- 80% of Maximo Bottlenecks Live in the Database Tier: Slow Work Order searches, stuck PM generation crons, BIRT report timeouts, and ESRI/Spatial map lag almost always stem from untuned Oracle Database execution plans, fragmented `WORKORDER`/`MATUSETRANS` indexes, and under-provisioned storage IOPS.
- MAS 9 OpenShift Complexity & Punitive Cloud Costs: Upgrading to Maximo Application Suite (MAS 9) requires Red Hat OpenShift Container Platform (OCP), MongoDB, Kafka, and IBM SLS license servers - which cost 35% to 50% more to run on AWS or IBM Cloud than on OCI Flexible Compute and high-IOPS Block Volumes.

---

## 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`) | On-Premises IBM Maximo 7.6.x (WebSphere ND VMs, Oracle / DB2 / SQL Server) & High-Cost Legacy Hosting | Full retirement / modernization |
| Target Architecture (`Stack Y`) | Two-Lane OCI Architecture: Lane 1 (Maximo 7.6 Lift-and-Shift on OCI VMs + Oracle 19c/23ai) or Lane 2 (MAS 9 on Red Hat OpenShift + OCI + APEX Companion Portals) | Production-grade HA/DR & security |
| Total Maximo Users (Core + Casual/Vendor) | `[Insert Count, e.g., 600 users]` | 100% functional parity & optimization |
| Maximo Database Size & BIRT / MIF Integrations | `[Insert Count, e.g., 180 artifacts/GB]` | 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]**: Pathway 1 - Fast Maximo 7.6 Lift-and-Shift to OCI (6-10 Weeks): We lift your existing Maximo 7.6.1 WebSphere ND application servers, JMS integration queues, and BIRT reporting tiers onto OCI Flexible VMs (`E5.Flex`) while migrating the Maximo database to OCI Base Database / Exadata (19c/23ai) using RMAN Cross-Platform Transportable Tablespaces (XTTS) or GoldenGate with near-zero downtime.
2. **[MODIFIABLE REQUIREMENT 2]**: Pathway 2 - Turnkey Upgrade to MAS 9 on Red Hat OpenShift on OCI: When ready for MAS 9, we provision multi-zone Red Hat OpenShift clusters on OCI, uplift legacy Java MBO customizations into upgrade-safe Python/Jython Automation Scripts, run the validated `updatedb` pipeline, and migrate Maximo Anywhere to MAS Mobile.
3. **[MODIFIABLE REQUIREMENT 3]**: Oracle ACE Database Tuning & Multi-Region Disaster Recovery: We tune the `MAXIMO` schema (SQL Plan Baselines, Text Indexes, table partitioning) and configure cross-region Oracle Active Data Guard (`RPO < 5 min`, `RTO < 60 min`) paired with Rackware/Velero application tier replication.
4. **[MODIFIABLE REQUIREMENT 4]**: APEX 24.2 Companion Portals to Cut MAS AppPoint Licensing: Casual requestors, external contractors, and executive dashboard viewers access live Maximo data via an Oracle APEX 24.2 portal connected to Maximo OSLC REST APIs and Active Data Guard read replicas - saving hundreds of thousands in MAS AppPoints.

### 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 | On-Premises Maximo 7.6.1 WebSphere ND & Admin VMs | Pathway 1: OCI E5.Flex Lift-and-Shift VMs | Pathway 2: MAS 9 on Red Hat OpenShift (OCP) | Fast lift-and-shift first or direct Ansible/Operator MAS 9 deployment on OCI | `[Mandatory / Optional]` |
| REQ-02 | On-Premises Maximo Database (Oracle / SQL Server / Db2) | OCI Oracle Base DB / Exadata 19c/23ai + Active Data Guard | Zero-downtime RMAN XTTS / GoldenGate cutover + MAXIMO schema index tuning | `[Mandatory / Optional]` |
| REQ-03 | Legacy Java MBO Class Extensions & Custom Workflows | MAS 9 Automation Scripts (Python/Jython) & OSLC Integration Hooks | Preserve 100% in Lift-and-Shift; refactor to upgrade-safe scripts for MAS 9 | `[Mandatory / Optional]` |
| REQ-04 | High-Cost Casual User & Vendor MAS AppPoints | Oracle APEX 24.2 Contractor & Work-Request Companion Portal | Zero-per-seat APEX portal reading Active Data Guard & posting via Maximo OSLC REST | `[Mandatory / Optional]` |
| REQ-05 | Single-Site Maximo Storage & Manual Backup Scripts | Multi-Region OCI Active Data Guard + Velero / Rackware DR | Automated cross-region failover (US-Ashburn <-> US-Phoenix / US-Chicago) | `[Mandatory / Optional]` |

### 3.3 Mandatory Platform & Tooling Standards
- Red Hat OpenShift Container Platform (OCP) on Oracle Cloud Infrastructure (OCI)
- Oracle Database 19c / 23ai with Active Data Guard and Real Application Testing
- Oracle APEX 24.2 & ORDS for AppPoint-saving vendor/contractor companion portals
- OCI Bastion, OCI Vault, Web Application Firewall (WAF), and Velero OpenShift backup

---

## 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: Is Red Hat OpenShift officially supported and certified to run IBM MAS 9 on Oracle Cloud Infrastructure (OCI)?
- **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. Red Hat OpenShift Container Platform (OCP) is fully certified and supported on OCI Compute shapes through the joint Red Hat and Oracle strategic partnership, allowing you to colocate MAS 9 OpenShift worker nodes on the same ultra-low-latency VCN subnet as your Oracle Database.
- **Evaluator Score (0 to 10 Points)**: `[   / 10 ]`

### Vendor Question 2: How can Oracle APEX reduce our IBM MAS AppPoint licensing costs?
- **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)**: External suppliers, invoice submitters, and occasional requestors do not need full MAS Manage seats. By routing vendor submissions and executive read-only dashboards through an Oracle APEX 24.2 portal connected to Maximo REST APIs and Active Data Guard read replicas, you cut AppPoint consumption substantially.
- **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 MAS 9 on OCI + OpenShift Reference Architecture diagram, the Maximo 7.6 `updatedb` pre-flight database tuning checklist, and an OCI vs. AWS/IBM Cloud 5-year TCO model.
- **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 `IBM Maximo Lift-and-Shift to OCI & MAS 9 Upgrade` 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-014` | Companion Portal: https://ibm-maximo-mas9-upgrade-oci.web.app/ | This site is designed by Viscosity.AI*