Preview

Novartis' Implementation Strategy

Satisfactory Essays
Open Document
Open Document
580 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Novartis' Implementation Strategy
With this implementation strategy, the new system is installed gradually or in one operation but on just small scale. To put simply, the old system will be replaced by the new system in small groups, across similar separate locations. If this is successful, then the pilot is extended until eventually replaces the old system completely. Within each location, the cutover is direct.

* Advantages: * Easy to control, the pilot can be halt at any time. * With this strategy, the pilot can be stopped at any time during the implementation process. * Easy to evaluate because the new and old systems are both running. * This implementation approach is also easy to evaluated because the both systems are running in different locations. * Low risk, if a small-scale pilot fails then not too much has been lost. * * Easy to train staff by letting them learn new skills on the pilot system. * * Disadvantages: * It can be slow to get a pilot to completely replace the old system. * * A pilot may not show up problems that a full-scale implementation would.
This is because a system can work well as a small-scale pilot but has difficulties when it is scaled up to a full operating system with more realistic volumes of data to be processed. *
Pros:
* Easy to control, the pilot can be halt at any time. * With this strategy, the pilot can be stopped at any time during the implementation process. * Easy to evaluate because the new and old systems are both running. * This implementation approach is also easy to evaluate because the both systems are running in different locations.
• Risk limited to one location at a time
The risk associated with this implementation strategy is limited to one location at a time. If the small-scale pilot fails, lost associated with the failure is not that much.
• If it goes well in early units, later units will support
If the

You May Also Find These Documents Helpful

  • Powerful Essays

    the biggest problems are the overall cost of training your employees on your new system.…

    • 3502 Words
    • 15 Pages
    Powerful Essays
  • Satisfactory Essays

    Unit 3 D2

    • 515 Words
    • 3 Pages

    Recommend one of these methods and create a specification defining what changes would need to be made to the current system to implement this method.…

    • 515 Words
    • 3 Pages
    Satisfactory Essays
  • Good Essays

    Some of the failures that can happen with in a distributed system may also occur within a centralized system as well.…

    • 726 Words
    • 3 Pages
    Good Essays
  • Good Essays

    IS3110 Risk Management

    • 663 Words
    • 3 Pages

    Answer : How long is implementation going to take? What is the predicted down time or chances of a failed change? Do we need other teams to be on standby in case of a worst case scenario?…

    • 663 Words
    • 3 Pages
    Good Essays
  • Satisfactory Essays

    Low risk time installation is another way of minimising risks as you can choose the time for the installation. So again the best time would be on the weekend, as there wouldn’t be that many people on. And the final one is the Pilot deployment as this would be useful to see if the installation is running well, as again working side by side with the old software. So to see if anything goes wrong and only one department may be…

    • 1002 Words
    • 5 Pages
    Satisfactory Essays
  • Good Essays

    * Scalable: It can operate correctly even as some aspect of the system is scaled to a larger size. For example, we might increase the size of the network on which the system is running. This increases the frequency of network outages and could degrade a "non-scalable" system. Similarly, we might increase the number of users or servers, or overall load on the system. In a scalable system, this should not have a significant effect.…

    • 833 Words
    • 4 Pages
    Good Essays
  • Satisfactory Essays

    EMSE 6801 HW1

    • 242 Words
    • 1 Page

    The goal of the final project is to use System Engineering concepts. In doing so, it would be helpful to select a system that has already been engineered or it is near its completion.…

    • 242 Words
    • 1 Page
    Satisfactory Essays
  • Powerful Essays

    Voip Implementation

    • 2535 Words
    • 11 Pages

    The first phases of the project will target Centranet users in a select department, as this is where the first trial can take place and help establish metrics for the system as a whole. Migration from existing Centranet system will happen as departments determine their existing equipment needs upgrades or replacements; although, it…

    • 2535 Words
    • 11 Pages
    Powerful Essays
  • Powerful Essays

    Mis Chapter 7

    • 1074 Words
    • 5 Pages

    10) Two computers using TCP/IP can communicate even if they are based on different hardware and software platforms.…

    • 1074 Words
    • 5 Pages
    Powerful Essays
  • Satisfactory Essays

    The Email Encounter

    • 313 Words
    • 2 Pages

    Low Cost Speedy Information Transfer Easy to Broadcast Decreased Managerial Layers Easy to Reference and Use Go Green Read Receipt…

    • 313 Words
    • 2 Pages
    Satisfactory Essays
  • Powerful Essays

    In case CEO of the company insists on implementing the function, a contingency plan is included suggesting the modifications required to be made in People Support function in order to reap maximum benefits.…

    • 1248 Words
    • 6 Pages
    Powerful Essays
  • Satisfactory Essays

    IT Audit Ch 5

    • 5295 Words
    • 35 Pages

    When determining the operational feasibility of a new system, the expected ease of transition from the old system to the new system should be considered.…

    • 5295 Words
    • 35 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Client - model provides a convenient way to interconnect programs that are distributed efficiently across different locations.…

    • 306 Words
    • 2 Pages
    Satisfactory Essays
  • Powerful Essays

    Red Hat Enterprise

    • 50613 Words
    • 203 Pages

    Copyright © 2012 Red Hat, Inc. and others. T he text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux® is the registered trademark of Linus T orvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries. All other trademarks are the property of their respective owners. 1801 Varsity Drive Raleigh, NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701…

    • 50613 Words
    • 203 Pages
    Powerful Essays
  • Good Essays

    Integration Testing

    • 3169 Words
    • 13 Pages

    * explain the purpose of the implementation phase in the system development life cycle and activities involved…

    • 3169 Words
    • 13 Pages
    Good Essays