BAB V KESIMPULAN DAN SARAN

dokumen-dokumen yang mirip
BAB I PENDAHULUAN Latar Belakang

TATA KELOLA TEKNOLOGI INFORMASI

Entry Meeting Bimtek Kapabilitas APIP Ittama Setjen DPR RI. 8 Desember 2017

BAB VIII Control Objective for Information and related Technology (COBIT)

Gambar 1 Tampilan Menu Login

CobiT COBIT. CobiT The IT Governance Framework. CobiT diantara Standard Lain. document from IT Processes

MANAJEMEN PROYEK FRAMEWORK

Kriteria untuk evaluasi dan pemilihan pemasok (klausul 8.4.1)

Analisis Tata Kelola TI Dengan Menggunakan. Metode Cobit 4.1

Integrasi Sistem Manajemen. Ihda Taftazani

Customer Request/Complaint. Send jobs by SMS Technical Spv. Confirmasi Solve by SMS. Monitoring worktime

KONSEP SISTEM INFORMASI

Implementing COBIT in Higher Education. at South Louisiana Community College (SLCC) in Lafayette, Louisiana, USA.

1.1 Latar Belakang Masalah

Inisiasi, Perencanan dan Esekusi dalam Proyek

PENERAPAN FRAMEWORK COBIT UNTUK IDENTIFIKASI TINGKAT KEMATANGAN TATA KELOLA TEKNOLOGI INFORMASI: STUDI KASUS DI FASILKOM UNWIDHA

ANALISIS TATA KELOLA TEKNOLOGI INFORMASI PT. SURVEYOR INDONESIA MENGGUNAKAN KERANGKA KERJA COBIT (STUDI KASUS : PROSES DS 13 - MENGELOLA OPERASI)

HARMONISASI SISTEM MANAJEMEN ISO 9001 DAN ISO DI TAHUN 2015

COBIT 5: ENABLING PROCESSES

Pengembangan. Chapter Objectives. Chapter Objectives. Systems Approach to Problem Solving 11/23/2011

IT GOVERNANCE AND RISK MANAGEMENT

ABSTRAK. Kata Kunci : COBIT 4.1, DS, delivery and support. iii Universitas Kristen Maranatha

1.1 Latar Belakang Masalah

ABSTRAK. Kata kunci: COBIT 5, evaluasi, mengelola, tenaga kerja. vi Universitas Kristen Maranatha

BAB 4 EVALUASI PENGENDALIAN SISTEM INFORMASI PENJUALAN PADA PT. CHANDRA ASRI PETROCHEMICAL CENTER

Dimulai dengan mendefinisikan secara keseluruhan seluruh parameter proyek dan mengatur proyek secara tepat dan kualitas yang dibutuhkan untuk

SISTEM MANAJEMEN INTEGRASI/TERPADU

Tips untuk Mengembangkan strategi IS / IT. Tujuan dari Pengembangan Strategi IS / IT. Masalah Perencanaan IS. Hendri Sopryadi,M.T.

PT. KORINDO HEAVY INDUSTRY BALARAJA PLANT Ulasan manajemen Management Review

BAB I PENDAHULUAN. Instrumen TI seperti COBIT (Control Objective for Information and Related Technology) banyak memberikan panduan bagaimana mengukur

GARIS-GARIS BESAR PROGRAM PENGAJARAN PROGRAM STUDI: S1 SISTEM INFORMASI Semester : 7

Lampiran 1 PO 1 Define a Strategic IT plan

SIKLUS HIDUP PENGEMBANGAN SYSTEM

Jawab : ya, karena telah terbukti dengan mendapatkan reward dari airline atas

Plainning & Organization


ABSTRAK. Kata Kunci: frase COBIT 5, APO12, Manajemen, Risiko, Manajemen Risiko. Universitas Kristen Maranatha

BAB 4 EVALUASI PENGENDALIAN SISTEM INFORMASI PENJUALAN PADA S BU PERBERAS AN PT. PERTANI. 4.1 Rencana Kerja Evaluasi

Inggang Perwangsa Nuralam, SE., MBA

LAPORAN AUDIT DENGAN FRAMEWORK COBIT 4.0 WASHIN ID MANAJEMEN SUMBER DAYA IT

ABSTRAK. Kata Kunci: COBIT 5, APO (Align, Plan, Organize), IT Department, Petrochina International Companies. Universitas Kristen Maranatha

ABSTRACT. vii. Universitas Kristen Maranatha

Introduction to. Chapter12. Hiring, Training, and Evaluating Employees. MultiMedia by Stephen M. Peters South-Western College Publishing

BAB 4 EVALUASI PENGENDALIAN SISTEM INFORMASI PENJUALAN PADA PT. SRIKANDI DIAMOND MOTORS

