| Client | Qwest Communications |
| Industry | Technology — Telecommunications (Regional Bell) |
| Oracle Version | Oracle E-Business Suite R12 |
| Modules | PO AP GL |
| Engagement Period | 2009 |
| Project Type | Oracle EBS RFP Response — Implementation Scoping & Proposal |
| Complexity | Medium · RFP Response · Telecom Oracle Context · Assumptions & Exclusions · Time Estimates |
Qwest Communications — the Denver-based regional Bell operating company serving the western United States, later merged with CenturyTel to form CenturyLink (now Lumen Technologies) — issued RFP #55 for Oracle EBS consulting services in 2009, and William Delaney Consulting responded with a formal proposal. The engagement artifacts — Consultant Questionnaire II (the structured capability assessment at the heart of the RFP response), an Assumptions and Exclusions document (v1.2), and a Time Estimates workbook — represent the complete response package for a competitive Oracle consulting bid at a major telecommunications company.
Responding to a formal Oracle RFP from a large telecom company is a distinctive professional milestone: Qwest's Oracle environment at the time was one of the larger and more complex Oracle EBS deployments in the telecommunications sector, supporting procurement and financial operations across a 14-state service territory. An RFP #55 designation indicates a well-established procurement process with multiple prior Oracle consulting engagements — a company that had developed sophisticated Oracle vendor evaluation criteria from experience.
Qwest Communications in 2009 operated Oracle EBS across a complex telecom enterprise: procurement for network infrastructure (central office equipment, outside plant cabling, fiber optic systems), indirect materials management, capital vs. operating expense classification for regulatory purposes, and financial reporting under FCC accounting requirements for rate-of-return carriers. Oracle PO and AP in this environment needed to handle the full spectrum from strategic capital procurement (multi-million dollar network equipment) to high-volume indirect materials purchasing across dozens of facilities.
The 2009 timing placed the RFP in the context of Qwest's CenturyTel merger discussions (completed in 2011) — a period when Oracle EBS strategic direction at a company may be deliberately uncertain, as post-merger ERP rationalization decisions can override mid-engagement implementation work. An RFP response in this context required explicit assumptions and exclusions to protect the scope — acknowledgement that merger-driven scope changes would require a formal change process.
Large telecom RFPs typically evaluate Oracle consulting firms on: demonstrated telecom Oracle experience, methodology (Oracle AIM or equivalent), specific module expertise in the RFP scope areas, key personnel qualifications, and commercial terms. The Consultant Questionnaire II format — a structured document that the Oracle vendor completes to demonstrate capability — was Qwest's primary qualification evaluation tool, allowing them to compare vendor responses on a consistent framework.
The Consultant Questionnaire is the core RFP response artifact: a structured capability assessment that asks Oracle consulting vendors to demonstrate experience across specific Oracle modules, methodology, implementation approach, and key personnel qualifications. Qwest's RFP #55 questionnaire (the second iteration, implying at least one prior RFP in this series) reflected a sophisticated buyer's knowledge of what Oracle implementation capability actually looks like. Effective questionnaire responses demonstrate depth through specific project references, not broad capability claims — a lesson that distinguishes successful Oracle RFP responses from generic consulting firm pitches.
The Assumptions and Exclusions document — at version 1.2, indicating at least two rounds of refinement during the proposal process — is the most commercially significant artifact in any Oracle proposal. Assumptions define what the consultant expects to be true (client resources available for X hours per week, Oracle environment exists and is accessible, etc.) and what happens if those assumptions prove false. Exclusions define what is explicitly not included in scope. In a telecom Oracle engagement, common exclusions include: Oracle technical administration, Oracle database patching, network infrastructure supporting Oracle access, and integration development beyond defined interfaces. A well-crafted Assumptions and Exclusions document protects both parties — it prevents scope creep and the disputes that accompany unmanaged scope expansion.
The Time Estimates workbook provided the labor hour and duration foundation for the commercial proposal — breaking the Oracle implementation scope into deliverable-level work packages with hour estimates by resource type (Functional Lead, Functional Analyst, Technical Developer). Time estimates for Oracle engagements at a large telecom reflect both the Oracle complexity and the client-side demands: configuration complexity scales with the number of operating units, GL segment structures, and supplier base; client review cycles add time in proportion to the stakeholder count; and data conversion effort scales with the legacy system's data quality and completeness.
| Deliverable | Type | Purpose |
|---|---|---|
| Consultant Questionnaire II Response | RFP Response | Structured capability demonstration covering Oracle module expertise, methodology, telecom experience, and key personnel |
| Assumptions and Exclusions (v1.2) | Commercial Artifact | Formal documentation of engagement assumptions and scope exclusions protecting both parties in the Oracle engagement |
| Time Estimates Workbook | Commercial Artifact | Deliverable-level labor hour estimates by resource type forming the commercial basis of the Oracle proposal |