TechDrivers presentation

1

To: The CIO

From:

Date: 08/16/2020

Subject: CEO’S Challenge: Implementation of the Splunk System at Techdrivers

Introduction

The integration of the Splunk system into Techdriver's operations will be a big boost to the logistics company. Techdrivers, being an IT-reliant company with many clients and staff accessing the systems remotely, has been facing challenges arising from cyber security threats, and lack of an efficient system to monitor and record all logs from various devices for analysis. Adopting the Splunk system will help address these challenges by improving incident prevention, monitoring, response, and reporting. The new system will enhance log file and data management and network access (Sigman and Delgado, 2016).

Implementation of Proposed Information System

Figure 1. Title (Source: www.source-of-graphic.edu )

Implementing the new Splunk system requires adequate preparation in terms of resources. The most crucial resources needed are finances, people, time, and information. There is need to equip IT staff at Techdrivers with skills on how operate and manage the Splunk platform. Besides, we will need support from Splunk staff to help us familiarize with how the system works. They will help to customize the new system to fit the needs of Techdrivers Company. Therefore, the staff from Splunk will offer extensive services through monitoring the system until it is fully integrated into Techdrivers’ operations.

Besides personnel, financial resources will be crucial in implementing the new log management system. Its implementation is costly, and without proper planning and budgeting, it may not be possible. A fully equipped data center will cost the company an average of $30,000 to install and further $3000 monthly to maintain. Techdrivers being a medium company may not have the capacity to implement such a resource-intensive system. With Splunk, it can implement a purely in-house hosted system, a cloud-based solution, or a hybrid system consisting of both in-house and cloud-based features (Wang et al., 2012). Techdrivers may not implement the fully in-house solution due to the high-cost implications. It should also not adopt a purely-based cloud system due to security and safety concerns (Sigman and Delgado, 2016). The company should consider adopting a hybrid system that is less costly and secure.

Project Risks and Scope Creep

Implementation of the Splunk system at Techdrivers will be accompanied by several risks. The risks fall into the categories if technological, natural and human risks. These are the concerns that the management at Techdrivers should be aware of while implementing the project. Some of the technological risks are viruses, software and hardware failure. The Splunk system might be incompatible with the Techdrivers’ system and that is a risk that can hinder implementation of the project. Technological risks will remain high at the beginning but reduces as the system gets fully integrated. Human risks refer to human errors, inadequate technical skills or any other factor that may hinder successful implementation of the system. They will remain constant throughout the years. Lastly, natural risks include unfortunate events like fire, floods or cyclones that may destroy the systems. Techdrivers should note all these risks

Change Management Strategy

Implementing the new system requires robust strategies to minimize the chances of failure. Change is not always welcome in institutions, and therefore, it must be managed well to avoid resistance from the concerned personnel. Bringing change will involve replacing the current information system at Techdrivers. The current system cannot efficiently handle or process log data. The new Splunk software will be integrated into the company's information system to work concurrently.

The staffs at Techdrivers’ Company need to undergo training on how to operate the Splunk system to read the log data, JSON data, and CSV data. They should also learn how to transfer data from the company's systems to the cloud system managed by the Splunk Company. They should also learn to troubleshoot all challenges that may arise from using the system. They should undergo extensive training that covers all aspects of the Splunk system. The duration of the training will depend on how fast the staffs learn about the new system. After training, they will then transition to using the new system under the guidance of Splunk’s support staff.

Implementing the new system may face resistance from some of the company's employees, especially those affected by its implementation. The IT personnel may oppose its implementation under the fear that it will be hard to learn how to use it. Others may fear losing jobs due to the automation of data management systems. To avoid such opposition, the company should involve the affected staff throughout the planning and implementation process through consultation and proper communication. Proper employee training will also minimize cases of resistance to change

Evidence of Feasibility

There is enough evidence that Splunk system project will succeed at Techdrivers. The evidence is not based on theories and assumptions but from testimonials of other firms that have benefited from the Splunk data management systems. Some of the firms that have effectively installed the Splunk system are SCADA, Mars Lands, London Gatwick Airport, Airbus, Keystart, among others (Splunk, 2020). These firms have all recorded success after utilizing Splunk in its data management. That’s enough feasibility study that the system will succeed at Techdrivers since it has efficiently worked in other similar firms.

References

Baltzon, P. (2020). Information systems. Mcgrewhill.

Connelly, B. et al. (2016). “Too much of a good thing: User Leadership at TPAC.” Information Systems Education Journal (ISEDJ).

Li, S., Xu, L., Wang, X., & Wang, J. (2012). Integration of hybrid wireless networks in cloud services-oriented enterprise information systems. Enterprise Information Systems, 6(2),165-187.

Sigman, B. P., & Delgado, E. (2016). Splunk Essentials. Packt Publishing Ltd.

Splunk. (2020). “Customer success story.” https://www.splunk.com/en_us/customers.html

Project Implementaion Risks

Technological risks Year 1 year 2 Year 3 4 2.5 1.5 Natural ri sks Year 1 year 2 Year 3 2.5 2.5 2.5 Human risks Year 1 year 2 Year 3 3 2 1.5

Years after implementation

Rate of Risk