PERJANJIAN PELAKSANAAN SAP ERP S/4 HANA /
AGREEMENT OF SAP ERP S/4 HANA
ANTARA / BETWEEN
PT NTT DATA BUSINESS SOLUTIONS
DAN / AND
PT JHONLIN GROUP
Perjanjian Pelaksanaan SAP ERP S/4 HANA (untuk
selanjutnya disebut sebagai “Perjanjian”) ini dibuat dan
ditandatangani pada hari ini [insert day, date, month,
year] oleh dan antara:
I. PT JHONLIN GROUP, suatu perseroan terbatas yang
diatur dan didirikan berdasarkan hukum Negara
Republik Indonesia, berkedudukan dan berkantor di
Jl. Raya Kodeco Km. 1, Ds. Gunung Antasari, Simpang
Empat, Tanah Bumbu, Kalimantan Selatan, 72271,
dalam perbuatan hukum ini diwakili secara sah oleh
_____ dalam jabatannya selaku _________, dengan
demikian sah bertindak untuk dan atas nama PT
Jhonlin Group, untuk selanjutnya disebut sebagai
“Pelanggan”; dan
II. PT NTT DATA BUSINESS SOLUTIONS, suatu
perseroan terbatas yang diatur dan didirikan
berdasarkan hukum Negara Republik Indonesia,
berkedudukan dan berkantor pusat di Wisma BCA,
Wing A, Lantai PH, Jl. Kapten Soebijanto
Djojohadikusumo, BSD City, Lengkong Gudang-
Serpong, Tangerang Selatan, dalam perbuatan
hukum ini diwakili secara sah oleh Hafferson H.
Manurung dalam jabatannya selaku Managing
Director yang bertindak untuk dan atas nama PT
NTT DATA BUSINESS SOLUTIONS, selanjutnya
disebut sebagai “NDBS”.
Pelanggan dan NDBS selanjutnya bersama-sama disebut
“Para Pihak” dan secara sendiri-sendiri disebut “Pihak”.
Bahwa, Pelanggan bermaksud melakukan kerjasama
dengan NDBS untuk melakukan pekerjaan Implementasi
SAP ERP S/4 HANA.
Page 1 of 44
This Agreement for SAP ERP S/4 HANA (hereinafter
shall be referred to as “Agreement”) is entered into
and executed on this day [insert day, date, month,
year] by and between:
I. PT JHONLIN GROUP, a limited liability company
governed and established under the laws of the
republic of Indonesia, having its domicile and
registered office at Jl. Raya Kodeco Km. 1, Ds.
Gunung Antasari, Simpang Empat, Tanah Bumbu,
Kalimantan Selatan, 72271 and is duly
represented by _____ in his/her capacity as a
________ therefore validly acts for and on behalf
of PT Jhonlin Group, hereinafter shall be referred
to as the “Customer”, and
II. PT NTT DATA BUSINESS SOLUTIONS, a Limited
liability Company governed and established under
the laws of the Republic of Indonesia, having its
domicile and registered office at Wisma BCA,
Wing A, Lantai PH, Jl. Kapten Soebijanto
Djojohadikusumo, BSD City, Lengkong Gudang-
Serpong, Tangerang Selatan, and is duly
represented by Hafferson H. Manurung in his
capacity as a Managing Director acting for and on
behalf of PT NTT DATA BUSINESS SOLUTIONS,
hereinafter shall be referred to as “NDBS”.
Customer and NDBS are hereinafter referred to as
“THE Parties” and individually as “Party”.
Whereas Customer intends to engage NDBS to
provide Implementation of SAP ERP S/4 HANA.
NDBS Customer
Berdasarkan hal-hal tersebut di atas dan dengan itikad Based on the above and in good faith, the Parties
baik, Para Pihak sepakat mengenai syarat-syarat dan mutually agree on the terms and conditions of Work
ketentuan-ketentuan pelaksanaan Pekerjaan performance (as defined below) as follows:
(sebagaimana didefinisikan dibawah) sebagai berikut:

PASAL 1 ARTICLE 1
ISTILAH DAN DEFINISI TERMS AND DEFINITIONS

Istilah-istilah yang dipergunakan dalam Perjanjian ini The terms used in this Agreement and its attachments
maupun lampian-lampirannya akan mempunyai arti shall have the meanings or definitions as follows:
atau definisi sebagai berikut:

1. Pekerjaan adalah layanan dan Deliverables yang 1. Work means the services and Deliverables to be
akan diberikan oleh NDBS yang dijabarkan secara provided by the NDBS as more fully described in
penuh pada Lampiran I, II dan III dalam Perjanjian ini. Attachments I, II and III of this Agreement.

2. Lokasi Kerja adalah lokasi dimana Pekerjaan akan 2. Work Site means the location(s) where the Work
dilaksanakan sebagaimana yang dimaksud dalam will be delivered as specified in Attachment I.
Lampiran I.

3. Deliverables adalah hasil Pekerjaan berupa barang 3. Deliverables means the result of Work as form of
dan/atau jasa yang dilakukan oleh NDBS berdasarkan good(s) and/or service(s) that implementing by
Perjanjian ini. NDBS based on this Agreement.

4. End Customer adalah pihak yang memiliki Pekerjaan 4. End Customer means the party that owned the
dimana menggunakan barang dan/atau jasa. Work which uses the goods and/or services.

5. Key User adalah perwakilan End-Customer yang 5. Key User means the End-Customer’s
memiliki peran dalam memonitor atau memantau representatives who are in charge of monitoring
dan/atau mengarahkan pekerjaan, menyediakan and/or supervising the Project, providing required
kebutuhan persetujuan dan informasi untuk approvals and information for the completion of
penyelesaian Pekerjaan termasuk bisnis, teknis dan the Work including business, technical and
kebutuan fungsional. functional requirements.

PASAL 2 ARTICLE 2
MAKSUD DAN TUJUAN PURPOSES AND OBJECTIVES

Tunduk pada syarat-syarat dan ketentuan-ketentuan Subject to such terms and conditions as set forth in this
sebagaimana diatur dalam Perjanjian ini, Pelanggan Agreement, Customer appoints NDBS and NDBS
menunjuk NDBS dan NDBS dengan ini menyatakan hereby accepts and agrees to perform the Work.
menerima dan setuju untuk melaksanakan Pekerjaan.

Page 2 of 44
NDBS Customer
 PASAL 3 ARTICLE 3
JANGKA WAKTU PERJANJIAN DAN JADWAL THE PERIOD OF AGREEMENT AND WORK
PELAKSANAAN PEKERJAAN IMPLEMENTATION SCHEDULE

Perjanjian ini berlaku efektif terhitung sejak tanggal
dimulainya Pekerjaan sebagaimana dituliskan secara
rinci dalam jadwal pelaksanaan Pekerjaan dalam
Lampiran II Perjanjian ini dan akan tetap berlaku sampai
dengan diselesaikannya seluruh hak dan kewajiban
setiap Pihak sebagaimana diatur dalam Perjanjian ini.
This Agreement shall be valid from the commencing of
the Work as stipulated details in schedule of the Work
in Attachment II of this Agreement and shall continue
to be valid until the completion of all each Party’s
rights and obligations as set forth in this Agreement.

PASAL 4 ARTICLE 4
RUANG LINGKUP PEKERJAAN SCOPE OF WORK

1. Lingkup Pekerjaan adalah yang tercantum pada 1. The scope of Work is specified in Attachment I of
Lampiran I Perjanjian ini. this Agreement.

2. Apabila terdapat pertentangan antara istilah di
dalam Perjanjian dan istilah di dalam Lampiran I
tentang Lingkup Pekerjaan, yang terakhir akan
berlaku sejauh berkaitan dengan ruang lingkup
layanan dan Deliverables yang akan disediakan oleh
NDBS.
2. In the event of a conflict between the terms of this
Agreement and the terms of Attachment I on
Scope of Work, the latter shall prevail insofar as it
relates to the scope of service and Deliverables to
be provided by NDBS.

PASAL 5 ARTICLE 5
BIAYA DAN CARA PEMBAYARAN FEES AND PAYMENT TERMS

1. Biaya secara keseluruhan tertuang pada Lampiran III 1. The total fees are stated in Attachment III on
tentang Komersial pada Perjanjian ini. Commercial of this Agreement.

2. Jika tidak ditentukan lain di dalam Lampiran III 2. If not stated otherwise in Attachment III on
tentang Komersial, biaya tidak termasuk out-of- Commercial, fees do not include out-of-pocket
pocket pengeluaran seperti Travel, per diem, expenses such as travel, per diem,
akomodasi, taxi, konsumsi, dan biaya untuk izin kerja accommodation, taxis, meals and costs for work
atau visa, yang akan ditanggung oleh Pelanggan. permits or visas, which will be borne by the
Customer.

Page 3 of 44
NDBS Customer
3. Setelah penyelesaian terkait milestone pembayaran
yang relevan oleh NDBS, NDBS akan menyerahkan
dokumen penagihan kepada Pelanggan untuk
persetujuan yang tidak akan ditahan atau ditunda
tanpa alasan. Pelanggan akan memiliki waktu
maksimum 5 (lima) hari kerja untuk menyetujui
dokumen penagihan. Setelah disetujui, Pelanggan
akan membayar jumlah yang ditagih sesuai dengan
Pasal 5 ayat 5. Jika lebih dari 5 (lima) hari kerja
Pelanggan tidak memberikan konfirmasi kepada
NDBS atas persetujuan dokumen-dokumen tagihan,
maka Pelanggan dianggap telah menyetujui
dokumen-dokumen tagihan dan biaya tersebut
menjadi jatuh tempo dan dapat dibayarkan.
4. Dokumen – dokumen yang perlu dilampirkan oleh
NDBS untuk penagihan adalah sebagai berikut:
• Berita Acara Serah Terima Pekerjaan masing-
masing tahap sesuai tahapan penagihan
• Invoice
• Faktur Pajak
• Surat Setoran Pajak
• Fotokopi NPWP
• Fotokopi Surat Keterangan Pengusaha Kena Pajak
(PKP)
5. Tagihan yang telah disetujui akan dibayarkan oleh
Pelanggan kepada NDBS 14 (empat belas) hari
kalender setelah seluruh dokumen di atas diterima
dan disetujui Pelanggan. Pembayaran tersebut
dalam Pasal ini akan dibayar oleh Pelanggan
kepada NDBS dengan cara transfer kepada:
Nama Perusahaan / Company Name
Bank
Cabang / Branch
Mata Uang / Currency
No. Rekening / No. Account
Pelanggan berkewajiban memberikan bukti
potong pajak telah dibayarkan kepada Instansi
Pemerintah yang sesuai jika diminta oleh NDBS,
dalam waktu 60 (enam puluh) hari kalender sejak
tanggal tagihan.
Page 4 of 44
3. Upon completion of the relevant payment
milestone by NDBS, NDBS will submit the billing
documents to the Customer for approval which
shall not be unreasonably withheld or delayed. The
Customer will have a maximum of 5 (five) business
days to approve the billing documents. Upon
approval, the Customer will pay the invoiced
amount in accordance with Article 5 paragraph 5.
If more than 5 (five) business days the Customer
does not provide confirmation to NDBS for
approval of billing documents, then the Customer
is deemed to have approved these documents and
the applicable Fees will become due and payable.
4. The documents that need to be attached by NDBS
for billing are as follows:
• The Minutes of work handover at each phase
according to the phases of invoicing
• Invoice
• Tax Invoice
• Tax Deposit Slip
• Copy of TIN (Taxpayer ID. No.)
• Copy of Taxable entrepreneur certificate (PKP)
5. The approved invoice will be paid by Customer
to NDBS within 14 (fourteen) calendar days after
all of the above documents have been received
and approved by the Customer. Such payment as
referred to in this article will be paid by
Customer to NDBS by way of transfer to:
: PT NTT DATA BUSINESS SOLUTIONS
: Bank Mandiri
: BSD
: Rupiah (Rp.) / Indonesian Rupiah (IDR)
: 164-0033322332
Customer is obliged to give a tax receipt that has
been paid to the relevant Government Instance
if requested by NDBS, within 60 (sixty) calender
days since invoice date.
NDBS Customer
6. NDBS akan membebankan bunga atas 6. NDBS will charge a late payment interest on all
keterlambatan untuk semua jumlah yang jatuh past-due amounts at the rate set out in Article
tempo berdasarkan nilai yang ditetapkan dalam 10. In addition to and without prejudice to other
Pasal 10. Sebagai tambahan dan tanpa remedies available to NDBS, NDBS reserves the
mengurangi solusi lain yang tersedia untuk NDBS, right to suspend the performance of the Work if
NDBS mencadangkan haknya untuk Customer delay to make payment. The Work
menangguhkan kinerja Pekerjaan apabila suspension is in effect from notification to
Pelanggan terlambat dalam melakukan Customer until payment is received by NDBS. For
pembayaran. Penangguhan Pekerjaan berlaku the purposes of paragraph 6, notification sent
sejak pemberitahuan kepada Pelanggan sampai via email by the NDBS is sufficient.
pembayaran diterima oleh NDBS. Untuk keperluan
ayat 6 ini, pemberitahuan yang dikirimkan melalui
email oleh NDBS sudah cukup.

7. Pelanggan akan mengganti kerugian dan
membebaskan NDBS terhadap pihak ketiga atas
segala biaya, denda, kehilangan, tanggung jawab,
klaim, kerusakan, tuntutan dan pengeluaran atau
penalti yang ditimbulkan oleh NDBS (termasuk
ongkos biaya perkara) karena pelanggaran oleh
Pelanggan terkait kewajiban pembayaran di Pasal 5
dan/atau penegakan NDBS atas ketentuan pada
Pasal 5.
7. Customer will indemnify and hold harmless NDBS
against any costs, fines, loss, liability, claims,
damages, demands and expenses or penalties
incurred by NDBS (including costs of legal fees) due
to Customer’s breach of its payment obligations in
Article 5 and/or NDBS’s enforcement of Article 5.

PASAL 6 ARTICLE 6
PAJAK TAX

Segala pajak-pajak dan bea-bea yang berkaitan dengan
pelaksanaan Perjanjian ini sepenuhnya menjadi
tanggung jawab masing-masing Pihak sesuai dengan
ketentuan yang diatur di dalam peraturan perundang-
undangan yang berlaku.
All taxes and duties relating to the execution of this
Agreement shall be solely the responsibility of each
Party in accordance with the provisions set forth in
the law regulation of applicable provisions.

PASAL 7 ARTICLE 7
PERSONIL PERSONNEL

NDBS berkewajiban untuk menyediakan personil NDBS is obliged to provide personnel for the
sebagaimana ketentuan atas Pekerjaan. provision of Work.

