ATTACHMENT A
OHCS System Requirements
NOTE: Proposers must have the capability at the time they submit a proposal to meet the mandatory requirements noted below. Proposals that do not meet all the mandatory requirements will not be considered for this RFP.
If however Proposer cannot currently provide a mandatory requirement, Proposer should note in the Description/Comment section whether the mandatory requirement will be fully met in a planned upgrade scheduled for release within six months of Proposer’s response.
Proposer Response:Y- Yes, fully meets
N- Not supported
(For N, provide plan for meeting requirement)
Requirement / Mandatory / Desirable / Meets? / Proposer Comments: description of plan to meet,proposed solution, work around.
- Ability to configure customizable risk criteria to create unique risk tolerance based on Department and industry criteria (including financial and property inspection criteria) with tools to analyze the results from a deal or portfolio level.
- Facilitate collection of financial data into the Systemdatabase.
- Adaptive Financial Analysis: ability to make calculations and analyze ALL Federal & State Tax Credit, Loan and Grant programs administered by OHCS
- System will provide comprehensive document management capability:
- Import/Export of files
- System will calculate risk ratings using compliance and physical inspect ratings, financial analysis outcomes and submission of required reports and/or responses collected within the database.
- System will facilitate business process workflow:
- Manage affordable housing projects from application/origination through development
- Manage asset management and compliance work flows
- Track workflow activities:
- Record stage changes in development projects
- Track asset management/compliance status
- Notifications and alerts based on role
- Set and manage reminders for activities/workflow tasks.
- Facilitates role based system rights:
- Staff
- External Partners.
- Associate staff/roles with a project or asset workgroup
- Reconcile annual and audited financial statements including auditor’s findings and notes.
- GUI based Ad-hoc reporting:
- Based on database fields and calculations
- Export to multiple formats (excel, scv, xml)
- Saved reports for later use
- Record audit tracking:
- Records changes made, time and user that made the change
- Excel and Word integration. The ability to push or pull data directly into or out of the System from Excel or Word documents
- Facilitates funding program management
- Manages funding draw workflow
- Live mapping of asset location with driving directions (like Google maps)
- Multi-Tennant property physical inspection tool:
- Mobile friendly
- REAC compatible
- Attach photos
- Can work without data connection
- Sync once data connection available
- Import all rent and income limits from HUD/MTSP in the file format provided by HUD/MTSP
- Secure Partner Web Portal
- Tennant data reporting (NAHMA 3.0 Compliant)
- Manual data entry capability
- Compliance testing
- Partner document submission
- Partner authentication
- Form and data validation
- Provides failure feedback to partner
- Scattered/Multi site management
- Ability to attach multiple applications per project
- Comprehensiverecord search capability
- Fee/Invoice management:
- Integrates with a notification/warning/reminder system
- Comprehensive mass mail/email functionality
- Ability to manage on-site inspections for construction and capital needs improvements
- System must be scalable to meet OHCS future needs.
- System must be browser-based and must have a user interface that has a common look and feel across all applications.
- System must be web-based and browser, platform and device independent.
- System must be built on multi-tier architecture, for example, presentation tier, business logic tier and data storage are maintained as independent tiers.
- System must operate on industry standard hardware, operating systems, application servers, storage and relational database management systems.
- System must provide multiple options for exchanging data with internal and external customers (e.g., Secure FTP, Web Services, etc)
- System must support on-premises implementation at Oregon Enterprise Technology Services (also referred to as State Data Center) in the event of a need arising to bring the system in-house.
- A hosted COTS or SaaS Systemmust have an uptime of __99.90%__. Uptime shall not include scheduled time for appropriate maintenance and upgrades.
RFP DASPS-2137-17 HOUSING AND COMMUNITY SERVICES DATA MANAGEMENT SYSTEM MODERNIZATIONAttachment A