Saving Energy Step 3 ? Towards a Variable Energy Bill

Do you remember the days when energy was so cheap we paid the bill almost without thinking about it? Things have changed and we have the additional duty of reducing consumption to help save the planet. This is the third article in our mini-series on saving energy. It follows on from the first that explored implementing a management system, and the second listing practical things to implement on the shop floor. These open up the possibility of the variable energy bill we expand on as follows.

If ?variable energy bill? sounds strange to you, I used the unusual turn of phrase to encourage you to view things in a different light. We need to move on from the ?pie chart? mentality where we focus on the biggest numbers like materials, facilities and labour, and zoom in on energy where we can achieve similar gains faster with less pain. But first, we need to see beyond the jargon that governments and consultants love, and get to grips with the reality that we can vary our energy bill and bring cost down.

As executives we recognise this, although other pressures distract us from accepting it as a personal goal. And so we delegate it down the organisation to a level where it becomes ?another crazy management idea? we have to follow to stay out of trouble. I read somewhere that half the world?s organisations do not have energy as a defined objective to monitor in the C Suite. No wonder commerce is only pecking away at energy wastage at a rate of 1% per year.

Find out where you are ?spending energy? and relate this to your core business. If there are places where you are unable to make a connection, challenge the activity?s right to exist. Following the energy trail produces unexpected benefits because it permeates everything we do.

  • Improved product design reducing time spent in factory
  • Streamlined production schedules reducing machine run times
  • Less wear on equipment reducing costly maintenance
  • A more motivated workforce that is prouder of ?what we do?

As you achieve energy savings you can pass these on in terms of lower prices and greater market share. All this and more is possible when you focus on the variables behind your energy bill. Run the numbers. It deserves more attention than it often gets.

Check our similar posts

What Is Technical Debt? A Complete Guide

You buy the latest iPhone on credit. Turn to fast car loan services to get yourself those wheels you’ve been eyeing for a while. Take out a mortgage to realise your dream of being a homeowner. Regardless of the motive, the common denominator is going into financial debt to achieve something today, and pay it off in future, with interest. The final cost will be higher than the loan value that you took out in the first place. However, debt is not limited to the financial world.

Technical Debt Definition

Technical debt – which is also referred to as code debt, design debt or tech debt – is the result of the development team taking shortcuts in the code to release a product today, which will need to be fixed later on. The quality of the code takes a backseat to issues like market forces, such as when there’s pressure to get a product out there to beat a deadline, front-run the competition, or even calm jittery consumers. Creating perfect code would take time, so the team opts for a compromised version, which they will come back later to resolve. It’s basically using a speedy temporary fix instead of waiting for a more comprehensive solution whose development would be slower.

How rampant is it? 25% of the development time in large software organisations is actually spent dealing with tech debt, according to a multiple case study of 15 organizations. “Large” here means organizations with over 250 employees. It is estimated that global technical debt will cost companies $4 trillion by 2024.

Is there interest on technical debt?

When you take out a mortgage or service a car loan, the longer that it takes to clear it the higher the interest will be. A similar case applies to technical debt. In the rush to release the software, it comes with problems like bugs in the code, incompatibility with some applications that would need it, absent documentation, and other issues that pop up over time. This will affect the usability of the product, slow down operations – and even grind systems to a halt, costing your business. Here’s the catch: just like the financial loan, the longer that one takes before resolving the issues with rushed software, the greater the problems will pile up, and more it will take to rectify and implement changes. This additional rework that will be required in future is the interest on the technical debt.

Reasons For Getting Into Technical Debt

In the financial world, there are good and bad reasons for getting into debt. Taking a loan to boost your business cashflow or buy that piece of land where you will build your home – these are understandable. Buying an expensive umbrella on credit because ‘it will go with your outfit‘ won’t win you an award for prudent financial management. This also applies to technical debt.

There are situations where product delivery takes precedence over having completely clean code, such as for start-ups that need their operations to keep running for the brand to remain relevant, a fintech app that consumers rely on daily, or situations where user feedback is needed for modifications to be made to the software early. On the other hand, incurring technical debt because the design team chooses to focus on other products that are more interesting, thus neglecting the software and only releasing a “just-usable” version will be a bad reason.