Page 5 of 44
NDBS Customer
 PASAL 8
TANGGUNG JAWAB PELANGGAN
1. Pelanggan bertanggung jawab untuk:
a. Menyediakan sarana dan prasarana seperti ruang
kerja, meja, printer, scanner, mesin fotokopi dan
jaringan data komunikasi, koneksi internet,
peralatan atau sistem yang dibutuhkan NDBS
untuk melaksanakan Pekerjaan di Lokasi Kerja/
secara remote serta infrastruktur pendukung
hardware seperti power supply, coolling system
(jika dibutuhkan).
b. Melakukan seluruh kewajibanya sebagaimana
diatur di dalam Lampiran I tentang Ruang
Lingkup Pekerjaan, termasuk personil dan
sumber daya yang diperlukan untuk Pekerjaan.
2. Pelanggan akan bekerja sama sepenuhnya dan
bertindak secara wajar dan dengan itikad baik
untuk membantu dalam kemajuan Pekerjaan
secara tepat waktu dan pemenuhan kewajiban
NDBS sesuai dengan Perjanjian ini termasuk
penyediaan semua informasi dan persetujuan yang
diperlukan untuk melaksanakan Pekerjaann.
3. Pelanggan akan bertanggung jawab untuk
menyiapkan Lokasi Kerja dan memberikan NDBS
akses untuk memasuki lokasi Kerja serta
mengizinkan untuk melakukan Pekerjaan.
4. Pelanggan menjamin untuk memberikan NDBS akses
dengan tepat waktu kepada dan/atau menyediakan
Key User yang memiliki informasi yang diperlukan
dan tingkat otoritas yang diperlukan oleh NDBS
untuk melakukan Pekerjaan.
5. Pelanggan akan bertanggung jawab penuh untuk
memastikan bahwa End-Customer atau Key User
tersedia dan akan secara wajar membantu dan
bekerja sama dengan NDBS dalam penyelesaian
Pekerjaan secara tepat waktu.
6. Setelah penyelesaian setiap milestone proyek dalam
Lampiran II tentang Timeline Pekerjaan, NDBS akan
menyerahkan sertifikat penyelesaian berupa Berita
Page 6 of 44
ARTICLE 8
CUSTOMER’S RESPONSIBILITIES
1. Customer shall be responsible for:
a. Providing an access to facilities and
infrastructures such as office space, desks,
printers, scanners, photocopy machine, data
communication network, internet connection,
equipment or systems required by NDBS to
perform the Work at the Work Sites/remote
and hardware infrastructure support as power
supply, coolling System (if needed).
b. The performance of all its obligations specified
in Attachment I on Scope of Work, including the
necessary personnel and resources for the
Project.
2. Customer will cooperate fully and act reasonably
and in good faith to assist in the timely progress of
Work and fulfillment of NDBS’s obligations
pursuant to this Agreement including the provision
of all information and approvals required for the
performance of Work.
3. Customer will be responsible for preparation of the
Work Site and give NDBS the access to enter the
Work Site and permit to perform the Work.
4. Customer warrants to provide NDBS with timely
access to and/or make available Key Users who
have the required information and authority levels
needed by NDBS to perform the Work.
5. Customer shall be fully responsible to ensure that
the End-Customer or Key Users are available and
will reasonably assist and cooperate with NDBS in
the timely completion of the Work.
6. Upon the completion of each project milestone in
Attachment II on Timeline of Work, NDBS will
submit a certificate of completion as form as
NDBS Customer
 Acara Serah Terima (BAST) kepada Pelanggan untuk
ditinjau dan/atau disetujui. Pelanggan akan memiliki
waktu maksimal 5 (lima) hari kerja untuk menyetujui
dan menandatangani BAST ("Periode Persetujuan").
Jika BAST disetujui, NDBS akan mulai bekerja pada
milestone berikutnya.
7. Jika pada akhir Periode Persetujuan, Pelanggan tidak
memberikan tanggapannya, maka Pelanggan
dianggap telah menyetujuinya dan NDBS akan
melanjutkan Pekerjaan ke tahap/ milestone
selanjutnya.
8. Jika Pelanggan, yang bertindak secara wajar dengan
memberikan peninjauan/ klarifikasi, maka NDBS
akan menanggapi tinjauan/klairifkasi tersebut. Para
Pihak akan saling menyetujui rencana remediasi
untuk milestone proyek yang diklarifikasi dan NDBS
harus memperbaiki semua kekurangan atau cacat
material sesuai dengan rencana remediasi. Setelah
menyelesaikan pekerjaan perbaikan, NDBS akan
mengirimkan kembali BAST untuk mendapat
persetujuan Pelanggan. Prosedur yang ditetapkan
dalam Pasal 8 ayat 6, 7 dan 8 harus diulang sampai
Pelanggan menyetujui BAST.
9. Terlepas dari apa pun dalam Perjanjian ini,
Pelanggan tidak dapat meminta perbaikan terhadap
NDBS sehubungan dengan keterlambatan pasokan
salah satu Pekerjaan atau milestone proyek atau
kegagalan untuk menyelesaikan bagian dari
Pekerjaan atau milestone proyek dimana
keterlambatan atau kegagalan secara langsung atau
tidak langsung atas tindakan atau kelalaian dari
Pelanggan, End-Customer atau pihak ketiga mana
pun yang tidak berada di bawah kendali NDBS atau
pelanggaran oleh Pelanggan atas Perjanjian ini.
NDBS akan menginformasikan kepada Pelanggan
dalam waktu yang wajar untuk mengetahui adanya
keterlambatan tersebut. Pelanggan akan
bertanggung jawab untuk membayar kepada NDBS
atas segala biaya, kewajiban, atau pengeluaran yang
masuk akal (termasuk biaya personil) yang mungkin
telah dilakukan oleh NDBS sebagai konsekuensi dari
Page 7 of 44
Minutes of Delivery to the Customer (BAST) for
review and/or approval. The Customer will have
up to 5 (five) business days to approve and sign
BAST (“Acceptance Period”). If BAST is approved,
NDBS will commence work on the next milestone.
7. If at the expiry of the Acceptance Period, Customer
does not give its response, then the Customer
have to deemed accepted and NDBS will continue
to the next milestone of Work.
8. If Customer, acting reasonably with the
observation/ clarification, then NDBS will address
the observation/clarification. The Parties shall
mutually agree upon a remediation plan for the
clarification of project milestone and NDBS shall
rectify all material deficiencies or defects in
accordance with the remediation plan. Upon
completion of the rectification work, NDBS will re-
submit the BAST for Customer’s approval. The
procedure set out in Articles 8 paragraph 6, 7 and
8 shall be repeated until Customer approves BAST.
9. Notwithstanding anything in this Agreement,
Customer has no remedy against NDBS in relation
to a delayed supply of any of the Work or project
milestones or failure to complete any portion of
the Work or project milestone where the delay or
failure is the direct or indirect result of any act or
omission of the Customer, End-Customer or any
third party not under the control of NDBS or a
breach by the Customer of this Agreement. NDBS
will notify the Customer within a reasonable time
of it becoming aware of any such delay. Customer
will be responsible for payment to NDBS for any
reasonable costs, liability, or expenses (including
personnel costs) that NDBS may incur as a
consequence of any such delay or failure under
this clause
NDBS Customer
 keterlambatan atau kegagalan yang dimaksud dalam
klausul ini.
PASAL 9
TANGGUNG JAWAB NDBS
1. NDBS bertanggung-jawab untuk merencanakan,
melaksanakan, menyelesaikan dan memelihara
semua Pekerjaan sesuai dengan syarat-syarat dan
ketentuan-ketentuan sebagaimana diatur dalam
Perjanjian ini.
2. NDBS harus menyediakan konsultan dengan
pengetahuan yang cukup untuk melakukan
Pekerjaan. Personil harus dapat diandalkan,
terampil, dan berpengalaman dalam bidang
Pekerjaan sesuai kebutuhan berdasarkan Perjanjian
ini.
3. NDBS dalam melakukan Pekerjaan berkewajiban
untuk mematuhi persyaratan peraturan perundang-
undangan yang berlaku untuk bisnis dan kinerja dari
NDBS, termasuk Pelanggan atau aturan/ kebijakan
internal End-Customer yang diberikan kepada NDBS
sebelumnya secara tertulis.
PASAL 10
KETERLAMBATAN
1. Apabila keterlambatan pembayaran Pekerjaan
sebagaimana Pasal 5 ayat 5 diatas oleh Pelanggan,
maka Pelanggan akan dikenakan bunga sebesar 1,5%
(satu koma lima persen) per bulan (18% per anum)
yang dihitung setiap bulannya dari tagihan yang
telah jatuh tempo.
2. Apabila terjadi keterlambatan penyelesaian
Pekerjaan disebabkan oleh Pelanggan termasuk
penundaan pekerjaan dalam Pasal 5 ayat (7) diatas
dibuktikan berdasarkan MoM, korespodensi dan
dokumen-dokumen pendukung lainnya, maka NDBS
berhak untuk meminta perubahan jangka waktu
Pekerjaan serta biaya lainya yang timbul akibat
adanya penundaan keterlambatan penyelesaian
Page 8 of 44
ARTICLE 9
NDBS’S RESPONSIBILITIES
1. NDBS shall be responsible for planning, executing,
completing and maintaining all of Work according
to such terms and conditions set forth in this
Agreement.
2. NDBS shall have to provide a consultant with
required sufficient knowledge to perform the
Work. Manpower must be reliable, skilled, and
experienced in Work field as needed under this
Agreement.
3. NDBS in performing Work is obliged to obey and
abide by the requirements of statutory regulation
applicable to NDBS’s business and performance of
the Work including Customer’s or End-Customer
internal rule/ policy that are provided to NDBS in
advance and in writing.
ARTICLE 10
DELAY
1. In the event of a delay in the payment of a project
milestone as set forth in Article 5 paragraph 5 by
the Customer, Customer will be imposed with an
interest of 1.5% (one and one-half percent) per
month (18% per annum) calculated monthly on
the past due amount.
2. In the event of any delay in the Work caused by
Customer including suspension of Work under
Article 5 paragraph (7) above, proved pursuant to
minutes of meetings, correspondence and other
supporting documents, or any change in the scope
of Work and fees, NDBS shall be entitled to ask for
the change to working period as well as other costs
that arise due to such delay in the completion of
NDBS Customer
 Pekerjaan. Perubahan dalam Perjanjian akan melalui
prosedur Pasal 13.
PASAL 11
KEWAJIBAN DAN GANTI RUGI
1. Tanggung jawab agregat maksimum dari NDBS
sehubungan dengan Perjanjian ini, dalam hal terjadi
kelalaian, gugatan, berdasarkan undang-undang
atau lainnya, akan terbatas pada biaya yang telah
dibayarkan oleh Pelanggan kepada NDBS sesuai
dengan Lampiran III tentang Komersial.
2. Dalam hal apa pun, Pihak mana pun tidak akan
bertanggung jawab kepada Pihak lain atas kerugian
konsekuensial atau tidak langsung yang diderita oleh
Pihak lain tersebut, seperti namun tidak terbatas
pada kehilangan keuntungan, kerugian produksi,
kehilangan bisnis, kehilangan data, kehilangan niat
baik, intteruption dalam bisnis, apakah salah satu
pihak mengetahui kemungkinan kerugian tersebut
atau kerugian semacam itu tidak dapat diperkirakan
sebelumnya.
PASAL 12
MASA SUPPORT
1. Masa/jangka waktu Support dilakukan efektif sejak
selesainya Go-Live sebagaimana diatur didalam
dengan Lampiran II tentang Timeline Pekerjaan.
2. Selama masa berlakunya Support NDBS wajib
melakukan atau memberikan layanan/jasa
perbaikan atas kesalahan dan cacat (defect) pada
Deliverable yang telah disetujui oleh Para Pihak
dalam dokumen Fit-Gap, yang menyebabkan tidak
dapat beroperasinya solusi, work around/action plan
terhadap masalah yang terjadi sejak Go-Live.
3. Layanan/jasa perbaikan sebagaimana dimaksud
dalam ayat (2) di atas tidak berlaku apabila
Pelanggan tanpa sepengetahuan dan persetujuan
NDBS melakukan modifikasi terhadap aplikasi atau
hasil pekerjaan yang dibangun/dikembangkan oleh
NDBS.
Page 9 of 44
Work. Any change in the Agreement will go
through the procedure in Article 13.
ARTICLE 11
LIABILITY AND INDEMNIFY
1. The maximum aggregate liability of the NDBS
under and in connection with this Agreement,
whether in negligence, tort, under statute or
otherwise, will be limited to the fees already paid
by Customer to NDBS pursuant to Attachment III
on Commercial.
2. In no event whatsoever shall either Party be liable
to the other Party for any consequential or indirect
loss suffered by said other Party, such as but not
limited to loss of profit, loss of production, loss of
business, loss of data, loss of goodwill, business
intteruption, whether or not a party knew of the
possibility of such loss, or such loss was otherwise
foreseeable.
ARTICLE 12
SUPPORT PERIOD
1. The validity period of Support shall be performed
effective from the completion of Go-Live in
accordance with Attachment II on Timeline of
Work.
2. During the validity period of Support, NDBS is
obliged to conduct or provide a rectification
service on any fault and defect in the Deliverable
approved by the Parties in Fit-Gap document,
which causes the non-operation of solution, work
around/ action plan to any problem that occurs
after Go-Live.
3. Such rectification service as referred to in
paragraph (2) above shall not be applicable if
Customer, End-Customer or a third party, without
NDBS’s acknowledgement and approval made a
modification to the application or work result
built/ developed by NDBS.
NDBS Customer
4. Setelah Periode Support berakhir, Para Pihak akan
menadatangani Berita Acara berakhirnya masa
Support yang diberikan oleh NDBS.
PASAL 13
PEKERJAAN TAMBAHAN
1. Para Pihak dapat melakukan perubahan terhadap
rencana Pekerjaan, Pekerjaan ataupun bagian dari
Pekerjaan apabila dianggap perlu atau dianggap
lebih baik untuk pelaksanaan Pekerjaan berdasarkan
kesepakatan Para Pihak, dan Para Pihak harus
melaksanakan perubahan dimaksud sebagai berikut:
a. Menambah lingkup Pekerjaan yang tercantum
dalam dokumen Perjanjian; dan/atau
b. Melaksanakan pekerjaan-pekerjaan tambahan
yang diperlukan untuk menyelesaikan Pekerjaan.
2. Dalam hal penambahan lingkup Pekerjaan
sebagaimana dimaksud pada ayat (1) Pasal ini
mengakibatkan penambahan atas nilai Perjanjian
dan/atau perubahan jangka waktu pelaksanaan
Pekerjaan, maka akan dilakukan penyesuaian nilai
Perjanjian dan/atau jangka waktu pelaksanaan
Pekerjaan berdasarkan kesepakatan tertulis Para
Pihak yang dituangkan dalam bentuk
addendum/amandemen terhadap Perjanjian ini.
3. Perubahan-perubahan atas Pekerjaan tidak boleh
dilaksanakan oleh NDBS tanpa adanya suatu
perintah perubahan. Perintah perubahan tersebut
harus diberikan secara tertulis oleh Pelanggan.
Dalam keadaan mendesak, perintah perubahan
tersebut dapat diberikan secara tertulis melalui
email oleh pihak yang ditunjuk untuk bertindak
untuk dan atas nama Pelanggan, yang selanjutnya
dikonfirmasi dengan perintah tertulis resmi dari
Pelanggan dalam waktu 2 (dua) hari kalender sejak
perintah tersebut disampaikan kepada NDBS.
4. Para Pihak wajib melaksanakan setiap perubahan
bagian Pekerjaan seperti yang tersebut pada ayat (1)
Page 10 of 44
4. Upon the expiry of Support Period, the Parties will
sign a Minutes of Delivery for the completion of
Support by NDBS.
ARTICLE 13
ADDED WORK
1. The Parties may make any change to the Work
plan, Work or part of work when deemed
necessary or deemed better for the
implementation of Work under the Parties mutual
agreement, and the Parties shall have to execute
said change as follows:
a. To add the scope of Work contained in the
Agreement document; and/or
b. To perform additional works required to
complete the Work.
2. In the event that such addition to the scope of
work as referred to in paragraph (1) of this Article
causes any addition to the fees and/or a change to
Work period, then it will be made an adjustment
on the fees and/or Work period under the Parties
written agreement stated out in the form of
addendum/amendment to this Agreement.
3. Any changes to the Work shall not be performed
by NDBS without an instructon for change. Said
instruction for change must be given in writing by
Customer. In an urgent condition, said instruction
for change can be given in writing by email by the
party appointed to act for and on behalf of
Customer, which hereinafter shall be confirmed by
an official written instruction from Customer
within 2 (two) calendar days since the instruction
was delivered to NDBS.
4. The Parties are obliged to perform each change to
such part of Work as referred to in paragraph (1)
NDBS Customer
 Pasal ini setelah adanya kesepakatan tertulis Para
