Portfolio

Power BI & Azure integration case study

Tullis Russell gains real-time reporting and cuts IT costs with Power BI solution

egforit Software helped manufacturer Tullis Russell get up-to-date business insights with Power BI. Read how in our Power BI-Azure integration case study.

Executive brief

Gaining insight with a Power BI manufacturing solution

Tullis Russell is a leading manufacturer of specialist paper and film coatings. The company engaged egforit to replace its legacy BI software with a modern Power BI system. A few benefits of this Power BI manufacturing project were:

near real-time reporting

low cost of ownership

easier report building

complete data view

To learn how we achieved these results, see the full Power BI & Azure integration case study below.

The full story

Purple arrow encouraging readers to scroll down for the rest of the insurance document management system case study

The challenge

Legacy BI software was hindering agility

Tullis Russell has been leading the paper and film coating industry for over 200 years. And like many long-established manufacturers, some of its software systems had gradually fallen behind more modern solutions. The manufacturer’s BI setup consisted of a COBOL ERP, Microsoft Excel, and a BI product called Matillion.

 

The drawbacks of this setup were:

  • data for reporting was only refreshed twice a day
  • external help was needed to configure new reports
  • data was spread across many disparate sources
  • the BI software was more costly than alternatives

 

Due to these disadvantages, the company’s IT and finance departments went in search of a modern alternative. This led Tullis Russell to find egforit’s Power BI consultancy.

The solution

Delivering Power BI integration with Azure

Based on the challenges Tullis Russell had described, egforit’s consultants proposed a solution using Power BI integration with Azure.

 

This solution entailed:

  • creating an Azure data pipeline from the COBOL ERP database
  • storing the data in an Azure-hosted Azure Synapse Studio data lake
  • connecting that data to Power BI via Azure Synapse Analytics

 

The use of Azure’s serverless cloud meant the company only paid for usage, with no baseline costs. Microsoft also took care of all the IT maintenance.

 

And most importantly, the new Power BI Azure integration updated the data every 15 minutes. So the finance team could now view the company’s progress in near real-time.

“egforit’s understanding of our unique business model has been brilliant. I always know where we are in the project thanks to regular updates.”

—Jordan Clough, Finance and IT Manager at Tullis Russell

The benefits

Low-cost, real-time, high-impact BI

Thanks to our Power BI integration with Azure, Tullis Russell now benefited from:

 

✓ Agile decision-making

The timely Power BI reports helped the company respond quickly to emerging trends.

 

✓ Cost-effective BI

The new BI system reduced operational costs and removed the need for maintenance.

 

✓ Future-proof system

Azure’s flexibility gave the manufacturer many more options for future data projects.

 

As Jordan Clough, Finance and IT Manager at Tullis Russell, explained, “This project will allow the sales team to become more autonomous with their data. In time we hope this will create more ownership and a belief that the figures are understood throughout the business.”

 

Following on from this success, Tullis Russell has also asked egforit to help build custom models and reports in Power BI.

Looking for Power BI Azure integration?

Is your organisation facing the same challenges that Tullis Russell faced? egforit is a BI consultancy and Microsoft Gold Partner with 30 years of experience. Get in touch for a free consultation with our BI experts.

Info

10th May 2021
Power BI, Azure, digital integration, business intelligence

Privacy Preference Center

Necessary

Advertising

Analytics

Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview

Other

WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.
wordpress_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by egforit.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress,
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
-id-[app_id],-session-[add-id]

×