23
3.3.1. Block Diagram
Gambar 3.1 Block Diagram Optimalisasi Penataan Barang. Pada Gambar 3.1 diatas menjelaskan tentang alur proses rancang bangun
aplikasi optimalisasi penataan barang dengan pengolahan data mulai dari input data, proses dan output yang diolah menjadi informasi agar dapat
dikaitkan dengan permasalahan yang ada dan kebutuhan dari pengguna.
3.3.2. System Flow
Penggambaran arus informasi akan dijabarkan pada alur sistem yang akan diimplementasikan dengan komputer berupa penjaluran antara data, proses dan
laporan.
24
A. System Flow Inbound
Inbound
Checker Administrasi
START
Sesuai ? Input data ASN
No Database
Putaway List
Receipt Report
Putaway List
END ASN
Suttle Input data receipt
Input Putaway Yes
Print Putaway List
Putaway confirm Receipt confirm
Receipt report
Gambar 3.2 System flow Inbound System flow Inbound
merupakan gambaran aliran proses data barang masuk dari aplikasi optimalisasi penataan barang. Adapun proses yang termasuk
didalamnya adalah proses asn, proses receipt dan proses putaway.
B. System Flow Outbound
System flow outbound menggambarkan alur proses pengirimankeluarnya barang dari gudang kedalam container. Setiap data barang keluar dari gudang
akan tercatat oleh aplikasi dan disimpan ke dalam database. Data yang dicatat
25
pada proses outbound adalah data shipment order, data pick dan data shipment. Alur proses outbound dapat dilihat pada gambar dibawah ini.
Outbound
Checker Administrasi
START
Tersedia ?
No Database
Picking List
Shipment Report
Picking List
END SO
Input data SO
Input Picking Yes
Print Picking
Picking confirm Input Shipment
Shipment report
Gambar 3.3 System flow Outbound.
C. System Flow Pallet Location
System flow pallet location adalah gambaran proses penentuan lokasi pallet berdasarkan ketersediaan lokasi pada gudang. Pada proses ini lokasi yang
tersedia untuk pallet tidak bersifat tetap, dimana pallet untuk salah satu negara konsumen dapat diletakan di lokasi konsumen negara lain dengan beberapa
aturan. Tampilan proses penentuan pallet location dapat dilihat pada gambar dibawah ini.
26
Pallet Location
Checker Administrasi
START Proses penentuan
pallet location
Apakah negara tersedia ?
Menentukan negara consumen
Menentukan lokasi pallet
Yes
No Database
Print doc. receiving
Menentukan lokasi alternatif by location
dan kapasitas Apakah kapasitas
lokasi tersedia ? Yes
No Simpan doc.
receiving
Pallet Label Putaway List
Pallet Label Putaway List
END Apakah kapasitas
lokasi tersedia ? No
Yes
Gambar 3.4 System flow Location
3.3.3. Data Flow Diagram DFD
Data Flow Diagram DFD menunjukkan aliran data dalam rancang
bangun aplikasi optimalisasi penataan barang.
A. Context diagram
Gambaran dari context diagram dapat dilihat pada gambar di bawah.
27
Gambar 3.5 Context Diagram Optimalisasi Penataan Barang Context diagram menggambarkan proses sistem aplikasi optimalisasi
penataan barang. Context diagram diatas mempunyai 2 entity yaitu admin wms dan checker. Admin wms melakukan input data-data master sebagai dasar dari
sistem. Admin wms menerima hasil proses sistem berupa laporan stock, laporan inbound, laporan outbound dan laporan transfer. Checker mempunyai tugas
melakukan konfirmasi terhadap data barang yang masuk dan keluar gudang. Detail dari context diagram dapat dilihat pada data flow diagram level 0.
B. Level 0
Rancangan level 0 dari data flow diagram sistem rancang bangun aplikasi optimalisasi penataan barang dapat dilihat pada gambar dibawah.
Shipment Confirm Shipment List
Data Location Data Whs Zone
Data Container Data State
Data City Transfer Report
Stock Report Outbound Report
Inbound Report
Data Customer Data Country
Data Product Doc SO
Doc Receipt ASN List
Transfer List Picking List
Putaway List Receipt List
Transfer Confirm Picking Confirm
Putaway Confirm Receipt Confirm
1
Sistem Optimalisasi Penataan Barang pada Gudang PT Kamadjaja Logistics
+
Unilever Checker
Supervisor Gudang
28
Gambar 3.6 DFD level 0 Optimalisasi Penataan Barang
C. Level 1 maintenance data inbound
Gambar 3.7 DFD level 1 Inbound
[Shipment Confirm] [Shipment List]
[Data Location] [Data Whs Zone]
[Data Container]
[Data State] [Data City]
Data Putaway
Data Picking
Data Product Data Customer
Data Country Data Shipment
Data SO Data Receipt
Data ASN
Data Transfer
Data Transfer Data City
Data State
Data Transfer Data Picking
Data SO Data Putaway
Data Receipt Data ASN
Data Whs Zone
Data Location Data Location
Data Whs Zone Data Whs Zone
Data Location Data Container
Data Product Data Country
Data Customer
Data Container Data Product
Data Country Data Customer
[Transfer Report] [Stock Report]
[Outbound Report] [Inbound Report]
[Picking List] [Putaway List]
[Picking Confirm] [Transfer Confirm]
[Receipt Confirm] [Putaway Confirm]
[Receipt List]
[Transfer List]
[Doc SO] [Doc Receipt]
[ASN List] [Data Customer]
[Data Country] [Data Product]
Checker Unilever
Supervisor Gudang
1.1 Maintenance Master
+
1.2 Menerima Barang atau
Inbound
+
1.3 Mengeluarkan Barang
atau Outbound
+
1.4 Memindahkan
Barang atau Transfer
+
1.5 Pembuatan Report
+
1 Customer
2 Country
3 Product
4 Container
5 Location
6 Warehouse Zone
7 ASN
8 Receipt
9 Putaway
10 SO
11 Picking
12 Shipment
13 State
14 City
15 Transfer
[Data ASN] [Data Product]
[Data Country] [Data Customer]
[Data Location] [Data Whs Zone]
[Data ASN]
[Data Receipt] [Data Putaway]
[Putaway List]
[Receipt Confirm] [Putaway Confirm]
[Receipt List] [Doc Receipt]
[ASN List] Unilever
Checker 1
Customer 2
Country 3
Product 5
Location 6
Warehouse Zone
7 ASN
8 Receipt
9 Putaway
1.2.1 Mencatat ASN
1.2.2 Mengecek Receipt
1.2.3 Membuat Putaway
List
29
Level 1 inbound menggambarkan alur data proses maintenance data inbound. Level 1 inbound merupakan detail dari level 0 proses optimalisasi
penataan barang. Pada level 1 inbound terdapat proses expected receivingASN, receiving dan putaway.
D. Level 1 maintenance data transfer
Gambar 3.8 DFD level 1 Maintenance Data Transfer
Level 1 maintenance data transfer merupakan detail dari proses transfer location pada level 0. Pada level 1 maintenance data transfer terdapat proses
transfer location untuk pemindahan lokasi barang.
E. Level 1 maintenance data outbound
Gambar 3.9 DFD level 1 Maintenance Data Outbound
Level 1 maintenance data outbound merupakan alur data secara detail dari proses outbound pada level 0. Level 1 maintenance data outbound memiliki tiga
proses yaitu proses shipment order, picking product dan shipment.
[Data Transfer] [Transfer Confirm]
[Transfer List] Checker
15 Transfer
1.4.1 Mencatat Transfer
Flow_239 [Data Product]
[Data Customer] [Data Country]
[Data Transfer] [Data Container]
[Data Picking] [Data SO]
[Data Whs Zone] [Data Location]
[Shipment Confirm] [Shipment List]
[Picking List] [Picking Confirm]
[Doc SO] Unilever
Checker 4
Container
5 Location
6 Warehouse Zone
10 SO
11 Picking
12 Shipment
2 Country
1 Customer
3 Product
1.3.1 Mencatat SO
1.3.2 Membuat Picking
List 1.3.3
Mencatat Shipment
30
F. Level 1 maintenance data master
Gambar 3.10 DFD level 1 Maintenance Data Master Level 1 maintenance data master merupakan alur data secara detail dari
proses maintenance master pada level 0. Level 1 maintenance data master memiliki lima proses yaitu proses maintenance product, maintenance country,
maintenance customer, maintenance location dan maintenance countainer.
[Data Whs Zone] [Data Location]
[Data Container]
[Data Product] [Data Country]
[Data Customer]
[Data State] [Data City]
[Data Whs Zone] [Data State]
[Data Product] [Data Location]
[Data Customer] [Data Country]
[Data Container] [Data City]
Unilever 1
Customer 2
Country
3 Product
4 Container
6 Warehouse Zone
5 Location
13 State
14 City
1.1.1 Maintenance
City 1.1.2
Maintenance Container
1.1.3 Maintenance
Country 1.1.4
Maintenance Customer
1.1.5 Maintenance
Location 1.1.6
Maintenance Product
1.1.7 Maintenance
State 1.1.8
Maintenance Whs Zone
31
G. Level 1 reporting
Gambar 3.11 DFD level 1 Reporting
Level 1 reporting merupakan alur data secara detail dari proses reporting pada level 0. Level 1 reporting memiliki empat proses yaitu proses pembuatan
report inbound, report transfer, report stock dan report outbound.
3.3.4. Entity Relationship Diagram ERD
Entity Relationship Diagram ERD yaitu alat untuk mempresentasikan
semua kebutuhan-kebutuhan sistem yang berkaitan dengan field-field yang digunakan berupa tipe dan atribut dari field-field tersebut, serta relationship dari
tabel-tabel yang mendukung sistem.
Flow_260 Flow_259
[Data Picking] [Data Shipment]
[Data SO] [Data Putaway]
[Data Receipt] [Data ASN]
[Data Transfer]
[Stock Report] [Transfer Report]
[Outbound Report] [Inbound Report]
Supervisor Gudang
15 Transfer
7 ASN
8 Receipt
10 SO
12 Shipment
11 Picking
9 Putaway
1.5.1 Membuat
Inbound Report
1.5.2 Membuat
Outbound Report 1.5.3
Membuat Transfer Report
1.5.4 Membuat Stock
Report
32
a. Conceptual Data Model
CDM
Gambar 3.12 Conceptual Data Model Rancang Bangun Aplikasi Optimalisasi Penataan Barang
Pada CDM terdapat 17 table yang masing-masing berisi atribut-atribut yang berfungsi sebagai data pada sistem informasi ini, kemudian diolah menjadi
PDM yang dihasilkan dari proses generate model dari table yang terdapat pada CDM.
Relation_782 Relation_688
Relation_687
Relation_686
Relation_685 Relation_499
Relation_496 Relation_495
Relation_494
Relation_493 Relation_487
Relation_432 Relation_431
Relation_377
Relation_322
Relation_321 Relation_134
Relation_129
Relation_119
Relation_118 Relation_117
Relation_92 Relation_69
Relation_67 Relation_55
Relation_47 Relation_25
Country country id
country name Customer
customer id customer name
address city
state zip code
email telp1
telp2 detail info receiving
detail info rcv id quantity
status create time
create by
product product id
product name weight
volume info receiving
info rcv id info date
plan rcv date status procces
Putaway putaway id
receiving receiving id
receiving date detail receiving
detail rcv id quantity rcv
location location id
location name priority
picking picking id
picking date detail picking
detail picking id quantity picking
order shipment order shipment id
order date plan shipment date
shipment shipment id
date shipment vehicle number
driver
detail order shipment detail order shipment id
quantity shipment total weight
total volume status order
container container id
container type capacity container
weight container
detail putaway detail putaway id
pallet id inventory
inventory id
33
b. Physical Data Model
PDM
Gambar 3.13 Physical Data Model Rancang Bangun Aplikasi Optimalisasi Penataan Barang
DETAIL_PUTAWAY_ID = DETAIL_PUTAWAY_ID
CUSTOMER_ID = CUSTOMER_ID COUNTRY_ID = COUNTRY_ID
PRODUCT_ID = PRODUCT_ID
LOCATION_ID = LOCATION_ID COUNTRY_ID = COUNTRY_ID
ORDER_SHIPMENT_ID = ORDER_SHIPMENT_ID PRODUCT_ID = PRODUCT_ID
PUTAWAY_ID = PUTAWAY_ID
LOCATION_ID = LOCATION_ID INFO_RCV_ID = INFO_RCV_ID
COUNTRY_ID = COUNTRY_ID COUNTRY_ID = COUNTRY_ID
CUSTOMER_ID = CUSTOMER_ID PRODUCT_ID = PRODUCT_ID
LOCATION_ID = LOCATION_ID RECEIVING_ID = RECEIVING_ID
CONTAINER_ID = CONTAINER_ID
ORDER_SHIPMENT_ID = ORDER_SHIPMENT_ID
ORDER_SHIPMENT_ID = ORDER_SHIPMENT_ID PRODUCT_ID = PRODUCT_ID
PICKING_ID = PICKING_ID PRODUCT_ID = PRODUCT_ID
RECEIVING_ID = RECEIVING_ID INFO_RCV_ID = INFO_RCV_ID
PRODUCT_ID = PRODUCT_ID COUNTRY_ID = COUNTRY_ID
COUNTRY COUNTRY_ID
integer COUNTRY_NAME varchar20
CUSTOMER CUSTOMER_ID
integer COUNTRY_ID
integer CUSTOMER_NAME varchar20
ADDRESS varchar50
CITY varchar20
STATE varchar20
ZIP_CODE varchar10
EMAIL varchar50
TELP1 varchar20
TELP2 varchar20
DETAIL_INFO_RECEIVING DETAIL_INFO_RCV_ID
varchar12 PRODUCT_ID
integer COUNTRY_ID
integer QUANTITY
integer STATUS
numeric1 CREATE_TIME
date CREATE_BY
date INFO_RCV_ID
integer
PRODUCT PRODUCT_ID
integer PRODUCT_NAME varchar50
WEIGHT integer
VOLUME integer
INFO_RECEIVING INFO_RCV_ID
integer INFO_DATE
date PLAN_RCV_DATE
date STATUS_PROCCES numeric1
PUTAWAY PUTAWAY_ID varchar15
RECEIVING_ID integer RECEIVING
RECEIVING_ID integer
INFO_RCV_ID integer
RECEIVING_DATE date DETAIL_RECEIVING
DETAIL_RCV_ID varchar20 PRODUCT_ID
integer COUNTRY_ID
integer QUANTITY_RCV integer
RECEIVING_ID integer
LOCATION LOCATION_ID
varchar5 LOCATION_NAME varchar5
COUNTRY_ID integer
PRIORITY varchar10
PICKING PICKING_ID
varchar16 ORDER_SHIPMENT_ID
varchar20 PICKING_DATE
date DETAIL_PICKING
DETAIL_PICKING_ID varchar15 PRODUCT_ID
integer QUANTITY_PICKING integer
LOCATION_ID varchar2
PICKING_ID varchar16
ORDER_SHIPMENT ORDER_SHIPMENT_ID
varchar20 ORDER_DATE
date PLAN_SHIPMENT_DATE
date SHIPMENT
SHIPMENT_ID varchar20
ORDER_SHIPMENT_ID varchar20
CONTAINER_ID varchar10
DATE_SHIPMENT date
VEHICLE_NUMBER varchar10
DRIVER varchar20
DETAIL_ORDER_SHIPMENT DETAIL_ORDER_SHIPMENT_ID
varchar20 PRODUCT_ID
integer CUSTOMER_ID
integer QUANTITY_SHIPMENT
integer TOTAL_WEIGHT
integer TOTAL_VOLUME
integer STATUS_ORDER
numeric1 ORDER_SHIPMENT_ID
varchar20 CONTAINER
CONTAINER_ID varchar10
CONTAINER_TYPE varchar10
CAPACITY_CONTAINER integer
WEIGHT_CONTAINER integer
DETAIL_PUTAWAY DETAIL_PUTAWAY_ID
integer PRODUCT_ID
integer LOCATION_ID
varchar2 PUTAWAY_ID
varchar15 PALLET_ID
varchar15 INVENTORY
INVENTORY_ID varchar15
LOCATION_ID varchar2
PRODUCT_ID integer
COUNTRY_ID integer
CUSTOMER_ID integer
DETAIL_PUTAWAY_ID integer
34
3.3.5. Struktur Tabel