ARCHIVE FOR THE ‘legacy-systems’ CATEGORY

Leadent CEO, Alastair Clifford-Jones tackles the tricky issue of ageing technology...

Many organisations that have implemented field service management solutions now face a dilemma. Recent advances in technology platforms, software and hardware, have caused these organisations, that had previously enjoyed a competitive advantage, to risk being left behind. And it’s not just the advancement of technology that is driving this, the focus for many field service organisations has changed due to consumers’ ever-increasing expectations, and the deregulation of some industries.

Given the pressure on organisations to provide a better customer experience, many assume the solution is to replace or upgrade ageing technology; especially considering that the replacement could be a Cloud or SaaS-based solution that would shift the costs into an OPEX bucket. Whilst this might be seen as a silver bullet, the truth is more complicated.

When organisations first considered field service management systems they were trying move away from the Chaotic Survival state (as per the maturity model shown below.) Business cases were predicted on an improvement in operational efficiency by ensuring the right job was given to the right operative, with the right skills/tools/parts to meet customer service levels at an optimal cost.

 

To become a Supply Led business required a limited change in technology, and more of an organisational change as it is much more about breaking down silos within a business.

However, transforming into a Demand Led organisation requires significant investment, and a completely different way of thinking. This is where organisations need to be truly digitally enabled with multi-channel customer touch-points.

So, what’s the right direction for organisations?

It depends. There are several aspects to be considered.

The first is not just what technology you have, but how well it’s been implemented into the business; are processes understood and adhered to? Does the business model match both the objectives, and process model?

Often organisations believe technology is at the root of their problems – if they could just have faster software or more flexible configuration life would be so much simpler. In reality it’s often the way technology has been implemented and this isn’t just about customisation or configuration, it’s about embedding process and mindset change into the business. Even in today’s world, there are far too many technology-driven implementations that are not owned or controlled by the business.

The second is deciding where the business needs to be. In the diagram above, it is clear the ‘best’ position is on the right-hand side, but this is primarily driven by consumers. If your customers don’t need you to be this type of business, there is no point trying to position yourself there. But don’t kid yourself, this would make you the exception, not the norm.

Your business’s starting point, and where you need it to be will give you an indication of the gap that needs to be closed to deliver competitive advantage. This then begins to formulate a basis for the decision to upgrade or replace technology. But, as ever, there are a number of ways to close this gap, with many requiring some technology, but how do you make the right decision?

The options are:

• Drive more value from a current deployment
• Implement point solutions to add functionality
• Upgrade an existing solution
• Replace the current system

Getting more Value from a Current Deployment

Many implementations have failed to deliver the anticipated value. It’s not that businesses are over optimistic when the business case is developed, but more that they don’t take the opportunity to truly transform. The field service management solution is seen as an operational tool and implemented in a silo.

This silo thinking has resulted in the lack of an integrated view of the end-to-end customer journey. In reality, this is not because the business failed in the implementation, but more that efficiency was the focus at the time.

 

Getting more from a current deployment is all about the end-to-end customer journey. Often greater value can be achieved from just having an integrated view, which means looking at processes and how the organisation matches this view.

In my experience, there is always more value that can be generated from a current deployment. But the big question is, is it ever enough to meet current and future requirements?

Implementing Point Solutions

If the scheduling and dispatch solution is working well, and an organisation is just trying to improve the customer experience, there is no reason why the existing solution cannot be enhanced by implementing greater functionality via integration with other software such as online booking or customer communications.

This way a customer can get the ‘digital experience’ with minimal disruption to operations. Given integration capabilities and the proliferation of APIs, it is much easier in today’s world to integrate a point solution with current platforms. The main gripe for customers is the lack of information from the organisation. If you keep your customers informed via appropriate channels - a web or mobile app, or even a lowly text message, it can dramatically enhance customer experience.

In addition to improving the customer experience, it alsomakes operational sense. The business case for delivering better customer information can often be satisfied by the reduction in calls to call centres alone.

Upgrade an Existing System

