Atlanta Housing requires the following list functionalities of the Respondent’s system: a. Ability for new customers to create a guest account. It should require a password of at least nine (9) characters in length and consist of numbers and upper- and lower-case letters. b. Ability for customers to request a new password through the LRMS that will be automatically generated and sent to the email address on file. c. Ability for customers to easily update, review and track changes made to their profiles. d. Ability for AH to upload and utilize existing AH forms. e. Ability for customers to utilize web-based smart forms to complete, e-sign and submit documents such as Request for Tenancy Approval (RTA), new Property Owner Applications (POAs), IRS 1099 Forms or any other existing AH forms. We would like for the vendor chosen to assist with the development of these forms and the submission process. f. Field validation for forms requiring customer input or other workflow process checks such as the uploading of supporting documentation, as defined by AH, prior to acceptance of forms. g. Allow the landlord to electronically complete and submit an application form (Request for Tenancy Approval). The form should be web-based and be smart enough to recognize if the landlord requests a rental amount for a unit that is higher than AH’s payment standard. AH’s payment standards are based on the number of bedrooms in the unit and the particular submarket that the unit is located in. The form should also be smart enough to recognize if the unit is not located in AH’s jurisdiction. h. Option for customers to opt in/out of features and notifications. i. Ability for AH to promote and drive participation in AH’s landlord services programs through targeted marketing. j. Personalization with AH’s brand identity, logo, colors, fonts, etc. and the ability of the system to be easily translated into multiple languages to meet customer needs. k. Ability of the system to provide data interfacing with AH’s ERP system via Application Programming Interface (“API”), batch, scripted or other such connectors. l. Configurability of the system to allow features or elements to be enabled or disabled on a user role basis. m. Ability for customers to access, view, export and print details, including payments, track document processing status and related reports, property reports and inspection reports, and update payment and bank information. n. The ability to combine all payment types into a single ledger.
