IT DISASTER RECOVERY PLAN DALAM MENDUKUNG BUSINESS CONTINUITY PLAN SAAT TERJADI FORCE MAJEURE
DOI:
https://doi.org/10.31000/jika.v6i3.6320Abstract
Kondisi geografis negara Republik Indonesia yang berada pada 3 lempengan besar dunia yaitu: lempeng Eurasia, lempeng Indo-Australia dan lempeng Pasifik, lokasi kantor, tingginya tingkat kelalaian tenaga kerja di Indonesia membuat sebuah perusahaan perlu menyusun sebuah Disaster Recovery Plan (DRP) untuk mendukung terimplementasinya Business Continuity Plan (BCP) yang cepat, akurat dan efisien apabila terjadi force majeure. Metode membangun sebuah Disaster Recovery Plan (DRP) dilakukan dengan membuat sebuah asesmen risiko dengan membuat daftar penyebab risiko, risiko apa saja yang akan timbul, perkiraan dampak yang ditimbulkan serta membuat Management Planing terhadap risiko yang ditimbulkan. Dengan mengimplementasikan Disaster Recovery Plan (DRP), Perusahaan akan dapat lebih memiliki daya saing, karena perusahaan juga dapat mengimplementasikan sebuah Business Continue Plan (BCP) pada semua infrastruktur IT dan database yang dimiliki sehingga jika terjadi Force Majure, pelayanan akan jasa yang diberikan perusahaan kepada pelanggan tetap dapat dijaga dengan baik.References
Erniwati, E. (2020). Konsepsi Force majeur dalam Kontrak/Perjanjian di Masa Pandemi. Jurnal Ilmiah Magister Ilmu Hukum SOL JUSTICA, 3(2), 189–198.
Fikri, A. M., Fachrureza, F., Octaraisya, N., Agustyana, N. A., Putra, M. G. L., & Amalia, D. N. (2021). Implementation of Business Continuity Planning Methodology in Making Business Continuity Planning Documents at PT. XYZ. JBTI Jurnal Bisnis Teori Dan Implementasi, 12(1), 51–62.
Hansen, S. (2020). Does the COVID - 19 Outbreak Constitute a Force Majeure Event? A Pandemic Impact on Construction Contracts. Journal of Civil Engineering FORUM, 6(2), 201–214.
IBM, S. & C. (2022). What is a disaster recovery (DR) plan? Https://Www.Ibm.Com/Uk-En/Services/Business-Continuity/Disaster-Recovery-Plan.
McLeod, R. J., & Schell, P. G. (2012). Sistem Informasi Manajemen (N. Setyaningsih, Ed.; 10th ed.). Salemba Empat.
Meilani, D., Ikhwan, A., & Habibitullah, M. (2019). Designing Disaster Recovery Plan of Data System for University. IOP Conference Series: Materials Science and Engineering, 1–11.
Muflihah, Y., & Subriadi, A. P. (20218). A basic element of it business continuity plan: systematic review. Jurnal Informatika Universitas Ahmad Dahlan, 12(1), 17–23.
Nayak, T., Routray, R., Singh, A., Uttamchandani, S., & Verma, A. (2010). End-to-end disaster recovery planning: From art to science. IEEE Journal.
Nurofik, A., Rahajeng, E., Munti, N. Y. S., Sutisna, Firmansyah, H., Sani, A., Hendarsyah, D., Adrianto, S., Darma, W. A., Herdiansah, A., Ariestiandy, D., Nurnaningsih, D., Setiawan, I., Wiyono, A. S., & Zaharah. (2021). Pengantar Tekologi Informasi (I. Kusumawati & M. Sari, Eds.; Ed.1). Insania.
Prasetyo, H. N., Supriatna, N., Raharjo, A. P., & Wikusna, W. (2019). Information Technology Disaster Recovery Plan (IT-DRP) Model-Based on NIST Framework in Indonesia. International Journal of Applied Information Technology, 3(1), 34–45.
Puspa, R. H., Wibowo, A., & Gunawan, I. (2013). IT risk assessment di biro administrasi kemahasiswaan dan alumni (BAKA) Universitas Kristen Petra . Jurnal Infra , 1(2), 1–6.
Shopshire, J. (2009). Developing the IT Distater Recovery Plannng Construct. Journal of Information Technology Management, XX(4), 37–57.
Syafitri, Y., Bahtiar, & Didik, Lalu. A. (2018). Analisis Pergeseran Lempang Bumi yang Meningkatkan Potensi Terjadinya Gema Bumi di Pulau Lombok. KONSTAN Jurnal Fisika Dan Pendidikan Fisika, 3(2), 139–146.
Wanarta, C., Wibowo, A., & Gunawan, I. (2013). IT Risk Assessment di PT. X. Jurnal Infra, 1(2), 1–7.
Downloads
Published
Issue
Section
License
License and Copyright Agreement
In submitting the manuscript to the journal, the authors certify that:
- They are authorized by their co-authors to enter into these arrangements.
- That it is not under consideration for publication elsewhere,
- That its publication has been approved by all the author(s) and by the responsible authorities – tacitly or explicitly – of the institutes where the work has been carried out.
- They secure the right to reproduce any material that has already been published or copyrighted elsewhere.
- They agree to the following license and copyright agreement.
Copyright
Authors who publish with International Journal of Advances in Intelligent Informatics agree to the following terms:
- Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License (CC BY-SA 4.0) that allows others to share the work with an acknowledgment of the work's authorship and initial publication in this journal.Â
- Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgment of its initial publication in this journal.
- Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work.
Licensing for Data Publication
International Journal of Advances in Intelligent Informatics use a variety of waivers and licenses, that are specifically designed for and appropriate for the treatment of data:
Open Data Commons Attribution License, http://www.opendatacommons.org/licenses/by/1.0/ (default)
Creative Commons CC-Zero Waiver, http://creativecommons.org/publicdomain/zero/1.0/
Open Data Commons Public Domain Dedication and Licence, http://www.opendatacommons.org/licenses/pddl/1-0/
Other data publishing licenses may be allowed as exceptions (subject to approval by the editor on a case-by-case basis) and should be justified with a written statement from the author, which will be published with the article.
Open Data and Software Publishing and Sharing
The journal strives to maximize the replicability of the research published in it. Authors are thus required to share all data, code or protocols underlying the research reported in their articles. Exceptions are permitted but have to be justified in a written public statement accompanying the article.
Datasets and software should be deposited and permanently archived inappropriate, trusted, general, or domain-specific repositories (please consult http://service.re3data.org and/or software repositories such as GitHub, GitLab, Bioinformatics.org, or equivalent). The associated persistent identifiers (e.g. DOI, or others) of the dataset(s) must be included in the data or software resources section of the article. Reference(s) to datasets and software should also be included in the reference list of the article with DOIs (where available). Where no domain-specific data repository exists, authors should deposit their datasets in a general repository such as ZENODO, Dryad, Dataverse, or others.
Small data may also be published as data files or packages supplementary to a research article, however, the authors should prefer in all cases a deposition in data repositories.