Project Integration Management

STRATEGIC PLANNING Dindin Abdul Muiz Lidinillah

Software Quality Assurace 9/18/ :50 PM 1

1.1 Latar Belakang Masalah

Kendali dan Audit Sistem Informasi. Catatan: diolah dari berbagai sumber Oleh: mardhani riasetiawan

ABSTRAK. vi Universitas Kristen Maranatha

THE NATURE OF PROJECT. Objectives. Definisi Proyek

RAHMADINI DARWAS. Program Magister Sistem Informasi Akuntansi Jakarta 2010, Universitas Gunadarma Abstrak

DESIGN OF IT GOVERNANCE AT PT INTI (INDUSTRI TELEKOMUNIKASI INDONESIA) USING COBIT 5 FRAMEWORK ON BUILD, ACQUIRE AND IMPLEMENT (BAI) DOMAIN

3.1. Desain Penelitian Berikut merupakan desain penelitian yang akan digunakan untuk memberikan gambaran dalam melakukan penelitian :

BAB I PENDAHULUAN. Latar Belakang Masalah

Lampiran 1. - Tabel Kuisioner Domain ME1 Sub domain ME ME1.1

BAB I PENDAHULUAN 1.1. Latar Belakang

BAB IV PEMBAHASAN DAN HASIL PENELITIAN. Sesuai dengan metodologi penelitian dan langkah-langkah yang telah

Perancangan Model Kapabilitas Optimasi Sumber Daya TI Berdasarkan COBIT 5 Process Capability Model

Ilustrasi 1: Teknologi Kamera

KERANGKA KENDALI MANAJEMEN (KENDALI UMUM)

BAB II LANDASAN TEORI

REQUIREMENT ENGINEERING

Departemen Hukum dan HAM Republik Indonesia Agustus 2009

1.1 Latar Belakang Masalah

ABSTRAK. Kata Kunci: COBIT 5, APO (Align, Plan, Organise), PT. POS INDONESIA. Universitas Kristen Maranatha

Abstrak. Kata kunci : COBIT, audit

Project Integration Management. Inda Annisa Fauzani Indri Mahadiraka Rumamby

ABSTRAKSI. Kata Kunci: ITIL V3, ITIL v3 Service Strategy, Service Asset, Service Structure, Service Provider Type, Service Unit, Bisnis Unit

Manajemen Kinerja dan Kompensasi

BAB II LANDASAN TEORI

BAB 2 LANDASAN TEORI

ISO Management System

IT GOVERNANCE (TATA KELOLA IT)

ANALISIS PENGUKURAN TINGKAT KEMATANGAN MENGGUNAKAN KERANGKA COBIT 4.1 (STUDI KASUS: PT SMI)

Kualitas adalah derajat dari beberapa karakteristik pemenuhan requairement Terdiri dari beberapa aktifitas

ABSTRAK. Kata kunci : Manajemen Risiko TI, Risk Governance, Framework Risk IT

ABSTRACT. have been conducted in accordance with Auditing Standards and Code of Ethics Audit of

Manajemen Sumber Daya Teknologi Informasi TEAM DOSEN TATA KELOLA TI

PENYUSUNAN METODA PENGUKURAN KINERJA DAN PENENTUAN METRIK KINERJA TEKNOLOGI INFORMASI PADA SEKTOR PERBANKAN DENGAN IT BALANCED SCORECARD DAN COBIT

ABSTRAK. vi Universitas Kristen Maranatha

ABSTRAK. Kata kunci: IPOS, Sistem Informasi, Analisis, Quality Assurance Control Manajemen, Kontrol Oleh Ron Weber. Universitas Kristen Maranatha

2/5/2015. Internal Control Concepts. CDG4I3 / Audit Sistem Informasi. Angelina Prima K Gede Ary W. KK SIDE Overview

FORUM KOORDINASI PENGAWASAN APIP PUSAT DAN APIP DAERAH SEMARANG, 2 JUNI Oleh: Ir. Slamet Soedarsono, MPP, QIA, CRMP*)

BAB I PENDAHULUAN 1.1 Latar Belakang

TINJAUAN MENYELURUH SISTEM INFORMASI AKUNTANSI

MANAJEMEN (RISK MANAGEMENT)

Bab 2 Keputusan Perencanaan Strategi

Melihat hasil penelitian seperti di atas maka ada beberapa saran yang diberikan untuk peningkatan komitmen organsiasi di PT Telkom Tbk Kantor Divre V

Project Initiation. By: Uro Abd. Rohim. U. Abd.Rohim Manajemen Proyek (Project Initiation) Halaman: 1

ABSTRAKSI. Kata Kunci : Layanan Operasi, ITIL v3, proses bisnis, teknologi informasi.

