qbo.Decision

Overview

The qbo.Decision module handles the coordinate of activity in a system, including:

• Workflow: execution of a flow chart of steps

• User tasks: a 'screen' (or custom form) that a user navigates to in order to review and complete work, and

• Work lists: the grouping and assignment of user tasks by team, person and priority

Workflow (aka 'Decisions')

The QBO Decision module constitutes a workflow engine, allowing power users to implement a flow chart as a 'Decision Template', and then instantiate individual workflows based on the template for specific work. Real-world examples of workflows implemented using QBO include:

• • Foreclosure timeline tracking used by Freddie Mac

  • Foreclosure management used by trustees (including generation of NOD/NOS, pub and post integrations, mailings, etc.)

  • Equity analysis for both senior and subordinate mortgages (including pulling AVMs, credit reports, and property inspection data)

  • Loan Modification analysis and execution (including servicing system integration to execute term changes)

  • Short sale processing

  • Bankruptcy processing

  • Debt collections (credit card, auto) processing

  • many, many more business areas

What Can a Workflow Do?

A workflow can orchestrate the executing anything QBO can do. When creating a workflow, many power users start with a flow chart representing their current workflows. Given a flow chart, a rule of thumb is:

• • Each flow chart is a "Decision Template"

  • Each shape on the flow chart is a "Step" in the workflow

  • Each line on the flow chart is a "Dependency" in the workflow

Workflow steps are powerful. Examples includes:

• • Creating a task: tasks are human-based steps, and cause users to be assigned to complete them

  • Generate a document: mail merge a document, and deliver the document to imaging, a print vendor, or a third party

  • If/Then statement: evaluate data to arrive at a true or false condition, on which other steps can depend

  • Polling step: cause the workflow to wait for some data condition

  • Launch a workflow: one workflow can launch a child workflow, and wait for the child to complete

  • Step: catch-all functionality to call any QBO functionality, including

    • ordering data products from vendors (e.g. credit reports, AVMs, SCRA status, writing to servicing systems, etc.)

    • generating emails

    • changing status or values in any QBO tables

User Tasks (aka 'Custom Forms')

In QBO, a 'custom form' is a web page that a user navigates to in order to accomplish a specific task. In very simple cases, such a form may merely have a due date, a completion date, and perhaps a comment field.  More complex examples include:

• Steps in a call script to handle borrower defaults

• NPV analysis screens to assist with deciding an appropriate loan modification path

• A BPO entry page, allowing a real estate broker to enter comps, property values, and upload photos

• A default analysis page that displays data from a variety of servicing system screens shots

• many, many more 

Work Lists (aka 'Smart Worklists')

Smart work lists are used to automate the assignment of work across an enterprise (or even outside the enterprise). They can be configured to doll work out to users on an as-needed basis, and can prioritize work based on matrix-driven team, user and priority assignment.

If you find your organization running reports, splitting the report output up in Excel, and emailing users parts of an Excel spreadsheet to work on, Smart Worklists are the replacement for this situation.