Pihak.
5. Setiap perubahan terhadap jangka waktu
penyelesaian Pekerjaan dan/atau nilai Perjanjian
yang disebabkan karena adanya perubahan
Pekerjaan sebagaimana tersebut pada ayat (1) Pasal
ini (apabila ada) akan dituangkan secara tertulis oleh
Para Pihak dalam bentuk suatu amandemen atau
purchase order tambahan terhadap Perjanjian.
6. Jika perubahan dalam ruang lingkup Pekerjaan
selama masa Pekerjaan dikarenakan akibat dari
kesalahan Pelanggan maka NDBS berhak untuk
meminta perubahan dan Pelanggan berkewajiban
untuk melakukan perubahan atas nilai harga atau
perubahan jangka waktu Perjanjian, dan jika
perubahan tersebut dinilai dapat menyebabkan
tidak berjalanya pelaksanaan Pekerjaan oleh NDBS
maka NDBS berhak untuk memutuskan Perjanjian
tanpa dikenakan denda atas pemutusan kontrak
oleh Pelanggan.
PASAL 14
PERNYATAAN DAN JAMINAN
1. Para Pihak menyatakan dan menjamin bahwa
memiliki wewenang hukum untuk menandatangani
Perjanjian ini termasuk namun tidak terbatas pada
mendapatkan persetujuan perusahaan yang
dibutuhkan berdasarkan “Anggaran Dasar” dari Para
Pihak.
2. Seluruh Deliverables dan personil yang harus
disediakan oleh NDBS, serta cara, kecepatan
pelaksanaan dan pemeliharaan Pekerjaan harus
dilaksanakan oleh NDBS berdasarkan persyaratan
didalam Perjanjian ini.
Page 11 of 44
of this Article upon a written mutual agreement of
the Parties.
5. Any change to the work completion period and/or
the fees in Agreement caused by a change to the
work as referred to in paragraph (1) of this article
(if any) will be spelled out in writing by the Parties
in the form of an amendment or an additional
purchase order to the Agreement.
6. If such change in the scope of Work during the
Work period is due to Customer’s negligence, then
NDBS shall be entitled to request for a change and
the Customer is obliged to make changes to the
fees or to the Agreement period, and if said
change is deemed capable of causing the un-
performance of work by NDBS then NDBS is
entitled to terminate the Agreement without
being imposed with a penalty for the termination
of contract by Customer.
ARTICLE 14
REPRESENTATIONS AND WARRANTIES
1. THE Parties represent and warrants that it has the
legal authority to enter into this Agreement
including but not limited to obtain any required
corporate approval under “The Articles of
Association” of the Parties.
2. All Deliverables and personnel that must be
provided by NDBS, as well as the method, speed of
implementation and maintenance of Work must
be performed by NDBS accordance with
requirement in this Agreement
NDBS Customer
 PASAL 15
RESIKO DAN KEPEMILIKAN
1. Risiko kerusakan atau kehilangan Deliverables akan
berpindah ke Pelanggan (i) pada saat pengiriman
oleh NDBS kepada Pelanggan sesuai dengan jadwal
yang disepakati oleh Para Pihak; atau (ii) jika NDBS
memasang Deliverables di tempat, kecuali jika
disetujui sebaliknya, pada saat pengiriman di
tempat.
2. Kepemilikan resmi untuk Deliverables hanya akan
berpindah kepada Pelanggan ketika NDBS telah
menerima pembayaran untuk Deliverables tersebut
secara penuh dan, sejauh diizinkan oleh undang-
undang yang berlaku, NDBS menerima pembayaran
secara penuh dari semua jumlah lainnya yang jatuh
tempo oleh Pelanggan berdasarkan perjanjian
lainnya dengan NDBS (atau afiliasinya). Sampai
kepemilikan yang sah atas Deliverables diberikan
kepada Pelanggan, Pelanggan harus (i) tidak
mengasimilasi, mentransfer, menjaminkan atau
menggadaikan apapun terhadap Deliverables, atau
memberikan hak atau beban apa pun dalam
Deliverables kepada pihak ketiga mana pun, dan (ii)
memastikan bahwa Deliverables tetap dapat
diidentifikasi sebagai Deliverables yang dimiliki oleh
NDBS. Jika terjadi pelanggaran oleh Pelanggan, NDBS
dapat meminta Pelanggan untuk mengembalikan ke
NDBS, atas biaya Pelanggan (termasuk biaya untuk
de-instalasi), semua Deliverables dimana yang
kepemilikannya belum berpindah dan Pelanggan
sepenuhnya akan bekerja sama untuk menyebabkan
NDBS untuk mengumpulkan Deliverables tersebut
dan memberikan akses gratis NDBS (atau
perwakilannya) ke lokasi Deliverables, dan peralatan
lain yang disediakan dan/atau digunakan oleh NDBS
dalam pelaksanaan Pekerjaan.
PASAL 16
PENUNDAAN PEKERJAAN
1. Atas alasan yang layak Pelanggan dapat meminta
kepada NDBS untuk menunda pelaksanaan
Pekerjaan atau bagian Pekerjaan selama jangka
waktu tertentu yang dianggap perlu oleh Pelanggan.
Page 12 of 44
ARTICLE 15
RISK AND TITLE
1. Risk of damage to or loss of Deliverables will pass
to Customer (i) upon delivery by NDBS to Customer
in accordance with the agreed schedule by the
Parties; or (ii) in the event that NDBS installs the
Deliverables on-site, unless agreed otherwise,
upon delivery on-site.
2. Official ownership to Deliverables will be
transferred to the Customer only when NDBS has
received payment for such Deliverables in full and,
to the extent permitted by applicable law, NDBS
received payment in full of all other amounts due
by Customer under any other agreement with
NDBS (or any of its affiliates). Until official
ownership to Deliverable has transferred to the
Customer, Customer shall (i) not assimilate,
transfer, pledge, or lien any of the Deliverables, or
grant any right or title in the Deliverables to any
third party and (ii) ensure that the Deliverables
remain identifiable as Deliverables owned by
NDBS. In the event of breach by the Customer,
NDBS may require Customer return to NDBS, at
Customer’s cost (including costs for de-
installation), all Deliverables in which the title has
not yet passed and Customer shall fully cooperate
to enable NDBS to collect such Deliverables and
grant NDBS (or its representative) free access to
the location of the Deliverables, and other
equipment supplied and/or used by NDBS in the
performance of Work.
ARTICLE 16
POSTPONEMENT OF WORK
1. Based on an appropriate reason, Customer may
ask NDBS to postpone the implementation of Work
or part of work for a certain period deemed
necessary by Customer..
NDBS Customer
2. Perintah penundaan Pekerjaan oleh Pelanggan
kepada NDBS harus dilakukan secara tertulis.
Perintah tersebut harus menyatakan dengan jelas
tanggal dan perkiraan jangka waktu penundaan.
Dalam keadaan mendesak, dapat diberikan perintah
penundaan melalui email, yang selanjutnya
dikonfirmasi dengan perintah tertulis resmi dari
Pelanggan dalam waktu 3 (tiga) hari kalender sejak
perintah tersebut disampaikan kepada NDBS.
3. Segera setelah NDBS menerima perintah penundaan
Pekerjaan dari Pelanggan, maka NDBS akan
melaporkan status akhir dari Pekerjaan dan NDBS
berhak melakukan penagihan dan menerima
pembayaran atas nilai Pekerjaan secara proporsional
sampai dengan kemajuan Pekerjaan (progres atas
milestone) yang sedang berjalan pada saat tanggal
efektif penundaan Pekerjaan.
4. Atas alasan yang layak Pelanggan sewaktu-waktu
dapat menyatakan selesainya masa penundaan
Pekerjaan dan memerintahkan NDBS untuk
melanjutkan kembali pelaksanaan Pekerjaan dengan
pemberitahuan 14 (empat belas) hari kerja sebelum
Pekerjaan dilanjutkan kembali.
5. Dalam hal Penundaan terjadi dikarenakan bukan
karena kesalahan NDBS maka Pelanggan
berkewajiban membayar kepada NDBS, biaya yang
diperlukan secara wajar yang ditanggung oleh NDBS
sebagai akibat penundaan tersebut.
6. NDBS berhak untuk mengakhiri Perjanjian jika
Pelanggan menunda dan/atau terlambat dalam
pembayaran biaya untuk Pekerjaan selama lebih dari
30 (tiga puluh) hari kalender atau periode yang lebih
lama seperti yang disepakati oleh NDBS atas
kebijakannya sendiri. Pengakhiran Perjanjian
tersebut akan diajukan secara tertulis dari NDBS
kepada Pelanggan. Setelah penghentian tersebut,
Pelanggan akan segera membayar NDBS semua
biaya, pengeluaran (jika ada) dan denda yang
dihitung sesuai dengan Pasal 10 ayat (1).
Page 13 of 44
2. Any instruction for work postponement by
Customer to NDBS must be made in writing. Said
instruction must state clearly the date and
estimated period of postponement. In an urgent
condition, it can be given an instruction for
postponement writing by email which hereinafter
shall be confirmed by an official written instruction
from Customer within 3 (three) calendar days since
the instruction was delivered to NDBS.
3. Immediately since NDBS receives an instruction for
Work postponement from Customer, NDBS will
report the final status of Work and NDBS shall be
entitled to make a collection and receive the
payment for work value proportionally up to the
progress of work (the progress on milestone) which
is running on the effective date of Work
Postponement.
4. Based on an appropriate reason, Customer at any
time may declare the completion of Work
postponement period and instruct NDBS to resume
the implementation of Work by 14 (fourteen)
business day’s notice prior to the resume of work.
5. In case that a postponement occurring not caused
by NDBS’s fault, then Customer is obliged to pay to
NDBS, any cost reasonably required which was
borne by NDBS as the consequence of said
postponement.
6. NDBS shall be entitled to terminate the Agreement
if Customer postpones and/or delays in paying the
Fees for the work for more than 30 (thirty)
calendar days or such longer period as agreed by
NDBS at its sole discretion. Such termination of
Agreement will be submitted in writing from NDBS
to Customer. Upon such termination, Customer
shall promptly pay NDBS all the outstanding fees,
expenses (if any) and any interest calculated in
accordance with Article 10 paragraph (1).
NDBS Customer
7. Setiap perubahan terhadap jangka waktu
penyelesaian Pekerjaan dan/atau biaya Perjanjian
yang disebabkan karena adanya penundaan
Pekerjaan sebagaimana tersebut pada ayat (1) Pasal
ini (apabila ada) akan dituangkan secara tertulis oleh
Para Pihak dalam bentuk suatu amandemen atau
tambahan/addendum terhadap Perjanjian.
8. Jika Pekerjaan dilakukan penundaan lebih dari 10
(sepuluh) hari kerja oleh Pelanggan maka NDBS
berhak mengganti personil yang ditempatkan di
dalam Pekerjaan.
PASAL 17
FORCE MAJEURE
1. Masing-masing Pihak dibebaskan dari tanggung
jawab atas keterlambatan atau kegagalan dalam
melaksanakan isi dari Perjanjian ini yang disebabkan
karena terjadinya Force Majeure.
2. Yang dimaksud dengan Force Majeure adalah semua
kejadian yang timbul diluar kendali atau kekuasaan
manusia pada umumnya yang mengakibatkan
Pelanggan maupun NDBS tidak dapat melaksanakan
sebagian maupun seluruh kewajibannya, yaitu
antara lain: gempa bumi, tsunami, taufan, badai,
perang, tindakan teroris, pandemi atau keadaan
bahaya lain yang diumumkan secara resmi
Pemerintah, kebakaran yang bukan disebabkan oleh
kelalaian Pelanggan maupun NDBS, aturan yang
diterbitkan oleh Pemerintah baik Pusat maupun
Daerah yang secara langsung berpengaruh terhadap
tidak dapat dilaksanaannya kewajiban-kewajiban
Para Pihak sebagaimana diatur dalam Perjanjian ini.
3. Apabila terjadi Force Majeure, maka Pihak yang
bersangkutan harus melaporkan kepada Pihak
lainnya disertai keterangan resmi dari pejabat
Pemerintah setempat yang berwenang, selambat-
lambatnya dalam jangka waktu 7 (tujuh) hari
kalender setelah terjadinya Force Majeure.
4. Jika dalam jangka waktu sebagaimana dimaksud
pada ayat (3) Pasal ini, Pihak yang terkena Force
Majeure tidak memberitahukan kepada Pihak
Page 14 of 44
7. Any change to the Work completion period and/or
the fees of Agreement caused by a postponement
to the work as referred to in paragraph (1) of this
Article (if any) will be spelled out in writing by the
Parties in the form of an amendment or an
addendum to the Agreement.
8. If the Work is postponed more than 10 (ten)
business days by Customer then NDBS has the right
to replace the personnel placed in the Work .
ARTICLE 17
FORCE MAJEURE
1. Either Party shall be relieved from the
responsibility for any delay or failure in performing
the contents of this Agreement which is caused by
a Force Majeure condition.
2. Force Majeure means is all of incidents that occur
beyond human’s control or power in general which
makes Customer or NDBS unable to perform part
or the whole of its obligations, namely among
others: earthquake, tsunami, typhoon, storm, war,
terroris act, pandemic or any other dangerous
condition announced officially by the government,
fire that is due to Customer’s or NDBS’s negligence,
a rule issued by the government either central or
regional which has a direct influence on the non-
exectuable of the Parties’ obligations as set forth
in this Agreement.
3. In the event of a Force Majeure, the affected Party
shall have to report it to other Party along with an
official statement from local authorized
government officers, no later than 7 (seven)
calendar days since the Force Majeure occurred.
4. If within such period as referred to in paragraph (3)
of this article, the Party affected by a Force
Majeure event does not inform the other Party or
NDBS Customer
 lainnya atau jika Pihak lainnya dapat membuktikan