ABSTRAK. Kata kunci : Manajemen, Risiko, COBIT 5, APO12

BAB 2 TINJAUAN PUSTAKA

BAB Menentukan Ruang Lingkup. produksi dengan menggunakan COBIT. dan IT internal perspective. 2. Menentukan Metodologi

MANAJEMEN RUANG LINGKUP PROYEK. Manajemen Proyek Teknologi Informasi

E-Business. Konsep Dasar ILKOM. Asep Wahyudin, M.T. (2398) Ilmu Komputer FPMIFA - Universitas Pendidikan Indonesia

KONTEKS & PROSES MANAJEMEN PROYEK. PERTEMUAN 2 Heru Lestiawan, M.Kom

Pengelolaan Proyek Sistem Informasi Manajemen Ruang Lingkup Proyek. Sistem Informasi Bisnis Pertemuan 2-3

PERANCANGAN TATA KELOLA TEKNOLOGI INFORMASI DI PT.INTI (INDUSTRI TELEKOMUNIKASI INDONESIA) MENGGUNAKAN FRAMEWORK COBIT 5 PADA DOMAIN EDM DAN MEA

TOPIK 4 MODEL MANAJEMEN MUTU

Transkripsi:

BAB V KESIMPULAN DAN SARAN 5.1 Kesimpulan 1. Perusahaan menyadari bahwa keselarasan antara strategi IT dan strategi perusahaan untuk jangka pendek dan jangka panjang harus selaras atau berkesinambungan 2. Keselarasan antara misi dan tujuan telah dilaksanakan, seperti slogan yang dimilikinya a delicious cousine destination tidak hanya menyediakan makanan yang bervariasi, lezat, dan lokasi yang nyaman. 3. Kepedulian mereka terhadap pelanggan sangat tinggi, lokasi mereka yang berada di pasar tanah abang blok A, dimana para pengunjungnya, banyak yang merasa kesulitan dalam melakukan transaksi elektronik pembelian makanan yang diinginkan, mereka dengan secara perlahan dan berkelanjutan tetap mempromosikan cara penggunaan transaksi elektronik tersebut. Dan telah membuahkan hasil, bahkan ini menjadi daya tarik tersendiri bagi foodcourt tersebut. 4. Pihak manajemen terus memperbaiki system yang ada, hal ini membuktikan bahwa pemikiran ditingkat manajemen tentang keselarasan antara strategis IT dan strategis bisnis perusahaan telah terbukti, walaupun mereka tidak mengikuti standar internasional untuk membuat keselarasan tersebut, tapi pemikiran bisnis mereka yang membuat hal tersebut menjadi hal yang menguntungkan dan membanggakan bagi manajemen disana. 77

78 5.2 Kesimpulan Berdasarkan COBIT 4.1 5.2.1 Penentuan Perencanaan Strategis IT 1. Perusahaan kurang menyadari pentingnya IT Value Management, dan telah melaksanakan strategi IT 2. Telah mempunyai perencanaan keselarasan antara strategi IT dan strategi Bisnis 3. Telah membuat rencana strategis yang melibatkan stakeholder terkait, dan secara umum telah membahas bagaimana IT dan bisnis diselaraskan dan pengertian bagaimana keduanya dapat saling mendukung 4. Telah melakukan IT tactical plan, walaupun belum sempurna dan terinci 5. Masih ada kekurangan mengenai full scope of effort untuk memperoleh outcomes, khususnya pada pendelegasian tanggung jawab untuk IT Support 6. Evaluasi terhadap IT tidak dilakukan secara berkala 5.2.2 Penentuan Arsitektur Informasi 1. Telah memiliki system arsitektur yang terintegrasi dari mulai transaksi penjualan, stok gudang, sampai laporan transaksi 2. Departemen IT yang kooperatif yang membantu users untuk penggunaan system yang berhubungan dengan pekerjaan mereka masing-masing 3. Telah terdapat pembagian hak akses pada sistem yang berjalan 4. Adanya standar operasional yang menjamin terintegrasinya tiaptiap bagian

