AU_Presentation_reqsactivitysystems.com/wp-content/uploads/2012/08/Conduit... · Web viewInformation Technology Division Project: Automated Underwriting Topic: AU Broker Presentation

Information Technology DivisionProject: Automated UnderwritingTopic: AU Broker Presentation Requirements

Automated Underwriting CONDUITPresentation Requirements

— Analysis —

Current Version: Version 1.2Effective Date: August 23, 2012

Revision History

Date Rev. # Purpose of Revision Author

03.09.2009 1.0 Client Delivery Pobrien

03.15.2009 1.1 Revisions Lsingleterry

03.16.2009 1.2 Global Format changes Pobrien

document.docx 1 of 54 Created/Revised: August 23, 2012/ August 23, 2012©2009 Aurora Loan Services Author: Patrick O’Brien.

This publication contains confidential and proprietary information of Aurora Loan Services, A Lehman Brothers Company. No part of this publication may be reproduced in any form without the prior written permission of

Aurora Loan Services.

Copyright 2009 Aurora Loan Services, A Lehman Brothers CompanyAll Rights Reserved.


Table of Contents1.0 Document Purpose........................................................................................................................................ 42.0 What this document covers............................................................................................................................ 43.0 Out of Scope.................................................................................................................................................. 44.0 Use Case Maps: CONDUIT........................................................................................................................... 6

4.1 Use Case Diagram Map:............................................................................................................................ 65.0 Site map: CONDUIT...................................................................................................................................... 76.0 CONDUIT Use Cases.................................................................................................................................... 8

6.1 Use Case: Manage Pipeline....................................................................................................................... 86.1.1 Workflow: Manage Pipeline................................................................................................................. 86.1.2 Rules: Manage Pipeline...................................................................................................................... 86.1.3 Use Case Description: Manage Pipeline.............................................................................................96.1.4 Alternate flows: Manage Pipeline........................................................................................................9

6.1.4.1 Invalid ID Format Error................................................................................................................. 96.1.4.2 Error Page.................................................................................................................................... 9

6.2 Use Case: View snapshot........................................................................................................................106.2.1 Use Case Description: View snapshot..............................................................................................10

6.3 Use Case: Register.................................................................................................................................. 116.3.1 Workflow: Register............................................................................................................................ 116.3.2 Rules: Register.................................................................................................................................. 116.3.3 Use Case Description: Register........................................................................................................116.3.4 Alternate flows: Register...................................................................................................................12

6.3.4.1 Invalid ID Format Error...............................................................................................................126.3.4.2 Error Page.................................................................................................................................. 12

6.4 Use Case: Request Credit Report............................................................................................................136.4.1 Workflow: Request Credit Report......................................................................................................136.4.2 Rules: Request Credit Report...........................................................................................................136.4.3 Use Case Description: Request Credit Report..................................................................................146.4.4 Alternate flows: Request Credit Report.............................................................................................14

6.4.4.1 Invalid CMS Format Error..........................................................................................................146.4.4.2 Error Page.................................................................................................................................. 14

6.5 Use Case: View Credit Report.................................................................................................................156.5.1 Workflow: View Credit Report...........................................................................................................156.5.2 Rules: View Credit Report.................................................................................................................156.5.3 Use Case Description: View Credit Report.......................................................................................166.5.4 Alternate flows: View Credit Report...................................................................................................16

6.5.4.1 Invalid CMS Format Error..........................................................................................................166.5.4.2 Error Page.................................................................................................................................. 16

6.6 Use Case: Request AU............................................................................................................................ 176.6.1 Workflow: Request AU......................................................................................................................176.6.2 Rules: Request AU............................................................................................................................ 186.6.3 Workflow: Liabilities Management.....................................................................................................19



6.6.4 Rules: Liabilities Management..........................................................................................................196.6.5 Use Case Description: Request AU..................................................................................................20

6.6.5.1 AU Borrower Info Page..............................................................................................................206.6.5.1.1 Add Borrower.........................................................................................................................20

6.6.5.2 AU Loan Information Page.........................................................................................................206.6.5.3 AU Declarations Page................................................................................................................206.6.5.4 AU Assets Page......................................................................................................................... 206.6.5.5 Use Case Description: AU Liabilities Management – omit and modify.......................................216.6.5.6 Use Case Description: Liabilities Management – add liability....................................................226.6.5.7 AU Product / Pricing Page.........................................................................................................226.6.5.8 Request Automated Underwriting..............................................................................................22

6.6.6 Alternate flows: Request AU.............................................................................................................236.6.6.1 Invalid Liabilities Format Error....................................................................................................236.6.6.2 Invalid Liabilities Format Error....................................................................................................236.6.6.3 Insufficient data to process AU – No credit Report....................................................................236.6.6.4 Insufficient data to process AU – under 20 fields missing..........................................................236.6.6.5 Insufficient data to process AU – over 20 fields missing............................................................23

6.7 Use Case: Manage Recommendations....................................................................................................246.7.1 Workflow: Manage Recommendations..............................................................................................246.7.2 Rules: Manage Recommendations...................................................................................................256.7.3 Use Case Description: Manage Recommendations: View Findings Report......................................256.7.4 Use Case Description: Manage Recommendations: Register..........................................................256.7.5 Alternate flows: Manage Recommendations.....................................................................................26

6.7.5.1 Invalid Submit Lock Format Error...............................................................................................26Wire Frames:.......................................................................................................................................................... 27