Some of the common reasons for technical debt include:

  • Inadequate project definition at the start – Where failing to accurately define product requirements up-front leads to software development that will need to be reworked later
  • Business pressure – Here the business is under pressure to release a product, such as an app or upgrade quickly before the required changes to the code are completed.
  • Lacking a test suite – Without the environment to exhaustively check for bugs and apply fixes before the public release of a product, more resources will be required later to resolve them as they arise.
  • Poor collaboration – From inadequate communication amongst the different product development teams and across the business hierarchy, to junior developers not being mentored properly, these will contribute to technical debt with the products that are released.
  • Lack of documentation – Have you launched code without its supporting documentation? This is a debt that will need to be fulfilled.
  • Parallel development – This is seen when working on different sections of a product in isolation which will, later on, need to be merged into a single source. The greater the extent of modification on an individual branch – especially when it affects its compatibility with the rest of the code, the higher the technical debt.
  • Skipping industrial standards – If you fail to adhere to industry-standard features and technologies when developing the product, there will be technical debt because you will eventually need to rework the product to align with them for it to continue being relevant.
  • Last-minute product changes – Incorporating changes that hadn’t been planned for just before its release will affect the future development of the product due to the checks, documentation and modifications that will be required later on

Types of Technical Debt

There are various types of technical debt, and this will largely depend on how you look at it.

  • Intentional technical debt – which is the debt that is consciously taken on as a strategy in the business operations.
  • Unintentional technical debt – where the debt is non-strategic, usually the consequences of a poor job being done.

This is further expounded in the Technical Debt Quadrant” put forth by Martin Fowler, which attempts to categorise it based on the context and intent:

Technical Debt Quadrant

Source: MartinFowler.com

Final thoughts

Technical debt is common, and not inherently bad. Just like financial debt, it will depend on the purpose that it has been taken up, and plans to clear it. Start-ups battling with pressure to launch their products and get ahead, software companies that have cut-throat competition to deliver fast – development teams usually find themselves having to take on technical debt instead of waiting to launch the products later. In fact, nearly all of the software products in use today have some sort of technical debt.

But no one likes being in debt. Actually, technical staff often find themselves clashing with business executives as they try to emphasise the implications involved when pushing for product launch before the code is completely ready. From a business perspective, it’s all about weighing the trade-offs, when factoring in aspects such as the aspects market situation, competition and consumer needs. So, is technical debt good or bad? It will depend on the context. Look at it this way: just like financial debt, it is not a problem as long as it is manageable. When you exceed your limits and allow the debt to spiral out of control, it can grind your operations to a halt, with the ripple effects cascading through your business.

 

Reduce Cost and Improve Productivity

Whether the economy is in a downturn or not, management will always aim for a more cost effective IT solution. If your current IT infrastructure is hurting your profitability, our expertise is both ‘tested and proven”.? Also “bleeding edge” solutions in the industry will enable us to find inexpensive alternatives for you.

For instance, have you started to wonder whether having a constantly growing number of servers, many of which are underutilised, is really the norm? Well, that used to be the case. However, with the advent of virtualisation and replication, that expensive exercise is steadily becoming a thing of the past.

By implementing solutions powered by these two technologies, organisations can now manage excess storage capacities and hardware resources by performing simpler processes at lesser costs. In addition to that, using the same pair of technologies, companies can also decrease the downtime suffered during maintenance and upgrades.

Thus, at the end of the day, not only do companies stand to reduce expenditures, they can also boost revenues as a result of increased productivity time.

Do we still have other IT solutions that tackle a different set of problems but arrive at the same outcome, i.e. reduced costs + improved productivity = higher profits? You bet we do.