79 5.2.3 Pemilihan Arah Teknologi 1. Teknologi yang dimiliki merupakan teknologi terkini dari mulai transaksi penjualan, stok gudang, sampai laporan transaksi 2. Telah mempunyai rencana infrastruktur IT, yang telah diselaraskan sehingga dapat mendukung bisnis pada lingkungan yang kompetitif, integrasi pada level staff dan pada level aplikasi dan platform 3. Standard teknologi yang ada telah sesuai relefansinya dengan bisnis perusahaan dan IT 4. Kurang adanya evaluasi pada arsitektur sistem secara berkala, yang dapat memastikan tingkat selaras antara IT dan bisnis 5.2.4 Penentuan proses, struktur organisasi, dan hubungan IT 1. Tidak adanya kerangka kerja internal control 2. Tidak adanya IT Committee pada level pimpinan perusahaan, tetapi pimpinan perusahaan sendiri yang mempunyai keinginan untuk menselaraskan IT dan bisni 3. Tidak adanya IT steerting committee yang dapat menentukan prioritas investasi IT yang akan digunakan 4. Terdapat IT Support pada setiap departemen yang siap membantu dan memberikan laporan kepada manajemen IT 5. Kurang adanyan evaluasi struktur organisasi IT untuk dapat mencapai tujuan bisnis dan keadaan yang berubah 6. Kurang adanya peraturan yang jelas mengenai batasan IT department dengan end-user 7. Tidak formilnya fungsi QA, dalam hal kepuasan penggunaan IT dalam organisasi 8. Personnel yang ada masing-masing mereka mempunyai tanggung jawab dan tugas masing-masing juga 9. Evaluasi yang kurang memadai untuk kebutuhan staff IT

80 10. Mempunyai key person yang memegang seluruh sistem informasi 5.2.5 Pengelolaan Investasi IT 1. Kurang adanya kerangka kerja rencana keuangan pada IT 2. Terdapat Prioritas belanja IT 3. Perusahaan telah memiliki nilai prioritas dalam belanja IT 4. Tidak ada evaluasi dari nilai prioritas IT 5. Tidak memiliki tools untuk menilai seberapa besar nilai kontribusi IT terhadap bisnis 5.2.6 Pengkomunikasian tujuan dan sasaran manajemen 1. Perusahaan telah memiliki control terhadap inventory IT dan juga telah disesuaikan dengan misi perusahaan 2. Perusahaan telah memiliki control atas resiko IT dan sejalan dengan tujuan perusahaan tetapi kerangka kerja yang digunakan tidak menggunakan kerangka kerja standar internasional 3. Perusahaan telah memiliki peraturan yang mendukung Strategi IT 4. Perusahaan telah melaksanakan dan menjalankan IT, dimana semua karyawan dan penyewa foodstall menjadi satu kesatuan harus menggunakan IT 5. Perusahaan telah memberikan pengertian kepada seluruh karyawan tentang Strategi IT yang digunakan 5.2.7 Pengelolaan sumber daya manusia bidang IT 1. Perusahaan telah menjalankan prosedur perekrutan staff IT yang sesuai dengan prosedur dan aturan perusahaan, tetapi untuk keterampilan dari staff IT kurang memenuhi kebutuhan perusahaan 2. Perusahaan tidak terlalu menginginkan staff IT yang berpengalaman

81 3. Perusahaan memberikan knowledge-transfer kepada staff IT yang dianggap pantas untuk itu 4. Staff IT diberikan pelatihan, diharapkan dapat memenuhi keterampilan yang dibutuhkan untuk pekerjaannya 5.2.8 Pengelolaan kualitas 1. Perusahaan tidak menggunakan QMS yang berstandar internasional 2. Menggunakan best practices untuk meselaraskan IT dan bisnis 3. Memperhatikan kebutuhan penyewa foodstall dan pelanggan untuk penggunaan sistem yang berjalan 4. Improvisasi yang dilakukan ada, walaupun tidak terlalu terlihat 5. Tetap melaukan monitoring agar sistem dapat terus sesuai dengan kebutuhan bisnis dan IT 5.2.9 Perkiraan dan pengelolaan resiko IT Pengelolaan resiko memang ada di perusahaan, tetapi tidak adanya kerangka kerja yang sesuai standard, tetapi hal ini tidak menghambat strategi IT dan bisnis yang berjalan 5.2.10 Pengelolaan proyek-proyek IT Kerangka kerja dalam pengelolaan proyek IT sesuai dengan yang dibutuhkan perusahaan dan selesai dengan tepat waktu, ini dikarenakan pimpinan perusahaan, IT, dan stakeholder semuanya mempunyai komitmen yang jelas dan solid untuk menyelesaikan proyek ini, masing-masing dari mereka telan mempunyai cakupan tentang yg mereka inginkan di dalam proyek.

82 5.3 Saran 1. Sedikit merubah cara pandang manajemen, yaitu dengan penggunaan prosedur sesuai dengan standar internasional, pendokumentasian, prosedur pelaksanaan, pelaksanaan operasional, prosedur pembuatan arsitektur system, prosedur sumber daya manusia, diskripsi pekerjaan, pelatihan dan prosedur kualitas. 2. Evaluasi secara berkala dan berkelanjutan melalui pengawasan internal dan eksternal untuk memantau seluruh prosedur yang ada. Pengawasan dapat dilaksanakan dengan menggunakan COBIT, salah satu framework untuk melakukan audit keselarasan. 5.4 Saran berdasarkan COBIT 4.1 5.4.1 Penentuan Perencanaan Strategis IT 1. IT Value Management, Establish fair, transparent, repeatable and comparable evaluation of business cases, including financial worth, the risk of not delivering a capability and the risk of not realising the expected benefits. 2. Business-IT Alignment, Establish processes of bi-directional education and reciprocal involvement in strategic planning to achieve business and IT alignment and integration. Mediate between business and IT imperatives so priorities can be mutually agreed.