WF_1.0............................................................................................................................................................... 27WF_2.1 a............................................................................................................................................................ 28WF_2.1 b............................................................................................................................................................ 29WF_2.1.1............................................................................................................................................................ 30WF_2.1.2............................................................................................................................................................ 31WF_2.3............................................................................................................................................................... 32WF_3.0............................................................................................................................................................... 33WF_4.0............................................................................................................................................................... 34WF_5.0............................................................................................................................................................... 35WF_5.1............................................................................................................................................................... 36WF_6.1............................................................................................................................................................... 37WF_6.2............................................................................................................................................................... 38WF_6.3............................................................................................................................................................... 39WF_6.4............................................................................................................................................................... 40WF_6.5............................................................................................................................................................... 41WF_6.5.1............................................................................................................................................................ 42WF_6.6............................................................................................................................................................... 43WF_6.7............................................................................................................................................................... 44



WF_6.8............................................................................................................................................................... 45WF_6.8.1............................................................................................................................................................ 46WF_6.8.2............................................................................................................................................................ 47WF_6.8.3............................................................................................................................................................ 48WF_6.8.4............................................................................................................................................................ 49WF_7.0............................................................................................................................................................... 50

7.0 Approvals..................................................................................................................................................... 51

Automated Underwriting

CONDUIT presentation requirements1.0 Document Purpose

This document presents the Information Architecture (IA) of CONDUIT. This document describes use cases, UML diagrams, work flows and wire frames that will be supported by the CONDUIT System. The activities are of the User Interface itself and what functions are delivered. At this level, specific technologies for the proposed System are not identified. This document outlines what the User(s) may be presented with at a very basic flow level. This document necessarily presumes a certain level of technical and business knowledge on the part of the reader. In order to fully comprehend this document and derive maximum benefit from it, the reader should be familiar with the following documents:Automated Underwriting: Current Systems Analysis [1]Automated Underwriting: Detailed Business Requirements [2] Automated Underwriting: Signoff_AURequiredFields.pdfAutomated Underwriting: ConduitAU_SRS_Liabilitites_v1.3

2.0 What this document covers Data Flow UI flow requirements Presentation-layer– UI Requirements

3.0 Out of Scope Future AU Phases All requirements outside of the Graphical User Interface (GUI) and User flows Reporting Requirements



4.0 Use Case Maps: CONDUIT4.1 Use Case Diagram Map:

AU

Conduit

AUManage

Recommendations

Findings Report

Credit Management Services

Credit Report

Pull Credit Report

View Credit Report

Manage Liabilities

Lehman_app_support

Manage Pipeline

Request AU

Manage BorrowersRegister

Manage Assets

Product Pricing

Snapshot

manage Declarations

AU Admin

AU ADMIN

Lehman_admin

Conduit_Admin



5.0 Site map: CONDUIT

Version 03.15.2006

Prepared byPobrien

Approved byProcess

Date3/15/06

ClientAU

Conduit AU_Site Map

A DB Page1.0

Legend

Off page connector

ALServices.com0.001 Login

Aurora Connect

0.1

Conduit lending 0.01

Borrower Information

6.1

Loan Information

6.2

Request AU6.0

AU Status(decision Report)

4.0

Loan Rec.’s3.0

Pull Credit Report

5.0

Register2.0

Liabilities Management

6.5

Credit Report

5.1

Assets6.4

Declarations6.3

Price6.6

Request AU6.7

401 info2.1

Submit/ confirm

2.1.1

Register AU9.0

Pipeline1.0

Results2.1.2

Report2.1.3

Quick Start Guide PDF

2.2



6.0 CONDUIT Use Cases6.1 Use Case: Manage Pipeline

6.1.1 Workflow Summary: Manage PipelineWorkflow Step Workflow Description Rules

1.0 User selects Conduit from Alservices.com and logs in

User must have valid lehmanlive ID

1.0.1 Error page if invalid Invalid form entry, system failure, or invalid ID

1.1 System presents user with pipeline where they can manage loan workflow

6.1.2 Workflow: Register

Process

Initial State

Final State

Legend

Decision

Page1.0

AC Error messaging

Conduit Log in

1.0Log in ID ID

invalid form entry

Pipeline1.1

valid

invalid

Error Page1.0.1

Valid

Form validation AC system validation

6.1.3 Use case Description: Manage Pipeline

Goal in Context

Users logs in and manages loan work flow through pipeline

Actor(s) ALS_Conduit, Lehman_app_support and Lehman_Admin



Precondition(s) User has a lemanlive id and access to “Conduit” section of alservices.com. User has logged into alservices.com, selected “Conduit” link and selected “pipeline” from top nav. User has either inputted or imported a 1003. Or inputted a 401.

Primary Post Conditions(s)

User successfully manages a loan through the pipeline workflow

Alternate Post Conditions(s)

See error handling in Alternate Flows

Trigger User has selected the Pipeline tab from the AC home page.

Main Success Scenario

STEP Action

1. This use case begins when the ALS_Conduit enters ALServices.com and selects “Conduit” from the top navigation.

2. The system presents the user with a log on page.

3. The user inputs user ID and Password and submits.

4. The System validates user id and presents the user with the CONDUIT Home page.

CONDUIT Home Page contains: View WF_0.1

5. From the AC home page, user selects “Pipeline” tab.

6. System returns View Pipeline Page (see WF_1.0 for screen) with Summary view and with following sections:

Search Filter Pipeline

7. User searches for loan using Search drop down and corresponding text field:

Loan Number Last Name Property Address Social Security Number (SSN)

8. System returns Loans matching search Criteria

9. User filters pipeline results via dropdown in Search Filter section: Current Loans not closed (<45 days)* Submitted but not locked loans Input but not submitted loans Locked Loans Locks expiring in 5 days Closed Loans Funded within last 30 daysCanceled/Denied All Loans All Loans not closed All Loans Submitted to AU All Loans with Entry Date All Loans status not = N/A

*Default value10. System returns loans matching filter selection



11. Once search and filter is complete, user selects loan using linked Loan # field or Borrower Name field.