Basically, this is how we’ll help your company arrive at the same winning formula:

  • Provide insights as to where and when changes have to be made. Oftentimes, initiatives to reduce cost and improve productivity are not preceded by the appropriate study especially as with regards to their impact on all departments in the organisation. This usually results in unnecessary duplication of resources, a sure way to increase costs instead.
  • Consolidate and automate. We’ll work within your budget in finding ways to consolidate your applications, hardware, storage, databases, and processes. Then we’ll integrate automation practices to simplify management and maintenance of all these assets. This will substantially free not only your IT infrastructure but also your IT staff, giving them more opportunities to innovate.
  • Create an innovative environment. One of the benefits you gain in having room to innovate is the potential to discover new ways to drive costs even further. A fraction of your savings can then be used to develop even better IT solutions, thus creating a productive cycle: IT solutions > savings and innovation > better IT solutions. Our role is to help you harness your potentials to keep that cycle running.
  • Work to reduce carbon footprint in all your procedures. By ensuring that energy consumption is brought to a minimum in every step you take, you can rest assured that costs have only one way to go – down. Check out our Energy Management Software ecoVaro.

Find out how we can increase your efficiency even more:

Contact Us

  • (+353)(0)1-443-3807 – IRL
  • (+44)(0)20-7193-9751 – UK
What Heijunka is & How it Smooths Call Centre Production

The Japanese word Heijunka, pronounced hi-JUNE-kuh means ?levelling? in the sense of balancing workflows. It helps lean organizations shift priorities in the face of fluctuating customer demand. The goal is to have the entire operation working at the same pace throughout, by continuously adjusting the balance between predictability, flexibility, and stability to level out demand.

Henry Ford turned the American motor manufacturing industry upside down by mass-producing his iconic black motor cars on two separate production lines. In this photograph, body shells manufactured upstairs come down a ramp and drop onto a procession of cars almost ready to roll in 1913.

Smoothing Production in the Call Centre Industry

Call Centres work best in small teams, each with a supervisor to take over complex conversations. In the past, these tended to operate in silos with each group in semi-isolation representing a different set of clients. Calls came through to operators the instant the previous ones concluded. By the law of averages, inevitably one had more workload than the rest at a particular point in time as per this example.

Modern telecoms technology makes it possible to switch incoming lines to different call centre teams, provided these are multi-skilled. A central operator controls this manually by observing imbalanced workflows on a visual system called a Heijunka Box. The following example comes from a different industry, and highlights how eight teams share uneven demand for six products.

This departure from building handmade automobiles allowed Henry to move his workforce around to eliminate bottlenecks. For example, if rolls of seat leather arrived late he could send extra hands upstairs to speed up the work there, while simultaneously slowing chassis production. Ford had the further advantage of a virtual monopoly in the affordable car market. He made his cars at the rate that suited him best, with waiting lists extending for months.

A Modern, More Flexible Approach

Forces of open competition and the Six Sigma drive for as-close-to-zero defects dictates a more flexible approach, as embodied in this image published by the Six Sigma organisation. This represents an ideal state. In reality, one force usually has greater influence, for example decreasing stability enforces a more flexible approach.

Years ago, Japanese car manufacturer Toyota moved away from batching in favour of a more customer-centric approach, whereby buyers could customise orders from options held in stock for different variations of the same basic model. The most effective approach lies somewhere between Henry Ford?s inflexibility and Toyota?s openness, subject to the circumstances at the moment.

A Worked Factory Example

The following diagram suggests a practical Heijunka application in a factory producing three colours of identical hats. There are two machines for each option, one or both of which may be running. In the event of a large order for say blue hats, the company has the option of shifting some blue raw material to the red and green lines so to have the entire operation working at a similar rate.

Predictability, Flexibility, and Stability at Call Centre Service

The rate of incoming calls is a moving average characterised by spikes in demand. Since the caller has no knowledge whether high activity advisories are genuine, it is important to service them as quickly as possible. Lean process engineering provides technology to facilitate flexibility. Depending on individual circumstances, each call centre may have its own definition of what constitutes an acceptably stable situation.

Contact Us

  • (+353)(0)1-443-3807 – IRL
  • (+44)(0)20-7193-9751 – UK

Ready to work with Denizon?

Contact Us Today