83 3. Assessment of Current Capability and Performance, Assess the current capability and performance of solution and service delivery to establish a baseline against which future requirements can be compared. Define performance in terms of IT s contribution to business objectives, functionality, stability, complexity, costs, strengths and weaknesses. 4. IT Strategic Plan, Create a strategic plan that defines, in co-operation with relevant stakeholders, how IT goals will contribute to the enterprise s strategic objectives and related costs and risks. It should include how IT will support IT-enabled investment programmes, IT services and IT assets. IT should define how the objectives will be met, the measurements to be used and the procedures to obtain formal sign-off from the stakeholders. The IT strategic plan should cover investment/operational budget, funding sources, sourcing strategy, acquisition strategy, and legal and regulatory requirements. The strategic plan should be sufficiently detailed to allow for the definition of tactical IT plans. 5. IT Tactical Plans, Create a portfolio of tactical IT plans that are derived from the IT strategic plan. The tactical plans should address IT-enabled programme investments, IT services and IT assets. The tactical plans should describe required IT initiatives, resource requirements, and how the use of resources and achievement of benefits will be monitored and managed. The tactical plans should be sufficiently detailed to allow the definition of project plans. Actively manage the set of tactical IT plans and initiatives through analysis of project and service portfolios. 6. IT Portfolio Management, Actively manage with the business the portfolio of IT-enabled investment programmes required to achieve specific strategic business objectives by identifying, defining, evaluating, prioritising, selecting,

84 initiating, managing and controlling programmes. This should include clarifying desired business outcomes, ensuring that programme objectives support achievement of the outcomes, understanding the full scope of effort required to achieve the outcomes, assigning clear accountability with supporting measures, defining projects within the programme, allocating resources and funding, delegating authority, and commissioning required projects at programme launch. 5.4.2 Penentuan Arsitektur Informasi 1. Enterprise Information Architecture Model, Establish and maintain an enterprise information model to enable applications development and decision-supporting activities, consistent with IT plans as described in PO1. The model should facilitate the optimal creation, use and sharing of information by the business in a way that maintains integrity and is flexible, functional, cost-effective, timely, secure and resilient to failure. 2. Enterprise Data Dictionary and Data Syntax Rules, Maintain an enterprise data dictionary that incorporates the organisation s data syntax rules. This dictionary should enable the sharing of data elements amongst applications and systems, promote a common understanding of data amongst IT and business users, and prevent incompatible data elements from being created. 3. Data Classification Scheme, Establish a classification scheme that applies throughout the enterprise, based on the criticality and sensitivity (e.g., public, confidential, top secret) of enterprise data. This scheme should include details about data ownership; definition of appropriate security levels and protection controls; and a brief description of data retention and destruction

85 requirements, criticality and sensitivity. It should be used as the basis for applying controls such as access controls, archiving or encryption. 4. Integrity Management, Define and implement procedures to ensure the integrity and consistency of all data stored in electronic form, such as databases, data warehouses and data archives. 5.4.3 Pemilihan Arah Teknologi 1. Technological Direction Planning, Analyse existing and emerging technologies, and plan which technological direction is appropriate to realise the IT strategy and the business systems architecture. Also identify in the plan which technologies have the potential to create business opportunities. The plan should address systems architecture, technological direction, migration strategies and contingency aspects of infrastructure components. 2. Technology Infrastructure Plan, Create and maintain a technology infrastructure plan that is in accordance with the IT strategic and tactical plans. The plan should be based on the technological direction and include contingency arrangements and direction for acquisition of technology resources. It should consider changes in the competitive environment, economies of scale for information systems staffing and investments, and improved interoperability of platforms and applications. 3. Monitor Future Trends and Regulations, Establish a process to monitor the business sector, industry, technology, infrastructure, legal and regulatory environment trends. Incorporate the consequences of these trends into the development of the IT technology infrastructure plan.