12. System returns 1003 screen, use case ends.

Alternate Flows

Step Branching Action

Step 2A More than 150 loans returned in pipeline search

1. System determines more than 150 loans returned in Pipeline for user

2. System returns message at bottom of screen:181 results returned. Only 150 results displayed. Please refine your Criteria

3. User refines search/Filter criteria

4. Main Flow steps 3 – end same

Step 3A User selects value from dropdown and does not enter corresponding value

1. Main flow steps 1 – 3 same

2. User selects value from Search dropdown, but does not enter value for dropdown selection

3. System returns error:Please enter valid search criteria

4. User selects “ok” from error window

5. User corrects search criteria

6. Main use case steps 4 – 7 same

Step 6A User selects Loan Status or Lock Status links from loan line

1. Main flow steps 1 – 5 same



2. User selects Loan Status link from loan with Valid Status link. Valid Statuses are:

Registered Submitted Float Closed Funded last 30 days Canceled Awaiting Float Awaiting Lock Funded Approved Denied Docs Drawn In Process Suspended Withdrawn Not Submitted Loans

3. System returns Loan Status page or Submit/Lock page

4. Use Case Ends

SUB-VARIATIONS

Branching Action

Error condition when user selects Loan Status link when loan status = None.

5Aa 1. Extension 5A steps 1 same

2. User Selects Loan Status where loan status = none

3. System returns error message:This loan has not be submitted, Please submit the load to view status

4. Extension 5A steps 3 – end same.



6.2 Use Case: View Snapshot

6.2.1 Use case Description: View Snapshot

Goal in Context

ALS_Conduit views the snapshot interface


Precondition(s) User has a lemanlive id and access to “Conduit” section of alservices.com. User has logged into alservices.com, selected “Conduit” link and selected “pipeline” from top nav. User has either inputted or imported a 1003.


ALS_Conduit successfully views the snapshot interface on all the applicable pages



Trigger User has selected a page loan detail page from pipeline


STEP Action

1. This use case begins when the ALS_Conduit selects one of the following pagesRegister/401 section:

401 Information (WF_2.1a and WF_2.1 b) Register Confirm (WF_2.1.1) Loan Submission (WF_2.1.2)

Automated Underwriting Section: Borrower Information Loan Information, Declarations Info Assets Info, Liabilities Management and Product Price All Request Automated Underwriting pages

2. The system presents the user with the selected page and the snapshot view The Snapshot contains:Header: Loan SnapshotSub Header: Borrower = "B1 last name"Sub Header: Address = "Prop Street # & Name”Grid elements:

None/Not Done Done

Grid Program N/A or "select""program name"

Grid Register Status

Not Started | Errors | Incomplete Registered

Grid Credit Status N/A Received

Grid AU Status N/A"decision"



6.3 Use Case: Register6.3.1 Workflow summary: Register

Workflow Step Workflow Description Rules

1.0 User selects register from pipeline and inputs register data if necessary

Pre-populate input fields if user selects a loan from pipeline

1.0.1 Error page if invalid Invalid form entry, system failure, or invalid ID

1.1 System presents user with summary screen. User submits

User must have filled in valid fields

1.2 System presents user with register report summary and a report

Report opens in new browser window

6.3.2 Workflow: Register

ProcessInitial State

Final State

Legend

Decision

Page1.0

Submit ACRegister Report

1.2valid

invalid

Error Page1.0.1

System validationRegister

Register review

1.1Submit for register

Register info1.0

Register AC valid

System validation

AU Error messaging

invalid form entry

6.3.3 Use Case Description: Register

Goal in Context

Users registers a Loan




Precondition(s)

User has a lemanlive id and access to “Conduit” section of alservices.com. User has logged into alservices.com, selected “Conduit” link and selected “pipeline” from top nav.


User successfully registers a loan through the pipeline workflow



Users logs in and manages loan work flow through pipeline

Trigger User has selected “register” from pipeline


STEP Action

1. This use case begins when the ALS_Conduit selects “register’ from the pipeline loan action.

2. The system presents the user with the Register Form.CONDUIT Register Page contains: View WF_2.1 a and WF_2.1 b

3. The System will pre-populate the register form if the user has uploaded a 1003 for a loan to register.

4. The user inputs any additional required fields and selects the “register” button.

5. The system validates the information and presents the user with a Confirm Registration Details screen.CONDUIT Registration Confirm page contains: View WF_2.1.1

6. The user verifies the data is correct and “submits”.

7. The system presents the user with a confirmation page and a Register report.CONDUIT Results Page contains: View WF_2.1.2

8. The system also presents the user with a “Register Report that pops up in a new window.CONDUIT Register report: View WF_2.1.3 *(need to get screen shot)

9. The use case ends when the user is presented the “Register Report”

Alternate Flows


Step 2A Invalid Format Error

1. On “Register info” page WF_2.1 a or WF_2.1 b the user enters an invalid format in text box field

2. The System returns the User to the “Register info” page WF_2.1 a or WF_2.1 indicating which field was incorrectly formatted – following CONDUIT standard error messaging.

3. The User corrects their invalid errors and submits

4. The System submits validates and completes Use Case.

Step 2A Missing required Data



1. On “Register info” page WF_2.1 a or WF_2.1 b the user does not compete all required fields

2. The System returns the User to the “Register info” page WF_2.1 a or WF_2.1 indicating which field are missing – following CONDUIT standard error messaging.

3. The User fills in the missing fields and submits

4. The System submits validates and completes Use Case.



6.4 Use Case: Request Credit Report6.4.1 Workflow summary: Request Credit ReportWorkflow Step Workflow Description Rules

1.0 User selects request credit from the pipeline for the loan the user wishes to pull credit for

