Введение
Параллельное внедрение — это метод перехода от предыдущей (ИТ) системы к целевой (ИТ) системе в организации. Для снижения рисков старая и новая системы работают одновременно в течение некоторого времени, после чего, если новая система соответствует установленным критериям, старая система выводится из эксплуатации. Этот процесс требует тщательного планирования и контроля, а также значительных трудозатрат.
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.
Обзор
В данной статье рассматривается общий процесс параллельного внедрения; примеры из реальной практики используются для более глубокого понимания процесса, если это необходимо. Кроме того, для визуализации процесса используется модель данных процесса, призванная дать полное представление обо всех этапах параллельного внедрения, однако основной упор будет сделан на уникальные особенности параллельного внедрения. Некоторые общие характеристики, в частности, определение стратегии реализации, применимы ко всем четырем основным типам внедрения и описаны в разделе "Внедрение (программного обеспечения)".
This entry focuses on the generic process of parallel adoption; (real world) examples are used for a more meaningful interpretation of the process if necessary. Moreover a process data model is used for visualizing the process which is intended to provide a complete overview of all the steps involved in the parallel adoption, but emphasis will be laid on the unique characteristics of parallel adoption. Some common characteristics, especially defining an implementation strategy, that go for all four generic kinds of adoption are described in Adoption (software implementation).
Другие виды усыновления
Помимо параллельного внедрения, можно выделить еще три общих типа внедрения. Выбор конкретного метода зависит от организационных характеристик; более подробная информация по этой теме будет представлена ниже. Эти три метода внедрения:
Big Bang Adoption/Plunge Adoption (Внедрение «Большой взрыв»/Резкое внедрение): Внедрение «Большой взрыв» подразумевает перенос всей организации со старой системы на новую системой единовременным переходом. Это самый дешевый вариант, но в случае сбоя новой системы организация столкнется с серьезными проблемами. Также существует риск непринятия системы пользователями. Однако это может быть единственным подходом, если две системы не могут сосуществовать или активация новой системы является критически важной. Поэтапное внедрение (также известное как постепенная конверсия): При поэтапном внедрении организация постепенно переходит на новую систему, поэтапно, по модулям или подсистемам. Некоторые системы невозможно внедрять по частям из-за их сильной зависимости от всей системы в целом. Поэтапное внедрение сопряжено с меньшими рисками, но вызывает наибольшие сбои из-за длительности перехода со старой системы на новую. Пилотное внедрение: Метод пилотного внедрения используется для крупных организаций с множеством филиалов или в значительной степени независимых подразделений. Новая система внедряется в одном из филиалов или подразделений и со временем распространяется на другие. (ограниченный масштаб в случае сбоя новой системы) (Turban, 2002)
Существуют ситуации, когда параллельное преобразование нельзя рассматривать как жизнеспособную стратегию. Во-первых, следует учитывать, содержит ли новая система значительные изменения схемы данных. Отсутствие необходимых элементов данных в одной из систем может привести, в лучшем случае, к неточности данных, а в худшем – к их повреждению. Другая проблема возникает, если система использует готовое программное обеспечение (COTS). Если в документации поставщика COTS указано, что несколько приложений не могут совместно использовать одну и ту же базу данных, то параллельное преобразование невозможно. Примером могут служить продукты Siebel от Oracle. Другие продукты COTS также могут накладывать ограничения, когда для установки исправлений или основных обновлений требуются уникальные лицензионные ключи. После применения они могут вносить изменения в базу данных, из-за чего приложение может ошибочно определять наличие параллельной системы, работающей с той же базой данных, как попытку обхода лицензионного контроля и, таким образом, отключать систему.
Besides parallel adoption, three other generic kinds of adoption can be identified. The choice for a specific adoption method depends on the organizational characteristics; more insight on this topic will be provided below. The three other adoption methods are:
Big bang adoption/Plunge Adoption: A big bang adoption entails transferring the entire organization from the old system to the new system in an instant changeover. This is the cheapest option but if the new System fails, the organization is in big trouble. It also opens risks for the system not to be accepted by its users. However, this may be the only approach to take when the two systems can not coexist or activating the new system is an emergency. Phased adoption (also known as gradual conversion): In phased adoption implementation, the organization is gradually transferring to a new system in different phases, per module or sub system. Some systems are incapable of being introduced in pieces as it is too reliant on the whole system. Using the phased adoption has less risks, but causes the most disruptions due to it taking the most time to transfer from the old system to the new. Pilot adoption: The pilot adoption method is used for large organizations that have multiple locations or largely independent departments. The new system is introduced in one of the locations or departments and extended to other locations or departments over time. (limited boundary if a new system is a failure) (Turban, 2002)
There are several instances when parallel conversion can not be considered a viable conversion strategy. First consider if the new system contains significant schema changes. Data elements required by one system that are not being populated by the other can lead to at best data inaccuracies and at worst data corruption. Another concern is if the system relies on consumer off the shelf technology (COTS). If a COTS vendor's documentation states that more than one application can not share the same database, then parallel conversion is not an option. An example would be Oracle's Siebel products. Other COTS products may also place restrictions when patches or major upgrades require unique license keys. Once applied they may make database changes that might cause the application to falsely detect a parallel system running against the same database as an attempt at getting around licensing controls and thereby disable the system.
Big bang adoption/Plunge Adoption: A big bang adoption entails transferring the entire organization from the old system to the new system in an instant changeover. This is the cheapest option but if the new System fails, the organization is in big trouble. It also opens risks for the system not to be accepted by its users. However, this may be the only approach to take when the two systems can not coexist or activating the new system is an emergency. Phased adoption (also known as gradual conversion): In phased adoption implementation, the organization is gradually transferring to a new system in different phases, per module or sub system. Some systems are incapable of being introduced in pieces as it is too reliant on the whole system. Using the phased adoption has less risks, but causes the most disruptions due to it taking the most time to transfer from the old system to the new. Pilot adoption: The pilot adoption method is used for large organizations that have multiple locations or largely independent departments. The new system is introduced in one of the locations or departments and extended to other locations or departments over time. (limited boundary if a new system is a failure) (Turban, 2002)
There are several instances when parallel conversion can not be considered a viable conversion strategy. First consider if the new system contains significant schema changes. Data elements required by one system that are not being populated by the other can lead to at best data inaccuracies and at worst data corruption. Another concern is if the system relies on consumer off the shelf technology (COTS). If a COTS vendor's documentation states that more than one application can not share the same database, then parallel conversion is not an option. An example would be Oracle's Siebel products. Other COTS products may also place restrictions when patches or major upgrades require unique license keys. Once applied they may make database changes that might cause the application to falsely detect a parallel system running against the same database as an attempt at getting around licensing controls and thereby disable the system.
Место в процессе реализации
Кажется, что в отношении процесса параллельного внедрения существует немного устоявшихся норм. В нескольких источниках (например, Turban, 2002, Eason, 1988, Rooijmans, 2003, Brown, 1999) не используется единое название для описания этого процесса. Термин "параллельное внедрение" используется в этих источниках, хотя и обозначается по-разному в каждом из них: параллельное преобразование, параллельная работа, теневое сопровождение, параллельный переход и параллельная реализация. Это, вероятно, связано с тем, что общее описание процесса не требует чёткой классификации. Существует ряд стандартных методов реализации, в которых описываются различные техники внедрения, но часто в практическом контексте – на примере реальных сценариев или в рамках более комплексных методик, таких как Regatta: метод внедрения, SIM и PRINCE2. В целом, параллельное внедрение лучше всего рассматривать как метод системной инженерии для внедрения новой системы. По сути, метод параллельного внедрения отличается от решения о смене системы в организации и может рассматриваться как один из возможных способов достижения этой цели. Однако при определении оптимальной стратегии реализации учитывается множество факторов. Более того, успех внедрения во многом зависит от выбранной техники внедрения (Lee, 2004).
There seem to be little conventions regarding the process of parallel adoption. Several sources (e. g.: Turban, 2002, Eason, 1988, Rooijmans, 2003, Brown, 1999), do not use a single process description name. The term parallel adoption is denoted in these sources, although consistent per source as: parallel conversion, parallel running, shadow running, parallel cutover and parallel implementation. This appears to be the case because a generic description of the process does not need a distinct classification. There are a quite some standard implementation methods, where different adoption techniques are described but often in a practical context; real world case scenario or a more comprehensive set of implementation techniques like Regatta: adoption method, SIM and PRINCE2. In general, parallel adoption can best be seen as a Systems Engineering method of implementation of a new system. In principle, the parallel adoption method is different from the decision to change a system in an organization and can be seen as one possible mean to achieve that goal. However, there are quite some factors that are being taken into account in determining the best implementation strategy. Moreover, a successful implementation can depend to a big extent on the adoption method. (Lee, 2004)
Процесс
Параллельный процесс внедрения не может быть представлен без учета этапов, предшествующих фактическому преобразованию, а именно разработки сценария преобразования и идентификации и тестирования всех требований. Поэтому процесс объясняется последовательным рассмотрением всех выявленных процессов, представленных на рисунке 1, с кратким обзором общих действий, необходимых для любой из идентифицированных стратегий преобразования. Рисунок 1 дает обзор параллельного процесса внедрения. Левая сторона отображает поток действий, способствующих процессу. Действия, выполняемые одновременно, предваряются толстой черной линией. После завершения параллельного выполнения действий они вновь соединяются аналогичной черной линией. Отсутствие стрелки от одного действия к другому указывает на то, что они являются агрегатами более крупного действия, расположенного выше. Действия разделены на четыре основных фазы: определение стратегии внедрения, которая определяет, какая стратегия внедрения должна быть реализована; предварительная реализация, связанная с разработкой плана всех аспектов и требований, связанных с реализацией; подготовка организации, которая требует надлежащей подготовки организации в соответствии с предыдущей фазой; и преобразование, включающее сам процесс преобразования и его завершение, а также переход к новой системе. Основные фазы подразделяются на другие действия, которые будут кратко описаны в таблицах 1.1 – 1.4. Правая сторона модели описывает данные, участвующие в процессах. Некоторые из этих концепций, представленные парой перекрывающихся открытых прямоугольников, могут быть подразделены на более чем одну концепцию. Пара перекрывающихся закрытых прямоугольников указывает на закрытую концепцию, что означает, что она может быть разделена на более мелкие концепции, но не представляет дальнейшего интереса для параллельного процесса внедрения. Фигура в форме ромба указывает, что связанная с ней концепция служит агрегированной концепцией и состоит из других концепций. Наконец, открытая стрелка представляет собой отношение "суперкласс-подкласс". Концепция, связанная со стрелкой, является суперклассом концепций, связанных с ней. Синтаксис на рисунке 1 соответствует стандартам Unified Modeling Language (UML). Концепции на рисунке 1 определены в таблице 2. Более подробный контекст этих поддействий в процессе будет представлен ниже таблиц.
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
таблица 1.1: Предварительная реализация
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
| Действие | Описание |
|---|---|
| Определить стратегию внедрения | Стратегия внедрения определяется на этом раннем этапе. (Brown, Vessey, 1999) |
| Создать основной сценарий внедрения | Проводится первый первоначальный анализ требований, состоящий из нижеперечисленных требований. (Venture, 2004) |
| Разработать временной план | Впервые разрабатывается временной план процесса внедрения. (Rooijmans, 2003) |
| Определить организационные требования | Здесь определяются организационные требования. (Rooijmans, 2003) |
| Определить ИТ-требования | Определяются ИТ-требования. (Rooijmans, 2003) |
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
таблица 1.2: Подготовка организации
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
| Действие | Описание |
|---|---|
| Установить требования | Для подготовки организации устанавливаются определенные требования. Организация готовится, а ИТ устанавливается на тестовые машины. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004) |
| Протестировать требования | Требования тестируются, чтобы определить, готова ли организация к внедрению. (Rooijmans, 2003) |
| Уточнить основной сценарий внедрения | Основной сценарий внедрения уточняется с учетом новой информации, полученной в процессе с помощью следующих действий. (Rooijmans, 2003) |
| Определить критерии-индикаторы | Для тестирования новой системы создаются критерии-индикаторы. (Rooijmans, 2003, Microsoft, 2004) |
| Сформулировать план обхода/отката | Также разрабатывается план обхода с сценарием отката. С помощью этих планов организация может соответственно попытаться исправить допущенные ошибки и вернуться к предыдущему состоянию, если внедрение на определенном этапе процесса не удастся. (Microsoft, 2004, Rooijmans, 2003) |
| Выполнить (сегментальное) тестовое преобразование | В очень сложных организациях может быть полезно провести тестовое преобразование перед переходом к "живой работе". (Microsoft, 2004, Rooijmans, 2003) |
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
таблица 1.3: Преобразование
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
| Действие | Описание |
|---|---|
| Догнать отставания | Процесс преобразования начался, ряд действий выполняется параллельно. На этом этапе происходит догонка по старой системе. Старая система лидирует, но новая работает параллельно. Все изменения в системе должны быть внесены в новую систему. (Microsoft, 2004, Rooijmans, 2003) |
| Контроль системы | Система постоянно контролируется системой контроля. С помощью определенных индикаторов и характеристик работы системы отслеживаются ошибки и недочеты. (Microsoft, 2004, Rooijmans, 2003) |
| Запустить лидирующую старую систему | Старая система лидирует, обрабатывая фактические данные. |
| Запустить новую систему | Новая система работает параллельно со старой и находится под пристальным наблюдением. (Microsoft, 2004, Rooijmans, 2003) |
| Перенести отставания в новую систему | Если критерии выполнены, отставания переносятся и передаются в новую систему, и процесс преобразования переходит к следующему этапу. (Microsoft, 2004, Rooijmans, 2003) |
| Выполнить стратегию обхода/отката | Если критерии не выполнены, выполняется стратегия обхода или отката, в зависимости от характера ошибок. (Microsoft, 2004, Rooijmans, 2003) |
| Догнать отставания | Отставания догоняются в целях безопасности, даже когда новая система лидирует. (Microsoft, 2004, Rooijmans, 2003) |
| Запустить старую систему | Старая система работает в качестве резервной, в целях безопасности. |
| Запустить лидирующую новую систему (1) | Новая система лидирует и находится в полном функционировании. Все транзакции и изменения в системе обрабатываются здесь. (Microsoft, 2004, Rooijmans, 2003) |
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
таблица 1.4: Завершение параллельного внедрения
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
| Действие | Описание |
|---|---|
| Запустить лидирующую новую систему (2) | Все отставания и проверки закрываются. Новая система является единственной работающей системой. (Microsoft, 2004, Rooijmans, 2003) |
| Отключить старую систему | Старая система больше не нужна и отключается. (Microsoft, 2004, Rooijmans, 2003) |
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Концепции из рисунка 1 определены в таблице 2.1 ниже.
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
таблица 2.1: Список определений концепций
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
| Концепция | Определение |
|---|---|
| Стратегия внедрения | Стратегия, которая будет выбрана для внедрения новой системы. Варианты: "большой взрыв", поэтапное, параллельное внедрение, пилотное преобразование или комбинация этих четырех. (Turban, 2002, Rooijmans, 2003) |
| Сценарий внедрения | Черновой вариант фактического сценария преобразования, состоящий из организационных требований, ИТ-требований и первоначального временного плана. (Venture, 2004, Eason, 1988) |
| Организационные требования | Требования внутри организации, которые должны быть выполнены для успешного внедрения. Они связаны с оптимизацией (изменением) организации для новой системы. Возможные вопросы: управление персоналом, изменение организационных схем и новые бизнес-структуры. (Rooijmans, 2003) |
| ИТ-требования | Требования к информационным технологиям - это требования к программному и аппаратному обеспечению, выбору платформы с учетом бюджета и существующих систем. (Rooijmans, 2003) |
| Временной план | План, в котором мероприятиям назначается временной период, в течение которого они должны быть завершены, обеспечивая общий обзор проекта внедрения с точки зрения доступного времени. (Eason, 1988) |
| Соответствие требованиям | Соответствие требованиям - это соответствие требованиям. (ISO 9000) |
| Сценарий преобразования | Уточненный сценарий внедрения с учетом соответствия требованиям. Кроме того, сценарий преобразования состоит из плана обхода и отката. Сценарий преобразования является планом проекта внедрения. (Rooijmans, 2003) |
| Стратегия обхода | Резервный план; стратегия, применяемая в сценарии преобразования для предотвращения ошибок в процессе преобразования и попытки обойти их, чтобы внедрение все же могло быть успешным. (Rooijmans, 2003) |
| Критерии-индикаторы | Количественные и измеримые критерии в отношении требований для определения успешности процесса внедрения. (Rooijmans, 2003) |
| Откат... |
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Определение стратегии параллельного осуществления
Параллельное внедрение (принятие) предшествует определению стратегии реализации, которая не является уникальной именно для параллельного внедрения, но может рассматриваться как часть процесса управления изменениями, в который вовлекается организация. (Ли, 2004). Некоторые факторы, влияющие на определение стратегии реализации в отношении методов внедрения, описаны более подробно в разделе "Внедрение (внедрение программного обеспечения)".
The parallel adoption is preceded with determining the implementation strategy, which is not unique for parallel adoption, but can be seen as part of the change management process that an organization enters. (Lee, 2004). Some factors involved in determining an implementation strategy regarding adoption methods is described more thoroughly in Adoption (software implementation).
Риск и затраты
Причиной выбора параллельного внедрения вместо пилотного преобразования, подхода "большого взрыва" или поэтапного внедрения часто является компромисс между стоимостью и риском (Andersson, Hanson, 2003). Параллельное внедрение – наиболее дорогостоящий метод внедрения (Chng, Vathanopas, 2002, Microsoft, 2004, Anderson et al., 2003), поскольку оно требует от организации одновременной работы двух систем в течение определенного периода. Одновременная работа двух систем означает необходимость инвестиций в человеческие ресурсы. Помимо надлежащей подготовки (дополнительного) персонала, который должен пройти через напряженный период параллельной работы, когда процедуры пересекаются и взаимодействуют. (Rooijmans, 2003, Eason, 1988) Необходимо приложить усилия для обеспечения целостности данных и предотвращения их повреждения между двумя системами (Chng et al. 2002, Yusuf, 2004). Это касается не только самого процесса преобразования, но и обучения персонала работе с новой системой. Если необходимо внедрить новую систему методом "большого взрыва", риск неудачи высок (Lee, 2004). Если организация сильно зависит от изменений в старой (устаревшей) системе, компромисс между дополнительными затратами на менее рискованный параллельный подход должен быть в пользу этих затрат (Lee, 2004). Однако мы видим, что внедрение ERP в большинстве случаев происходит методом "большого взрыва" (Microsoft, 2004, Yusuf, 2004). Это означает, что организация должна тщательно продумать свою стратегию внедрения и интегрировать это решение в анализ управления рисками или управления изменениями.
The reason for an organization to choose for parallel adoption in favour of a pilot conversion, big bang or phased adoption is often a trade off between costs and risk (Andersson, Hanson, 2003). Parallel adoption the most expensive adoption method (Chng, Vathanopas, 2002, Microsoft, 2004, Anderson et al., 2003), because it demands from the organization that two systems run parallel for a certain period. Running two systems simultaneously means that an investment in Human Resources has to be made. Besides a good preparation of the (extra) personnel, that has to go through a stressful period of parallel running where procedures cross each other. (Rooijmans, 2003, Eason, 1988) Efforts should be placed on data consistency and preventing data corruption between the two systems. (Chng et al. 2002, Yusuf, 2004 ) Not only for the conversion process itself, but also in training them for handling the new system. When it is necessary for the new system to be implemented following a big bang approach, the risk of failure is high (Lee, 2004). When the organization demands heavily on the old (legacy) system to be changed, the trade off between extra involved costs for a less risky parallel approach, should be in favour of those extra costs (Lee, 2004), despite this, we see that ERP adoption follows a big bang adoption in most cases (Microsoft, 2004, Yusuf, 2004). This means that an organization should think clearly about their implementation strategy and integrate this decision in their Risk management or Change management analysis.
Требования к ИТ
Для правильной подготовки организации необходим анализ требований как к ИТ-требованиям, так и к организационным требованиям. Более подробная информация об анализе требований и управлении изменениями приведена в другом месте. При параллельном внедрении наиболее важным ИТ-требованием (если это применимо) является обеспечение одновременной работы обеих систем. На этапе перехода существует период времени, когда старая система является основной. Для переноса данных из старой системы в период синхронизации с новой системой необходимо наличие переходного модуля (Microsoft, 2004). Другие методы внедрения не предусматривают этого требования напрямую. Дополнительную информацию об ИТ-требованиях можно найти в области разработки программного обеспечения.
To prepare the organization properly a requirements analysis of both IT requirements as well as organizational requirements is necessary. More information on requirements analysis and change management can be found elsewhere. For parallel adoption, the most important IT requirement (if applicable) is attention for running the two systems simultaneously. In the conversion phase there is a timeslot, where the old system is the leading system. In order to transfer the data from the old system in the catch up period to the new system, there must be a transition module available (Microsoft, 2004). Other implementation methods do not directly have this requirement. More information about IT requirements can be found in Software Engineering.
Планирование времени
Очень важно иметь подробный план внедрения новой системы в организации (Lee, 2004, Eason, 1988). Самое важное в планировании времени при параллельном переходе – не спешить и не бояться возможных задержек на этапе фактического перевода. (Lee, 2004). Также может быть очень полезно работать с четко определенными вехами (Rooijmans, 2003), подобными используемым в методологии PRINCE2. Дополнительную информацию о планировании времени можно найти в разделах "Планирование" и "Стратегическое планирование".
It is very important to have a detailed plan of conducting the new system in an organization (Lee, 2004, Eason, 1988). The most important thing about time planning for a parallel conversion is not to rush things and not be afraid of possible delays in the actual conversion phase. (Lee, 2004). It can be very beneficial also to work with clearly defined milestones (Rooijmans, 2003), similar to the PRINCE2 method. More information on time planning can be found in Planning and Strategic planning.
Оценка требований
Оценка требований включает в себя переопределение плана реализации. Необходимо протестировать сформулированные ИТ- и (по возможности) организационные требования. Некоторые тесты могут быть проведены для оценки как организационных обязанностей (Rooijmans, 2003), так и ИТ-требований. Здесь вновь важно заручиться поддержкой и вовлеченностью высшего руководства (Eason, 1988). Если высшее руководство не выделит ресурсы для оценки, внедрение может оказаться безуспешным. После этой оценки план реализации перерабатывается в более детальный сценарий преобразования.
The requirements evaluation involves redefining the implementation script. The IT and (if possible) organizational requirements that were made should be tested. Some tests can be run where the organizational responsibilities can be evaluated (Rooijmans, 2003) as well as the IT requirements. Here it is also again important to have top management support and involvement (Eason, 1988). If they do not make resources available to evaluate, the implementation can be unsuccessful as a direct consequence. After this evaluation the implementation script is redefined into a more explicit conversion scenario.
Сценарий конверсии
Таким образом, сценарий перехода представляет собой план организационных изменений во всех аспектах. Однако есть две темы, которым еще не уделено должного внимания в рамках параллельного внедрения. Стратегия обхода / план отката: в отличие от других сценариев внедрения, в сценарий перехода также интегрирована стратегия обхода или план действий в чрезвычайных ситуациях с планом отката. Стратегия обхода определяется в более широком контексте в другом документе, но в данном случае она означает, как указано в вышеприведенной таблице: резервный план; стратегия, применяемая в сценарии перехода для предотвращения ошибок в процессе преобразования и попыток их обойти, чтобы обеспечить успешную реализацию (Microsoft, 2004). План отката, являясь одной из возможных стратегий обхода, активируется, если что-то пойдет не так на этапе преобразования. Поскольку в случае параллельного внедрения обе системы работают одновременно, план отката подразумевает, что база данных или другая система, обрабатывающая транзакции, должна быть полностью восстанавливаемой в устаревшей системе (Microsoft, 2004). Фактически, параллельное внедрение по определению предусматривает наличие такого плана отката благодаря своей природе, заключающейся в наличии ведущей и резервной (не ведущей) системы. Критерии-индикаторы: поскольку сценарий перехода является планом реализации передачи двух систем, он также включает в себя количественно определяемые критерии. Пересмотренные ИТ и организационные требования преобразуются в измеримые компоненты. Если критерии не выполняются в ходе тестового преобразования, следует задействовать стратегию обхода.
The conversion scenario thus consists of a blueprint for the organizational change in all aspects. However, there are two topics that did not yet get the attention they deserve in the parallel adoption scope. Workaround strategy / Rollback plan: Being distinct from the other adoption scenarios, also integrated in the conversion scenario is the workaround or contingency strategy with a rollback plan. The workaround strategy is defined in a broader scope in another entry, but in this context it indicates as defined in the above table: A backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Microsoft, 2004). The rollback plan, as being one possible workaround strategy, is initiated if something goes wrong in the conversion phase. Since the two systems run simultaneously, in a parallel adoption, the rollback plan indicates that the database or other system that handles the transactions should be fully retraceable in the legacy system (Microsoft, 2004). In fact the parallel adoption provides per definition this rollback plan due to its nature of a leading system and a (non leading) backup system. Criteria indicators: Since the conversion scenario is a blueprint of executing the transfer of the two systems, is also entails quantifiable criteria. The redefined IT and organizational requirements are being transferred into measurable components. When the criteria are not being met in the test conversion, the workaround strategy should be deployed.
Перевод
Фактически, этап внедрения уже запущен. В течение этого процесса организация переживает период повышенного напряжения (Eason, 1988, Rooijmans, 2003). Обе системы работают параллельно в соответствии со сценарием перехода, и новая система находится под пристальным контролем. Когда критерии новой системы будут выполнены, старая система перестанет быть основной, и новая система возьмет на себя управление. Операции наверстывания, являющиеся частью стратегии обходного решения, представляют собой резервные копии старой системы и обеспечивают возможности для разработки надежности и восстановления данных. Существуют два способа выполнения операций наверстывания: автоматический и ручной. (Rooijmans, 2003). При необходимости может быть также развернута служба удаленного резервного копирования.
The actual conversion phase is now in place. During this process, the organization is in a stressful period (Eason, 1988, Rooijmans, 2003). The two systems run parallel according to the conversion scenario and the new system is being monitored closely. When the criteria of the new system are met, the old system will cease being the leading system and the new system takes over. The catch ups that are part of the workaround strategy are the back ups of the old system and provide the means for reliability engineering and data recovery. There are two kinds of ways to make catch ups: automatic catch ups and catch ups by hand. (Rooijmans, 2003). If applicable a remote backup service can be deployed as well.
Система управления
Автоматические догоняющие операции: Догоняющие операции, передаваемые автоматизированной системой, созданной на этапе подготовки организации. Эта система автоматически передает данные или информацию в новую систему при переходе от старой основной системы к новой основной системе. Преимущество автоматизированной системы – скорость и точность. Недостаток – необходимость затрачивать время на создание системы передачи на раннем этапе. Ручная доработка: Если фактический перенос данных занимает немного времени или сложность передаваемой информации невелика, организация может выбрать ручную доработку. Преимущество этого подхода – отсутствие необходимости в системе (программном обеспечении) для передачи информации и связанных с ней возможных проблем. Однако это достигается за счет точности и времени. Ручная доработка требует значительно больше времени и более подвержена небольшим человеческим ошибкам (Rooijmans, 2003). Более того, дополнительные затраты на рабочее время и так высоки, а ручная система доработки создает еще большую нагрузку на персонал.
Automatic catch ups: Catch ups that are being transferred by an automated system, created in the preparing the organization phase. This system automatically transfers the data or information to the new system when the conversion goes from the old leading system to the new leading system. The benefit of an automated system is that it is fast and accurate. The disadvantage is that is takes time to produce a transfer system in an earlier stage. Catch ups by hand: When the actual conversion entails only a small amount of time, or the complexity of information that should be transferred to the new system is small, an organization can choose to transfer the catch ups manually. The advantage of this procedure is that there is no need for a system (software program) to transfer the information and the possible problems that come with such kind of a transfer program. The trade off is accuracy and time. It takes a considerable amount of extra time, to transfer the catch ups manually and it is more vulnerable for small human errors (Rooijmans, 2003). Moreover, the additional investment in labour hours is high already; a manual catch up system places even more pressure on the personnel.
Статьи
Андерссон И., Хансон К. (2003). Диффузия технологий в организации, разрабатывающей программное обеспечение, диссертация на соискание степени лиценциата по прикладной информатике, Университет Гётеборга.
Brown, C. V. & Vessey, I. (1999). Подходы к внедрению ERP: к построению ситуационной модели, материалы 20-й Международной конференции по информационным системам, Шарлотт, Северная Каролина, 13–15 декабря, 411–416.
Chng, S., & Vathanophas V. (2002). К межорганизационной корпоративной системе: исследование с использованием фокус-групп. 6-я Тихоокеанско-Азиатская конференция по информационным системам (PACIS 2002). Токио, Япония, 2–4 сентября 2002 г.
Lee, O. (2004). Анализ случая системы DMV штата Невада, Журнал Академии бизнеса и экономики, том 3.
Ribbers, P. & Schoo, K. C. (2002). Разработка комплексных программ внедрения программного обеспечения, 35-я ежегодная Гавайская международная конференция по системным наукам (HICSS'02), том 8.
Yusuf, Y. & Gunasekaran, A. & Abthorpe M. S. (2004). Реализация проектов корпоративных систем: тематическое исследование внедрения ERP в Rolls Royce. Международный журнал экономики производства, 87, 251–266.
Andersson I. Hanson, K. (2003). Technology diffusion in a software organization, Licentiate Thesis in applied Information Technology, University of Goteborg
Brown, C. V. & Vessey, I. (1999). ERP Implementation Approaches: Toward a Contingency Framework, Proceedings of the 20th International Conference on Information Systems, Charlotte, NC, December 13–15, 411 416. Chng, S., & Vathanophas V. (2002). Towards an Inter Organizational Enterprise System: A Focus Group Study. The 6th Pacific Asia Conference on Information Systems (PACIS 2002). Tokyo, Japan. September 2–4, 2002. Lee, O. (2004). A Case Study of Nevada DMV system, Journal of the Academy of Business and Economics, Volume 3
Ribbers, P. & Schoo, K. C. (2002). Designing Complex Software Implementation Programs, 35th Annual Hawaii International Conference on System Sciences (HICSS'02), Volume 8
Yusuf, Y. & Gunasekaran, A. & Abthorpe M. S. (2004). Enterprise systems project implementation: A case study of ERP in Rolls Royce. International Journal of Production Economics, 87, 251 266.
Brown, C. V. & Vessey, I. (1999). ERP Implementation Approaches: Toward a Contingency Framework, Proceedings of the 20th International Conference on Information Systems, Charlotte, NC, December 13–15, 411 416. Chng, S., & Vathanophas V. (2002). Towards an Inter Organizational Enterprise System: A Focus Group Study. The 6th Pacific Asia Conference on Information Systems (PACIS 2002). Tokyo, Japan. September 2–4, 2002. Lee, O. (2004). A Case Study of Nevada DMV system, Journal of the Academy of Business and Economics, Volume 3
Ribbers, P. & Schoo, K. C. (2002). Designing Complex Software Implementation Programs, 35th Annual Hawaii International Conference on System Sciences (HICSS'02), Volume 8
Yusuf, Y. & Gunasekaran, A. & Abthorpe M. S. (2004). Enterprise systems project implementation: A case study of ERP in Rolls Royce. International Journal of Production Economics, 87, 251 266.