Big bang adoption

Last updated

Big bang adoption or direct changeover is when a new system is adopted instantly, with no transition period between the old and new systems. [1] [2] [3]

Contents

When a new system needs to be implemented in an organization, there are three different ways to adopt this new system: the big bang adoption, phased adoption and parallel adoption. In case of parallel adoption the old and the new system are running parallel, so all the users can get used to the new system, and meanwhile do their work using the old system. Phased adoption means that the adoption will happen in several phases, so after each phase the system is a little nearer to be fully adopted. With the big bang adoption, the switch between using the old system and using the new system happens at one single date, the so-called instant changeover of the system. Everybody starts to use the new system at the same date and the old system will not be used anymore from that moment on.

The advantage of a big bang adoption is that the new system does not need to be compatible or connected with any old systems it is replacing. This significantly simplifies the design of the new system, especially in an organization that is running on multiple incompatible systems. However, the big bang adoption type is riskier than other adoption types because there are fewer learning opportunities incorporated in the approach, so more preparation is needed to get to the big bang. [1] This preparation will be described below, illustrated by the process-data model of the big bang adoption.

Implementation

Once the management has decided to use the big bang method, and supports the changes which are needed for this, the real changing process can start. This process comprises several steps: converting the system, releasing parts of the system and training the future users. [1]

The activities in the process are explained in the table below, to state them clearly. The concepts that are used to execute the activities are in capitals.

ActivitySubactivityDescription
Prepare management (see Adoption) Determine organizational changes The process of determining the changes that will have to take place to make the big bang possible that results in a report of organizational changes
Agree on organizational changes To be able to introduce the big bang, there has to be agreement about the change-plan which results in an agreement contract. If there's no agreement a new agreement meetings are necessary or the changes need to be determined different again and again, until an agreement contract is created.
Convert system Make planning for future users Create a plan for the people who will have to deal with the new system, so they have an overview of the events that are going to happen [1]
Convert data from old system Convert data from the old system so it can be used in the new system (Koop, Rooimans and de Theye, 2003)
Load data into new system Load data the converted data into the new system [1]
Test data in new system Test data so it'll be known whether if the data will be usable in the new system [1]
Execute offline trials Execute trial with the system and with the users of the system to check whether if the system will work correct [1]
Check to verify validity Checking validity so the system can be made ready to become released (Koop, Rooimans and de Theye, 2003)
Release parts Release converted database Release the new database which is converted from the old database [1]
Release produced application Release the application which is produced for the staff [1]
Release infrastructure Release the new infrastructure [1]
Prepare users Maintain buffer of experienced staff Create a buffer of staff who can take over the duties of the people who have to be trained in using the new system, so the daily work can go on [1]
Train users Train users in preparation for the big release of the system, to create a list of trained users

Convert the system

At first, a plan for the whole adoption process is needed. The plan allows future users to know what will happen and when they should expect certain changes, which avoids unnecessary uncertainties and therefore creates a better working atmosphere. The plan also makes clear when the real adoption takes place and gives the future users the opportunity to get ready for this change. [1] The model below shows that the activities (in the grey box) lead to outcomes (in the boxes next to the grey box) to be able to have a partial outcome: the converted system

Convert system with Big bang.jpg

When the plan is made and everyone knows what is expected from them, the technical changeover can start. First the old data needs to be converted into a form which is able to work with the data in the new system (Koop, Rooimans and de Theye, 2003). Then this data needs to be loaded into the new system, which results in the so-called loaded data. This loaded data needs to be tested to check the efficiency of the data and to test the level of understanding of the future users. Off-line trials need to be executed to check whether the system and the users can work together. Not only do the efficiency and the understanding need to be tested, but the validity needs to be tested to make the level of data validation clear. [1] If the data is not valid, the management need to determine the changes again and the organisation will have to prepare a different way of executing the Big bang adoption.

Release parts of the system

Release parts with Big bang.jpg

If all the data is valid, separate parts of the system can be released. The database which is converted from the old database needs to be released, so the new data is accessible. Next, the produced application needs to be released, so the new application can also be used. The infrastructure of the whole new system also needs to be released, so that it is clear what the system will look like and how everything is connected (Koop, Rooimans and de Theye, 2003). In this phase only separate parts are released, which don't form the new system yet, but only parts of it. All of this happens off-line: only the system developers see this, while the users are still working on the old system. The model above shows what activities need to be executed (in the grey box) by the system controller, to get the outcomes that lead to the released parts. If the release of the parts failed, the management need to determine new changes again (See Adoption; Prepare an organization for adoption).

Train the organization in using the system

Prepare users with Big bang.jpg

If the release of the separate parts succeeded, the next step will be to prepare the users. To be able to introduce the whole new system, i.e. to adopt it, all users need to be trained in working with the new system. Without huge consequences for the production level of an organization, training everyone is only possible if there is a buffer of experienced staff who can take over the daily work of the users that need to be trained. This means that for all the people that need to be trained, there will be staff available who can take over the work, so there won't be an enormous delay of work. [1] The human resources department will create the buffer of experienced staff (activity in the grey box) by inviting applicants for the buffer. Then the users can be trained and the trained users can be listed, so a user preparation report can be written.