System informs user in Credit status if the credit needs to be pulled by indicating view or request – user can only request credit from the “request” link

1.1 The user inputs the borrower(s) information into the required credit report form fields

System retrieves Credit report from CMS

1.0.1 Error page if invalid Invalid form entry or system failure

1.2 System presents user with credit report form

6.4.2 Workflow: Request Credit Report

Request credit form

1.1submit

Pipeline1.0

AU Error messaging

AU CMS

invalid form entry

Credit Report1.2valid

invalid

Error Page1.0.1

Valid

System validationRequest Credit Flow

6.4.3 Use Case Description: Request Credit Report

Goal in Context

ALS_Conduit uses CONDUIT to request/view credit report




Precondition(s)

User has a lemanlive id and access to “Conduit” section of alservices.com. User has logged into alservices.com, selected “Conduit” link and selected “pipeline” from top nav. User has either inputted or imported a 1003.


ALS_Conduit successfully pulls Credit report data into users pipeline



Trigger User has selected “pull credit report” from pipeline


STEP Action

1. The user selects “request credit” link in the “credit status” column from the pipeline or from the action drop down for the loan/borrower the user wishes to pull credit for. The credit status messages to the user whether credit has been pulled on the borrower for the loan. To submit a loan to Automated Underwriting Credit must be pulled.

2. After the User selects request credit, the system presents the user with a Credit request form.CONDUIT Request Credit page contains: View WF_5.0

3. The system inputs the borrower(s) information into the required text fields

4. The user verifies the information is correct and submits.

5. The system retrieves the Credit report from CMS (credit management Services) and displays the requested credit report(s).CONDUIT Requested Credit Report page contains: View WF_5.1

Alternate Flows


Step 1A Invalid CMS Format Error

1. On “Request Credit” page WF_5.0 User enters an invalid format in text field

2. The System presents the User with the “Request Credit” page indicating which field was incorrectly formatted – following CONDUIT standard error messaging.

3. The User corrects their invalid errors and submits

4. The System submits valid CONDUIT Request Credit Page and completes Use Case.



6.5 Use Case: View Credit Report

6.5.1 Rules: View Credit ReportWorkflow Step Workflow Description Rules

2.0 User selects “view” link in pipeline

System/user must have requested/pulled credit report to view. CMS manages permissions

2.0.1 System error – unable to request or present credit report

CMS manages permissions

2.1 System presents user with credit report form

6.5.2 Workflow: View Credit Report

Pipeline2.0

View Report AUCredit Report

2.1valid

invalid

Error Page2.0.1

System validation

Request Credit

View Credit Flow

6.5.3 Use Case Description: View Credit ReportGoal in Context ALS_Conduit uses CONDUIT to request/view credit report

Actor(s) ALS_Conduit, Lehman_app_support and Lehman_Admin)

Precondition(s) ALS_Conduit has logged in and selected “CONDUIT” link, from Shared Services page. ALS_Conduit successfully pulled credit report.


ALS_Conduit successfully views Credit report



Trigger User has selected “pull credit report” from pipeline




STEP Action

1. The user selects “view” link in the “credit status” column from the pipeline for the loan/borrower the user wishes to pull credit for. The credit status messages to the user whether credit has been pulled on the borrower for the loan. To submit a loan to Automated Underwriting Credit must be pulled.

2. The system retrieves the Credit report from CMS (credit management Services) and displays the requested credit report(s).CONDUIT Requested Credit Report page contains: View WF_5.1

Alternate Flows Step Branching Action

Step 1A System Error

1. On pipeline page WF_5.0 User enters a valid format in text field

2. The System is unable to process the User data

3. The User is presented with an error screen that informs them that there was a problem with processing their request and to attempt the update at a later date



6.6 Use Case: Request AU6.6.1 Rules: Request AU


1.0 User selects a loan from the pipeline and requests AU

Must have selected a loan to run AU

1.0.1 System validates that the user has submitted a valid loan for AU – if missing data presented error page

System validates 1003 input/ import, credit report for each borrower and required AU fields

1.1 User presented Manage borrower page

By default first page the system presents to the user after selecting request from AU from pipeline

1.2 User can manage Loan information before submitting

Can submit to AU from this page

1.3 User can manage Declaration information

Can submit to AU from loan information page

1.4 User can Manage Asset information


1.5 User can ManageLiabilities


1.6 User can get Product/Price info for loan


1.7 AU confirmation page after requesting AU from the left nav

System generates a summary view for the user to verify loan data

1.0.1 System error page – user has not inputted correct data or is missing data – user will follow error handling process

System validates loan data for AU

1.8 After submission the user is presented the loan recommendations page to view the AU findings report

System generates findings report





6.6.2 Workflow: Request AU

Manage Loan

information1.2

Manage Liabilities

1.5

Initial State

Final State

Legend

Decision

Page1.0

Pipeline1.0

Request AU AU

Manage Borrower

information1.1

Request

invalid

Error Page1.0.1

System validation

Import/input 1003 data

Manage Asset

information1.4

Manage Declaration information

1.3

Product/Price 1.6

Review AU1.7

valid

AU

invalid

Error Page1.0.1

System validation

valid

Request

Input missing data

SubmitRecommendations

summary1.8

Submit

Correct

Process

6.6.3 Rules: Liabilities Management


1.0 User inputs and submits liability edits

Form validation rules

1.1 System presents user updated liabilities screen

by default the System presents all open and closed liabilities

1.0.2 Error page Form validation rules

2.0.1 Error page if no credit report Must have credit report to view liabilities

2.0 Liabilities page

2.1 Add liabilities pop up Valid format

2.0.2 Error page Form validation rules

2.2 Updated liabilities with additional liability



6.6.4 Workflow: Liabilities Management