Upgrades come in many forms. Vendors are working hard to shift customers from on-premise solutions to their new cloud variants. While the existing cloud vendors are innovating and adding functionality to stay out in front. Often the decision to upgrade is with the supplier in that support will usually be withdrawn for non-upgraded systems, for example, where the cloud option becomes the only option.

Where the organisation has an option to upgrade to get enhanced technological capabilities, it is very important to understand the impact it will have on the people and processes. In my experience, upgrades often fail because the processes have not be realigned, or the teams have not been properly informed or trained.

Organisations that have really benefited from enhanced functionality have conducted a full impact analysis on the processes and realigned their businesses appropriately to make best use of new capabilities.

Replacing a Current System

To many organisations, replacing a system fills them with dread as the initial implementation was a particularly expensive and painful experience but, in reality, much of the hard work has already been done. Much of that pain was in moving from a manual system to auto-scheduling and mobile dispatch. This was a change management exercise, and isn’t a reason not to replace. In fact, if it was done well, it’d be shame not to further capitalise on that investment.

Additionally, moving to a cloud or SaaS based system will not require the capital outlay which was required in the past and, should an organisation choose to move to the cloud, the new IT landscape and architecture needs to be considered, particularly in terms of integration and security.

 

Of course, there are benefits of replacing a current system beyond those of better functionality, for instance, some new systems offer much greater business flexibility. For example, the way different providers treat capacity can offer greater benefits; where many assign an engineer at the time of appointment, some now look at the overall capacity and perform the assignment on the day. For the majority of businesses and use cases, this increases efficiency.

If we are looking at moving organisations to the right on the maturity model it’s essential to have an integrated approach to the end-to-end customer experience, which may be constrained by that organisation’s field service management solution.

Don’t Get Left Behind!

As we’ve seen, moving towards a truly Demand Led model for field service can be achieved via a number of different paths. Where your organisation sits within the maturity model and how much focus is placed on the customer journey will dictate the path you need to take.

But in all cases, it is imperative to make those decisions with a critical eye on your own maturity and the end-to-end customer experience in mind. Failure to do so risks leaving the business trailing in the wake of those who do.

 

---

 

Be social and share

What should businesses consider when deciding whether an On-Premise or a Cloud solution is the best fit for their business? In Part One, we explored the attractions of the Cloud. In Part Two we take at look at why some field service companies still prefer an on-premise solution.

Judging by the amount of publicity recently about the Cloud and its benefits for business, you might think that every company is planning to migrate IT systems to it, including ERP and field service software, or at least thinking about it.

Filter out the noise, though, and it becomes apparent that there is resistance out there and for reasons other than mere reluctance to adopt a new way of managing the company's IT infrastructure. So why might on-premise still be best for your company?

Connectivity

A hosted cloud-based field service may not suit your business, advises Simon Spriggs, account manager Exel Computer Systems. "One reason many companies retain an on-premise ERP solution is the unreliability of their broadband connection. Broadband speed has a major impact on the efficient running of the business. It's not just field-service data going to and fro down that pipe, but everything the company does electronically. If the connection to the Internet fails, you won't be able to communicate with your engineers, manage workflows or give customers real-time information."

[quote float="left"]One reason many companies retain an on-premise ERP solution is the unreliability of their broadband connection.

 

Legacy systems

"Organisations which have made a big investment in data flows are naturally reluctant to migrate all their activities to the Cloud," points out Steve Mason, Vice President International Sales for Streetsmart, Click Software's service management app for SMEs and SMBs. While Click has been one of the pioneers of Cloud solutions, it also has a long heritage of providing on-premise solutions to customers who prefer to keep their activities behind the company walls. Mason likens the current debate to similar discussions that took place when companies migrated from investing in their own mainframes to having virtual servers. "It took time to build trust in those virtual systems. Moving all your processes to the Cloud is a major step: it takes time and people to plan it without disrupting normal business activities. Companies may well have more urgent priorities."

Larger companies will have made a significant investment in Enterprise-class software ERP and won't want that diluted by going to the cloud, accepts Mason. "Companies will have customised legacy software they are reluctant to adapt or processes they are not yet ready to change. They may also have a long-term contractual commitment to their systems integrator or software supplier."