Poor training can have bad outcomes for an organization, as the FoxMeyer case illustrates (Scott, Vessey, 2000). This company used the big bang method to implement an Enterprise Resource Planning (ERP) system. Wrong training was given, the assumption was made that users already knew enough about it and the wrong skills were taught. Dow Corning also had big problems with acquiring the necessary skills during their big bang ERP implementation (Scott, Vessey, 2000). Using a new system demands various skills and knowledge, which in several cases seem to be underestimated by those managing the switchover.

Techniques

There are several techniques to implement a new system. The adoption phase is only one phase of the whole implementation. Regatta (Koop, Rooimans and de Theye, 2003) is for example a method which is developed to implements systems. This method, developed by Sogeti, treats a changeover as a project and focuses several stages of this project, for example the preparation phase of an adoption and on the acceptance of an implementation method. SAP Implementation is another technique specialized in implementing and adopting SAP AG software, which is divided into several techniques.

Risks

Because of the instant changeover, everything must be done in a fixed time schedule. This is a risky operation. The organization might not be ready yet for this, an incorrect dataset might be used, or the information system can get stuck, because of a lack of experience and start up problems. Also an incapable fall-back method can be a risk in implementing a system using the Big Bang (Koop, Rooimans and de Theye, 2003).

UK stock market, 1980s

The 1986 the London Stock Exchange closed on Friday night and the computers were all switched on the following Monday morning. [4] [5] It has been alleged that this caused large losses.[ citation needed ]

Dow Corning

Dow Corning formerly used systems that were focused on specific departments. The management decided that they wanted to become a truly global company, that would use only one information system: an Enterprise Resource Planning (ERP)-system. To adopt this new ERP-system, they used the big bang adoption type and they spent considerable time and effort reexamining its business processes. The company was prepared for the adoption and first conducted three pilot implementations, before using the new system across the global organization.(Scott, Vessy, 2000)

Dow Corning monitored the progress constantly and made decisions to make sure that the deadlines would be met. This was only possible with feedback and good communication.(Scott, Vessey, 2000)

Another risky strategy is to focus only on the outcome, not on how to achieve this outcome and underrating the learning process for users. It is very hard to plan learning or knowledge, though these are necessary to be able to execute the big bang changeover.

FoxMeyer

FoxMeyer adopted an ERP-system with ambitious warehouse automation software, using the big bang adoption to gain competitive advantage. But FoxMeyer seemed to have an overoptimistic management with unrealistic expectations: the change was too big and too drastic. This resulted in very high work pressure to meet the deadlines for all the employees. So unrealistic expectations of the management are also a risk (Scott, Vessy, 2000).

FoxMeyer failed in having communication and attention that was necessary to be able to give fast and effective feedback. They instead tried to minimize problems by ignoring them, and gave discouraging criticism, which resulted in ambiguous feedback. This hindered organizational learning, something which is very important during an organizational change. So bad communication and ambiguous feedback are also risks when adopting a system with the big bang (Scott, Vessey, 2000).

See also

Related Research Articles

<span class="mw-page-title-main">Enterprise resource planning</span> Corporate task of optimizing the existing resources in a company

Enterprise resource planning (ERP) is the integrated management of main business processes, often in real time and mediated by software and technology. ERP is usually referred to as a category of business management software—typically a suite of integrated applications—that an organization can use to collect, store, manage and interpret data from many business activities. ERP systems can be local-based or cloud-based. Cloud-based applications have grown in recent years due to the increased efficiencies arising from information being readily available from any location with Internet access.

A management information system (MIS) is an information system used for decision-making, and for the coordination, control, analysis, and visualization of information in an organization. The study of the management information systems involves people, processes and technology in an organizational context. In other words, it serves, as the functions of controlling, planning, decision making in the management level setting.

<span class="mw-page-title-main">Data management</span> Disciplines related to managing data as a resource

Data management comprises all disciplines related to handling data as a valuable resource, it is the practice of managing an organization's data so it can be analyzed for decision making.

Business software is any software or set of computer programs used by business users to perform various business functions. These business applications are used to increase productivity, measure productivity, and perform other business functions accurately.

<span class="mw-page-title-main">Accounting information system</span> System of collecting, storing and processing financial and accounting data

An accounting information system (AIS) is a system of collecting, storing and processing financial and accounting data that are used by decision makers. An accounting information system is generally a computer-based method for tracking accounting activity in conjunction with information technology resources. The resulting financial reports can be used internally by management or externally by other interested parties including investors, creditors and tax authorities. Accounting information systems are designed to support all accounting functions and activities including auditing, financial accounting porting, -managerial/ management accounting and tax. The most widely adopted accounting information systems are auditing and financial reporting modules.

