performance, the external entities Sub Director of Forest Product Manufacture, Sub Director of Production, and Sub Director of Marketing
and Industry Assessment were used the system and data that have been inputted as defined on the first and second process. Referring to the overall
process, there are several outputs provided, i.e.: 1 Information of forestry industry activities; 2 Forestry industry performance; 3 Location of forestry
industry and material supplier; 4 Map of material distribution. All those output were used to monitor and evaluate forestry industry by the external
entities.
3. Conceptual Model
A conceptual model used to describes the data content on the system proposed. On conceptual model, the data was drawn into Entity –
Relationship E – R diagram and use a symbol to illustrate the relationship between data. The E – R diagram consists of entities, relationships between
entities, and attribute of entities. The E – R diagram is used to represent the meaning of data.
Figure 4.7 illustrated the E – R diagram of the system proposed. Here, the entity identified as a table that has independent physical or conceptual
existence i.e. forestry industry U_Perusahaan_Umum, forestry industry product U_Jenis Produk, and workers U_Tenaga_Kerja where the
attributes describes the properties of entity i.e IPHHK_id, Nama_IPHHK, jenis_produk, etc. A relationship was drawn with a line connected between
entities. The order of relationship defined as a set association between two or
more participating entity types. The order was expressed as one to one relationship 1:1; one to many relationship 1:M; and many to many
relationship M:M. For the relationship of entity “forestry industry” with “forestry industry product” the order can be categorized as 1 : M relationship.
It means that “one industry can have many kinds of product”.
Figure 4.7. Entity – Relationship diagram of developed system
4. Logical Model
Logical modeling phase is related to the actual implementation of the conceptual data model in a commercial DBMS. Logical model defines as the
basic organization of a database. Table 4.2 described the logical model of the system developed. The table list of all files in the database, the number of
records in each file, and the names of each fields. Table 4.2. Logical data model of system developed
No Category
Entity Attributes
U_Alamat_Prsh IPHHK_id, jl_pusat, desa_pusat, kec_pusat,
kab_pusat, telp_pusat, prov_pusat, jl_wakil, desa_wakil, kec_wakil, kab_wakil, telp_wakil,
prov_wakil
U_izin_kapasitas IPHHK_id, kode_produk, jenis_produk,
kelompok_industri, kapasitas_izin, satuan, kapasitasa_terpasang, satuan_pasang, rendemen,
kebutuhan_bb, satuan_butuh, jenis_bb
U_Perusahaan_Umum IPHHK_id, Nama_IPHHK, No_akta_berdiri,
notaris_berdiri, npwp, investasi_rp, investasi_dollar, notaries_saham, tgl_saham_notaris,
no_saham_notaris, komisaris_utama, direktur_utama, jenis_pnm_modal
1 Profile
U_Jenis_Produk Kode, jenis_produk, kelompok_industri, nomor
BB_jenisBB Kode, jenis_BB
BB_kebutuhan IPHHK_id, jenis_produk, rendemen, kebutuhan_bb,
jenis_bb, nomor BB_Pemasok_RKT
Pemasok_id, tahun, rkt, stock BB_Pemenuhan
IPHHK_id, tahun, bulan, Jenis_BB, Realisasi, pemasok_id, jenis_kayu, kategori_pemasok,
kode_bulan, iphhk_prov
BB_Penggunaan IPHHK_id, tahun, bulan, Jenis_BB,
Jenis_produk_jenis_kayu, pengguna_bb, keterangan, kode_bulan, nomor, kategori_industri,
kelompok_industri
BB_Produksi IPHHK_id, tahun, bulan, kelompok_industri,
jenis_produk, kategori_industri, Jenis_bb, realisasi_prod, persentase_prod, keterangan,
iphhk_prov, kode_bulan, nomor, satuan
BB_Prsh_Pemasok Pemasok_id, Nama_Prsh, kategori_prsh, kel_prsh,
LH, LHP, LBE, EL, EB, EV 2 Materials
BB_Rencana_Pemenuhan IPHHK_id, tahun, pemasok_id, Jenis_bb,
jenis_kayu, jumlah_kategori_pemasok
3 Machine Mesin
no_m, IPHHK_id, tahun, kategori, jenis_mesin, unit, merk, kapasitas, Negara_pembuat, tahun_buat,
tahun_pasang, keterangan, tipe
5. Physical Design
