It was a sad day when I realized that there wasn't a Transformation for address abbreviation standardization like there is in IOM (https://support.omaticsoftware.com/s/article/RegularExpressionDictionaryforAddressAbbreviations) and sadder still when I learned that I couldn't create a transformation of my own. While the 'Replace' transformation will IDENTIFY a field value containing a qualifying text string just fine, it will also replace the ENTIRE field value (not just the identified text string) with whatever replacement value you designate. Thought you could use a transformation for common address standardizations like replacing "Street" with "St"? Think again, because the way it exists now will replace "123 Main Street," "456 Elm St," and any other incoming field value with the word "Street" in it with just "St". But sadder even still is that this kind of standardization is absolutely critical because OC won't do fuzzy address matches (see https://omatic.uservoice.com/forums/950413-omatic-cloud/suggestions/46745101-allow-matching-on-fuzzy-address-formats). So, I'm forced to either create a bunch of duplicate records with OC (which my org paid a lot of money for) or fall back on IOM until RE Database View sunsets. Blargh.