IT Systems Implementation

Are you ready to find out how your newly accepted IT system fares in the real world? Although a rigorous Acceptance testing process can spot a wide spectrum of flaws in a newly constructed IT system, there is no way it can identify all possible defects. The moment the IT system is delivered into the hands of actual end users and other stakeholders, it is effectively stepping out of a controlled and secure environment.

Thus, it is during this phase wherein issues having direct impact on the business can arise.

It is our duty to ensure that the Systems Implementation phase is carried out as thoroughly, professionally, and efficiently as possible.

Thoroughly, because we need to include all relevant data and other deliverables, eliminate hard-to-detect miscalculated results, and substantially reduce the probability of business and mission critical issues popping up in the future;

Professionally, because it is the best way to address the sensitive process of turning over a new system to users who have gotten used to the old one;

And efficiently, because we want to minimise the duration over which all stakeholders have to adapt to the new system and allow them to move on to the process of growing the business.

Preparation

Louis Pasteur once said, “Luck favours the mind that is prepared.”

While we certainly won’t leave anything to chance, we do put substantial weight on the Preparation stage of Systems Implementation. We’re so confident with the strategies we employ in Preparation, that we can assure you of an utterly seamless Deployment and Transition phase.

By this we mean that issues that may arise during Deployment and Transition will be handled smoothly and efficiently because your people will know exactly what to do.

Here’s how we will prepare your organisation for Deployment:

  • Identify all key players for the Systems Implementation phase and orient them on their specific roles. We’ll make sure they know what possible hitches may come their way and how to deal with them.
  • Identify all end users and their corresponding functions, then assign appropriate access rights.
  • Draw multi-layered contingency plans to capture and address each possible concern that may crop up during Deployment.
  • Prepare a systematic step-by-step procedure and checklist for the entire Deployment stage. Both of them should have been copied from a similar procedure and checklist used in the Acceptance testing phase.
  • Make all stakeholders understand the conditions required before Deployment can commence.
  • Set the appropriate environment so that all stakeholders know what to expect and when to expect them the moment Deployment commences.
  • Prepare Technical Services and Technical Support personnel for the gruelling mission ahead.
  • Make sure all communication processes are well coordinated so that everyone affected will know who to contact and how to get in touch with them when a problem arises.
  • Plan and schedule training sessions so that they can be conducted “just in time”. Training sessions conducted way ahead of Deployment are often useless because the trainees tend to forget about what they learned when the time comes to apply them. Similarly, training sessions conducted way after Deployment also become useless because trainees are seldom able to internalise instructions delivered during crash courses.

Deployment

There are two sets of issues to keep an eye on during Deployment:

  1. Issues directly related to the technology itself, e.g. application functionality and data integrity, and
  2. Issues emanating from the end users, i.e., their unwillingness to use the new system. One reason may be because they find the interface and procedures too confusing. Another would be due to other inconveniences that come with adapting to a new set of procedures.

Despite all the meticulous scrutiny employed during Acceptance testing, there are just some problems that are made obvious only during Deployment. Issues belonging to the first set are dealt with easily because of the plans and procedures we put in place during the Preparation stage. As an added measure, our team will be on hand to make sure contingency plans are executed accordingly.

While the second set of issues is often neglected by many IT consultancy companies, we choose to meet it head on.

We fully understand that end users are most sensitive to the major changes that accompany a new system. It is precisely for this reason why our training activities during Deployment are designed not only to educate them but also to make them fully appreciate the necessity of both the new system and the familiarisation phase they will need to go through.

The faster we can bring your end users to accept the new system, the faster they can refocus on your company’s business objectives.

Here’s what we’ll do to guarantee the smoothest Deployment process you’ve ever experienced.

  • Employ the procedure and checklist formulated during the Preparation stage.
  • Ensure all end users are well acquainted with any additional tasks they would need to perform (e.g. filling up manual logs).
  • Assess which legacy systems can still be used alongside the new technology and which ones have to be retired.
  • Supervise the installation and optimal configuration of all supporting hardware and software to make sure the likelihood of errors originating from them are brought to near-zero levels.
  • Supervise the installation and optimal configuration of the products themselves.
  • Carry out data migration tasks if necessary.
  • Organise and oversee parallel runs to check for data and report inconsistencies.
  • Conduct training sessions in a professional and well-timed manner to eliminate end-users’ feelings of agitation and to take advantage of memory absorption and retention duration as with regards to their assigned duties and responsibilities.