When ERP systems were developed the need to incorporate mobile workforces was minimal" points out Neil Lewis, Consulting Director, EMEA Sales, ServiceMax. "Mobility projects were silos within a company. Today, not only are there much larger numbers of mobile workers, they need greater integration with those on-premise ERP systems from customer databases to accounts."

 

ERP solution providers have bought mobile solution providers to bridge the gap between ERP and mobile, he points out, but integrating old and new technologies is never straightforward. "How do you ensure the same employee can access the ERP from the office and from their mobile device. It might require modifications to the ERP or to the mobile system to get it to work and that is trickier with some ERP system than others. ServiceMax operate a single platform that automatically takes care of any device the field engineer is using. Configuration is done in one place and automatically deployed to the various devices."

Half-way house

Some companies have adopted a half-way house strategy in which they retain on-premise ERP, but migrate some activities to the Cloud, particularly those with a large customer-facing elements such as CRM and field service. "CRM was in the first way of Cloud migration because the need to deliver excellent customer service required greater integration with internal data silos than is often possible with legacy ERP systems," points out Mason. "Start with those apps which will leverage the most immediate gains to the business, make data streams more agile and easily-accessible from mobile devices, " advises Mason.

The complexities of integrating mobile workflow processes into legacy data streams is one reason field service solutions are often in the Cloud while ERP systems. "If your field service solution is browser-based, a lot of the integration issues are taken care of," remarks Spriggs. "It also future-proofs your investment."

Most of the field service software companies can integrate a Cloud-based field service app or platform with on-premise ERP systems. "Solarvista LIVE will connect to virtually any on-premise system via our NET technology which is designed to connect on-premise systems (private) to systems in the cloud (public)," points out Paul Adams, Marketing and Development Director, Solarvista. "Our connection tools support the major communication protocols, so you can be sure your data is secure."

"We have found that the service management industry is a diverse bunch with different requirements so we offer the ability to Pick ‘n’ Mix," says Colin Brown, Managing Director, Tesseract. "Some customers take the rental and support option but would rather install the software on their own server; other customers require remote hosting and support but they prefer to buy the software and others want the whole SaaS package of hosting, rental and support. With all three options, the internet and/or an intranet are the delivery routes."

 

Whether on-premise or Cloud solution, productivity will be affected if engineers are unable to work unless they are connected, so any mobile app should facilitate that, says Adams. "Our Mobile apps are designed for field-based users and operate on an occasionally-connected basis."

It's a mistake to assume that all field service platform solutions include off-line capability and automatic synchronisation, warns Lewis. "Engineers need to be able to download their jobs for the day, update schedules and customer history, for example, without being connected, and to have all that data automatically synchronised without manual intervention when communications are restored."

Security

While concerns over security have abated somewhat, some organisations remain sensitive about their data being in the hands of a third-party. With on-premise-solutions, all software resides behind that wall. Your own IT people can check authorization attempts and manage system access. There's always some risk involved in moving systems and data outside the physical walls of the business, which is there is so much emphasis on choosing the right Cloud platform provider and on service level agreements if you do go that route.

Some service organisations operate in industries where there are strict compliance and regulatory rules. Some sectors require high levels of access security, making on-premise solutions the pragmatic solution. However, bear in mind that asking mobile workers to go through myriad layers of protection to gain access to the system will have a detrimental effect on productivity.

 

IT resources

Don't under-estimate the IT skills and cost of investing in an on-premise solution, advise our experts. "Do you have the resources to manage IT requirements internally, including server management? What is the budget and the available IT resource to manage things on-premise going forward?" These are key questions, says Simon Spriggs. "If there are any concerns about the level of IT commitment required, the Cloud may be the way to go. However, it is worth remembering that the service model is always a more expensive option long-term than the outright purchase mode." This is especially true if you already have server agreements in place, he adds.

In conclusion

As with many aspects of field service, the starting point when deciding whether to adopt an on-premise or Cloud strategy for your IT needs should be to ensure you have a full understanding of your business processes and requirements and those of your customers.  Do listen to the pros and cons but ultimately only you can decide which is best for your organisation.

 

---

Be social and share this article