Liabilities Mgmt.

1.0AU

Updated liabilities

1.1valid

invalid

Error Page1.0.2

System validation

Pull Credit Report

Add Loan Pop up

2.1


Final State

Legend

Decision

Page1.0

Liabilities Mgmt.

2.0Add liability

AU Error messaging

Submit AU AU

invalid form entry

Updated Liabilities

2.2valid

invalid

Error Page2.0.2

Valid

System validation

Manage: Edit Liabilities

Manage: Add Liabilities

Submit Request AU

proccess manage

Pull Credit Report

Request AU proccess

6.6.5 Use Case Description: Request AUGoal in Context ALS_Conduit uses CONDUIT to request a Automated Underwriting


Precondition(s) User has a lemanlive id and access to “Conduit” section of alservices.com. User has logged into alservices.com, selected “Conduit” link and selected “pipeline” from top nav. User has either inputted or imported a 1003.


User successfully submits a loan to Automated Underwriting





Goal in Context ALS_Conduit uses CONDUIT to request/view credit report

Trigger User has selected “Request AU” from pipeline


STEP Action

1. The user selects a loan from the pipeline and selects Run AU from the Loan action drop down.

2. The system validates that all the conditions to run AU have been theses include:

Pulled credit for all borrowers associated with the loan

All Required AU data fields have been inputted with correct data

3. The system validates the user data and presents the user with the AU Borrowers information pageCONDUIT Borrowers info Page contains: View WF_6.1

4. The User modifies data elements on Borrower Info page. Borrower Page is identical to existing 1003 page with the addition of an “add Borrowers” link.

5. The user selects the “Add Borrower” link.

6. The system presents the user the 1003 borrower page where they would add a borrower with the existing 1003 borrower page.

7. The User selects save

8. The system presents the user the pipeline page.

9. The User will need to pull credit for the additional borrowers they added to return to Automated Underwriting - UC_Pull Credit.

10. The user returns to the AU Borrowers information page

11. The system presents the user with an updated AU borrower screen with the added borrowers.The User modifies data. The user saves and continues on to the AU Loan information page by selecting “save and next”

12. The system presents the user with the AU Loan information page.CONDUIT Loan info Page contains: View WF_6.2

13. The User modifies data. The user saves and continues on to the AU Declarations page by selecting “save and next”

14. The system presents the user with the AU Declarations information page.CONDUIT Loan info Page contains: View WF_6.3

15. The User modifies data. The user saves and continues on to the AU Assets page by selecting “save and next”

16. The system presents the user with the AU Assets page.CONDUIT Assets Page contains: View WF_6.4

17. The User modifies data. The user saves and continues on to the AU Liabilities Management page by selecting “save and next”

18.



6.6.5.1 Use Case Description: AU Liabilities Management – omit and modifyThe system presents the user with the AU Liabilities page

CONDUIT Liabilities Management Page contains: View WF_6.5To manage the liabilities the user has the option of omitting a liability or editing the following:

Balance Payment Remaining Term Max Credit Limit Pay at close Pay current assets

When the user omits a liability line item, the system prompts the user to indicate a reason for the “omit”. From a drop down the user selects one of the following descriptions:

Court Assigned Debt Debt Paid by Business Debt Paid by Third Party Duplicate Not Their Account Other Paid Off Servicing Transfer

To omit a liability the user selects the check box under omit. The system presents the user with a pop up window that lists all the reasons for an omission.

CONDUIT Liabilities omit pop page contains: View WF_6.5After the user selects a reason, the user clicks save and is shown an updated Liabilities management page. The 30, 60, 90 day late period is shown when the user hovers the mouse over the Liability Account # under the Account # column.After the user inputs, modifies, or omits the editable fields the user has the option to:

Revert to Original – Reverts all the liabilities to the state that the data was first imported in

Revert to last saved – Reverts all the data to the previous save state the user submitted

Save- Saves all data on the screen for submission to AUThe user saves the new inputted data and adds a Liability.

6.6.5.2 Use Case Description: Liabilities Management – add liabilityTo add a liability, the user selects the add liability button. The system presents the user a pop up window with all the required fields necessary to add a liability.

CONDUIT Add Liabilities Management Page contains: View WF_6.5The user inputs all the required data and submits. The system validates and presents the user with an updated manage liability screen with the new liabilities added.The use case ends when the user either closes the browser window, or submits the loan data for Automated Underwriting by selecting the Request Automated Underwriting” from the left nav.The user continues on to AU Price/ Product Page.



6.6.5.3 AU Product / Pricing PageThe system presents the user with the AU Product Pricing page

CONDUIT Product / Pricing Page contains: View WF_8.6The User modifies data; functionality is similar to existing Quick Submit/Float Product Pricing Info page in Quick Submit/Float minus the loan and lock status functionality The user selects products and pricing. The system returns eligible and ineligible products. User selects eligible products for pricing and selects get pricing. The system returns pricing for eligible products. User selects price. The system returns the user to AU Product and pricing page.The user saves the requested product and pricing selections.The user continues on to Request Automated Underwriting

6.6.5.4 Request Automated UnderwritingThe user selects “Request Automated Underwriting” from the left nav of any of the AU pages. The system presents the user with the Review Request for AU page

CONDUIT Review Request for AU Page contains: View WF_6.7The user verifies that the information on the screen matches the loan they want to run for AU and selects “Validate for Automated Underwriting” button. The system validates that the user has completed all the AU required fields and presents the user with a confirmation page:

CONDUIT confirmation Request for AU Page contains: View WF_6.8.4The user selects the “submit for Automated Underwriting” button.The use case ends when the system submits the loan for AU and presents the user with the recommendations pages with the status and findings report of the Automated Underwriting.