Transition

Do you often feel uneasy whenever the reins to a newly purchased IT system are handed over to you? Perhaps there are some issues that you feel haven’t been fully settled but, at the same time, find it too late to back out, having already invested so much time and resources.

Alright, so maybe the thought of “backing up” never crossed your mind. However, the concern of being “not yet ready” is raised by many organisations towards the tail end of most Deployment stages. This usually drags the Deployment stage into a never-ending process.

Our team of highly experienced specialists will make sure you reach this point with utmost confidence to proceed on your own.

To wrap up our comprehensive IT Systems Implementation offering, we’ll take charge of the following:

  • Verify that all deliverables, including training materials and other technical documentation, are accomplished and expected outcomes are realised.
  • Make sure all technical documentation are placed in a secure and accessible location.
  • Institute best practices to ensure the IT system becomes fully utilised and to reduce its exposure to avoidable risks.
  • Establish open communication lines with the Technical Support team to enable quick resolution of issues.
  • Ensure complete knowledge transfer has been fully achieved so that your people will spend less time calling Technical Support and more on operations contributory to business growth.

Check our similar posts

Fine-tuning your Operations and keeping our staff Happy with FieldElite

They are the engine that drives your operations, but are you really giving you value for your money? How much time is spent by your personnel on lengthy paperwork and record-keeping, as opposed to actually providing the service to your customers? Manual tasks create bottlenecks and slow your operations, which in turn affects service delivery and customer satisfaction. You want to reach more clients and boost your brand image, growing your market share and generating more revenue. Field Service Management (FSM) software comes in optimise the operations of your mobile workforce, cut down resource wastage, and enhance your productivity as a firm, by actually enabling your field staff to get more done, thus achieving their individual goals. In fact, according to a report published by Fortune Business Insights?, the global FSM market- which stood at $2.29 billion as recently as 2018, will have expanded to $7.27 billion by 2026. What does this mean for your employees, and how do they benefit from FieldElite?

  • Skipping the paperwork with end-to-end automation

Filing reports, keeping track of equipment used, working on the Excel sheets for multiple jobs on a daily basis, all through to the routing and billing- it can be a logistical nightmare. It’s not just about the hours spent poring through documents and typing away at calculators. Manual work exposes you to the risks of human error. Missing records, inaccurate assessments of the situation on the ground due to the overwhelming data streaming in, putting the head office staff under strain- it all hampers the productivity of the company. 

Take scheduling for instance. You have different employees, and various jobs that need their attention, at different locations. It can be a plumbing company whose clients have water filters that need to be repaired, gas boilers inspected, leaking pipes fixed, and others who need new installations to be set up. Assigning your personnel to the different situations will need to take into account the type of job, and the amount of time that it will require, aspects such as the location and the crew that is closest to it. At the head office you will want to keep tabs on the jobs that are in progress, pending, complete, those on hold, and even those that have been cancelled. Running all these through traditional manual processes is enough to drive you to the edge. What’s more, tasks that slip through your fingers amidst the confusion will result in negative feedback from your customers- which you don’t want hitting your brand.

With a field service job management software like FieldELite, you get to handle it all from one dashboard. Optimise your service delivery using the accurate scheduler, that allows you to account for the location of your employees, the status of the job- from the urgent ones like emergency tasks, to the normal duties such as routine maintenance, and low-priority tasks. The field service scheduling software comes with a real-time location feature that allows you to determine the employees closest to the client’s premises who will be appropriate for the job, map out the service areas and give you a birds-eye view of all the operations on the ground, while being updated with the progress of each specific task. Less time is spent travelling to- and from the central office, and more on actually tending to your client’s needs. You can even have situations where you can assign end-of-day tasks to employees who will be passing on that route on their way home.

  • Enhanced resource utilisation that promotes personal and professional development

