Implementing the Google Maps Extension involves planning for licensing, coordinating API access, validating functionality, and ensuring alignment with Bonterra’s implementation methodology. This methodology must be followed closely to prevent issues with functionality or future compatibility.

The following steps will guide you through the implementation process for this extension, from initial planning through post-implementation management.

Pre-implementation planning

Step 1: Define your requirements

• Identify which proposal types (e.g., volunteer event registration) will require Google Maps functionality.
• Document how the map integration should support event creation, search, and sign-up workflows.

Step 2: Obtain a Google Maps license

• Open a Google Maps account.
• Acquire access to the following required APIs:
  • Geocoding API
  • Maps JavaScript API
  • Places API
• Ensure your license covers projected usage and complies with Google’s rate limits.

Step 3: Coordinate internal resources

• Involve your program administrators and IT teams early to confirm ownership of the Google Maps account and credentials.
• Ensure your team can manage long-term access and monitor API usage.

Step 4: Notify your Bonterra team

• Communicate your readiness to your Bonterra business analyst.
• Share API credentials securely as directed.

Implementation process

Step 5: Configuration by Bonterra

• Bonterra will enable and configure the extension within the CyberGrants environment using your licensed API access.

Step 6: User acceptance testing (UAT)

• Participate in a full testing cycle to validate the address autocompletion, embedded maps on sign-up pages, and event search functionality.
• Provide feedback and approval before deployment.

Step 7: Final approval and deployment

• Once UAT is complete and approved, Bonterra will deploy the functionality to your production environment.

Post-implementation management

Step 8: Monitor API usage

• Track usage of the Google Maps APIs via your Google Maps account to ensure you do not exceed your quota.

Step 9: Review functionality annually

• As only one update is allowed per year within scope, review your needs in advance before requesting changes.

Step 10: Prepare for change requests

• Be aware that post-deployment changes outside the approved scope may require additional scoping, cost, and time.

Step 11: Maintain communication with Bonterra

• Maintain an open line of communication with your Bonterra business analyst for support, future enhancement discussions, or technical troubleshooting.

By following these best practices and steps, you will ensure a successful and sustainable implementation of the Google Maps Extension in your CyberGrants platform.

What else do you need help with?