Brown Account Tagger (BAT)
How "BAT Keys" replaced account numbers when Brown moved their financial system to Workday's cloud product
I was the lead designer on the Brown Account Tagger (BAT) project. With a pending move to the new Workday financial system, Brown had 40,000 active account numbers that needed to be adapted to Workday's transaction attribute tagging paradigm (which does not use account numbers). Other systems that need to integrate with Workday, however, require something that looks like an account number. Thus, BAT Keys were conceived of to act as identifiers that map to a set of transaction attributes. After modeling the BAT database, I wrote many large SQL queries (~500 lines long) to test different BAT Key name generators until a simplified standard was chosen. I then moved on to feasibility testing for Ruby on Rails, DataMapper, and Oracle. I modeled the UX and made the wireframes for the UI. The UI was built by two other developers and a third developer built much of the Linux middleware. Brown's Workday financial system went live in July 2013. I have taken over upgrades and maintenance to all parts of BAT and have much technical debt to pay back. The UI is fairly simple but the rest of the project was massive.