System Implementation Plan



System Implementation Plan

by

Kavith

(Class)

(Name of Professor)

(University)

3.3 Start-up & Cutover:

Wireless connectivity systems of Coast to Country Parks (CCP) club will be installed from scratch. Newly acquired equipment will be installed starting from the head office to all the regional offices. The work will be completed in the head office first for new installations because it will host the central management database of CCP club. Each start-up of newly acquired components installation will begin from the head office and then move to the regional offices. While replacing the existing components, either software or hardware, the cutover process will be sliced into different portions ADDIN ZOTERO_ITEM CSL_CITATION {"citationID":"FaLAjoaA","properties":{"formattedCitation":"(Sligo et al., 2017)","plainCitation":"(Sligo et al., 2017)","noteIndex":0},"citationItems":[{"id":55,"uris":["http://zotero.org/users/local/BeyJjeak/items/XF6BJAFC"],"uri":["http://zotero.org/users/local/BeyJjeak/items/XF6BJAFC"],"itemData":{"id":55,"type":"article-journal","title":"A literature review for large-scale health information system project planning, implementation and evaluation","container-title":"International journal of medical informatics","page":"86-97","volume":"97","author":[{"family":"Sligo","given":"Judith"},{"family":"Gauld","given":"Robin"},{"family":"Roberts","given":"Vaughan"},{"family":"Villa","given":"Luis"}],"issued":{"date-parts":[["2017"]]}}}],"schema":"https://github.com/citation-style-language/schema/raw/master/csl-citation.json"} (Sligo et al., 2017). For example, to replace the operating system of endpoints, not all the machines will be upgraded at the same time. The process will be completed gradually upgrading one machine at a time to avoid complications in the process.

3.4 Training and Documentation:

Experts from the organization working on the project will provide short training to the employees of CCP club. CCP club will require basic troubleshooting guides and service manuals of critical infrastructure components. Documentation will be provided by the vendors of the components. Information technology team working on the implementation plan will maintain the step by step documentation of the project. Leader of the implementation team will decide the schedule of implementation of different components.

3.5 Implementation Schedule:

As the implementation of new technologies will be completed in several parts, the first thing will be to create the restoration points of already installed software products. The second step will be the penetration testing of the installed system to discover vulnerabilities. The third step will be the implementation of newly purchased WiFi equipment starting from head office and moving towards branch offices. The fourth step will be the upgradation of software components and operating systems of end user devices. The final step will be testing and documentation of the project. The team leader may further divide the implementation schedule into smaller steps.

4. Implementation Staff & Support:

The experts from the solutions provider organization will undertake the implementation of software and hardware components. Total time required for the completion of the project is anticipated to be fifteen days. However, it may vary as per the requirement of the project. Heads of existing IT staff of the CCP clubs will also participate in the implementation of the system. So, that they can have a better understanding of the system. It will help them to understand troubleshooting steps as well.

5. Performance Monitoring:

Stress tests of the installed hardware and software solutions will be performed after the completion of each step to ensure the performance of the system. The performance results will be compared with the pre-defined and agreed performance matrix described in service level agreements with the provider ADDIN ZOTERO_ITEM CSL_CITATION {"citationID":"enG0S96l","properties":{"formattedCitation":"(Ali and Miller, 2017)","plainCitation":"(Ali and Miller, 2017)","noteIndex":0},"citationItems":[{"id":56,"uris":["http://zotero.org/users/local/BeyJjeak/items/IS7CRT3F"],"uri":["http://zotero.org/users/local/BeyJjeak/items/IS7CRT3F"],"itemData":{"id":56,"type":"article-journal","title":"ERP system implementation in large enterprises–a systematic literature review","container-title":"Journal of Enterprise Information Management","page":"666-692","volume":"30","issue":"4","author":[{"family":"Ali","given":"Mahmood"},{"family":"Miller","given":"Lloyd"}],"issued":{"date-parts":[["2017"]]}}}],"schema":"https://github.com/citation-style-language/schema/raw/master/csl-citation.json"} (Ali and Miller, 2017). The system will be monitored for performance continuously by in-house IT teams and any anomalies will be reported to the service provider for correction as per the service level agreements.

6. Back-off Plan:

The implementation plan is divided into smaller parts to reduce the probability of failure. Software restore points will be created before upgradation to ensure that they can be restored to the previous working state without service interruptions. For hardware components to be replaced, the existing components will be preserved in the exact working order. So, that they can be restored appropriately to previous working conditions in case of any fatal error or failure of the new components.

7. Post-implementation Plan and Verification:

After the implementation of the system, all of the components will be verified for proper functioning. The performance of individual components will be matched to the matrix defined in service level agreements ADDIN ZOTERO_ITEM CSL_CITATION {"citationID":"YCxtZyMP","properties":{"formattedCitation":"(Van Grembergen and De Haes, 2018)","plainCitation":"(Van Grembergen and De Haes, 2018)","noteIndex":0},"citationItems":[{"id":57,"uris":["http://zotero.org/users/local/BeyJjeak/items/R5GPRJZG"],"uri":["http://zotero.org/users/local/BeyJjeak/items/R5GPRJZG"],"itemData":{"id":57,"type":"article-journal","title":"Introduction to the Minitrack on IT Governance and its Mechanisms","author":[{"family":"Van Grembergen","given":"Wim"},{"family":"De Haes","given":"Steven"}],"issued":{"date-parts":[["2018"]]}}}],"schema":"https://github.com/citation-style-language/schema/raw/master/csl-citation.json"} (Van Grembergen and De Haes, 2018). Finally, the project will be handed over to the CCP club and service provider will be responsible for future support as per the defined rules of service level agreements.

Bibliography

ADDIN ZOTERO_BIBL {"uncited":[],"omitted":[],"custom":[]} CSL_BIBLIOGRAPHY Ali, M., Miller, L., 2017. ERP system implementation in large enterprises–a systematic literature review. J. Enterp. Inf. Manag. 30, 666–692.

Sligo, J., Gauld, R., Roberts, V., Villa, L., 2017. A literature review for large-scale health information system project planning, implementation and evaluation. Int. J. Med. Inf. 97, 86–97.

Van Grembergen, W., De Haes, S., 2018. Introduction to the Minitrack on IT Governance and its Mechanisms.