Case Study - The UPS Store®
Supporting the Technology Needs of an International FranchiseMost IT departments struggle to strike the right balance between providing for the needs of the many vs. the needs of the few. Standardization of hardware and software is typically the only means of controlling quality, cost and the administrative burden. The downside to standardization is that it often ignores the unique needs of the individual. This situation is particularly acute within the context of a franchise. And, when the franchise spans cultural and national boundaries then standardization sometimes fails to address critical needs of the individual franchisee. The UPS Store®, the world's largest franchisor of retail shipping, postal, and business service centers recently addressed such issues within its Caribbean region. The area franchisee recognized right away that the regional franchises had no effective tools for pricing and processing packages, and proceeded to create a customized application to address this need. Each store needed local versions of shipping rates for each carrier and service and there needed to be some way to maintain the rates without having to manually perform updates in each store. Differences in business rules between the stateside and local operations prevented the standardized system from functioning. Even without the differences in business rules, the connectivity requirements of the standard system prevented it from being a viable option given the inadequate local telecommunications infrastructure. Clearly, these issues had to be fixed to maintain the quality and service people have come to expect from the franchise. Data Distribution in a Disconnected WorldIn examining this issue, several key requirements were outlined. First, for certain carriers, the local store owners must be able to create and maintain their own customized rates outside of the standard set of rates provided. Second, shipment information must be uploaded to a server every night for backup and billing purposes. And finally, local stores had to be able to operate if their internet connectivity was extremely slow or down during business hours. In order to meet these requirements the disconnected data model was used. Each store would have a local copy of the database used for the manifest system. However, early on it became evident that it would be difficult, without major changes to the manifest software, to keep all the local copies in synch with a centralized master version of the database. This is where MetaBase.NET was utilized. By leveraging the service oriented architecture of MetaBase.NET, the UPS Store® was able to provide a common, universally accessible, and secure way to synchronize data across the regional franchisees. Creating a Data DomainUsing services built into MetaBase.NET, each store was given access to only the data it needed to synchronize its copy with the master database. Also, MetaBase.NET allowed data retrieval to be performed on as 'as needed' and 'as available' basis. If the internet connection was down, no problem. As soon as it was available, it would try again without any noticeable interruption to the end user and more importantly the customer. With MetaBase.NET, there were additional improvements made to the software which were not available previously like a regional customer registry and centralized 'shadow' copies of local store data. Through the use of Metabase.NET, a customer can have access to her personalized address book from any The UPS Store® in the region. As an additional benefit to the store owners, their localized rate data and shipment information are automatically synchronized with a remote server. Not only do they gain the benefit of 'no-touch' rate updates, but they also enjoy the benefit of automatic data backup, ensuring that their data will be preserved even in the event of a catastrophic failure in their store. All this combines to provide the 'feel' of a customized solution to the franchisee.
ConclusionsThrough the implementation of MetaBase.NET, The UPS Store® was able to quickly obtain the benefit of data customization, synchronization, and access. Moreover, they were able to keep their standardized set of software while at the same time accommodating the individual user's needs - a balancing act indeed. |