86 4. Technology Standards, To provide consistent, effective and secure technological solutions enterprisewide, establish a technology forum to provide technology guidelines, advice on infrastructure products and guidance on the selection of technology, and measure compliance with these standards and guidelines. This forum should direct technology standards and practices based on their business relevance, risk and compliance with external requirements. 5. IT Architecture Board, Establish an IT architecture board to provide architecture guidelines and advice on their application, and to verify compliance. This entity should direct IT architecture design, ensuring that it enables the business strategy and considers regulatory compliance and continuity requirements. 5.4.4 Penentuan proses, struktur organisasi, dan hubungan IT 1. IT Process Framework, Define an IT process framework to execute the IT strategic plan. This framework should include an IT process structure and relationships (e.g., to manage process gaps and overlaps), ownership, maturity, performance measurement, improvement, compliance, quality targets and plans to achieve them. It should provide integration amongst the processes that are specific to IT, enterprise portfolio management, business processes and business change processes. The IT process framework should be integrated into a quality management system (QMS) and the internal control framework. 2. IT Strategy Committee, Establish an IT strategy committee at the board level. This committee should ensure that IT governance, as part of enterprise

87 governance, is adequately addressed; advise on strategic direction; and review major investments on behalf of the full board. 3. IT Steering Committee, Establish an IT steering committee (or equivalent) composed of executive, business and IT management to: Determine prioritisation of IT-enabled investment programmes in line with the enterprise s business strategy and priorities Track status of projects and resolve resource conflict Monitor service levels and service improvements 4. Organisational Placement of the IT Function, Place the IT function in the overall organisational structure with a business model contingent on the importance of IT within the enterprise, specifically its criticality to business strategy and the level of operational dependence on IT. The reporting line of the CIO should be commensurate with the importance of IT within the enterprise. 5. IT Organisational Structure, Establish an internal and external IT organisational structure that reflects business needs. In addition, put a process in place for periodically reviewing the IT organisational structure to adjust staffing requirements and sourcing strategies to meet expected business objectives and changing circumstances. 6. Establishment of Roles and Responsibilities, Establish and communicate roles and responsibilities for IT personnel and end users that delineate between IT personnel and end-user authority, responsibilities and accountability for meeting the organisation s needs. 7. Responsibility for IT Quality Assurance, Assign responsibility for the performance of the quality assurance (QA) function and provide the QA

88 group with appropriate QA systems, controls and communications expertise. Ensure that the organisational placement and the responsibilities and size of then QA group satisfy the requirements of the organisation. 8. Responsibility for Risk, Security and Compliance, Embed ownership and responsibility for IT-related risks within the business at an appropriate senior level. Define and assign roles critical for managing IT risks, including the specific responsibility for information security, physical security and compliance. Establish risk and security management responsibility at the enterprise level to deal with organisationwide issues. Additional security management responsibilities may need to be assigned at a system-specific level to deal with related security issues. Obtain direction from senior management on the appetite for IT risk and approval of any residual IT risks. 9. Data and System Ownership, Provide the business with procedures and tools, enabling it to address its responsibilities for ownership of data and information systems. Owners should make decisions about classifying information and systems and protecting them in line with this classification. 10. Supervision, Implement adequate supervisory practices in the IT function to ensure that roles and responsibilities are properly exercised,to assess whether all personnel have sufficient authority and resources to execute their roles and responsibilities, and to generally review KPIs. 11. Segregation of Duties, Implement a division of roles and responsibilities that reduces the possibility for a single individual to compromise a critical process. Make sure that personnel are performing only authorised duties relevant to their respective jobs and positions.

89 5.4.5 Pengelolaan Investasi IT 1. Financial Management Framework, Establish and maintain a financial framework to manage the investment and cost of IT assets and services through portfolios of IT enabled investments, business cases and IT budgets. 2. Prioritisation Within IT Budget, Implement a decision-making process to prioritise the allocation of IT resources for operations, projects and maintenance to maximise IT s contribution to optimising the return on the enterprise s portfolio of IT-enabled investment programmes and other IT services and assets. 3. IT Budgeting, Establish and implement practices to prepare a budget reflecting the priorities established by the enterprise s portfolio of ITenabledinvestment programmes, and including the ongoing costs of operating and maintaining the current infrastructure. The practicesshould support development of an overall IT budget as well as development of budgets for individual programmes, with specific emphasis on the IT components of those programmes. The practices should allow for ongoing review, refinement and approval of the overall budget and the budgets for individual programmes. 4. Cost Management, Implement a cost management process comparing actual costs to budgets. Costs should be monitored and reported. Where there aredeviations, these should be identified in a timely manner and the impact of those deviations on programmes should be assessed.together with the business sponsor of those programmes, appropriate remedial action should be taken and, if necessary, theprogramme business case should be updated.

