• Statechart Class Well
Gambar 4.33 Statechart Well
EVENT ATTRIBUTE
Production Production_per_Day
Develop Start_Develop_Date, End_Develop_Date
Drill Well_Type Dry_Hole Well_Status
• Statechart Class Seismic
Gambar 4.34 Statechart Seismic
EVENT ATTRIBUTE
Draft Seis_Line, Seismic_Year, Seismic_Vint,
Seismic_Serie, Seismic_Status, Seismic_Image
• Statechart Class Survey Seismic
Gambar 4.35 State Chart Survey Seismic
EVENT ATTRIBUTE
Survey_Start, Survey_End Situation, Main_Terrain, Survey_Name, Survey_Status, Survey_Method,
Survey_Purpose, Survey_Seismic_Image, Seis_Type
Start_Shot Start_Shot_Date, Shot_Point
End_Shot End_Shot_Date, Shot_Length
Detect_Seis_Line Designated_Number, Center_Lat, Center_Long
4.1.7 Revised Class Diagram
4.1.7 Object Definition Language Class Block {
( extent Block
Key Block_Name ) Attribute varchar Block_Name ; Attribute varchar Operator ; Attribute varchar Production ; Attribute date Start_Contract_Date ; Attribute date End_Contract_Date ; Attribute date Start_Explore_Date ; Attribute date End_Explore_Date ; Attribute varchar Prospect_Status ; Attribute blob Block_Image ;
Relationship Area consists_of inverse Area :: represented_by ;
Relationship set<Seismic> represented_by Inverse Seismic :: part of ;
Void Start_Contract ( ) ; Void End_Contract ( ); Void Start_Explore ( ) ; Void End_Explore ( ) ; };
Class Seismic {
( extent Seismic
Key Seismic_ID )
Attribute varchar Seismic_Line ; Attribute date Seismic_Year ; Attribute varchar Seismic_Vint ; Attribute varchar Seismic_Serie ; Attribute varchar Seismic_Status ; Attribute blob Seismic_Image ;
Attribute blob Seismic_Interpretation_Image ; Relationship Block part_of inverse
Block :: represented_by ;
Relationship set<Survey_Seismic> consist_of inverse Inverse Survey_Seismic :: include ;
Void Draft ( ) ;
Void Interpretation ( ); Void View ( );
Class Survey_Seismic { ( extent Survey_Seismic
Key Survey_Name ) Attribute varchar Provience ; Attribute varchar Survey_Name ; Attribute varchar Designated_Number ; Attribute varchar Situation ;
Attribute varchar Main_Terrain ; Attribute date Start_Shot_Date ; Attribute date End_Shot_Date ; Attribute varchar Survey_Status ; Attribute varchar Survey_Method ; Attribute varchar Survey_Pupose ; Attribute varchar Shot_Length ; Attribute varchar Shot_Point ; Attribute varchar Seis_Type ; Attribute varchar Center_Lat ; Attribute varchar Center_Long ;
Attribute blob Survey_Seismic_Image ; Relationship Seismic include_of inverse
Seismic :: consists_of ; Void Detect_Seis_Line ( ) ; Void Start_Shot ( ) ;
Void Survey_Start ( ) ; Void Survey_End ( ) ; }; Class Area { ( extent Area Key Area_Name ) Attribute varchar Area_Name ; Attribute varchar Well_Total ; Attribute date Start_Drilling_Date ; Attribute date End_Drilling_Date ; Attribute varchar Drilling_Status ; Attribute varchar Depth_Measure ; Attribute blob Area_Image ;
Relationship set<Block> represented_by ; Inverse Block :: consists_of ;
Relationship set<Coordinate> represented_by ; Inverse Coordinate :: include_of ; Relationship Well consists_of inverse
Well :: represented_by ; Void Start_Drill ( ) ;
Void End_Drill ( ) ; };
Class Coordinate {
( extent Coordinate ) Attribute varchar Latitude_Dec_Degs ; Attribute varchar Longitude_Dec_Degs ; Attribute varchar Latitude ;
Attribute varchar Longitude ; Attribute varchar Coodinate_Qual ; Relationship Area include_of inverse
Area :: represented_by ; Void Determine_Coordinate ( ) ; }; Class Well { ( extent Well Key Well_ID )
Attribute varchar Well_ID ; Attribute varchar Well_Type ; Attribute varchar Well_Status ;
Attribute varchar Production_per_Day ; Attribute date Start_Develop_Date ; Attribute date End_Develop_Date ; Relationship set<Area> represented_by ;
Relationship set<Contractor_Rig> represented_by ; Inverse Contractor_Rig :: part_of ;
Relationship set<Drilling_History> represented_by ; Inverse Area :: include_of ;
Void Drill ( ) ; Void Production ( ) ; Void Develop ( ) ; Void Dry_Hole ( ) ; }; Class Drilling_History { ( extent Drilling_History ) Attriute date Event_Date ; Attribute varchar Qual ;
Attribute varchar Event_Type ; Attribute varchar Activity_Type ; Attribute varchar Mud_Depth ; Relationship Well include inverse
Well :: represented_by ; };
Class Contractor_Rig { ( extent Contractor_Rig
Key Contractor_Name ) Attribute varchar Contractor_Name ; Attribute varchar Rig_Name ;
Attribute varchar Rig_Category ; Attribute varchar Location ; Attribute date Start_Rent_Date ; Attribute date End_Rent_Date ; Relationship Well part_of inverse
Well :: represented_by ; Void Start_Rent ( ) ;
4.1.8 Persistence Database Table Seismic Seismic ID Seismic Line Seismic Year SeismicVint Seismic Serie Seismic Status Seismic Image Seismic Interpretation Image Tabel 4.9 Seismic
Table Survey Seismic Survey ID Provience Survey Name Designated Number Situation Main Terrain Start Shot Date End Shot Date Survey Status Survey Method Survey Purpose Shot Length Shot Point Seis Type Center Lat Center Long Survey Seismic Image
Tabel 4.10 Survey Seismic
Seismic_ID dan Survey_ID adalah merupakan transformasi agregasi antara class seismic dan survey_seismic.
Seismic_ID Survey_ID
Table Block Block ID Block Name Operator Start Contract Date End Contract Date Start Explore Date End Explore Date Prospect Status Block Image Tabel 4.12 Block Table Area Area ID Area Name
Well Total Start Drilling Date End Drilling Date Drilling Status Depth Measure Area Image Tabel 4.13 Area Table Well
Well ID Well Type Well Status Production per Day Start Develop Date End Develop Date Tabel 4.14 Well
Table Drilling History Drilling History
ID
Qual Event Type Activity Type Mud Depth
Tabel 4.15 Drilling History
Table Coordinate
Coordinate ID Latitude Dec Degs
Longitude Dec Degs
Latitude Longitude Coordinate Qual
Tabel 4.16 Coordinate
Block ID, Area ID, Well ID, Drilling History ID, dan Coordinate Id adalah merupakan transformasi agregasi antara class Block, Area, Well, Drilling History, dan Coordinate
Block ID Area ID Well ID Drilling History ID
Coordinate ID
Table Contractor Rig Contractor
Rig ID
Contractor Name
Rig Name Rig Category
Location Start Rent Date
End Rent Date
4.2 User Interface (UI)
• UI Block
Gambar 4.37 UI Memilih Block
UI Block :
Pengguna dapat memilih block yang diinginkan dari beberapa pilihan menu block yang ada.
• UI Block
UI Block :
Pengguna dapat melihat peta dan informasi block operasi eksplorasi perusahaan. Dari
block tersebut pengguna dapat memilih area operasi eksplorasi secara lebih terperinci
untuk mendapatkan informasi mengenai area eksplorasi perusahaan tersebut dan garis
seismic yang ada di block tersebut, dengan cara mengklik nama dari area dan garis dari seismic tersebut.
• UI Area
Gambar 4.39 UI Area
UI Area :
Pengguna dapat melihat peta dan informasi area eksplorasi. Lalu setelah memasuki tampilan area, pengguna dapat melihat informasi mengenai titik koordinat, garis seismic dan sumur yang ada didalam area tersebut, dengan cara megklik titik dari sumur dan garis dari seismic tersebut.
• UI Coordinate
Gambar 4.40 UI Coordinate
UI Coordinate :
Berisi informasi mengenai titik koordinat suatu area.
• UI Well
Gambar 4.41 UI Well UI Well :
• UI Drilling History
Gambar 4.42 UI Drilling History
UI Drilling History :
Berisi informasi mengenai drilling history dari suatu sumur.
• UI Contractor Rig
Gambar 4.43 UI Contractor Rig
UI Contractor Rig :
Berisi informasi mengenai contractor rig yang digunakan perusahaan untuk membor suatu sumur.
• UI Seismic
Gambar 4.44 UI Seismic
Gambar 4.46 UI Seismic Interpretation Image
UI Seismic :
Berisi informasi mengenai data seismic dan gambar seismic hasil proses dari survey
seismic dan gambar seismic hasil interpretasi. Dari UI ini pengguna juga dapat
• UI Survey Seismic
Gambar 4.47 UI Survey Seismic
UI Survey Seismic :
Berisi informasi mengenai data dan gambar hasil survey seismic.
• UI Memasukan Data
Gambar 4.49 UI Memasukan Data Block
Gambar 4.51 UI Memasukan Data Well
Gambar 4.52 UI Memasukan Data Drilling History
Gambar 4.54 UI Memasukan Data Contractor Rig
Gambar 4.56 UI Memasukan Data Survey Seismic
UI Menasukan Data Block, Area, Coordinate, Well, Drilling History, Contractor Rig,
Seismic dan Survey Seismic :
4.3 Rencana Implementasi
4.3.1 Spesifikasi Perangkat Keras
Spesifikasi perangkat keras minimum yang diperlukan dalam
implementasi aplikasi basis data pada Kondur Petroleum SA adalah sebagai berikut : • Pada Server :
o Processor : Pentium IV Hyper Threading 4GHz o Memory : 2 GB
o Hard Disk : 100 Tera Byte o Monitor : SVGA 15”
• Pada Client :
o Processor : Pentium IV 2GHz o Memory : 512 MB
o Hard Disk : 60 GB
o Monitor : Dual Monitor WUXGA 19”
4.3.4 Spesifikasi Perangkat Lunak
Rancangan aplikasi serta basis data akan digunakan pada bagian-bagian yang terlibat langsung dalam pengolahan informasi yang masuk di Kondur Petroleum SA, tepatnya pada bagian yang menangani kegiatan eksplorasi perusahaan.
Sedangkan perangkat lunak yang akan dipergunakan adalah : 1. Object Store
2. Visual C++ 6
4. NeuraLog 5. NeuraMap 6. NeuraSection
4.3.5 Jaringan Komputer