This document provides an overview of a proof-of-concept for a credit limit increase request management process using Oracle BPM 11g. The goals are to increase visibility, reduce processing time, and improve fraud detection for a financial company's credit card services. Key deliverables and milestones include developing a web application for requests, implementing the basic approval workflow, adding management reports, and customizing the process to allow for suspensions, cancellations, and notifications.

1. <Insert Picture Here>
Oracle BPM 11g Advanced Workshop
Proof-of-concept Overview

2. Use Case Scenario
Overview
• Your customer is a financial company issuing credit
cards
• They are facing number of issues with the current
process, which is manual to a large extent
• Goals
• Increase visibility
• Reduce time to process customer requests
• Better fraud detection and handling
• As a proof-of-concept one of the many credit card
processes is chosen
• Credit limit increase request management

3. Use Case Scenario
Requirements
• Define and capture key performance indicators for
reporting
• Leverage existing IT assets
• Handle manual interventions in the process for
approvals and exception management
• Interrupt an on-going process to either suspend or
cancel
• Support multiple channels for receiving credit limit
increase requests

4. Credit Card Increase Request Process
Household
Cards
Transactions
• Credit Score
• Transaction History
• Cards For Household
• Approve/Reject/Investigate
Approvals
Calculate Increase
Update Legacy System
Auto Approve
Auto Reject
ApproveInvestigate
Reject
•Create Request
•Suspend
•Cancel Request
•Terminate Process
•Start Compliance Process
•Resume
Oracle Confidential

5. POC Milestones
Deliverable Due By
High-level Process model without
any implementations
End of Day 1
Credit Card Web Application for
submitting requests
Mid-day Day 2
Basic, happy-path process –
deployed and running
End of Day 2
Management reports End of Day 2
Custom task form for approval Mid-day Day 3
Business Rules implementation Mid-day Day 3
Notification implementation End of Day 3
Canceling and suspending
processes
Mid-day Day 4
End-to-end complete solution End of Day 4

6. POC Timeline