Disaster Recovery

Because information technology is now integrated in most businesses, a business continuity plan (BCP) cannot be complete without a corresponding disaster recovery plan (DRP). While a BCP encompasses everything needed – personnel, facilities, communications, processes and IT infrastructure – for a continuous delivery of products and services, a DRP is more focused on the IT aspects of the plan.

If you’re still not sure how big an impact loss of data can have, it’s time you pondered on the survival statistics of companies that incurred data losses after getting hit by a major disaster: 46% never recovered and 51% eventually folded after only two years.

Realising how damaging data loss can be to their entire business, most large enterprises allocate no less than 2% of their IT budget to disaster recovery planning. Those with more sensitive data apportion twice more than that.

A sound disaster recovery plan is hinged on the principles of business continuity. As such, our DRP (Disaster Recovery Plan) blueprints are aimed at getting your IT system up and running in no time. Here’s what we can do for you:

  • Since the number one turn-off against BCPs and DRPs are their price tags, we’ll make a thorough and realistic assessment of possible risks to determine what specific methods need to be applied to your organisation and make sure you don’t spend more than you should.
  • Provide an option for virtualisation to enjoy substantial savings on disaster recovery costs.
  • Provide various backup options and suggest schedules and practices most suitable for your daily transactions.
  • Offer data replication to help you achieve business continuity with the shortest allowable downtime.
  • Refer to your overall BCP to determine your organisation’s critical functions, services, and products as well as their respective priority rankings to know what corresponding IT processes need to be in place first.
  • Implement IT Security to your system to reduce the risks associated with malware and hackers.
  • Introduce best practices to make future disaster recovery efforts as seamless as possible.

We can also assist you with the following:

Check our similar posts

Strategy and Portfolio Management

 

A well planned strategy is the necessary bridge between brilliant leadership and excellent execution. Without it, your entire organisation cannot hope to respond quickly and effectively to challenges and changes within the landscape on which it operates.

Strategic planning involves identifying objectives, understanding what resources are needed to attain them, and then allocating the resources to the appropriate units to ensure they are used optimally towards the achievement of desired objectives. Among the end results which can be reflected by your team members are:

  1. Deeper understanding of the competitive environment;
  2. Snappy execution of plans;
  3. Faster, more aligned actions; and
  4. More intelligent and apt responses against strategic moves of the competition.

We understand the need to institute strategic management in such a way that your organisation can easily adapt to unforeseen developments. As such, all our solutions are formulated to make your organisation not only well-guided but also as dynamic as possible.

Strategy Formulation

Before you can proceed to map out any strategy for your company, you’ll have to study your company’s current environment. This will help you determine what courses of action should be taken to be able to navigate through such environment on your way to the end goal.

If you’re not a full time strategist, such a task can either be very daunting or deceivingly easy… the former can prevent your team from getting started, while the latter can lead your team astray.

Ideally, strategy formulation should be carried out as quickly and as efficiently as possible so you can move on to implementation before the competition can react. Our methods can enable your leaders to hit the ground running each time they set out on a strategic plan.

How?

  • We can assist in accurately applying strategic tools like SWOT and Gap analysis, then help integrate the results into an effective strategic plan.
  • We’ll train your team how to carry out effective research techniques so that the information they gather will really be what we need. This is because the tools mentioned earlier can only work effectively if the inputs were picked intelligently. Of course, if you want the entire process expedited, we can also conduct the research ourselves.
  • We’ll establish best practices for top-down, bottom-up, and collaborative strategic management processes. We’ll even show you how to organise and hold meetings where team members are constantly engaged and in-sync, so action plans can be developed and relayed fast.
  • We’ll see to it that strategies for all functional departments (such as IT management, supply-chain, HR, marketing, and legal) are in line with your business strategies, which should in, turn be aligned with your overall corporate strategy.

Strategy Evaluation

Your strategies have to be periodically assessed if you want to determine whether they are attuned to variations affecting your organisation. These changes may include new technologies, emerging competitors, new opportunities, as well as unexpected developments in the economic environment and political climate.