6.6.6 Alternate flows: Request AU6.6.6.1 Invalid Liabilities Format Error

On “Liabilities Management Page” page WF_6.5 User enters an invalid format. The System presents the User with the “Liabilities Management Page” indicating which field was incorrectly formatted – following CONDUIT standard error messaging.The User corrects their invalid errors and submitsThe System presents valid Liabilities Management Page and completes Use Case.

6.6.6.2 Invalid Liabilities Format ErrorOn “Liabilities Management Page” page WF_6.5 User enters an invalid format. The System presents the User with the “Liabilities Management Page” indicating which field was incorrectly formatted – following CONDUIT standard error messaging.The User corrects their invalid errors and submits

6.6.6.3 Insufficient data to process AU – No credit ReportAfter the user has selected “Request Automated Underwriting” The system validates that the user has uploaded a credit report for all the borrowers listed in the 1003, if the credit report is missing the system will present the user with an updated AU request page that messages to the user how to pull credit report.

CONDUIT Request Automated Underwriting: View WF_6.8.2



After pulling all the necessary credit reports (UC_6.3) the user moves forward with the primary request flow (UC_6.5)

6.6.6.4 Insufficient data to process AU – under 20 fields missingAfter the user has selected “Request Automated Underwriting” The system validates that the user has input all the necessary data to submit, if the data is not complete, and there are less than 20 errors, the system will present the user with an updated Request Automated Underwriting page that displays to the user which data fields are incomplete with links that send the user to the page missing the data.

CONDUIT Request Automated Underwriting: View WF_6.8.16.6.6.5 Insufficient data to process AU – over 20 fields missing

After the user has selected “Request Automated Underwriting” The system validates that the user has input all the necessary data to submit, if the data is not complete, and there are more than 20 errors, the system will present the user with an updated FE request page that displays to the user that they will need to upload a 1003.

CONDUIT Request Automated Underwriting: View WF_6.8.3



6.7 Use Case: Manage Recommendations

Description ALS_Conduit uses CONDUIT to manage their recommendations page including viewing history of all AU submissions for the Loan and Locking the loan

Actor(s) ALS_Conduit

Precondition(s) User has a lemanlive id and access to “Conduit” section of alservices.com. User has logged into alservices.com, selected “Conduit” link and selected “pipeline” from top nav. User has submitted at least one Loan to AU


ALS_Conduit successfully views Findings Report and submits for Lock



6.7.1 Workflow: Manage Recommendations

Recommendations

1.0 View Report AUFindings

report1.1

valid

invalid

Error Page1.0.1

System validation

Request AU

View Findings Report


Final State

Legend

Decision

Page1.0

Recommendations

2.0 Submit for lock AUUpdated Pipeline

2.2valid

invalid

Error Page2.0.1

System validation

Request AU

Submit to Lock

Lock review2.1

Submit for lock

6.7.2 Rules: Manage Recommendations




1.0 User selects the link in recommendation pipe AU Status

System/user must have requested AU findings report to view

1.0.1 System error – unable to present Findings Report

Error message page

1.1 System presents user with Findings report

Report generated from AU

2.0 User selects “Submit Lock” to lock Loan

User can only lock the last run AU Loan

2.1 Lock review page Details of findings report listed

2.0.1 System error – unable to lock

2.2 Updated pipeline view After successful submission user presented updated pipeline

6.7.3 Use Case Description: Manage Recommendations: View Findings ReportThis use case begins after the user has requested Automated Underwriting. From the pipeline the user can view the AU status in the AU status column. After the system has completed AU and produced a findings report the user would select the “Traditional” or “Express” link in the AU Status bar. The system presents the user with the “Loan Recommendations” page.

CONDUIT Loan Recommendations Page contains: View WF_3.0From the Loan Recommendations page the user could view the liabilities, individual loan app builder pages or the individual findings report. To view the findings report the user selects the “Express” or “traditional” hyperlink under AU Status. The system presents the user the Findings Report associated with the hyperlink.

CONDUIT Findings Report Page contains: View WF_4.0To view liabilities from the recommendations page the user selects the “view” link under liabilities. The system presents the user with all the liabilities that were submitted to Automated Underwriting for that transaction. The system presents the user Liabilities post AU, and is unable to edit any fields.

CONDUIT Liabilities post AU Page contains: View WF_6.5.1

6.7.4 Use Case Description: Manage Recommendations: Register



This use case begins after the user has requested Automated Underwriting. From the pipeline the user can view the last run AU submission as loan on the top row with a “Register” button. The user selects “Register”. The system presents the user with the register review page:

CONDUIT Register Page contains: View WF_9.0

The user verifies that the information on the screen matches the loan they want to register and selects “Submit”. The use case ends when the system validates the request and presents the user with an updated Pipeline (WF_1.0) page.

6.7.5 Alternate flows: Manage Recommendations

6.7.5.1 Invalid Submit Lock Format ErrorOn “AU register” page WF_9.0 User enters an invalid format in text fieldThe System presents the User with the “Request Credit” page indicating which field was incorrectly formatted – following CONDUIT standard error messaging.The User corrects their invalid errors and submitsThe System submits valid CONDUIT Request Credit Page and completes Use Case.



Wire Frames:WF_0.1AU Conduit Wire Frame: WF_0.1 Conduit Home



WF_1.0

AU Conduit Wire Frame: WF_1.0 Pipeline Summary

Pipeline: Loan Summary

Pipeline:

Aurora Loan #

123456789

155456489

SSN

223-55-1234

223-55-1234

Borrower Name

Doe, John

Smith, Jane

Address

102 Central Park West, NEW YORK

11101 E. Alameda Avenue, Denver

123456789

155456489

223-55-1234

223-55-1234Jackson, Jack

Jones, Jim 102 Central Park West, NEW YORK