Skill is key across the industries- from electrical services, solar panel installation, landscaping, home remodelling, pest control, plumbing, HVAC system maintenance, to construction and property management. For the job to be done appropriately and make your clients happy, you want to assign the task to an employee who is particularly proficient at it. This tends to be glimpsed over during manual scheduling since the personnel at the head office will be swamped with so many files, and will pick the first one that comes close to fitting the job description, leading to overlapping of roles. Sure, they may get it done, having seen their colleagues do it and even helping them out when they worked together before on similar projects- but will it be up to the required standard? On the other hand, the FSM allows you to ensure that you get the right technician for the task- who will be more motivated, boosting their performance.

What about accidents? Your employees want to feel safe as they go about their mandate. Many of the field service jobs are hazardous- such as electrical repair jobs, window cleaning tasks at high rise buildings, to elevator repair jobs where a slight glitch can lead to severe ramifications. Field service management software also comes in handy here, where the head office can be notified of any emergency the moment it occurs, and arrange for the necessary action to be taken immediately. That way, your employees will not feel neglected while they are out in the field, showing them that their safety is a priority to your business- which in turn increases their morale. 

  • Readily available knowledgebase and feedback system

When the employees have been assigned a specific job, they will require certain information about it. This includes the scope of the task, history of previous repairs or maintenance that was carried out, accompanying images if needed, risk assessment, any hazards or contaminants that they will need to prepare for, to notes left by technicians who had handled it. Having to keep checking their email, or picking up documents at the office for the day’s job and walking around with them all day as they tend to one customer after another, will slow things down, and not to mention frustrate them. However, the FSM system is directly accessible by the employees via app on their phones. The information needed for each specific task will thus be at their fingertips, speeding up the process and ensuring that they will be ready for each project being handled. 

While carrying out the job itself, the employees will use the very same app to update the system on how it is progressing, chat with the staff at the head office, update the inventory and even place orders for extra parts if necessary. Since mobile service management software apps like FieldElite also work in offline mode, the photos, reports and other entries that are made are collected by the app and saved on the device. Once a network connection is established, they are then updated to the central database- thus ensuring that the job can proceed regardless of the location. 

Once the job is completed, the customer input is also taken, registered in the system through their e-signature. A signoff comment included gives the customer the opportunity to indicate their experience with the job, and the feedback that they would like to provide. In case the job has not been completed, then the scheduling software kicks in, putting it in queue for another appointment to take care of the task, or resolve the issue that had caused it not to be completed the first time. The completed tasks head right to invoicing, which is also handled within the field service management platform, making it a seamless task for the head office staff.

2015 ESOS Guidelines Chapter 1 ? Who Qualifies

The base criteria are any UK undertaking that employs more than 250 people and/or has a turnover in excess of ?50 million and/or has a balance sheet total greater than ?43 million. There is little point in attempting to separate off high polluting areas. If one corporate group qualifies for ESOS, then all the others are obligated to take part too. The sterling equivalents of ?38,937,777 and ?33,486,489 were set on 31 December 2014 and apply to the first compliance period.

Representatives of Overseas Entities

UK registered branches of foreign entities are treated as if fully UK owned. They also have to sign up if any overseas corporate element meets the threshold no matter where in the world. The deciding factor is common ownership throughout the ESOS system. ecoVaro appreciates this. We have seen European companies dumping pollution in under-regulated countries for far too long.

Generic Undertakings that Could Comply

The common factor is energy consumption and the organisation’s type of work is irrelevant. The Environmental Agency has provided the following generic checklist of undertakings that could qualify:

Limited Companies Public Companies Trusts
Partnerships Private Equity Companies Limited Liability Partnerships
Unincorporated Associations Not-for-Profit Bodies Universities (Per Funding)

Organisations Close to Thresholds

Organisations that come close to, but do not quite meet the qualification threshold should cast their minds back to previous accounting periods, because ESOS considers current and previous years. The exact wording in the regulations states:

?Where, in any accounting period, an undertaking is a large undertaking (or a small or medium undertaking, as the case may be), it retains that status until it falls within the definition of a small or medium undertaking (or a large undertaking, as the case may be) for two consecutive accounting periods.?

