2017-0030 LANDLORD RELATIONSHIP MANAGEMENT SYSTEM
FUNCTIONALITY MATRIX Please utilize this form to document the proposed systems's ability to provide the described functionality as reference in the Scope of Work (a.-o.). For each descrption referenced, please use the Category Code Reference Guide (by inserting one or more of the category codes F2, CO, CU, NA) to indicate, in the appropriate section, the functionality and characteristics of the software application. If additional narritave is necessary, please attach an additional sheet (while also referencing the appropriate Description letter, i.e. a., b., or c.) to further explain the system's capability to perform the described functionality. Please be sure to consolidate the files and upload one file as your response to Question No. 2.2.
CATEGORY CODE REFERENCE GUIDE F2
Fully provided "Out of the Box"
CO
Configuration (table set-up required, no changes to sorce code)
CU
Cusomization (requiring changes to source code)
NA
Not Available
DESCRIPTION
F2
CO
CU
N/A
a. Does the proposed system have the ability for new customers to create a guest account using their property address? It should require a password at least nine (9) characters in length and consist of numbers and upper and lower case letters. b. Does the proposed system have the ability for customers to request a new password through the Landlord Relationship Management System that will be automatically generated and sent to the email address on file? c. Does the proposed system have the ability for customers to update and view profiles and report delivery preferences, including paperless communication or preferred contact method? d. Does the systems have the ability for customers to easily review and track changes made to their profiles? e. Does the proposed system have the ability for AHA to upload and utilize existing AHA forms without modification? f. Does the proposed system have the ability for customers to upload, complete, e-sign and submit documents such as IRS 1099 Forms or existing AHA forms? g. Does the proposed system possess field validation for forms requiring customer input or other workflow process checks, as defined by AHA, prior to acceptance of forms? h. Does the sytem have the option for customers to opt in/out of features and notifications? j. Does the system have functionality to personalize the system with AHA's brand identity, logo, colors, fonts, etc. and the ability tof the sytem to be easily translated into multiple languages to meet customer needs? k. Does the proposed system have the ability to provide data interfacting with AHA's ERP system via Application Programming Interface, batch scripted or other such connectors? l. Does the proposed system allow features or elements to be enabled or disabled on a user role basis? m. Does the proposed system have the ability for customers to accesss, view and print details, including payments, track document processing status and related reports, property reports and inspection reports, create custom reports, and update payment and bank information? n. Does the system have the functionality to enable two-way commnication exchanges between AHA and customers, including, e-signed documents, alerts and messaging? o. Does the system allow AHA support staff to log into the system and "see what the customers see"? _______________________________________________ SUBMITTED BY (COMPANY NAME)
CATEGORY CODE REFERENCE GUIDE F2
Fully provided "Out of the Box"
CO
Configuration (table set-up required, no changes to sorce code)
CU
Cusomization (requiring changes to source code)
NA
Not Available
DESCRIPTION
F2
CO
CU
N/A
a. Does the proposed system have the ability for new customers to create a guest account using their property address? It should require a password at least nine (9) characters in length and consist of numbers and upper and lower case letters. b. Does the proposed system have the ability for customers to request a new password through the Landlord Relationship Management System that will be automatically generated and sent to the email address on file? c. Does the proposed system have the ability for customers to update and view profiles and report delivery preferences, including paperless communication or preferred contact method? d. Does the systems have the ability for customers to easily review and track changes made to their profiles? e. Does the proposed system have the ability for AHA to upload and utilize existing AHA forms without modification? f. Does the proposed system have the ability for customers to upload, complete, e-sign and submit documents such as IRS 1099 Forms or existing AHA forms? g. Does the proposed system possess field validation for forms requiring customer input or other workflow process checks, as defined by AHA, prior to acceptance of forms? h. Does the sytem have the option for customers to opt in/out of features and notifications? j. Does the system have functionality to personalize the system with AHA's brand identity, logo, colors, fonts, etc. and the ability tof the sytem to be easily translated into multiple languages to meet customer needs? k. Does the proposed system have the ability to provide data interfacting with AHA's ERP system via Application Programming Interface, batch scripted or other such connectors? l. Does the proposed system allow features or elements to be enabled or disabled on a user role basis? m. Does the proposed system have the ability for customers to accesss, view and print details, including payments, track document processing status and related reports, property reports and inspection reports, create custom reports, and update payment and bank information? n. Does the system have the functionality to enable two-way commnication exchanges between AHA and customers, including, e-signed documents, alerts and messaging? o. Does the system allow AHA support staff to log into the system and "see what the customers see"? _______________________________________________ SUBMITTED BY (COMPANY NAME)