123456789

155456489

223-55-1234

223-55-1234Bond, James

Child, Julia 102 Central Park West, NEW YORK


AU Status

N/A

Traditional

N/A

Express

Traditional

Traditional

Register

Not Started

Incomplete

Completed

Errors

Completed

Completed

Credit StatusRequest

View

Request

View

View

View

Request AURegister Pull Credit

All LoansAll Registered Loans

Registration Status = IncompleteRegistration Status = Errors

All Loans Submitted to AU



WF_2.1 a

AU Conduit Wire Frame: WF_2.1 Register Information part A

▪ Register▪ Quick Start Guide

Register 401

Loan snapshot

AU Status N/A

Register status RegisteredCredit Status Request

Program Program name

B1 Last nameProp Street # & Name



WF_2.1 bAU Conduit Wire Frame: WF_2.1 Register Information part B

Loan Information


Register 401

Loan snapshot

AU Status N/A




Submit to RegisterCancel



WF_2.1.1

AU Conduit Wire Frame: WF_2.1.1 Registration: confirm


Register 401

Loan snapshot

AU Status N/A






WF_2.1.2

AU Conduit Wire Frame: WF_2.1.2 Registration: Results

▪ Register▪ Quick Start Guide▪ Registration History

Register 401

Loan snapshot

AU Status N/A






WF_3.0

AU Conduit Wire Frame: WF_3.0 Recommendations

Transaction ID # Run By AU StatusAU run date/

time123456789 Jane Doe Traditional08/05/2005

Program

Alt-A

ProductALT-A 15

YEAR FIXED

ALT-A 15 YEAR FIXED

ALT-A 20 YEAR FIXED

155456489 JIm Doe Express08/05/2005 Mortgage Maker

443456789 Jane Smith Express08/05/2005 Alt-A

DateView By:

ALT-A 30 YEAR FIXED

ALT-A 20 YEAR FIXED

155456489 JIm Doe Express08/05/2005 Alt-A

443456789 Jane Smith Express08/05/2005 Alt-A

| Next 5 | 1, 2, 3 | Show All | Viewing Scenarios: 1 to 5 (18 total)

Loan 12343232 Jones, Jim summary

Loan: Recommendations

Liabilitites

View

View

View

View

View

Register*

*The last AU run is considered the final



WF_4.0

AU Conduit Wire Frame: WF_4.0 FE Findings Report

Findings Report Print Email



WF_5.0

1 100%First | Next | Prev | Last | Report: of 5 View:

AU Conduit Wire Frame: WF_5.0 Credit Report

Credit Report

ACME Conduit



WF_5.1

Request Type:Select

AU Conduit Wire Frame: WF_5.1 Pull Credit Report

Pull Credit Report

Overwrite LiabilitiesYes No



WF_6.1


▪Borrower Information▪ Loan Information▪ Declarations Info ▪Assets Info▪ Liabilities Management▪ Product Price▪ Request Automated Underwriting

AU Conduit Wire Frame: WF_6.1 AU Borrower Information

Loan snapshot

AU Status N/A

Register status RegisteredLock Expiration Show dateCredit Status Request

Program Program nameLoan status Submit


Commitment #



WF_6.2

AU Conduit Wire Frame: WF_6.2 AU Loan Information

AU Loan Information


▪Borrower Information ▪Loan I nformation▪ Declarations I nfo ▪Assets I nfo▪ Liabilities Management▪ Product Price▪ Request Automated Underwriting

There will be a 2nd

Loan snapshot

AU Status N/A






WF_6.3

AU Conduit Wire Frame: WF_6.3 AU Declarations

AU Loan Declarations


▪Borrower Information▪ Loan Information ▪Declarations Info ▪Assets Info▪ Liabilities Management▪ Product Price▪ Request Automated Underwriting

Loan snapshot

AU Status N/A






WF_6.4

AU Conduit Wire Frame: WF_6.4 AU Assets

AU Loan Assets


▪Borrower Information▪ Loan Information▪ Declarations Info ▪Assets Info▪ Liabilities Management▪ Product Price▪ Request Automated Underwriting

Jane SmithMary Jessica Parkerbob EdwardsizinchikyMary KayJane Jones, Jim Jones

Save & Previous Save Save & Next

Loan snapshot

AU Status N/A






WF_6.5

AU Conduit Wire Frame: WF_6.5 AU Liabilities Management

AU Liabilities Management


Creditor

Finance CE

Bank One

PaymentAccount #

2112432

1231231

WeOwnU Inc.

N/A N/A

45455576

Remaining term (mos)Balance

$1,150.00

$1,750.00

$3,150.00

$150.00

$150.00

$50.00

$350.00

$10.00

6

12

48

N/A

Revert All to original Revert All to last saved Add Liability

Omit

LiabilitiesPay at close

Pay Current Assets

Total Liabilities $76,000.00

Add LiabilitiesAdd Liabilities

Max. Credit Limit

$1150.00

$500.00

$3500.00

$100.00

Total Monthly Payments $750.00

Borrower *

Type *

Creditor *

Account # *

Balance *

Payment *

Remaining Term

Max. Credit limit

Owed to

Jim Jones

Collections Judgements and Liens

$

$

$

Save Cancel Clear

Save


▪Borrower I nformation▪ Loan I nformation▪ Declarations I nfo ▪Assets Info ▪Liabilities Management▪ Product Price▪ Request Automated Underwriting

View

View

View

View

Revert All to 1003 liabilities

Loan snapshot

AU Status N/A




Omit LiabilityOmit LiabilityPlease select a reason for omitting this selection from the FE submission. NOTE: This will only Omit this liability from the Full Evaluation submission”.

To Be Paid Off from Proceeds and maps to Condition at Closing