Stages-of-growth model is a theoretical model for the growth of information technology (IT) in a business or similar organization. It was developed by Richard L. Nolan during the early 1970s, and with the final version of the model published by him in the Harvard Business Review in 1979.

A product software implementation method is a systematically structured approach to effectively integrate a software based service or component into the workflow of an organizational structure or an individual end-user.

A Systems Applications Products audit is an audit of a computer system from SAP to check its security and data integrity. SAP is the acronym for Systems Applications Products. It is a system that provides users with a soft real-time business application. It contains a user interface and is considered very flexible. In an SAP audit, the two main areas of concern are security and data integrity.

The eCRM or electronic customer relationship management coined by Oscar Gomes encompasses all standard CRM functions with the use of the net environment i.e., intranet, extranet and internet. Electronic CRM concerns all forms of managing relationships with customers through the use of information technology (IT).

<span class="mw-page-title-main">Phased adoption</span> Implementation strategy

Phased adoption or phased implementation is a strategy of implementing an innovation in an organization in a phased way, so that different parts of the organization are implemented in different subsequent time slots. Phased implementation is a method of System Changeover from an existing system to a new one that takes place in stages. Other concepts that are used are: phased conversion, phased approach, phased strategy, phased introduction and staged conversion. Other methods of system changeover include direct changeover and parallel running.

In computing, adoption means the transfer (conversion) between an old system and a target system in an organization.

Parallel adoption is a method for transferring between a previous (IT) system to a target (IT) system in an organization. In order to reduce risk, the old and new system run simultaneously for some period of time after which, if the criteria for the new system are met, the old system is disabled. The process requires careful planning and control and a significant investment in labor hours.

<span class="mw-page-title-main">SAP ERP</span> German enterprise resource planning software

SAP ERP is an enterprise resource planning software developed by the German company SAP SE. SAP ERP incorporates the key business functions of an organization. The latest version of SAP ERP (V.6.0) was made available in 2006. The most recent SAP enhancement package 8 for SAP ERP 6.0 was released in 2016. It is now considered legacy technology, having been superseded by SAP S/4HANA.

<span class="mw-page-title-main">Parallel running</span> Strategy for system changeover

Parallel running is a strategy for system changeover where a new system slowly assumes the roles of the older system while both systems operate simultaneously. This conversion takes place as the technology of the old system is outdated so a new system is needed to be installed to replace the old one. After a period of time, when the system is proved to be working correctly, the old system will be removed completely and users will depend solely on the new system. The phrase parallel running can refer to the process of changing a fragment of business information technology operation to a new system or to the technique applied by the human resources departments in which the existing staff stay on board during the transition to a new staff.

<span class="mw-page-title-main">Accounting software</span> Computer program that maintains account books

Accounting software is a computer program that maintains account books on computers, including recording transactions and account balances. It may depend on virtual thinking. Depending on the purpose, the software can manage budgets, perform accounting tasks for multiple currencies, perform payroll and customer relationship management, and prepare financial reporting. Work to have accounting functions be implemented on computers goes back to the earliest days of electronic data processing. Over time, accounting software has revolutionized from supporting basic accounting operations to performing real-time accounting and supporting financial processing and reporting. Cloud accounting software was first introduced in 2011, and it allowed the performance of all accounting functions through the internet.

In software engineering, a software development process or software development life cycle (SDLC) is a process of planning and managing software development. It typically involves dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management. The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.

Agile Business Intelligence (BI) refers to the use of Agile software development for BI projects to reduce the time it takes to show value to the organization in comparison to other approaches. It helps in quickly adapting to changing business needs. Agile BI enables the BI team, business people or in general stakeholders to make better business decisions, and to start doing this more quickly.

<span class="mw-page-title-main">Adoption of electronic medical records in U.S. hospitals</span>

The adoption of electronic medical records refers to the recent shift from paper-based medical records to electronic health records (EHRs) in hospitals. The move to electronic medical records is becoming increasingly prevalent in health care delivery systems in the United States, with more than 80% of hospitals adopting some form of EHR system by November 2017.

Disciplined agile delivery (DAD) is the software development portion of the Disciplined Agile Toolkit. DAD enables teams to make simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including scrum, agile modeling, lean software development, and others.

Configuration Lifecycle Management (CLM) is the management of all product configuration definitions and configurations across all involved business processes applied throughout the lifecycle of a product.

References

  1. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Eason, 1988
  2. ↑ Copley, Steve. "Implementing the New System". IGCSE ICT. Retrieved 13 August 2011.
  3. ↑ Wainwright, Stewart (2009). IGSCE and O Level Computer Studies and Information Technology. Cambridge University Press. p. 29.
  4. ↑ "How technology has influenced The Stock Market. – Computers in the City". www.citc.it. 18 September 2015. Retrieved 19 June 2017.
  5. ↑ "Today's News".
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.