Addressing ATM + branch locator requests

Our engineering team helps set up, maintain, and migrate locations for the ATM + branch locator used on our Banno CMS sites as well as our online and mobile apps. For new implementations, we engage with engineers during initial setup to prepare the locator to work on the new website and also engage with them to migrate locations from the pre-launch environment to the production environment as we prepare for site launch. Post-launch, engineers may need to be engaged as ATM + branch locator setup needs change for each institution.

Requesting ATM + branch locator setup

During implementation, the ATM + branch locator will need to be set up for each institution to ensure it is functional on the new site, includes the right networks for the institutions, and will allow for new branch and ATM locations to be added prior to website launch. To request setup, engage with engineers by opening a ticket in Jira.

1. Access the ATM Locator project.
2. Select Create (+). Note: Each issue should cover a single institution.
3. Project: ATM Locator (ATM)
4. Issue Type: ATM Locator Setup
5. Summary: title the issue using a succinct but specific description of the request. For these requests, the summary should begin with the institution name, followed by ‘ATM Locator Setup’, then jSource number (ex: ‘Ovation Bank: ATM Location Setup - #22222’).
6. Description: provide any additional details that may be helpful to engineers as they complete locator setup.
7. Attachment: attach any files related to the request, if applicable.
8. Pre-Launch URL: indicate the pre-launch URL that has been created for the institution.
9. Live Website URL: indicate URL that will be used for the live website.
10. Custom Network: include the name and details for any custom or private networks to be set up for the institution (ex: Ovation Bank ATMs). List all custom networks that should be included.
11. ATM Network: indicate the external ATM network(s) to include as part of this institution’s locator setup, as requested by the institution during implementation. Check all that apply. Leave all unchecked if no external networks will be included.

• Accel
• Advantage
• Alliance One
• Allpoint
• AlphaLink Alliance
• American Express
• ATM Access
• BMO Harris
• Community Cash
• CO-OP
• CU$
• CU24
• CU24 No Premium
• CU Anytime
• CUHere
• CULIANCE
• CU Service Centers
• Discover
• FreedomATM
• In Balance
• InterCept
• J&J Ventures
• Kwik Trip ATMs
• Mastercard
• MoneyPass
• NetWorks
• NetWorks Surcharge Free
• NYCE
• One Stop
• Plus
• PNC
• Presto!
• Pulse
• Regions
• Shared Branch
• Shazam
• Shazam Privileged
• Sheetz
• Star
• Stripes
• SUM
• TransFund
• UltraSF
• Visa

12. Institution ID: indicate the institution ID for the institution.
13. Due Date: identify the date the setup should be completed. These requests should be set 5 business days out.
14. Click Create.

This opens the issue in the ATM Locator project in Jira and creates a link that can be used to track progress and as a reference point for discussions with the engineering team.

Requesting migration of ATM + branch locations

As part of the preparation for website launch, ATM and branch locations for an institution should be migrated from the pre-launch environment to the production environment. Doing this allows all locations that have been added in the pre-launch environment to live in the new production environment and be available on the site at launch. To request the migration of locations, engage with engineers by opening a ticket in Jira.

1. Access the ATM Locator project.
2. Select Create (+). Note: Each issue should cover a single institution.
3. Project: ATM Locator (ATM)
4. Issue Type: ATM & Branch Migration
5. Summary: title the issue using a succinct but specific description of the request. For these requests, the summary should begin with the institution name, followed by ‘ATM Migration’, then jSource number (ex: ‘Ovation Bank: ATM Migration - #22222’).
6. Description: provide any additional details that may be helpful to engineers as they migrate locations to production.
7. Attachment: attach any files related to the request, if applicable.
8. Pre-Launch URL: indicate the institution’s pre-launch URL.
9. Live Website URL: indicate URL that will be used for the live website.
10. Institution ID: indicate the institution ID for the institution.
11. Due Date: identify the date the migration should be completed. These requests should be set 5 business days out.
12. Click Create.

This opens the issue in the ATM Locator project in Jira and creates a link that can be used to track progress and as a reference point for discussions with the engineering team.

Requesting changes to the ATM + branch locator setup

Post-launch, institutions may need to adjust the ATM networks that are available and showing to users on their website. Engineers can assist in adding or removing custom networks or external networks at any time post-launch. To request changes to the locator setup for an institution, engage with engineers by opening a ticket in Jira.

1. Access the ATM Locator project.
2. Select Create (+). Note: Each issue should cover a single institution.
3. Project: ATM Locator (ATM)
4. Issue Type: ATM Locator Setup
5. Summary: title the issue using a succinct but specific description of the request. For these requests, the summary should begin with the institution name, followed by ‘ATM Locator Change’. jSource number can be included, for your own reference but should follow the institution name and request (ex: ‘Ovation Bank: ATM Locator Change - #22222’).
6. Description: provide the engineers specific direction on the adjustments that need to be made to the current setup, indicating any additions or removals of networks, as well as any additional details that may be helpful as they adjust setup. Note: this field should always be completed so engineers have specific direction on changes needed.
7. Attachment: attach any files related to the request, if applicable.
8. Pre-Launch URL: indicate the institution’s pre-launch URL.
9. Live Website URL: indicate URL that will be used for the live website.
10. Custom Network: include the name and details for any custom or private networks to be set up for the institution (ex: Ovation Bank ATMs). List all that should be included in the new/adjusted setup.
11. ATM Network: indicate the external ATM network(s) to include as part of the institution’s new/adjusted locator setup. Check all that apply. Leave all unchecked if no external networks will be included.

• Accel
• Advantage
• Alliance One
• Allpoint
• AlphaLink Alliance
• American Express
• ATM Access
• BMO Harris
• Community Cash
• CO-OP
• CU$
• CU24
• CU24 No Premium
• CU Anytime
• CUHere
• CULIANCE
• CU Service Centers
• Discover
• FreedomATM
• In Balance
• InterCept
• J&J Ventures
• Kwik Trip ATMs
• Mastercard
• MoneyPass
• NetWorks
• NetWorks Surcharge Free
• NYCE
• One Stop
• Plus
• PNC
• Presto!
• Pulse
• Regions
• Shared Branch
• Shazam
• Shazam Privileged
• Sheetz
• Star
• Stripes
• SUM
• TransFund
• UltraSF
• Visa

12. Institution ID: indicate the institution ID for the institution.
13. Due Date: identify the date the setup should be completed. These requests should be set 5 business days out.
14. Click Create.

This opens the issue in the ATM Locator project in Jira and creates a link that can be used to track progress and as a reference point for discussions with the engineering team.

Managing ATM + branch locator requests through Jira

Once an issue has been created within Jira, the issue will be managed here until there is a resolution. The engineering team will review all issues submitted, communication about the requests will happen within Jira on each ticket, we will use workflows to indicate status of the issue as it is being worked on and indicate when the work is complete.

Engineering review process

The engineering team will sweep through requests on the ATM Locator board as they come in and will use the workflow statuses to indicate progress on the issue. These requests should be completed by engineering within 5 business days, unless it is indicated that the issue is blocked or waiting on information.

If you have a high priority request, ping @curry-firefighter in the #prod-content Slack channel, using the :urgent: symbol and reference the Jira ticket.

In Slack, discuss individual topics within a single thread to help keep the channel cleaned up and easy to navigate. The engineering team will filter and manage incoming requests and loop in other team members, when necessary.

Communication on locator requests

Where possible, discussions in regards to Jira issues should take place in Jira. Operations team members can comment on the ticket, when needed, to engage with engineers. The engineering team will also adjust status and/or comment on the ticket within Jira as progress is made, so the operations team knows the current status of each request.

At times, discussions about a request may happen outside of Jira (e.g. Slack, email). When this happens, relevant details from the discussion should be captured as a comment on the original issue, so the history is complete and can be easily referenced later. This may include screenshots, linking to Slack archives, or summarizing a discussion/email thread.

If a member of the operations team wants an update on a request and aren’t getting one through Jira, they should put a note in the #prod-content Slack channel, with a link to the referenced request from Jira. Any conversations in the Slack channel should be summarized as comments on the issue itself.

Workflow status

We will use workflow statuses within Jira to keep the engineering and operations teams informed with where we are on each particular request. As progress is made, the status should be updated, as well.

Below is an outline of the various statuses and corresponding descriptions of how and when they should be used.