To Be Paid off from Verified Assets and maps to Condition at Closing

To Be Paid Down from Proceeds and maps to Condition at Closing

To Be Paid Down from Verified Assets and maps to Condition at Closing

Exclude\Omit

Save Cancel



WF_6.5.1

AU Conduit Wire Frame: WF_6.5.1 AU Liabilities Management post submit

AU Liabilities Management


▪Borrower Information▪ Loan Information▪ Declarations Info ▪Assets Info ▪Liabilities Management▪ Product Price▪ Request Automated Underwriting


Creditor

Finance CE

Bank One

Payment

$150.00

$50.00

Account #

2112432

1231231

WeOwnU Inc.

N/A

$350.00

$10.00N/A

45455576

Remaining term

6

12

48

N/A

Balance

$1,150.00

$1,750.00

$3,150.00

$150.00

Omit

View

LiabilitiesPay at close

No

No

Yes

Yes

Pay Current Assets

No

No

No

Yes

Total Liabilities 76,000.00

Max. Credit Limit

$1150.00

$500.00

$3500.00

$100.00

Total Monthly Payments 750.00

Loan snapshot

AU Status N/A




Omit LiabilityOmit LiabilityPlease select a reason for omitting this selection from the FE submission. NOTE: This will only Omit this liability from the Full Evaluation submission”.

To Be Paid Off from Proceeds and maps to Condition at Closing

To Be Paid off from Verified Assets and maps to Condition at Closing

To Be Paid Down from Proceeds and maps to Condition at Closing

To Be Paid Down from Verified Assets and maps to Condition at Closing

Exclude\Omit

Save Cancel



WF_6.6

AU Conduit Wire Frame: WF_6.6 AU Price

AU Price

Save


▪Borrower Information▪ Loan Information▪ Declarations Info ▪Assets Info▪ Liabilities Management ▪Product Price▪ Request Automated Underwriting

Save & NextSave & Previous

Loan snapshot

AU Status N/A






WF_6.7

AU Conduit Wire Frame: WF_6.7 Review Automated Underwriting

Review Automated Underwriting

Validate for Automated Underwriting

Loan Number : 0032238172

Address Line One: 10267 Sandia Creek Drive

Borrower Name: Jane Doe

Product Code: J10L

Loan Amount: $ 2,000,000.00

Total Income: $12,000.00

Total Assets: $ 3,000,000.00

Total Liabilities: $ 76,000.00

PrintCancel


▪Borrower Information▪ Loan Information▪ Declarations Info ▪Assets Info▪ Liabilities Management▪ Product Price ▪Request Automated Underwriting

Loan snapshot

AU Status N/A






WF_6.8

AU Conduit Wire Frame: WF_6.8 Review Automated Underwriting


We're sorry. We are unable able to run Automated Underwriting at this time. Your loan contains 5 missing fields. Select the “Complete Automated Underwriting” button below to enter the missing data. Once the information has been completed, click “Request Automated Underwriting”

Required Data fields missing:Loan Documentation Type

Amortization Term





Product Code: J10L

Loan Amount: $ 2,000,000.00


Total Assets: $ 3,000,000.00


PrintCancel



Loan snapshot

AU Status N/A






WF_6.8.1

AU Conduit Wire Frame: WF_6.8.1 Review Automated Underwriting


We're sorry. We are unable able to run Automated Underwriting at this time. Your loan contains 5 missing fields. Select the “Complete Automated Underwriting” button below to enter the missing data. Once the information has been completed, click “Request Automated Underwriting”

Required Data fields missing:Loan Documentation Type

Amortization Term





Product Code: J10L

Loan Amount: $ 2,000,000.00


Total Assets: $ 3,000,000.00


Print

Cancel



Loan snapshot

AU Status N/A






WF_6.8.2



ERROR Message 1:

We're sorry. We are unable to run Automated Underwriting at this time. You must request a credit report to complete Automated Underwriting.

To request a credit report click here





Product Code: J10L

Loan Amount: $ 2,000,000.00


Total Assets: $ 3,000,000.00


PrintCancel



Loan snapshot

AU Status N/A






WF_6.8.3



ERROR Message 1:

We're sorry. We are unable to run Automated Underwriting at this time. You must request a credit report to complete Automated Underwriting.

To request a credit report click here





Product Code: J10L

Loan Amount: $ 2,000,000.00


Total Assets: $ 3,000,000.00


PrintCancel



Loan snapshot

AU Status N/A






WF_6.8.4

AU Conduit Wire Frame: WF_6.8.4 Complete Automated Underwriting

Complete Automated Underwriting

You have completed all the necessary fields to Run a Automated Underwriting. Please select the “complete Automated Underwriting” button below to submit this loan to Automated Underwriting

CancelComplete Automated Underwriting




Product Code: J10L

Loan Amount: $ 2,000,000.00


Total Assets: $ 3,000,000.00




Loan snapshot

AU Status N/A






WF_7.0

AU Conduit Wire Frame: WF_7.0 AU Register

Automated Underwriting Register

Findings Report info




Product Code: J10L

Loan Program:

Loan Product:

Price Code:

Lock Period:

Pricing effective period:



Loan snapshot

AU Status N/A




Register loan


lsinglet, 03/15/06,

Take out lock period


7.0 ApprovalsThis document has been reviewed and approved by the project sponsor(s) and stakeholder(s), as evidenced by the signatures below.

_______________________________________ ______________Vic Pepe Date

_______________________________________ ______________Michael Kolbrener Date

_______________________________________ ______________Dana Chrisfield Date


Documents

AU_Presentation_reqsactivitysystems.com/wp-content/uploads/2012/08/Conduit... · Web viewInformation Technology Division Project: Automated Underwriting Topic: AU Broker Presentation