# CAKRA · VDT configuration import / Impor konfigurasi VDT

This guide is for app users. No code installation or server setup is needed.
Panduan ini untuk pengguna aplikasi. Tidak perlu instalasi kode atau setup server.

## Practice package / Paket latihan

Download `cakra-rno-config-v1.json` from the documentation. It is a valid synthetic training package, not actual operator inventory or a verified road route. Keep the original file for comparison.

Unduh `cakra-rno-config-v1.json` dari dokumentasi. Paket latihan sintetis ini valid untuk impor, bukan inventori operator atau rute jalan terverifikasi. Simpan file asli untuk perbandingan.

The package contains explicit units, project revision, six LTE/NR sectors, radio/receiver/mobility settings, thresholds, a timed route and small terrain/building examples.

Paket berisi unit eksplisit, revisi proyek, enam sektor LTE/NR, setting radio/receiver/mobilitas, threshold, rute dengan waktu serta contoh terrain/bangunan kecil.

## Use it in CAKRA / Gunakan di CAKRA

1. Sign in and open **Virtual Drive Test** with an eligible plan. / Masuk dan buka **Virtual Drive Test** dengan paket yang sesuai.
2. Choose **Import configuration** and select the downloaded JSON. / Pilih **Impor konfigurasi** lalu JSON yang diunduh.
3. Review the project, revision, sector count, units, positions, frequencies, bandwidth, power, antenna gain/height, azimuth and separate electrical/mechanical tilts. / Review proyek, revisi, jumlah sektor, unit, posisi, frekuensi, bandwidth, daya, gain/tinggi antena, azimuth serta tilt electrical/mechanical terpisah.
4. Expand **Complete validated input** to inspect settings, route and environment details. Read warnings. Cancel if the values are not what you intended. / Buka **Seluruh input tervalidasi** untuk memeriksa setting, rute serta detail lingkungan. Baca warning. Batalkan bila nilainya tidak sesuai.
5. Choose **Apply configuration** to fill the editable VDT inputs. Review the route and site positions before proceeding. / Pilih **Terapkan konfigurasi** untuk mengisi input VDT. Periksa rute serta posisi site sebelum melanjutkan.
6. If you want a prediction, press **Run**. Run performs local RF preflight first. If all checks are ready, the same click can proceed to current Enterprise authorization and prediction, without a processing-credit deduction. Blocked checks stop the run; warnings pause for review/acknowledgment and another Run. / Bila ingin prediksi, tekan **Run**. Run melakukan RF preflight lokal dahulu. Jika semua check ready, klik yang sama dapat melanjutkan otorisasi Enterprise saat ini serta prediksi, tanpa pemotongan credit pemrosesan. Check blocked menghentikan Run; warning menunggu review/persetujuan lalu Run lagi.
7. Inspect the completed map/route and playback; compare with compatible field measurements when available. Save/export deliberately. / Periksa peta/rute selesai serta playback; bandingkan dengan pengukuran lapangan kompatibel bila tersedia. Simpan/ekspor sesuai kebutuhan.

**Apply is not Run or Save.** Import review and Apply do not consume prediction credits or save remotely. Apply replaces editable inputs and clears their current preview/result; the retained completed Run archive is separate. Cancel does not change the inputs.

**Terapkan bukan Run atau Simpan.** Review impor serta Terapkan tidak memakai credit prediksi atau menyimpan remote. Terapkan mengganti input editable serta mengosongkan preview/hasil saat ini; arsip Run selesai terpisah. Batal tidak mengubah input.

## Prepare your own package / Siapkan paket sendiri

Use authorized, verified RNO data and the accompanying field guide. Do not rename a PDF, Word or Excel file to JSON: arbitrary vendor documents are not automatically parsed. Numeric fields must contain numbers, not strings such as `43 dBm`. Preserve the supported schema and explicit units.

Gunakan data RNO terverifikasi yang berwenang Anda gunakan beserta panduan field. Jangan mengganti ekstensi PDF, Word atau Excel menjadi JSON: dokumen vendor sembarang tidak diparse otomatis. Field numerik harus berisi angka, bukan string seperti `43 dBm`. Pertahankan schema yang didukung serta unit eksplisit.

- Conducted carrier power is in dBm, not EIRP. / Daya carrier conducted dalam dBm, bukan EIRP.
- Peak antenna gain is dBi; antenna height is above local ground. / Gain antena puncak dBi; tinggi antena terhadap tanah lokal.
- Azimuth is clockwise from north; electrical and mechanical tilts are separate. / Azimuth searah jarum jam dari utara; tilt electrical dan mechanical terpisah.
- Route coordinates are latitude/longitude; optional elapsedMs starts at zero and strictly increases on every vertex. / Koordinat rute latitude/longitude; elapsedMs opsional dimulai nol dan meningkat ketat pada setiap vertex.
- Keep the original RNO package and environment attachments. Exported native scenario JSON alone does not retain every attachment. / Simpan paket RNO serta lampiran lingkungan asli. JSON skenario native hasil ekspor saja tidak menyimpan seluruh lampiran.

Practice data and predictions are not field measurements. Validate the equipment, sites, environment and model against independent observations before using the results for real engineering decisions.

Data latihan serta prediksi bukan pengukuran lapangan. Validasi equipment, site, lingkungan serta model terhadap pengamatan independen sebelum menggunakan hasil untuk keputusan engineering nyata.

## Larger Jakarta exercise / Latihan Jakarta lebih lengkap

The documentation also provides `CAKRA-Jakarta-RNO-Test-Pack-v1.0.zip`. Extract it; start with `01-full-route/CAKRA-Jakarta-LTE-B3-Overview.rno.json` for the full planned road route, or `02-rf-clusters/LTE-B3/CAKRA-Jakarta-LTE-B3-C01.rno.json` for a denser local exercise. NR-n1 files are separate scenarios. Import one `.rno.json` at a time using the same review/Apply steps above, not the ZIP or master inventory. Read `START-HERE.md` and the documents in `04-engineering` before Run.

Dokumentasi juga menyediakan `CAKRA-Jakarta-RNO-Test-Pack-v1.0.zip`. Ekstrak; mulai dari `01-full-route/CAKRA-Jakarta-LTE-B3-Overview.rno.json` untuk rute jalan planning penuh, atau `02-rf-clusters/LTE-B3/CAKRA-Jakarta-LTE-B3-C01.rno.json` untuk latihan lokal lebih rapat. File NR-n1 adalah skenario terpisah. Impor satu `.rno.json` setiap kali dengan langkah review/Terapkan di atas, bukan ZIP atau master inventory. Baca `START-HERE.md` dan dokumen `04-engineering` sebelum Run.

Public road geography and manufacturer references are distinct from assumed BTS locations/configuration and predicted RF. The router distance is about 61.6 km, not an exact reconstruction of the 51.18 km screenshot. Cluster runs are separate: their mobility counts cannot be combined as one continuous drive. Road access and field safety still require local verification.

Geografi jalan publik serta referensi pabrikan berbeda dari asumsi lokasi/konfigurasi BTS dan RF prediksi. Panjang router sekitar 61,6 km, bukan rekonstruksi persis screenshot 51,18 km. Run cluster terpisah: count mobilitasnya tidak dapat digabung sebagai satu drive kontinu. Akses jalan serta keselamatan lapangan tetap perlu verifikasi lokal.