AGFG Online Member Portal RFP FAQ

Technical documentation for the Membership Application and Deposit Tracking System is not available for distribution at this juncture but will be provided to the selected respondent at the appropriate stage of engagement.

Secure direct database access will be supported. We are also open to REST or SOAP integrations, provided they are compatible with our system requirements.

Details regarding the key data objects or fields expected to be exchanged between systems cannot be disclosed at this juncture but will be made available to the selected respondent at the appropriate stage.

New user registration should be managed via the Member Portal itself.

There are no specific requirements for MFA. SMS OTP, Google Authenticator, and Microsoft Authenticator are all acceptable options.

AGFG does not have a defined preference for user account management. The solution may rely solely on internal user accounts or integrate with external identity providers (e.g., SSO, LDAP, OAuth2), based on what is most suitable for the proposed architecture.

Per the RFP, we are seeking a cloud-based hosting model.

Per the RFP, AGFG is open to various approaches and does not require a specific set of technologies per se, however AGFG is currently using and prefers Microsoft SQL Server and VB.NET applications as its core tools, and therefore it is important to AGFG that the Online Member Portal be integrated with those tools and is flexible enough to efficiently handle future integrations and updates.

The minimum requirement includes both a Production and a UAT environment. Additional environments such as DR and Staging environments may be considered as needed.

AGFG has no preference regarding the hosting region.

Per the RFP [page 3, General Requirements], we are seeking a cloud-based hosting model and are open to various providers, however it is important to AGFG that the Online Member Portal be integrated with it core tools (Microsoft SQL server and VB.NET) and is flexible enough to efficiently handle future integrations and updates.

There aren't any restrictions regarding data residency. A sandbox or staging environment for UAT is required for development and testing.

AGFG is open to both an out-of-the-box solution like a standard AMS, provided it aligns well with our requirements, as well as a custom-developed option if that proves to be a better fit. Our priority is finding a solution that best supports our current and future needs for the Online Member Portal, so we're evaluating all viable approaches.

The approximate user base is 600 and could be more or less. The expected number of concurrent user logins is something we can't really quantify at this time due to the nature of our current system.

Yes, data migration of existing member records and reporting will be required. That data currently resides in Microsoft SQL Server databases and Image Right, which is our imaging system.

The portal is expected to provide detailed logging of user activities as a primary requirement. In addition, general system-level event logging should also be implemented to support a comprehensive audit trail.

At this juncture, AGFG does not require any additional compliance beyond HIPAA and GDPR. However, we reserve the right to introduce additional compliance requirements, such as SOC 2, FedRAMP, or state-specific standards, if they are deemed necessary in the future.

Payment processing will not be a function of the online member portal; therefore, PCI DSS compliance is not required.

The online member portal will not support any financial transactions, including payment of member assessments or reconciliations. As such, there is no preferred or existing payment processor to be considered.

The details of our data retention policy cannot be shared at this juncture but will be provided to the selected respondent during the next phase of the process.

AGFG prefers that 24/7 technical support for critical items be available post go-live. However, for general non-critical issues, support during standard business hours is acceptable.

AGFG expects response and resolution times to follow industry best practices, with prioritization based on incident severity. Detailed service-level targets will be established in coordination with the selected vendor during the contractual phase.

AGFG expects that regular data backups will be conducted as part of standard operational procedures. Adequate data redundancy and disaster recovery capabilities must be implemented to ensure business continuity and minimize the risk of data loss or extended system outages.

Yes, AGFG requires the provision of comprehensive training materials, user documentation, and live training sessions to support both members and internal staff during the rollout and ongoing use of the system.

Yes, the selected respondent should provide ongoing training as new features are rolled out to ensure users remain informed and proficient with system updates.

AGFG's vendor evaluation process is outlined in the RFP on page 10 under the 'Selection Process' section. Beyond cost, the evaluation will take into account the vendor’s experience, technical approach, and references.

A predefined budget range cannot be shared at this juncture but will be discussed with the selected respondent during the negotiation phase of this process.

Yes, AGFG will designate a dedicated internal resource—such as a product owner or technical lead—to actively support and facilitate the implementation process.

User acceptance testing (UAT) procedures will be developed as part of the implementation process, and defined acceptance criteria must be met before the system is deployed to production.