While no time limit is imposed for the build-up of resources vital to the attainment of a specific objective, the window of opportunity can shut on you before you can start amassing such resources. Given this possibility, it is important for your strategies to undergo evaluation processes that will determine whether you should pursue them or not.

Using only the most reliable evaluation techniques, we’ll help you establish whether:

  • Your strategies will place your company in a position that will give it competitive advantage or will erode whatever advantage the competition already has;
  • Your strategies are consistent with the landscape on which your company currently traverses;
  • They are realistic enough in relation to the resources you have on hand;
  • The associated risks have all been identified and the appropriate control measures have already been put in place;
  • The time frames for their full realisation are both realistic and acceptable.

Portfolio Management

In today’s highly competitive market, many of the more successful enterprises are driven by project-based systems.

Now, there’s always a tendency for project managers to become overenthusiastic and to come up with a number of projects that can’t be sustained by available resources. If your project-based company frequently runs out of resources, then either you just have too many projects running or too much is being allocated to a select few.

In both instances, the problem does not necessarily lie on the individual project managers themselves. Rather, what is needed is the ability to have full control over existing projects and investments.

Your leadership should be able to rank projects in terms of their impact to your organisation’s growth, positioning, and profitability. This will give you sufficient information when deciding which projects to pursue, prioritise, or shut down. These are the benefits you’ll gain from our services:

  • A vivid presentation of the big picture. Only when you can step back from all the detail and see the interplay of investments and resources will you be able to make wise decisions regarding how and where to position them.
  • The ability to distinguish between projects with the highest potentials and those that are outdated.
  • Access to expertise that will help you distribute your present IT infrastructure, human resources, financial resources, and facilities across running projects to obtain the biggest benefits for all stakeholders.

Contact Us

  • (+353)(0)1-443-3807 – IRL
  • (+44)(0)20-7193-9751 – UK
How Alcoa Canned the Cost of Recycling

Alcoa is one of the world?s largest aluminium smelting and casting multinationals, and involves itself in everything from tin cans, to jet engines to single-forged hulls for combat vehicles. Energy costs represent 26% of the company?s total refining costs, while electricity contributes 27% of primary production outlays. Its Barberton Ohio plant shaved 30% off both energy use and energy cost, after a capital outlay of just $21 million, which for it, is a drop in the bucket.

Aluminium smelting is so expensive that some critics describe the product as ?solid electricity?. In simple terms, the method used is electrolysis whereby current passes through the raw material in order to decompose it into its component chemicals. The cryolite electrolyte heats up to 1,000 degrees C (1,832 degrees F) and converts the aluminium ions into molten metal. This sinks to the bottom of the vat and is collected through a drain. Then they cast it into crude billets plugs, which when cooled can be re-smelted and turned into useful products.

The Alcoa Barberton factory manufactures cast aluminium wheels across approximately 50,000 square feet (4,645 square meters) of plant. It had been sending its scrap to a sister company 800 miles away; who processed it into aluminium billets – before sending them back for Barberton to turn into even more wheels. By building its own recycling plant 60 miles away that was 30% more efficient, the plant halved its energy costs: 50% of this was through process engineering, while the balance came from transportation.

The transport saving followed naturally. The recycling savings came from a state-of-the-art plant that slashed energy costs and reduced greenhouse gas emissions. Interestingly enough, processing recycled aluminium uses just 5% of energy needed to process virgin bauxite ore. Finally, aluminium wheels are 45% lighter than steel, resulting in an energy saving for Alcoa Barberton?s customers too.

The changes helped raise employee awareness of the need to innovate in smaller things too, like scheduling production to increase energy efficiency and making sure to gather every ounce of scrap. The strategic change created 30 new positions and helped secure 350 existing jobs.

The direction that Barberton took in terms of scrap metal recycling was as simple as it was effective. The decision process was equally straightforward. First, measure your energy consumption at each part of the process, then define the alternatives, forecast the benefits, confirm and implement. Of course, you also need to be able to visualise what becomes possible when you break with tradition.

Contact Us

  • (+353)(0)1-443-3807 – IRL
  • (+44)(0)20-7193-9751 – UK
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.

 

Ready to work with Denizon?

Contact Us Today