bahwa kejadian yang dimaksud bukan karena Force
Majeure maka hal tersebut dianggap tidak pernah
terjadi dan oleh karenanya semua risiko yang timbul
atas keadaan tersebut menjadi beban dan tanggung
jawab Pihak yang bersangkutan.
PASAL 18
PEMUTUSAN PERJANJIAN
1. Pelanggan dapat memutuskan Perjanjian secara
lebih awal dalam hal terjadi keadaan sebagai berikut:
a. Force Majeure (keadaan kahar) melebihi 60
(enam puluh) hari berturut turut yang
menyebabkan tidak terselesaikannya Pekerjaan
setelah diambil langkah-langkah sebagaimana
disebutkan dalam Pasal 17;
b. NDBS melakukan pelanggaran terhadap syarat-
syarat dan ketentuan-ketentuan Perjanjian atau
NDBS tidak melaksanakan kewajibannya setelah
NDBS mendapatkan 2 (dua) kali surat teguran
dengan masing-masing surat berlaku untuk 30
(tiga puluh) hari kalender sebagaimana yang telah
ditetapkan dalam Perjanjian dan pelanggaran
atau non-kinerja tersebut tidak dapat
disembuhkan setelah jangka waktu surat teguran
kedua berakhir atau 30 (tiga puluh) hari kalender
sejak diterimanya pemberitahuan tertulis surat
teguran kedua dari Pelanggan;
c. NDBS berada dalam keadaan bangkrut (pailit);
d. Apabila Pelanggan memutuskan Perjanjian
karena sebab sebagaimana tersebut diatas, maka
NDBS tetap berhak mendapatkan pembayaran
secara proporsional sampai dengan kemajuan
Pekerjaan yang sedang berjalan pada saat
dilakukan pemutusan Perjanjian ditambah biaya
bahan atau alat yang telah dibeli oleh NDBS untuk
Pekerjaan tersebut dengan ketentuan
selanjutnya bahan atau alat tersebut sepenuhnya
menjadi hak milik Pelanggan.
Page 15 of 44
if the other Party is able to prove that said event is
not due to a Force Majeure, then said event shall
be deemed as never occurred and therefore all of
risks that arise from said condition shall become
the relevant Party’s burden and responsibility.
ARTICLE 18
TERMINATION OF AGREEMENT
1. Customer may terminate the Agreement earlier in
the event of such conditions as follows:
a. Force Majeure event exceeding a period of 60
(sixty) consecutive days which results in the
un-completion of work after it has been taken
such measures as mentioned in Article 17;
b. NDBS committed a material violation ofthe
terms and conditions of the Agreement or
NDBS does not perform its obligations after
the NDBS receives 2 (two) letters of reprimand
with each letter valid for 30 (thirty) calendar
days as set forth in the Agreement, and such
violation or non-performance is not cured
after the period of second letter of reprimand
ended or at least 30 (thirty) calendar days from
receipt of a second written notice from
Customer;
c. NDBS is in bankrupt (insolvent) condition;
d. If Customer terminates the Agreement due to
such causes as mentioned above, then NDBS
shall remain entitled to receive a payment on
proportional basis up to the progress of work
which is running when the termination is made
added by the cost of material or equipment
purchased by NDBS for said work provided that
thereafter said materials or equipment shall
become Customer’s property.
NDBS Customer
2. NDBS dapat memutuskan Perjanjian secara lebih
awal dalam hal terjadi keadaan sebagai berikut:
a. Pelanggan tidak dapat melaksanakan kewajiban
seperti diatur dalam Perjanjian dan
ketidakberhasilan tersebut tidak diperbaiki dalam
waktu 30 (tiga puluh) hari kalender sejak
diterimanya pemberitahuan tertulis dari NDBS;
b. Force Majeure (keadaan kahar) yang terjadi
melebihi 60 (enam puluh) hari berturut turut
yang menyebabkan tidak terselesaikannya
Pekerjaan setelah diambil langkah-langkah
sebagaimana disebutkan dalam Pasal 17;
c. Pelanggan menunda pelaksanaan pekerjaan lebih
dari 30 (tiga puluh) hari kalender;
d. Pelanggan melakukan perubahan secara material
dan major terhadap Ruang Lingkup Pekerjaan
yang mengakibatkan tidak terselesaikannya
Pekerjaan.
e. Apabila NDBS memutuskan Perjanjian karena
sebab sebagaimana tersebut diatas, maka NDBS
tetap berhak mendapatkan pembayaran secara
proporsional sampai dengan kemajuan Pekerjaan
yang sedang berjalan pada saat dilakukan
pemutusan Perjanjian ditambah biaya bahan atau
alat yang telah dibeli oleh NDBS untuk Pekerjaan
tersebut dengan ketentuan pembayaran tersebut
telah disetujui oleh Para Pihak selanjutnya bahan
atau alat tersebut menjadi milik Pelanggan.
3. Pemutusan Perjanjian secara lebih awal oleh
Pelanggan dan/atau NDBS yang disebabkan oleh
satu dan lain hal dengan membuat pernyataan
tertulis serta disetujui dan ditandatangani oleh Para
Pihak.
4. Pemutusan Perjanjian secara sepihak sebagaimana
disebutkan dalam ayat (1), ayat (2), dan ayat (3) Pasal
ini wajib disampaikan oleh Pihak yang bersangkutan
kepada Pihak lainnya paling lambat 30 (tiga puluh)
hari kalender sebelum tanggal efektif pemutusan.
Page 16 of 44
2. NDBS may terminate the Agreement earlier in the
event of such conditions as follows:
a. Customer is unable to perform its obligations
as set forth in the Agreement and such non-
performance is not rectified within 30 (thirty)
calendar days of receipt of written notice from
the the NDBS;
b. Force Majeure event exceeding 60 (sixty)
consecutive days which results in the Customer
unable to perform its obligations after it has
been taken such measures as mentioned in
Article 17;
c. Customer suspend the implementation of work
for more than 30 (thirty) calendar days;
d. Customer materially or major changes the
Scope of Work which adversely impacts the
NDBS’s ability to complete the Work .
e. If NDBS terminates the Agreement due to such
causes as mentioned above, then NDBS shall
remain entitled to receive a payment on
proportional basis up to the progress of work
which is running when the termination is made
added by the cost of material or equipment
purchased by NDBS for said work provided that
said payment has been agreed on THE Parties
and thereafter said materials or equipment
shall become Customer’s property.
3. The termination of Agreement earilier by
Customer and/or NDBS which is caused by one
and another reason is done by making a written
statement and being approved and signed by the
Parties.
4. Such termination of Agreement as referred to in
paragraph (1), paragraph (2), and paragraph (3) of
this Article is required by the relevant Party to the
other Party no later than 30 (thirty) calender days
prior to the effective date of termination
NDBS Customer
5. Untuk pengakhiran Perjanjian secara lebih awal
melalui pemutusan Perjanjian dan Pembatalan
Perjanjian berdasarkan pasal ini, maka Para Pihak
sepakat untuk mengesampingkan berlakunya
ketentuan Pasal 1266 Kitab Undang-Undang Hukum
Perdata. Sepanjang tidak diatur/ditentukan lain pada
ketentuan yang terdapat dalam Perjanjian ini, maka
Para Pihak juga sepakat untuk mengesampingkan
berlakunya ketentuan Pasal 1267 Kitab Undang-
Undang Hukum Perdata terhadap pengakhiran
Perjanjian secara lebih awal tersebut.
PASAL 19
NON-SOLICITATION
Selama jangka waktu Perjanjian ini dan untuk periode 12
(dua belas) bulan setelahnya (“Non-Solicitation
Period”), tidak ada Pihak yang boleh secara langsung
atau tidak langsung, meminta, mempekerjakan,
menawarkan untuk mempekerjakan atau
mempertahankan jasa personel Pihak lainnya yang
mungkin berhubungan dengan Pihak tersebut untuk
tujuan Perjanjian ini. Jika salah satu Pihak
mempekerjakan personel tersebut dari Pihak lainnya
selama Non-Solicitation Period, Pihak tersebut harus
membayar kepada Pihak lainnya 15% (lima belas persen)
dari remunerasi kotor tahunan personel tersebut.
Sekalipun demikian, klausul ini tidak dapat ditafsirkan
untuk melarang salah satu Pihak untuk mempekerjakan
personel Pihak lainnya yang melamar suatu posisi
sebagai tanggapan terhadap iklan pekerjaan umum.
PASAL 20
HAK KEKAYAAN INTELEKTUAL
1. Hak Kekayaan Intelektual adalah semua hak
kekayaan intelektual, termasuk namun tidak
terbatas pada, paten, model utilitas, desain industri,
merek dagang, tanda jasa, aplikasi untuk hal-hal yang
disebutkan di atas (dan hak untuk mengajukan
permohonan untuk hal-hal yang disebutkan di atas),
hak desain, kepemilikan penemuan, informasi hak
milik dan/atau pengetahuan teknis, hak cipta,
kepengarangan, apakah dapat dipatenkan atau tidak
dan hak-hak serupa lainnya.
Page 17 of 44
5. For the early termination of the Agreement
through termination of the Agreement and
Cancellation of the Agreement based on this
article, the Parties agrees to waive the enactment
of the provisions of Article 1266 of the Civil Code.
As long as it is not regulated / otherwise stipulated
in the provisions contained in this Agreement, THE
Parties also agrees to waive the application of
Article 1267 of the Civil Code to the earlier
termination of the Agreement.
ARTICLE 19
NON-SOLICITATION
During the term of this Agreement and for a period of
12 (twelve) months thereafter (the “Non-Solicitation
Period”), neither Party shall directly or indirectly,
solicit, employ, offer to employ, or retain the services
of the other Party’s personnel with whom the Party
may have come into contact with for the purposes of
this Agreement. If either Party hires such personnel of
the other Party during the Non-Solicitation Period, it
shall pay to the other Party fifteen percent (15%) of
the respective personnel’s gross annual remuneration.
Notwithstanding the foregoing, this Clause shall not
be construed to prohibit either Party from hiring the
other Party’s personnel who applies for a position in
response to a general employment advertisement.
ARTICLE 20
INTELLECTUAL PROPERTY
1. Intellectual Property Rights means all intellectual
property rights, including but not limited to,
patents, utility models, registered designs and
models, trademarks, service marks, applications
for any of the foregoing (and the rights to apply for
any of the foregoing), design rights, ownership of
inventions, proprietary information and /or
technical know-how, copyright, authorship,
whether patentable or not and any similar rights.
NDBS Customer
2. Pelanggan akan memiliki kepemilikan penuh atas
semua Deliverables dan produk kerja dikembangkan
atau dikontribusikan oleh NDBS, sehubungan
dengan Pekerjaan sebagaimana ditentukan dalam
Lampiran I tentang Lingkup Pekerjaan namun, setiap
Hak Kekayaan Intelektual yang sudah ada
sebelumnya seperti sumber atau bahan referensi,
program komputer, dokumentasi dan informasi
serupa, bahan, know-how, dan sejenisnya yang
merupakan hak milik NDBS yang digunakan untuk
menghasilkan Pekerjaan, termasuk setiap modifikasi
dan peningkatan yang dibuat di dalamnya selama
penyediaan Pekerjaan akan menjadi milik tunggal
dan eksklusif dari NDBS. NDBS dengan ini
memberikan kepada Pelanggan, lisensi yang dapat
dibatalkan, tidak eksklusif, bebas royalti, untuk
menggunakan Hak Kekayaan Intelektual dalam
Deliverables semata-mata untuk memenuhi
kewajibannya dalam Pekerjaan.
3. Setiap Pihak menjamin bahwa (i) metode dan proses
yang digunakan olehnya untuk melakukan Pekerjaan
dan (ii) Pekerjaan tersebut tidak melanggar Hak
Kekayaan Intelektual dari pihak ketiga mana pun.
Para Pihak akan bertanggung jawab untuk dan akan
memberikan penggantian yang dijamin kepada Pihak
lainnya dan mengganti rugi dan tidak
membahayakan dari setiap dan semua kewajiban,
klaim (termasuk setiap hak gadai dan sitaan lainnya
terhadap properti), penilaian, kerugian, denda,
penalti, penalti, biaya dan segala biaya yang
berkaitan karenanya (termasuk namun tidak
terbatas pada biaya pengadilan dan biaya
pengacara) sehubungan dengan pelanggaran
terhadap Hak Kekayaan Intelektual tersebut.
PASAL 21
KORESPONDENSI
1. Setiap pemberitahuan atau komunikasi lainnya
antara Para Pihak sehubungan dengan Perjanjian ini
akan dilaksanakan dalam bentuk tertulis dan
disampaikan secara:
a. Diantar langsung;
Page 18 of 44
2. Customer shall have full ownership of all
Deliverables and work product developed or
contributed by NDBS, in connection with the
Works as specified in Attachment I on Scope of
Work however, any pre-existing Intellectual
Property such as source or reference materials,
computer programs, documentation and similar
information, materials, know-how and the like
which are proprietary to NDBS that are used to
produce the Works, including any modifications
and enhancements made thereto during the
provision of the Works shall be the sole and
exclusive property of NDBS. NDBS hereby grants to
the Customer, a revocable, non-exclusive, royalty
free, to use the Intellectual Property Rights in the
Deliverables solely for the fulfilment of its
obligations in the Work.
3. Each Party warrants that (i) the method and
processes used by it to perform the Work and (ii)
the Work do not infringe any Intellectual Property
Rights of any third parti(es). The Parties shall be
liable for and shall provide guaranteed
reimbursement to other Party and indemnify and
hold harmless from any and all liabilities, claims
(including any liens and other encumbrances
against property), judgments, losses, fines,
penalties, expenses and any costs relating thereto
(including but not limited to court costs and
lawyers' fees) in respect of infringement of any
such Intellectual Property Rights.
ARTICLE 21
CORRESPONDENCE
1. Any notices or other communications between
the Parties regarding with this Agreement will be
executed in writing and deliverance as follows:
a. Delivered in person,
NDBS Customer
 b. Dengan e-mail yang dikonfirmasi; b. by confirmed e-mail,
c. Dengan surat tercatat; c. By registered mail,
d. Dengan pos berbayar dan bukti terima; atau d. By paid post and proof of receipt, or
e. Melalui layanan pengiriman ekspres yang
dikenal secara nasional, e. Through a nationally recognized express
delivery service,

dialamatkan pada wakil Para Pihak yang telah
ditentukan oleh masing-masing Pihak dengan
pemberitahuan pada Pihak lainnya menurut
Perjanjian ini, seluruh pemberitahuan akan berlaku
efektif sejak diterimanya pemberitahuan tersebut.
addressed to a representative of the Parties
determined by each Party with notice to the other
Party under this Agreement, all notices shall be
effective from the date of receipt of such notice.

2. Surat menyurat agar dialamatkan sebagai berikut : 2. Any correspondence can be addressed as follows:
a. Untuk Pelanggan a. for Customer

Alamat / Address : ________________

Telp / Phone : ________________

Faks / Fax : ________________

Email : ________________

U.p. /Attn. : ________________

b. Untuk NDBS b. For NDBS

Alamat / Address : PT NTT DATA BUSINESS SOLUTIONS

Wisma BCA Wing A, Lantai PH Jl. Kapten Soebijanto
Djojohadikusumo, BSD City, Lengkong Gudang, Serpong,
Tangerang Selatan, Indonesia, 15321.
Telp / Phone : (021) 531 92001

Faks / Fax : (021) 531 92002

Email : satria.salazar@nttdata.com

U.p. / Attn. : Satria Salazar

Page 19 of 44
NDBS Customer
 PASAL 22
KEPATUHAN
1. Pelanggan maupun NDBS dilarang untuk melakukan
praktik korupsi, kolusi, dan nepotisme serta
penipuan. Terkait dengan hal tersebut, masing-
masing pihak dilarang untuk:
a. Menawarkan, memberi atau menjanjikan untuk
memberi atau setuju untuk memberi hadiah,
komisi, rabat, imbalan atau berupa apa saja
kepada Dewan Komisioner, Kepala Eksekutif,
pegawai atau setiap pihak yang bertugas untuk
dan atas nama Pelanggan maupun NDBS, untuk
mempengaruhi hal yang berkaitan dengan
pelaksanaan Perjanjian; dan
b. Membuat dan/atau menyampaikan secara tidak
benar dokumen dan/atau keterangan lain yang
disyaratkan untuk penyusunan dan pelaksanaan
Perjanjian.
c. Melakukan tindakan atau kelalaian yang
menempatkan salah satu Pihak untuk melanggar
ketentuan hukum yang berlaku, ketentuan dan
peraturan.
2. Para Pihak akan tunduk dengan regulasi yang diatur
di dalam FCPA (Foreign Coruption Practices Act),
Kitab Undang - Undang Hukum Pidana Indonesia dan
Undang-Undang No. 20 Tahun 2001 tentang
Perubahan atas UU Nomor 31 tahun 1999 tentang
Pemberantasan Tindak Pidana Korupsi serta
peraturan perundang-undangan lainya yang berlaku.
PASAL 23
KERAHASIAAN
1. Tanpa persetujuan tertulis dari Pihak lainnya, Para
Pihak DILARANG memberitahukan, membuka atau
memberikan informasi, keterangan dan/atau yang
sejenisnya yang menyangkut isi atau yang
berhubungan dengan Perjanjian ini kepada Pihak lain
di luar Perjanjian ini, baik yang berupa badan hukum
maupun perseorangan, kecuali:
Page 20 of 44
ARTICLE 22
COMPLIANCE
1. Customer and NDBS are prohibited to practice
corruption, collusion, and nepotism as well as
fraud. In this regard, each party is prohibited to:
a. Offer, give or promise to give or agree to give
gifts, commissions, rebates, rewards or in
whatever form to the Board of Commissioners,
Chief Executive, employees or any party who is
in charge of and on behalf of the Customer or
the NDBS, to influence matters relating with
the implementation of the Agreement; and
b. Make and/or submit incorrect documents
and/or other information required for the
preparation and implementation of the
Agreement.
c. Acts or omissions that place the Party in
violation of applicable laws, rules and
regulations.
2. The Parties will comply with the regulation set out
in the FCPA (Foreign Corruption Practices Act), the
Indonesian Criminal Code and Law No. 20 of 2001
concerning Amendments to Law Number 31 of
1999 concerning Eradication of Corruption Crimes
as well as other applicable laws and regulations
ARTICLE 23
CONFIDENTIALITY
1. Without a written consent from the other Party,
the Parties are prohibited to notify, open or give
the information, statement and/or the kind which
pertain to the contents or those relating to this
Agreement to another Party beyond this
Agreement, either in the form a legal entity or
individual person, except:
NDBS Customer
 a. Diwajibkan oleh instansi pemerintah yang
berwenang mengatur atau mengeluarkan ijin
tentang hal-hal yang diperjanjikan dalam
Perjanjian ini;
b. Diperintahkan oleh badan peradilan atau instansi
pemerintah lainnya yang berhubungan dengan
penegakan hukum secara tertulis, resmi, dan
merupakan putusan final;
c. Menurut peraturan perundangan-undangan yang
berlaku di Indonesia, informasi tersebut harus
diberikan kepada Pihak lain yang disebut secara
jelas dalam peraturan perundang-undangan
tersebut.
2. Meskipun Perjanjian ini telah berakhir, Para Pihak
wajib menjaga kerahasiaan atas segala informasi baik
yang berbetuk tertulis maupun lisan yang dapat
mengakibatkan kerugian Pihak lainnya dalam
Perjanjian ini kecuali telah mendapat persetujuan
tertulis dari Pihak tersebut;
3. Kegagalan dalam mentaati kewajiban dimaksud ayat
(1) dan (2) Pasal ini, maka Pihak yang gagal
mentaatinya, berkewajiban untuk memberikan ganti
rugi pada Pihak lainnya yang dirugikan.
PASAL 24
ADDENDUM/AMANDEMEN
1. Segala perubahan, tambahan dan hal-hal lain yang
belum diatur atau belum cukup diatur dalam
Perjanjian ini akan diatur kemudian oleh Para Pihak
dalam suatu addendum/amandemen yang
merupakan lampiran dan menjadi bagian serta satu
kesatuan yang tidak dapat dipisahkan dari Perjanjian
ini.
2. Dengan ditandatanganinya Perjanjian ini,
kesepakatan baik secara tertulis maupun tidak
tertulis diantara Para Pihak berikut segala
perubahan, penambahan dan/atau penggantiannya
menjadi tidak berlaku lagi.
Page 21 of 44
a. That it is required by any government instance
authorized to regulate or issue permits
regarding those matters agreed upon in this
Agreement;
b. That it is instructed by a juridical party or any
other government instance that relates to law
enforcement in writing, officially, and
constitutes a final decision;
c. That according to the statutory regulation
applicable in Indonesia, said information must
be given to another Party mentioned clearly in
said statutory regulation.
2. Even though the Agreement is terminated, the
Parties are obliged to keep the confidentiality of all
information both in written and verbal forms that
may cause a loss to the other Party to this
Agreement except having obtained a written
consent from said Party.
3. Any failure in obeying those obligations referred to
in paragraphs (1) and (2) of this article, the Party
who failed to obey it, is obliged to pay an
indemnity to the other Party being harmed.
ARTICLE 24
ADDENDUM/AMENDMENT
1. Any amendment, addendum and other matters
not regulated or not suffiiciently regulated yet in
this Agreement will be set forth later by THE
Parties in an addendum / amendment being an
attachment and becomes part as well as an
integral and inseparable part of this Agreement.
2. With the signing of this Agreement, then any
agreement either written or unwritten between
THE Parties and any amendments, additions
and/or replacements shall become void.
NDBS Customer
 PASAL 25
PENYELESAIAN PERSELISIHAN
1. Semua perselisihan yang timbul akibat pelaksanaan
Perjanjian ini akan diselesaikan dengan cara
musyawarah untuk mencapai mufakat dalam jangka
waktu maksimal 30 (tiga puluh) hari kalender;
2. Apabila Para Pihak gagal untuk menyelesaikan
perselisihan secara musyawarah setelah timbulnya
perselisihan, ketidaksepakatan atau perbedaan
pendapat dalam jangka waktu yang ditetapkan pada
ayat (1) diatas, maka Para Pihak sepakat untuk
menyelesaikan perselisihan tersebut sesuai dengan
peraturan Badan Abitrasi Nasional Indonesia
(”BANI”), dan Keputusan BANI merupakan putusan
final dan mengikat bagi Para Pihak dan tidak dapat
dilakukan banding ke pengadilan atau badan lainnya;
3. Penyelesaian perselisihan diselesaikan melalui
Arbitrase di Jakarta, Indonesia, sesuai dengan
Peraturan Arbitrase dan penilaian atas penghargaan
yang diberikan oleh para arbiter dapat dimasukkan
dalam pengadilan yang memiliki yurisdiksi. Majelis
arbitrasi terdiri dari 3 (tiga) arbiter yang ditunjuk
berdasarkan peraturan BANI. Arbitrase diadakan di
Jakarta, Indonesia dan diselenggarakan dengan
bahasa Indonesia. Satu anggota dipilih oleh
Pelanggan, satu anggota dipilih oleh NDBS dan
anggota ketiga yang akan menjadi pemimpin, dipilih
oleh kesepakatan Para Pihak.
PASAL 26
LAIN-LAIN
1. Pengalihan
NDBS maupun Pelanggan tidak diperkenankan tanpa
izin terlebih dahulu sebelumnya dari Pihak lainnya
untuk mengalihkan baik sebagian atau seluruh
Perjanjian ini kepada pihak ketiga, dan dengan
demikian maka segala pengalihan yang demikian
dianggap batal demi hukum.
Page 22 of 44
ARTICLE 25
DISPUTE OF SETTLEMENT
1. All of disputes that arise due to the
implementation of this Agreement will be settled
by deliberation for consensus with a maximum 30
(thirty) calender days;
2. If the Parties fail to settle the dispute by
deliberation after the occurrence of disputes,
disagreements or dissent within the period of time
that stated in paragraph (1), then the Parties
agrees to settle the dispute in accordance with the
regulations of the Indonesian National Abitration
Agency (“BANI”), and the Decision BANI is final
and binding for the Parties and not subject to
appeal to any court or other body;
3. Settlement of disputes settled through Arbitration
in Jakarta, Indonesia, in accordance with the
Arbitration Rules and the assessment of the
awards granted by the arbitrators can be
submitted in jurisdictional court. The arbitral panel
shall consist of 3 (three) arbitrators appointed
under BANI rules. Arbitration is held in Jakarta,
Indonesia and organized in Bahasa Indonesia. One
member shall be elected by the Customer, one
member elected by the NDBS and the third
member who shall be the leader, shall be elected
by agreement of THE Parties.
ARTICLE 26
MISCELLANEOUS
1. Transfer
NDBS and Customer are not permitted without a
prior consent from the OTHER Party to transfer
either partly or the whole of this Agreement to any
third party, and therefore any of such transfer
shall be deemed null and void by law.
NDBS Customer
2. Keseluruhan Perjanjian; Perubahan-perubahan;
Judul-judul
Perjanjian ini merupakan keseluruhan perjanjian
antara Para Pihak mengenai ihwal tersebut di
dalamnya, serta membatalkan dan
mengesampingkan seluruh dokumen-dokumen,
perjanjian-perjanjian sebelumnya, apakah dalam
bentuk lisan, tertulis atau lainnya antara Para Pihak
mengenai ihwal tersebut, kecuali apabila hal-hal
dimaksud dijadikan bagian dari Perjanjian ini dalam
bentuk Lampiran dari Perjanjian.
Dalam hal terjadinya ketidakcocokan atau
perbedaan antara ketentuan yang terdapat dalam
Perjanjian ini dengan ketentuan yang terdapat dalam
Lampirannya maka yang berlaku adalah ketentuan
dalam Perjanjian ini, kecuali apabila ditentukan lain
dalam Perjanjian ini. Setiap ketidakcocokan atau
perbedaan dimaksud akan diselesaikan dan
disampaikan secara tertulis oleh Para Pihak.
Judul-judul pada Perjanjian ini semata-mata dibuat
untuk memudahkan dan tidak mempengaruhi
pengertian Perjanjian ini.
3. Lampiran-lampiran
Dokumen Perjanjian ini terdiri juga atas lampiran dan
merupakan satu kesatuan dan bagian yang tak
terpisahkan dari Perjanjian ini dan setiap Pasal harus
diartikan sedemikian sehingga antara satu dengan
yang lain sejalan dan saling menunjang. Lampiran
sebagaimana yang dimaksud adalah sebagai berikut:
Lampiran I : Ruang Lingkup Pekerjaan
Lampiran II : Timeline Pekerjaan
Lampiran III : Komersial
4. Bahasa
Perjanjian ini dibuat dalam Bahasa Indonesia dan
Bahasa Inggris, dengan ketentuan bahwa apabila
terjadi ketidaksesuaian karena perbedaan
penafsiran bahasa, maka Perjanjian yang ditulis
dalam Bahasa Indonesia yang berlaku.
Page 23 of 44
2. The Entire Agreement; Amendments; Titles
This Agreement constitutes the entire agreement
between the Parties on the subject matter therein,
as well as cancelling and waiving all of the previous
documents, agreements, whether in the verbal,
written or other forms between the Parties
concerning said subject matter, except when said
matters are made a part of this Agreement in the
form of Attachment to the Agreement.
In the event of any discrepancy or difference
between the provisions set forth in this Agreement
and the provisions set forth in its attachments
then the prevailing ones are the provisions in this
Agreement, unless stipulated otherwise in this
Agreement. Any said discrepancy or difference will
be settled and conveyed in writing by the Parties.
Titles in this Agreement are made merely for the
convenience and shall not influence the meaning
of this Agreement.
3. Attachments
The documents of this Agreement also comprise of
an attachment and constitute an integral unit and
an inseparable part of this Agreement and each
Article must be interpreted at such so that
between one to another is inline and mutually
supportive. Such attachments as referred herein
are as follows:
Attachment I : Scope of Work
Attachment II : Timeline of Work
Attachment III : Commercials
4. Language
This Agreement is made in both Indonesian and
English. Should there be any inconsistencies due to
difference of language interpretation, the
Indonesian version shall prevail.
NDBS Customer
5. Hukum Yang Berlaku 5. Governing Law
Perjanjian ini tunduk kepada hukum Negara Republik This Agreement is governed by the laws of the
Indonesia. Republic of Indonesia.

PASAL 27 ARTICLE 27
PENGENYAMPINGAN WAIVERS

Tidak satupun dari syarat dan ketentuan yang terdapat
dalam kontrak ini dianggap untuk dikesampingkan oleh
Para Pihak kecuali pengenyampingan tersebut
berbentuk tertulis, dinyatakan secara jelas sebagai
pengenyampingan atas suatu aturan dalam Perjanjian
ini dan ditandatangani oleh Para Pihak.
None of the terms and conditions contained in this
Agreement shall be deemed to be waived by Parties
unless such waiver is in writing, is expressly stated to
be a waiver of a specifed provision of this Agreement
and is signed by THE Parties

PASAL 28 PASAL 28
KETERPISAHAN SEVERABILITY

Ketidakabsahan atau keberlakukan ketentuan Perjanjian
tidak akan mempengaruhi validitas atau keberlakuan
ketentuan yang lainnya. Perjanjian akan diberikan efek
seolah-olah istilah yang tidak sah atau tidak dapat
ditetapkan telah digantikan oleh istilah dengan efek
ekonomi yang serupa.
The invalidity or enforceability of any terms of the
Agreement will not adversely affect the validity or
enforceability of the remaining terms. The Agreement
will be given effect as if the invalid or unenforceable
term had been replaced by a term with a similar
economic effect.

Demikian Perjanjian ini dibuat dan ditandatangani oleh In witness whereof this Agreement and made and
Para Pihak dalam rangkap 2 (dua) bermeterai cukup, signed by the Parties in 2 (two) copies on duty stamp,
dimana masing-masing rangkap mempunyai kekuatan where each copy has an equal and legal binding.
hukum yang sama dan mengikat.

Pelanggan/ Customer NDBS

PT JHONLIN GROUP PT NTT DATA BUSINESS SOLUTIONS

[Name] Hafferson H. Manurung

[Title] Managing Director

Page 24 of 44
NDBS Customer
 LAMPIRAN I / ATTACHMENT I
RUANG LINGKUP PEKERJAAN / SCOPE OF WORK

A. End-Customer:
1. PT Jhonlin Group (“JG”)

B. Ruang lingkup Pekerjaan / Scope of Work:

Implementation of SAP ERP S/4HANA

- Organizational entities in scope:

1. PT Jhonlin Group (“JG”)
2. PT Jhonlin Baratama (“JB”)
3. PT Jhonline Marine Line (“JML”)
4. PT Jhonlin Marine Trans (“JMT”)
5. PT Samudera Timur Mas (“STM”)
6. PT Dua Samudra Perkasa (“DSP”)

- SAP Modules:
o FI (Finance Accounting)
o CO (Controlling)
o MM (Material Management)
o PM (Plant Maintenance)
o CS (Customer Service)
o SD (Sales & Distribution)
o PP (Production Planning)
o PS (Project System)
o FM (Fund Management)
o HCM (Human Capital Management)
▪ Organizational Management
▪ Personnel Administration
▪ Time Management
o FIORI

- Pilot Project
o Duration:
▪ 7 (seven) months implementation
▪ 1 (one) month hypercare support
o Fit-Gap for 6 (six) companies which is JG, JB, JML, JMT, STM, and DSP is included in pilot project
o Implementation will cover 2 (two) companies which is JG and JB
o WRICEF: 15 (fifteen) objects

- Roll Out Project

o Duration
▪ 3 (three) months implementation
▪ 1 (one) month hypercare support
o Implementation will cover 4 (four) companies which is JML, JMT, STM, and DSP
o WRICEF: 10 (ten) objects

Page 25 of 44
NDBS Customer
 - SAP Modules Implemented in each entity

Module JG JB JML JMT STM DSP

FI      
CO      
MM      
PM     
CS   
SD     
PP 
PS      
FM      
HCM      
FIORI      

Project Functional Scope

The project functional scope will be as stated herein below. Any SAP business processes not explicitly listed herein
below are outside the scope of the Services unless otherwise agreed to separately by way of executing a Change
Request (CR) mutually agreed upon by both parties.

SAP Module Sub-Module

FI (Financial Accounting)
CO (Controlling)
MM (Materials Management)
PM (Plant Maintenance)
Page 26 of 44
• FI-GL (General Ledger)
• FI-AP (Accounts Payable)
• FI-AR (Accounts Receivable)
• FI-AA (Asset Accounting)
• FI-BL (Bank Accounting)
• FI Reporting
• CO-OM (Overhead Cost Controlling, including Cost
Element, Cost Center and Internal Order)
• CO-PA (Profitability Analysis)
• CO-PCA (Profit Center Accounting)
• CO Reporting
• MM-CBP (Consumption-based Planning)
• MM-PUR (Purchasing)
• MM-IM (Inventory Management)
• MM-SRV (External Services Management)
• MM-IV (Logistics Invoice Verification)
• MM Vendor Evaluation & MM Reporting
• PM-EQM (Equipment and Technical Object)
• PM-PRM (Preventive Maintenance)
• PM-WOC (Maintenance Order Management)
NDBS Customer

CS (Customer Service)
SD (Sales and Distribution)
PP (Production Planning)
PS (Project System)
FM (Fund Management)
HCM (Human Capital Management)
FIORI
• PM-IS (Reporting)
• PM-MINING (Timesheet, Ritase DT & Coal Getting)
• CS-EQM (Equipment and Technical Object)
• CS-PRM (Planned Service)
• CS-SOC (Service Order Management)
• CS-IS (Reporting)
• SD-BF (Basic Functions and Master Data)
• SD-CAS (Sales Support)
• SD-SLS (Sales)
• SD-SHP (Shipping)
• SD-TRA (Transportation)
• SD-BIL (Billing)
• SD-IS (Reporting)
• PP-MD (PP Master Data)
• PP-SOP (Sales & Operation Planning)
• PP-MP (Master Planning)
• PP-CRP (Capacity Planning)
• PP_MRP (Material Requirement Panning)
• PP-PI (Production Planning for Process Industry)
• Project Structure
• Project Planning
• Budgeting
• Project Execution
• Project Closing
• Budget Entry
• Budget Realization
• Budget Supplement, Transfer and Return
• Commitment Carry Forward
• Budget CarryForward
• Organizational Management
• Personnel Administration
• Time Management
• Fiori Applications (Transactions and Analytics).
Quota of SAP Fiori is 20 (Twenty) Fiori Standard
Applications.

SAP ABAP Scope

SAP suggests to keep core clean and Fit/adopt SAP standard processes. But due to specific requirements of client, there
could be requirement of custom objects. So considered minimum numbers, beyond which considered as Change
Request. SAP Development Tools to develop customized reports, interfaces, conversions, enhancements, forms, and
workflows (WRICEF). Quota of WRICEF Development is 15 Objects based on Fit-Gap for Pilot Project and 10 Objects for
Roll-Out Project.

Page 27 of 44
NDBS Customer
Key Considerations for WRICEF scope:
- SAP Development Tools to develop customized workflos, reports, interfaces, conversions, enhancements, and
forms (WRICEF). Quota of WRICEF Development is 15 for Pilot Project and 10 for Roll-out Project.
- Any additional custom ABAP developments over and above the mentioned objects will be considered as a change
request (CR).
- The are no third-party application and vendors applicable during this project.

SAP BASIS Scope

NDBS will provide the required Basis consultants for carrying out SAP Implementation project related Basis activities
to handle the following activities:
- User and security management
- Setup Development, QAS and Production Server (Installation, User Access, SAP Basic Config, Test login)
- Transport management and administration

Data Conversion & Migration

As per the requirement of data migration, NDBS proposes to migrate the master data and cut over data from the
existing systems as part of the data migration scope. The following is the responsibility matrix for the Data Migration
activity during the implementation. NDBS will provide the template to collect the master and cutover data. However,
we suggest that CUSTOMER should be sole responsible for data preparation and the accuracy of the data.

Testing Scope

The way to ensure that the service has been delivered with the right quality is to test it thoroughly and present the
test results to CUSTOMER prior to the sign-off of the service. The objectives of testing are:
- Ensuring that the system meets all the business requirements defined in the scope
- Ensuring that the system meets technical requirements and service levels for application

Test Plan: The purpose of the test plan is to provide the entire service delivery team with a central document that
outlines what needs to be tested to complete the services.

Page 28 of 44
NDBS Customer
- Testing will include Unit Testing, Integration testing (including Integration testing with user Authorizations
configured) and UAT
- All the Test scripts will be prepared by NDBS’s Team and will be validated and approved by the CUSTOMER’s
team
- CUSTOMER will execute User Acceptance Testing
- If applicable CUSTOMER will own and execute regression testing.

Training Scope

- NDBS will adopt “Train the Trainer” Model for training the super users and selected end users identified by
CUSTOMER
- NDBS will prepare the training plan in coordination with CUSTOMER Team

Project Methodology

The SAP Activate Methodology is SAP’s content rich, agile methodology for the implementation of SAP solutions across
industries and customer environments. Built on our experience from tens of thousands of SAP projects, SAP Activate
methodology provides pre-built implementation content, accelerators, tools, and best practices, which help
consultants, deliver consistent and successful results across industries and customer environments. The five phases of
SAP Activate provide support throughout the project life cycle of SAP solutions.

Underlying these phases is a series of value delivery and quality checks to ensure the solution, as implemented, delivers
the expected value. The diagram below illustrates the Five Phase approach of the SAP Activate Methodology. The SAP
Activate methodology is designed to support project teams in the new implementation of SAP solutions on premise or
in private managed cloud environment. The methodology is structured into Five project phases, each containing a list
of deliverables, and supporting tasks.

Project Deliverable

The following table lists of Deliverables:

All new requirements that are identified after the Fit-Gap Confirmation Sign-off are considered as Change
Requests and shall be charged in addition.
Page 29 of 44
NDBS Customer
RACI Matrix

The project follows the applicable parts of the SAP Activate methodology with the following responsibility matrix of
tasks per phase.
- Responsible (R): Charged with performing the activities. The project plan may define additional detailed
responsibility at the work unit level.
- Accountable (A): The Customer has overall accountability for the whole Project and all the tasks identified below.
Hence, Accountable (A) does not appear for the tasks below.
- Consulted (C): Provides input on how best to produce the activity and actively supports the execution of the
activity.
- Informed (I): Provided with information.

Page 30 of 44
NDBS Customer
C. Personil & Organisasi Proyek/ Personnel and Project Organization:

Project Organization

NDBS Resources
NDBS will provide the Project with project team members identified as SAP consultants. NDBS will serve the role of
sourcing, managing and invoicing CUSTOMER for all NDBS provided project resources.

From time to time, it may be necessary for NDBS to replace its personnel, provided/deployed for the project, for
reasons such as the resignation of a consultant, death, disability, termination, and/or the removal of the consultant
due to performance issues. NDBS replacement personnel will be skilled and trained as SAP consultants and NDBS will
provide CUSTOMER reasonable advanced notification regarding any resource changes either into or out of the Project.

Customer Resources
CUSTOMER will provide resources for the roles identified as belonging to the CUSTOMER for the project team. Upon
NDBS's request, CUSTOMER will deploy knowledgeable Subject Matter Expert (SME) on an "as needed" basis within a
maximum of Five (5) working days. CUSTOMER's Business Process Owners and technical project team resources will
be available at the Project start date. CUSTOMER's project team members will possess knowledge and experience in
both CUSTOMER's business and existing IT legacy system environment.

CUSTOMER project team members will accurately represent all business units and locations that are impacted by the
Project. If, in the reasonable and good faith / opinion of the NDBS Project Manager, any CUSTOMER project team
member fails to complete work assignments necessary to the ongoing operations of the Project or their respective
work product is inadequate, then NDBS will first provide a written notice to the CUSTOMER Project Manager. The
CUSTOMER Project Manager shall then correct the condition or performance issue. If any such condition or
performance issue continues for Five (5) business days after the date of written notice, then NDBS has the right to
request immediate replacement of the CUSTOMER project team member.

NDBS shall have no responsibility for the performance of contractors or vendors engaged by CUSTOMER or delays
caused by them in connection with the Project. CUSTOMER shall be responsible for the contractual relationships with
such third-party contractors or vendors and for ensuring that they cooperate with NDBS. In case of delays caused, if
any, by the CUSTOMER or any of its third-party contractors, which impact the timelines and delay the project
deliverables, NDBS shall raise a Change Request to get additional compensation for the delays caused as per the rate
mentioned.

Project Management & Procedures

Project Planning & Monitoring

The purpose of the Project planning and monitoring activities is for both parties to establish standards, procedures,
and guidelines for the "who," "how," and "when" of the Project. Early in the Project Preparation phase, the initial
project work plan, budget, and resource allocation ("project plan") are created by the project team and agreed to by
both parties. This project plan is periodically reviewed by the Project Managers throughout the entire duration of the
Project. As mutually agreed, changes occur during the Project, the NDBS and CUSTOMER Project Managers will monitor
the plan-to-actual progress and re-plan, when necessary, in attempt to keep the Project on schedule.

NDBS and CUSTOMER project manager will monitor the tasks assigned to the entire project team for timeliness and
quality of the deliverables. In case of delay in task completion on either side, the Project Managers will schedule an
urgent Steering Committee meeting to discuss the resolution process.

Page 31 of 44
NDBS Customer
Project Communication and Plan Overview
To promote consistent and effective communications throughout the Project, the parties need to plan communications
for the stakeholders, end users, CUSTOMER, vendors, and project team. A properly defined and executed
communication plan is designed to (i) confirm that end users are familiar with the Project at an appropriate level of
detail; (ii) promote open communications among the project team; and (iii) enhance communications between the
project team and the Steering Committee.

Project Documentation
Establishing standards for Project documentation is necessary to maintain the status and results of Project activities.
The project team members need to have ready access to documentation when referencing project decisions, issue
resolution, or configuration changes. NDBS will provide guidance and assistance to CUSTOMER project team members
in the development of content and use of SAP and/or NDBS templates for Project documentation. NDBS and
CUSTOMER project team members will be responsible for completing Project documentation.

Scope Management
Managing scope is an important task of a Project. Change to the scope will affect the commercials and will result in
increase or decrease in price and duration. NDBS shall carryout the implementation of the modules and business
processes for the CUSTOMER as per the Scope agreed in this SOW. Project scope changes originating from internal or
external factors may need to be accommodated through the life of the Project. The following situations may result in
the need for a scope management, including but not limited to:
A. Additions and/or Changes to Project Scope – An item that was initially considered out of scope is decided to be
necessary for the current Project, thus incurring probable additional costs and/or linear time for the Project.
B. Delays – The Project is delayed for a temporal reason, and thus the date of completion is extended. Examples of
these include delay of dates to coincide with business cycles or pauses the Project for business needs such as
acquisitions, divestitures, or personnel turnover.
C. Inclusion of Scope During and After Prepare Phase – With a more detailed understanding of Project requirements,
re-estimation may be necessary.
D. Changed Business Requirements – Since the market may change, the Project may need to absorb additional
requirements during implementation.
E. Other Unanticipated Situations – When agreed upon by both parties.
F. Any business requirement changes and business process changes resulting in changes to the signed-off business
design /fitgap document either in terms of scope or the process flow.

Scope and Change management is designed to control any additions, deletions, or modifications to the Project scope
and the Project plan during the prepare, explore / design phase and particularly after the explore / design phase sign-
off. The investigation of a proposed change evaluates what effect the change could have on the Project budget,
schedule, and resources. The CUSTOMER Project Manager with active assistance of NDBS Project Manager will oversee
the scope and change management process and procedures as defined in Scope Management Plan.

All requests for changes must be evaluated and approved (or disapproved) by both parties in writing in order to
recognize and control "scope creep". NDBS will submit a change order for the approved change and will undertake the
execution of the change order only after the change order commercials are agreed to and signed off.

Page 32 of 44
NDBS Customer
Proposed Team Structuture

Estimate Time Commitment

NDBS is dependent on CUSTOMER for certain obligations and responsibilities for completion of the Project. NDBS is
dependent on CUSTOMER for Steering Committee consisting of the key stakeholders including CUSTOMER Project
Manager, NDBS Project Manager, NDBS Management Team Representative & CUSTOMER Management Team
Representative.

Line of Business and Business User

- CUSTOMER will establish a location equipped with necessary technology infrastructure, Laptop, and tools for
Project facilitation during the onsite execution of certain project phases
- CUSTOMER is responsible for organizational change management
- Adaptable Organization, willing to change and accept SAP best practices
- Defined business direction by the top management and communicated down to the individual team members
and end users
- True commitment to leverage NDBS and/or SAP pre-existing and proprietary implementation tools and
accelerators
- Availability for extended work hours at critical points within the Project as determined by the NDBS and
CUSTOMER Project Managers; actual timing will be determined by Project needs
- Commitment to Project Readiness Activities:
- Identify and backfill key project team members
- Support resources required at various sites to support Go-Live
- Sufficient participation required from representatives of all sites
- Super users to be identified for each line of business that will support Go Live at all sites

Page 33 of 44
NDBS Customer
NDBS estimates time commitment from business process owners to be as per the table below.

Realize Deploy Go-live &

Resources Explore Phase
Phase Phase Support
Project Manager 100% 100% 100% 100%

Functional BPO 50% 100% 100% 90%

Technical 25% 100% 100% 25%

System Admin 50% 50% 40% 50%

Project Reporting
Our proprietary collaboration site for managing all aspects of the project including tasks and worklists,
issues, risks, decisions, project calendars, and documentation repositories; one source of information
maintained by the entire project team. The data that is put into the various lists and tools can easily be
pushed out into meaningful PMO reports.

One source of truth that allows for real-time report generation because each individual contributor can
maintain it constantly.
- Individual and teamwork load
- Current status
- “Are we going to get there?”
- Impact on schedule due to timeline creep
- Visibility to critical items
- Are due dates aligned with phase dates?

Knowledge Transfer
NDBS consultants will conduct product Knowledge Transfer activities with CUSTOMER project team members
throughout the life of the Project as part of the project activities. Knowledge Transfer occurs when NDBS consultants
verbally or in writing:
- Facilitate product functionality via demonstrations and discussions
- Provide hands-on training on the use of the product solution as part of project work
- Knowledge transfer regarding configuration training / review of configuration is not in scope

Training
CUSTOMER end-user training is supported by NDBS project team members during the end of the Deploy phase of the
Project and delivered during the System Readiness phase of the Project. The CUSTOMER is responsible for the following
end-user training and reference document tasks:
- Assess end-user proficiency in pre-requisite skills regarding desktop / laptop computer
- device and related operating system.
- Design, coordinate and communicate training schedule and related logistics.
- Establish training room and provide necessary training aides, tools and supporting technology.
- Ensure attendance and participation of the attendees during the training sessions

Page 34 of 44
NDBS Customer
NDBS is responsible for the following activities:
- Delivering product training content to Project core team members with the train the trainer approach. The core
team members will train the end-user community.
- Assisting the core team on preparing the end user training documents
- Supporting CUSTOMER project team member by answering questions and/or clarifying issues per CUSTOMER
request.

Acceptance Criteria
A decision-making process will be put into place by CUSTOMER to avoid delays on issues which could jeopardize the
implementation date, budget and/or outcome of the Project. It is imperative that CUSTOMER resolves all outstanding
decisions within Three (3) business days (72 hours) from receipt of the issue. If the issue cannot be resolved in Three
(3) business days, it should be escalated to the SAP Project Sponsor and appropriate Steering Committee members for
final resolution. Delays beyond three (3) business days could adversely affect the Project, delay the implementation
time and result in additional consulting costs being incurred by CUSTOMER.

The Steering Committee will be actively involved in the decision-making process. The Steering Committee will be in
place by commencement of the Project. Matters regarding agreed policy or procedural changes that are perceived to
have a critical impact on the CUSTOMER Project timetable, budget and/or the outcome of the implementation will be
presented to the Steering Committee for a decision as determined by the CUSTOMER SAP Project Sponsor. The Steering
Committee, as a rule of thumb, is advised to adopt policy of strongly resisting modifications to the SAP system.

NDBS shall submit a Change Request to the CUSTOMER if the project activities are stalled beyond Three (3) days, either
for the entire project or for any specific Phase/Stream/Module. Increased CUSTOMER executive involvement may be
required so that business decisions are made in a timely fashion as needed throughout the life of the Project to avoid
the impact on the project in terms of price and duration.

To maintain the timeline of the Project it is imperative that CUSTOMER makes timely acceptance decisions of each
deliverable. Any indecision at acceptance either delays the Project or creates rework and additional costs at later stages
of the Project. Deliverables and Services that substantially conform to the deliverable specifications or description shall
be accepted. All deliverables submitted to the CUSTOMER shall be deemed accepted, if within Two (2) working days of
delivery/submission to the CUSTOMER, the CUSTOMER has not provided NDBS with the sign-off or a written notice
identifying specifically any basis for not approving the deliverables. Further, CUSTOMER shall provide sign-off for the
milestones within Five (5) working days of completion of each such milestone, in the absence of which, such milestone
will be deemed accepted by the CUSTOMER.

The next phase execution starts only after the previous phase closure sign-off and payment by the CUSTOMER. In case
of an exceptional situation when NDBS is required to move forward with a conditional sign-off, any such conditions
should be resolved before the end of subsequent phase, failing which they will be deemed resolved and the phase
closed.

NDBS shall be entitled to rely on all decisions and approvals of the CUSTOMER in connection with the Services or
deliverables. When all the deliverables within a phase are complete, the phase itself is considered complete and shall
be signed off as completed and accepted by CUSTOMER. At the end of hyper care period (PGLS/Run), project would be
deemed complete with no pending deliverables and will automatically move into AMS. If and any issues pending at the
end of the hyper care period will be considered as ongoing support issues and shall be transferred to AMS team /
Partner for resolution unless a specific issue / matter has been agreed by both the parties to be worked upon Post Go-
Live.

NDBS shall not be liable for in any manner, financially or otherwise for any delays arising out of any factors which are
not directly under the control of NDBS.
Page 35 of 44
NDBS Customer
Key Project Assumption
- Historical data migration is not included.
- Processes would be configured to the extent customizations are available within SAP solution.
- CUSTOMER should make available the Project Managers and Process Owners to provide timely sign off for phase
closures and milestones.
- Training of end users will be the responsibility of CUSTOMER whereas NDBS will follow Train the Trainer approach
- Ownership of the Source systems is CUSTOMER responsibility
- The dependent source systems should be live and functional during the tenure of the project
- The CUSTOMER Project Manager will coordinate selection and scheduling of all internal core team.
- Additional requirements if any raised during the course of the project will be treated as Change Request (CR).
However, the delivery of the same may or may not happen along with Go Live
- The scope covered in this document has been mutually decided and agreed upon. If the scope changes, NDBS and
CUSTOMER will jointly evaluate the impact on efforts and timeline, and suitable change request will be raised
- Project schedules, tasks, costs, and deliverables are estimates based on our current understanding of the project
scope and objectives. Schedules are important to achieve but nonetheless represent estimates and may be
revised during the course of carrying out the project upon agreement with CUSTOMER management.
- All product limitations should be dealt with SAP directly. We will help messaging with SAP but cannot be held
responsible for the same
- If WRICEF is more than mentioned the scope, it should be routed via change management.
- SAP Fiori Apps needs to be finalized by Explore phase. If the SAP Fiori Apps is not finalized by Explore phase or
SAP Fiori Apps finalized is less than the SAP Fiori Apps mention in the proposal, the remaining SAP Fiori Apps of
shall be considered as lapsed. If finalized SAP Fiori Apps is more than mentioned in the proposal, it should be
routed via change management.
- Project will be kick-started with a lead time of 8-12 weeks from PO is release, SOW sign-off.
- SAP System should be inplace for the consultants to start the work.
- All functional requirements need to be given by Explore phase itself.
- Submission of the final list of Transport requests (TR’s) denotes the completion of Baseline configuration

Communication Management Plan

Overview
To promote consistent and effective communications throughout this Project the parties need to plan communications
for the stakeholders, end users, vendors and CUSTOMERs impacted by the implementation and, of equal importance,
are the communications within the project team. A properly defined and executed communication plan is intended to:
(i) confirm that end users are familiar with the project at an appropriate level of detail; (ii) promote open
communications among the project team; and (iii) enhance communications between the project team and the
Steering Committee. The purpose of this part is to illustrate the requirements and application of the Project's
Communication Management Plan.

Steering Committee Communications

The CUSTOMER SAP Project Sponsor will report to the executive leadership on a quarterly basis, at a minimum. This
communications opportunity will be used primarily to review the Project progress, costs incurred to date, and expected
expenditures required for completing the Project. The Project Sponsor will also use this opportunity to review business
process changes/improvements and CUSTOMER's expected benefits of the Project. This communication will primarily
occur in a presentation format.

There will be two primary methods of communicating between the project team and the Steering Committee. The first
communication method is through periodic status reports. The status report will be issued weekly and will be written
and confirmed by the CUSTOMER Project Manager. Distribution to the Steering Committee will be via the CUSTOMER's
Page 36 of 44
NDBS Customer
email system and will also be stored in the Project repository. The status report will be issued in a standard format and
will cover the following topics: achievements and significant activities for the week, new issues or problems, and
planned activities for the following week.

The information in the status reports will form the agenda for the Steering Committee Meetings, which is the second
standard communication method between the Project Team and the Steering Committee. Steering Committee
Meetings will occur as required and will cover the items in the status report, project plan, upcoming events, project
issues, and any other pertinent Project related information. The meeting frequency will be determined during the
Project Preparation phase.

Project Team Communications

To confirm communications within each of the different functional and technical areas, project team meetings will be
held once a week at a mutually agreed upon time. These meetings will cover action items, issues, project progress, and
integration issues between functional and technical areas. The entire project team including business process
representatives, members of the Core technical team, and, if necessary, SMA's will attend this weekly meeting.

Consultants will document their weekly activities using individual status reports and deliver these status reports to the
NDBS Project Manager each week by a mutually agreed upon day and time. The NDBS Project Manager will aggregate
information and provide a project status report to the CUSTOMER Project Manager at a predefined time.

Additionally, each functional and technical sub-team will document and publish their activities using the same
individual status report template. These reports will be submitted to the CUSTOMER Project Manager at the weekly
project team status meeting. The CUSTOMER Project Manager will generate weekly project summary status reports
from these individual and sub-team status reports.

End User Communication

End user communications will occur throughout the Project flowing primarily through the functional project sub-team.
The functional project sub-teams will initiate the communications during their requirements gathering activities. The
functional project sub-teams will communicate specifics about what will be changing in the different functional areas
as the Project approaches Go Live.

The second method for end user communications will be through the CUSTOMER Project Manager. The project
management communications will cover specific topics that must be received by the end users, such as training
schedules and meetings or process validation sessions.

Vendor Communications
At an appropriate interval prior to Go Live a communication will be sent to CUSTOMER's vendors, and employees to
inform them of the new formats for the documents they regularly receive from CUSTOMER, such as invoices, payments,
purchase orders, etc. These letters will be written by the CUSTOMER Project Manager or CUSTOMER business
representatives and sent to the appropriate audience as determined by CUSTOMER. Targeted date for these
communications is at least two (2) weeks prior to the Go Live date.

Issue Management Plan

Overview
Issues are items that are identified by project team members during the Project that may impact the Project and that
cannot be resolved internally within the project team. Typically, issues are: (i) items that were not anticipated; (ii) tasks
that cannot be completed due to resource constraints; (iii) external factors; or (iv) scope management considerations.
The issue management procedure identified in this part must be followed for communicating, managing and closing
issues throughout the life of the Project.
Page 37 of 44
NDBS Customer
For the duration of the Project, the project team will use an MS-Excel spreadsheet to document and track issues to
resolution (the "Issues List"). The Issues List is not meant to be nor should it become a "To Do List." There are other
mechanisms that will be used throughout the course of the Project such as the project plan or the Go Live checklist
where "reminders" for tasks that must be completed can be documented.

Managing issues is the responsibility of the CUSTOMER Project Manager who will focus on preventing or quickly
resolving issues. Since issues may arise during the Project, the project team members will document issues as quickly
as they are discovered and follow the issue management procedure outlined below.

Issue Management Procedure Summary

Once an issue is identified, a project team member completes the Issue Form template and mails it to the CUSTOMER
Project Manager for review. The CUSTOMER Project Manager then reviews the item and decides whether the item
should be categorized as an issue or needs to be addressed in some other manner. If the item is categorized as an issue,
the CUSTOMER Project Manager must first enter the item into the Issues List assigning a priority rating and required
completion date and then assign the issue to a project team member who will work on resolving the issue.

Communication between the project team and CUSTOMER Project Manager is necessary in order to:
- Identify obstacles that may prevent the resolution of open issues.
- Keep the project management informed of any changes to the current plan.
- Agree on closure of open issues.
- Prevent obstacles from becoming emergencies.

This communication should occur during the weekly project team meetings, or more often as required by the project
timeline. Once an issue has been resolved, the resolution is documented in the Issues List for tracking and reference
purposes.

Issue Management Procedure Steps

# Responsible Person
1 Any project team member
2 CUSTOMER Project
Manager
3 CUSTOMER Project
Manager & Initiator
4 CUSTOMER Project
Manager
5 CUSTOMER Project
Manager
6 Assignee
7 Initiator
Step Description
Creates a new issue using the Issue Form template ("Initiator").
Screens all submitted issues and determines if the issue is relevant to the scope
of the Project
Prioritizes and categorizes the issue based on its impact to other tasks or
phases. Defers the issue if it is contingent on the resolution of another issue.
Assigns the issue to a project team member who is responsible to investigate
and find the appropriate resolution within a pre-defined time period
("Assignee").
Manages the issue to resolution, monitors and tracks the status of each issue,
and escalates as required.
Investigates and resolves the issue and documents the issue resolution in the
Issues Database.
Reviews Issue Resolution for completeness.

Project Manager Procedures

The CUSTOMER Project Manager must review the submitted issues and determine if such issues are relevant to the
scope of the Project. Part of the screening process is to route the issue in one of three manners:
- Reject - The CUSTOMER Project Manager rejects the issue if it is not relevant to the Project scope. If rejected, the
issue is returned to Initiator with an explanation of why it was rejected.
- Defer - The CUSTOMER Project Manager defers the issue if it is contingent on another issue that has not yet been
resolved. If necessary, the CUSTOMER Project Manager will expedite resolution of the related issue.
Page 38 of 44
NDBS Customer
- Accept - The CUSTOMER Project Manager accepts the issue if it may impede the progress or outcome of the Project.
Once the issue is accepted, the CUSTOMER Project Manager will manage the timely resolution of the issue.

The CUSTOMER Project Manager then assigns accepted issues to an individual project team member. In all cases, the
CUSTOMER Project Manager assigns the issue to the person with the highest level of authority required to reach a
quick resolution, as determined by the CUSTOMER Project Manager.

The CUSTOMER Project Manager must make it part of their regular duties to review the status of issues and to evaluate
the progress toward resolution. The following are suggestions for managing open issues:
- Approach major issues before minor ones.
- Tackle high priority issues before low priority ones.
- Consider segmenting more complex issues into multiple smaller issues.
- Talk to the project team members to understand their perspectives on the issues. By asking open-ended questions
and delving into the issues at hand, the CUSTOMER Project Manager is able to identify obstacles in advance and
prevent any need for expediting the issues. Further, the project team members may identify related issues or
additional details that have been overlooked.

Expedite or Escalate
As the Project progresses, issues may need to be expedited to resolution or escalated to another level for resolution.
The following steps are availabpale to the CUSTOMER Project Manager at this point:
- Expediting - If an issue is not resolved by the forecasted date, and the lack of resolution will affect other Project
steps, the CUSTOMER Project Manager evaluates the following expediting steps:
a. Change the priority of tasks assigned to the project team members.
b. Rearrange the project schedule to accommodate issue resolution, keeping in mind the CUSTOMER's business
and project goals.
- Escalating - If the issue is not resolved according to the Project plan and this may affect the project timeline, and
there is no resolution through expediting the issue, the CUSTOMER Project Manager may opt to escalate it to the
Steering Committee. Critical issues not resolved within 48 hours following assignment to the project team member
may be escalated to the Steering Committee for resolution, as determined by the CUSTOMER Project Manager.

Closing the Issues

Open issues are reviewed in the weekly project status meeting. Once the Assignee has completed the issue to the
CUSTOMER Project Manager and Initiator's reasonable satisfaction, resolution is reviewed at the weekly meeting. The
Assignee completes the resolution fields in the Issues Form and marks the issue as complete. Additionally, notes and
documentation on the resolution are entered into the Issues Form for tracking and audit purposes. The CUSTOMER
Project Manager will use the resolution information to complete the resolution field in the Issues List.

Issue Follow-up
There may be issues that remain open past the Go Live date. The CUSTOMER Project Manager will be responsible for
the transition / re-assignment of open issues from NDBS personnel to CUSTOMER personnel.

Assignee Issue Management Procedures

- Review the issue within the Issues List and the SAP Issues Form to determine the nature of the issue.
- If necessary, discuss the issue with the Initiator to get a better understanding of the details of the issue.
- Resolve the issue.
- Update the issue in the Issues Form with details on the resolution of the issue. If necessary, attach supporting
documentation.
- Submit the updated Issues Form to the CUSTOMER Project Manager for issue closure.

Page 39 of 44
NDBS Customer
Scope Management Plan

The purpose of scope management is to establish a process for managing project scope changes. Effective scope
management requires that scope be clearly established and aggressively maintained. Scope changes must be fully
documented, including expected impact on both Project budget and schedule.

The baseline scope of the CUSTOMER Project is defined in the Statement of work. All proposed changes to the Project
will be measured and/or compared to the baseline scope.

When an item is identified that is out of the baseline scope of the Project then a Change Request Form shall be
completed by a project team member and the item is also to be logged by CUSTOMER Project Manager into a MS-Excel
spreadsheet or equivalent CUSTOMER tool. These "out of scope" items will typically be requested by the system's end
users and will be identified as opportunities to improve the functioning of the existing processes. The CUSTOMER
Project Manager will assess the impact of the change to the Project's budget and schedule and will add this information
on the Change Request Form. The change request will then follow the resolution process as outlined below.

Scope Management Procedure Steps

No Responsible Person Step Description

1 Any team member
2 CUSTOMER Project Manager
3 CUSTOMER Project Manager
& Initiator
4 CUSTOMER Project Manager
5 Assignee
6 CUSTOMER Project Manager
7 CUSTOMER Project Sponsor/
Steering Committee
8 Initiator
Creates a change request using the SAP Change Request template or
equivalent CUSTOMER Toolset ("Initiator").
Screens all submitted requests and determines if the request is
relevant to the scope of the Project.
Prioritizes and categorizes the request based on its impact to other
tasks or phases.
Assigns the request to a project team member who is responsible to
investigate the scope change request ("Assignee").
Investigates the scope change request and documents the amount of
time/effort required for the change.
Reviews the schedule impact and total costs with the Steering
Committee and Project Sponsor.
Reviews the scope change and decides to both accept the scope
change, costs, and schedule impact or defers the scope change until a
future date.
Reviews the scope change request decision.

D. Lokasi Pekerjaan / Location of Work:

Pelaksanaan akan dilakukan dalam metode hybrid yaitu Fit-Gap (4 minggu), UAT (3 minggu), dan Pelatihan
(2 minggu) akan dilakukan Onsite pada lokasi Pelanggan di Batulicin, Kalimantan Selatan, sementara
Configuration dan SIT akan dilakukan secara remote/

Implementation will be delivered in hybrid method in which Fit-Gap (4 weeks), UAT (3 weeks), and Training
(2 weeks) will be Onsite at Customer site in Batulicin, Kalimantan Selatan, while Configuration and SIT can
be done remotely.

Page 40 of 44
NDBS Customer
E. Ketentuan tambahan / Additional Terms:

1. Setiap keterlambatan yang tidak disebabkan oleh NDBS akan dihitung sebagai Change Request/ Any
delay not caused by NDBS will be considered as Change Request.

F. Pengeluaran / Expenses:
1. The infrastructure for the project resources including office infrastructure, Laptop, LAN and internet
connectivity, printers, scanners will be provided by the Customer.
2. Any travel to Customer offices in other locations from base onsite location (Jakarta) is to the account of
Customer as per NDBS’s travel policy. Air Travel, Meals, Accommodation, Per Diem and Local
Conveyance for NDBS consultants will be taken care by the Customer.
3. Home tirp during Onsite, outside JABODETABEK area, is every 2 (two) weeks
4. Go-live definition is the application ready to be used.
5. Any delay not caused by NDBS will be considered as Change Request.
6. Project delay more than 3 days due to delay in validation of documents / approval would attract
additional charges.
7. Any other additional work outside the scope of work will be considered as Change Request and will use
rate at IDR 4,000,000 per man-day.
8. In case the Customer wishes to hold the project for some time, then NDBS will charge a holding fee to
maintain the continuity of resources with additional rate as mentioned in point 7 above.
9. If for some unforeseen business reasons, the project has to be called off during the course of its
execution, then Customer shall pay the amounts pro-rated to the proportion of total effort already spent
by NDBS team.

Page 41 of 44
NDBS Customer
 LAMPIRAN II / ATTACHMENT II
TIMELINE PEKERJAAN / TIMELINE OF WORK

A. Start Date/ Tanggal Mulai:

January 22, 2024 / 22 Januari 2024
B. End Date/Tanggal Selesai:
January 26, 2025 / 26 Januari 2025
C. Timeline of Work/Timeline Pekerjaan:

1. SAP ERP S/4 HANA

Pilot Project Duration : 7 Months & 1 Month Hypercare Support

Roll-out Project Duration : 3 Months & 1 Month Hypercare Support
Month 1 Month 2 Month 3 Month 4 Month 5 Month 6 Month 7 Month 8 Month 9 Month 10 Month 11 Month 12
Project Activity (Pilot)
W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12 W13 W14 W15 W16 W17 W18 W19 W20 W21 W22 W23 W24 W25 W26 W27 W28 W29 W30 W31 W32 W33 W34 W35 W36 W37 W38 W39 W40 W41 W42 W43 W44 W45 W46 W47 W48

Prepare (All Companies)

- Project Planning
- Overview Training
- Kickoff Meeting
- Infrastructure Provisioning
Explore (All Companies)
- System Preparation (Development)
- Blueprint Workshop
- Blueprint Confirmation
- Master Data Template Socialization
- RICEF List
Realize (Pilot: JG, JB)
- System Preparation (QAS & PRD)
- Configuration Development System
- Authorization Development
- Functional Specification Dev
- RICEF Development
- Unit/ Functional Test
- System Integration Test (SIT)
- Key User Training
- User Acceptance Test (UAT)
Deploy (Pilot: JG, JB)
- Basis Activity
- End User Training
- Data Migration & Cut Over
- Final Preparation (Go No Go)
Run (Pilot: JG, JB)
- Go Live and Support

Project Activity (Roll-Out)

Realize (Roll-Out : JMT, JML, STM, DSP)

- Finalize Configuration Development System
- Authorization Development
- System Integration Test (SIT)
- Key User Training
- User Acceptance Test (UAT)
Deploy (Roll-Out : JMT, JML, STM, DSP)
- Basis Activity
- End User Training
- Data Migration & Cut Over
- Final Preparation (Go No Go)
Run (Roll-Out : JMT, JML, STM, DSP)
- Go Live and Support

Few important Points to note are:

• During the project Prepare phase a detailed plan will be prepared and shared with CUSTOMER Project Manager.
However, total project duration and intermediate milestones would be maintained as per the above plan.
• NDBS would follow the Global Delivery Methodology and execute the project on Onsite/Remote model
• The plan also allows End User training to be done in the Deploy phase.
• This being a very aggressive plan, we assume that CUSTOMER will ensure effective organization change management
is already in place to achieve the timely completion of this engagement.
• In case CUSTOMER requires changes in the project schedule for business related reasons, the same will be
accommodated with a change order for the revised efforts and commercials

Page 42 of 44
NDBS Customer
Impact of project delay beyond planned timeline:
When project goes beyond the planned timeline/duration, it will have an impact on resource allocation and cost. Such
situations will call for change management.

Consultant working days and availability:

Typical NDBS consultants’ work Schedule /week at NDBS office/CUSTOMER’s facility will be Five (5) days, Monday
through Friday, excluding NDBS public holidays, with working hours following CUSTOMER’s timezone from 8 AM to 5 PM
and a provision for 1-hour lunch break.

D. Masa Support/ Support Period:

1 (satu) bulan/ 1 month.

Page 43 of 44
NDBS Customer
 LAMPIRAN III/ ATTACHMENT III
KOMERSIAL/COMMERCIL

Nilai biaya Perjanjian secara keseluruhan adalah
sebesar Rp17.730.000.000,00 (tujuh belas miliar
tujuh ratus tiga puluh juta rupiah) belum termasuk
Pajak Pertambahan Nilai (PPN) sebesar 11% dengan
rincian nilai Pekerjaan sebagai berikut:
The total fees of Agreement is IDR17,730,000,000,00
(seventeen billion seven hundred thirty million
Indonesian rupiah) exclude Value Added Tax (VAT)
11% with details of amount of Work as follows:

A. Pembayaran biaya Perjanjian oleh Pelanggan A. Payment of the Agreement fees by the Customer
kepada NDBS akan dilakukan dengan tata cara to NDBS will be made with below method:
sebagai berikut:

Implementation of SAP ERP S/4HANA

Payment Milestone Percentage Sub Total

#1 On Kick Off Meeting 30% 5,194,500,000
#2 On completion of Explore phase 20% 3,463,000,000
#3 UAT Sign-Off Pilot 10% 1,731,500,000
#4 Go-live Pilot 10% 1,731,500,000
#5 Hypercare Pilot 5% 865,750,000
#6 UAT Roll Out 10% 1,731,500,000
#7 Go-Live Roll Out 10% 1,731,500,000
#8 Hypercare Roll Out 5% 865,750,000
100% 17,315,000,000

B. Termin Pembayaran pada ayat (A) diatas bukan
merupakan suatu urutan tahapan Pembayaran,
bahwa masing-masing tahap akan dibayarkan
sesuai dengan penyelesaian Pekerjaan oleh
NDBS.
B. Terms of Payment in Article (A) above are not in
sequence of stages of payment, that each stage
will be paid based on the completion of Work by
NDBS.

Page 44 of 44
NDBS Customer