90 5. Benefit Management, Implement a process to monitor the benefits from providing and maintaining appropriate IT capabilities. IT s contribution to the business, either as a component of IT-enabled investment programmes or as part of regular operational support, should be identified and documented in a business case, agreed to, monitored and reported. Reports should be reviewed and, where there are opportunities to improve IT s contribution, appropriate actions should be defined and taken. Where changes in IT s contribution impact the programme, or where changes to other related projects impact the programme, the programme business case shouldbe updated. 5.4.6 Pengkomunikasian tujuan dan sasaran manajemen 1. IT Policy and Control Environment, Define the elements of a control environment for IT, aligned with the enterprise s management philosophy and operating style. These elements should include expectations/requirements regarding delivery of value from IT investments, appetite for risk, integrity, ethical values, staff competence, accountability and responsibility. The control environment should be based on a culture that supports value delivery whilst managing significant risks, encourages cross-divisional co-operation and teamwork, promotes compliance and continuous process improvement, and handles process deviations (including failure) well. 2. Enterprise IT Risk and Control Framework, Develop and maintain a framework that defines the enterprise s overall approach to IT risk and control and that aligns with the IT policy and control environment and the enterprise risk and control framework.

91 3. IT Policies Management, Develop and maintain a set of policies to support IT strategy. These policies should include policy intent; roles and responsibilities; exception process; compliance approach; and references to procedures, standards and guidelines. Their relevance should be confirmed and approved regularly. 4. Policy, Standard and Procedures Rollout, Roll out and enforce IT policies to all relevant staff, so they are built into and are an integral part of enterprise operations. 5. Communication of IT Objectives and Direction, Communicate awareness and understanding of business and IT objectives and direction to appropriate stakeholders and users throughout the enterprise. 5.4.7 Pengelolaan sumber daya manusia bidang IT 1. Personnel Recruitment and Retention, Maintain IT personnel recruitment processes in line with the overall organisation s personnel policies and procedures (e.g., hiring, positive work environment, orienting). Implement processes to ensure that the organisation has an appropriately deployed IT workforce with the skills necessary to achieve organisational goals. 2. Personnel Competencies, Regularly verify that personnel have the competencies to fulfil their roles on the basis of their education, training and/or experience. Define core IT competency requirements and verify that they are being maintained, using qualification and certification programmes where appropriate.

92 3. Staffing of Roles, Define, monitor and supervise roles, responsibilities and compensation frameworks for personnel, including the requirement to adhere to management policies and procedures, the code of ethics, and professional practices. The level of supervision should be in line with the sensitivity of the position and extent of responsibilities assigned. 4. Personnel Training, Provide IT employees with appropriate orientation when hired and ongoing training to maintain their knowledge, skills, abilities, internal controls and security awareness at the level required to achieve organisational goals. 5. Dependence Upon Individuals, Minimise the exposure to critical dependency on key individuals through knowledge capture (documentation), knowledge sharing,succession planning and staff backup. 6. Personnel Clearance Procedures, Include background checks in the IT recruitment process. The extent and frequency of periodic reviews of these checks should depend on the sensitivity and/or criticality of the function and should be applied for employees, contractors and vendors. 7. Employee Job Performance Evaluation, Require a timely evaluation to be performed on a regular basis against individual objectives derived from the organisation s goals, established standards and specific job responsibilities. Employees should receive coaching on performance and conduct whenever appropriate. 8. Job Change and Termination, Take expedient actions regarding job changes, especially job terminations. Knowledge transfer should be arranged, responsibilities reassigned and access rights removed such that risks are minimised and continuity of the function is guaranteed.

93 5.4.8 Pengelolaan kualitas 1. Quality Management System, Establish and maintain a QMS that provides a standard, formal and continuous approach regarding quality management that isaligned with business requirements. The QMS should identify quality requirements and criteria; key IT processes and their sequence and interaction; and the policies, criteria and methods for defining, detecting, correcting and preventing non-conformity. The QMS should define the organisational structure for quality management, covering the roles, tasks and responsibilities. All key areas should develop their quality plans in line with criteria and policies and record quality data. Monitor and measure the effectiveness and acceptance of the QMS, and improve it when needed 2. IT Standards and Quality Practices, Identify and maintain standards, procedures and practices for key IT processes to guide the organisation in meeting the intent of the QMS. Use industry good practices for reference when improving and tailoring the organisation s quality practices. 3. Development and Acquisition Standards, Adopt and maintain standards for all development and acquisition that follow the life cycle of the ultimate deliverable, and include sign-off at key milestones based on agreed-upon sign-off criteria. Consider software coding standards; naming conventions; file formats; schema and data dictionary design standards; user interface standards; interoperability; system performance efficiency; scalability; standards for development and testing; validation against requirements; test plans; and unit, regression and integration testing.