Considering the ?50,000 penalty for not completing an assessment or making a false or misleading statement, it makes good sense for close misses to comply.

Joint Ventures and Participative Undertakings

If one element of a UK group qualifies for ESOS, then the others must follow suit with the highest one carrying responsibility. Franchisees are independent undertakings although they may collectively agree to participate. If trusts receive energy from a third party that must do an ESOS, then so must they. Private equity firms and private finance initiatives receive the same treatment as other enterprises. De-aggregations must be in writing following which separated ESOS accountability applies.

How DevOps oils the Value Chain

DevOps ? a clipped compound of development and operations – is a way of working whereby software developers are in a team with project beneficiaries. A client centred approach extends the project plan to include the life cycle of the product or service, for which the software is developed.

We can then no longer speak of a software project for say Joe?s Accounting App. The software has no intrinsic value of its own. It follows that the software engineers are building an accounting app product. This is a small, crucially important distinction, because they are no longer in a silo with different business interests.

To take the analogy further, the developers are no longer contractors possibly trying to stretch out the process. They are members of Joe?s accounting company, and they are just as keen to get to market fast as Joe is to start earning income. DevOps uses this synergy to achieve the overarching business goal.

A Brief Introduction to OpsDev

You can skip this section if you already read this article. If not then you need to know that DevOps is a culture, not a working method. The three ?members? are the software developers, the beneficiaries, and a quality control mechanism. The developers break their task into smaller chunks instead of releasing the code to quality control as a single batch. As a result, the review process happens contiguously along these simplified lines.

Code QC Test ? ? ?
? Code QC Test ? ?
? ? Code QC Test ?
? ? ? Code QC Test
Colour Key Developers Quality Control Beneficiary

This is a marked improvement over the previously cumbersome method below.

Write the Code ? Test the Code ? Use the Code
? Evaluate, Schedule for Next Review ?

Working quickly and releasing smaller amounts of code means the OpsDev team learns quickly from mistakes, and should come to product release ahead of any competitor using the older, more linear method. The shared method of working releases huge resources in terms of user experience and in-line QC practices. Instead of being in a silo working on its own, development finds it has a richer brief and more support from being ?on the same side of the organisation?.

The Key Role that Application Program Interfaces Play

Application Program Interfaces, or API?s for short, are building blocks for software applications. Using proprietary software-bridges speeds this process up. A good example would be the PayPal applications that we find on so many websites today. API?s are not just for commercial sites, and they can reduce costs and improve efficiency considerably.

The following diagram courtesy of TIBCO illustrates how second-party applications integrate with PayPal architecture via an API fa?ade.

Working quickly and releasing smaller amounts of code means the OpsDev team learns quickly from mistakes, and should come to product release ahead of any competitor using the older, more linear method. The shared method of working releases huge resources in terms of user experience and in-line QC practices. Instead of being in a silo working on its own, development finds it has a richer brief and more support from being ?on the same side of the organisation?.

imgd2.jpg

The DevOps Revolution Continues ?

We close with some important insights from an interview with Jim Stoneham. He was general manager of the Yahoo Communities business unit, at the time Flickr became a part. ?Flickr was a codebase,? Jim recalls, ?that evolved to operate at high scale over 7 years – and continuing to scale while adding and refining features was no small challenge. During this transition, it was a huge advantage that there was such an integrated dev and ops team?

The ?maturity model? as engineers refer to DevOps status currently, enables developers to learn faster, and deploy upgrades ahead of their competitors. This means the client reaches and exceeds break-even sooner. DevOps lubricates the value chain so companies add value to a product faster. One reason it worked so well with Flickr, was the immense trust between Dev and Ops, and that is a lesson we should learn.

?We transformed from a team of employees to a team of owners. When you move at that speed, and are looking at the numbers and the results daily, your investment level radically changes. This just can’t happen in teams that release quarterly, and it’s difficult even with monthly cycles.? (Jim Stoneham)

Contact Us

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

Ready to work with Denizon?

Contact Us Today