ATCO CASE STUDY – cAPITAL plANNING
If you’ve ever driven by a construction site, you will most likely see the familiar black and gold ATCO logo. Fun fact, ATCO is an acronym for the Alberta Trailer Company which started in 1947 renting utility trailers in Calgary. Fast forward to today and ATCO is a 3.5-billion-dollar multinational company with subsidiaries including ATCO Gas and ATCO Electric – distributing energy across Western Canada, Puerto Rico, Mexico, and Chile.
Now, building gas and electric distribution and transmission infrastructure is definitely a capital-intensive business. For ATCO’s Oracle EPM capital planning implementations, I was the vendor executive sponsor, and BluMarble’s chief architect, Juan Alvarez designed the capital planning applications for both organizations. The purpose of the applications was to budget and track ATCO Gas and ATCO Electric’s large project portfolios and manage capitalization, track fixed assets, calculate depreciation and amortization, and manage regulatory considerations. They were using Excel and home-grown systems to do this work and were having all the classic Excel and legacy system issues.
Handling the regulatory budget was of major importance to ATCO. Infrastructure project development costs needed to be tracked (typically over a number of years) and then presented to the Alberta Utilities Commission in order to justify rate increases to consumers as the new infrastructure was brought on-line. The numbers in the EPM applications were used in the preparation of rate case justifications.
These capital planning applications were integrated with ATCO’s ERP – at that time E-business suite (specifically the Fixed Asset and Project Accounting modules). Once the capital plan was approved, capital costs flowed from the capital budget into the financial budget applications.
One very valuable benefit of these applications to ATCO was their ability to store multiple sets of books. One for the internal budget, another for presentation to regulatory authorities, and another for strategic planning. This was accomplished through Oracle EPM’s ability to house multiple scenarios in one application, and then stack those scenarios for comparison and analysis. An additional complexity handled by the system was that each budget book had a different time horizon. The internal budget was 5 years, regulatory 3, and the strategic budget went out 7 years. All at different levels of granularity. Different people managed the different books, and the software allowed them to work in parallel as required.