94 4. Customer Focus, Focus quality management on customers by determining their requirements and aligning them to the IT standards and practices. Define roles and responsibilities concerning conflict resolution between the user/customer and the IT organisation. 5. Continuous Improvement, Maintain and regularly communicate an overall quality plan that promotes continuous improvement. 6. Quality Measurement, Monitoring and Review, Define, plan and implement measurements to monitor continuing compliance to the QMS, as well as the value the QMS provides. Measurement, monitoring and recording of information should be used by the process owner to take appropriate corrective and preventive actions. 5.4.9 Perkiraan dan pengelolaan resiko IT 1. IT Risk Management Framework, Establish an IT risk management framework that is aligned to the organisation s (enterprise s) risk management framework. 2. Establishment of Risk Context, Establish the context in which the risk assessment framework is applied to ensure appropriate outcomes. This should include determining the internal and external context of each risk assessment, the goal of the assessment, and the criteria against which risks are evaluated. 3. Event Identification, Identify events (an important realistic threat that exploits a significant applicable vulnerability) with a potential negative impact on the goals or operations of the enterprise, including business, regulatory, legal, technology, trading partner, human resources and operational aspects.

95 Determine the nature of the impact and maintain this information. Record and maintain relevant risks in a risk registry. 4. Risk Assessment, Assess on a recurrent basis the likelihood and impact of all identified risks, using qualitative and quantitative methods. The likelihood and impact associated with inherent and residual risk should be determined individually, by category and on a portfolio basis. 5. Risk Response, Develop and maintain a risk response process designed to ensure that cost-effective controls mitigate exposure to risks on a continuing basis. The risk response process should identify risk strategies such as avoidance, reduction, sharing or acceptance; determine associated responsibilities; and consider risk tolerance levels. 6. Maintenance and Monitoring of a Risk Action Plan, Prioritise and plan the control activities at all levels to implement the risk responses identified as necessary, including identification of costs, benefits and responsibility for execution. Obtain approval for recommended actions and acceptance of any residual risks, and ensure that committed actions are owned by the affected process owner(s). Monitor execution of the plans, and report on any deviations to senior management. 5.4.10 Pengelolaan proyek-proyek IT 1. Programme Management Framework, Maintain the programme of projects, related to the portfolio of IT-enabled investment programmes, by identifying, defining, evaluating, prioritising, selecting, initiating, managing and controlling projects. Ensure that the projects support the programme s objectives. Co-ordinate the activities and interdependencies of multiple

96 projects, manage the contribution of all the projects within the programme to expected outcomes, and resolve resource requirements and conflicts. 2. Project Management Framework, Establish and maintain a project management framework that defines the scope and boundaries of managing projects, as well as the method to be adopted and applied to each project undertaken. The framework and supporting method should be integrated with the programme management processes. 3. Project Management Approach, Establish a project management approach commensurate with the size, complexity and regulatory requirements of each project. The project governance structure can include the roles, responsibilities and accountabilities of the programme sponsor, project sponsors, steering committee, project office and project manager, and the mechanisms through which they can meet those responsibilities (such as reporting and stage reviews). Make sure all IT projects have sponsors with sufficient authority to own the execution of the project within the overall strategic programme. 4. Stakeholder Commitment, Obtain commitment and participation from the affected stakeholders in the definition and execution of the project within the context of the overall IT-enabled investment programme. 5. Project Scope Statement, Define and document the nature and scope of the project to confirm and develop amongst stakeholders a common understanding of project scope and how it relates to other projects within the overall IT enabled investment programme. The definition should be formally approved by the programme and project sponsors before project initiation.

97 6. Project Phase Initiation, Approve the initiation of each major project phase and communicate it to all stakeholders. Base the approval of the initial phase on programme governance decisions. Approval of subsequent phases should be based on review and acceptance of the deliverables of the previous phase, and approval of an updated business case at the next major review of the programme. In the event of overlapping project phases, an approval point should be established by programme and project sponsors to authorise project progression. 7. Integrated Project Plan, Establish a formal, approved integrated project plan (covering business and information systems resources) to guide project execution and control throughout the life of the project. The activities and interdependencies of multiple projects within a programme should be understood and documented. The project plan should be maintained throughout the life of the project. The project plan, and changes to it, should be approved in line with the programme and project governance framework. 8. Project Resources, Define the responsibilities, relationships, authorities and performance criteria of project team members, and specify the basis for acquiring and assigning competent staff members and/or contractors to the project. The procurement of products and services required for each project should be planned and managed to achieve project objectives using the organisation s procurement practices. 9. Project Risk Management, Eliminate or minimise specific risks associated with individual projects through a systematic process of planning, identifying, analysing, responding to, monitoring and controlling the areas or events that have the potential to cause unwanted change. Risks faced by the project management process and the project deliverable should be established and centrally recorded.

98 10. Project Quality Plan, Prepare a quality management plan that describes the project quality system and how it will be implemented. The plan should be formally reviewed and agreed to by all parties concerned and then incorporated into the integrated project plan.