Perbedaan sistem pembukuan manual dan komputerisasi

Perbedaan Sistem Pembukuan Manual Dengan Sistem Pembukuan Komputerisasi

October 4, 2012 at 4:48 pmadminNo comments

A. Secara Manual tanpa Sistem Komputerisasi
(Menggunakan pensil atau software spreadsheet seperti Lotus 123 atau Ms Excel)

Pada pembukuan manual Anda harus mencatat banyak hal secara manual pada beberapa kertas kerja/buku, dan menyusun jurnal double entry yang cukup membingungkan bagi mereka yang tidak mengerti akuntansi, serta sangat memakan waktu dan beresiko apabila tidak teliti.

Berikut Penjelasan bagaimana proses pembukuan manual terjadi

3. Membuat Jurnal Double Entry

Dari transaksi-transaksi yang sudah ada, apakah itu penjualan, pembelian, dan lainnya harus dibuatkan transaksi jurnal double entry (debet – kredit).

Si pembuat jurnal transaksi harus mengetahui nomor rekening setiap transaksi, bila tidak dihafal maka melihat pada tabel

Misalkan penjualan barang A, akan dicatat pada rekenin nomor 41100, sebagai penjualan barang A, kemudian dicatat pula pada rekening piutang usaha misalkan pada rekening 14100.

Untuk transaksi yang cukup kompleks proses pembuatan jurnal ini akan sangat sulit, misalkan suatu penjualan melibatkan discount, pajak, uang muka dan biaya pengiriman.

2. Menghitung Harga Pokok dan mencatatnya pada kartu stok barang.

Untuk penjualan barang dagangan, proses pembuatan jurnal juga menjadi rumit, karena harus mengetahui rekening apa untuk barang tersebut, dan harus menghitung harga pokok barang manual – satu persatu dari kartu stok tiap barang, apakah menggunakan metode FIFO, LIFO atau Rata-rata.

Karena rumitnya perhitungan harga pokok dan pembuatan jurnya, maka banyak perusahaan menerapkan sistem stok opname di akhir minggu atau akhir bulan.

Dengan cara ini laba rugi perusahaan baru diketahui pada akhir minggu atau akhir bulan, tidak setiap saat.

3. Mencatat Kartu Piutang dan Hutang Usaha

Setiap terjadi penjualan harus dicatat pada kartu piutang usaha, dan tiap terjadi pembelian juga dicatat pada kartu hutang.

Tujuan pencatatan ini adalah mengetahui sisa hutang/piutang yg masih harus dibayar dan kapan waktu pembayarannya.

4. Menghitung penyusutan asset

Setiap harta atau asset perusahaan dicatat pada buku tersendiri. Setiap bulan akan dihitung beban penyusutan dan beban amortisasinya. Selanjutnya dibuat jurnal transaksi penyusutan.

5. Menyusun Buku Besar

Dari transaksi-transaksi jurnal yang telah dibuat, disusun dan dikelompokkan berdasarkan nomor rekeningnya masing-masin, ini disebut Buku Besar.

Contoh : Buku Besar Piutang Usaha
1/2/2005 Penjualan PT ABC          Rp 1.000.000,-
3/2/2005 Penjualan PT DKL          Rp 5.000.000,-
5/2/2005 Penjualan PT ABC          Rp 2.000.000,-
2/2/2005 Pembayaran PT ABC     Rp    500.000,-
—————————————————————————
Total Piutang Usaha                           Rp 8.500.000,-

6. Membuat Worksheet atau Neraca Lajur

Total nilai per masing-masin buku besar seluruh rekening yang ada dikumpulkan dalam worksheet

Kemudian disusun pada kolom-kolom apakah pada posisi debet atau kredit, dicari saldo awalnya dan dihitung saldo akhirnya.

7. Menyusun Laporan Necara dan Laba Rugi

Dari Worksheet atau neraca lajur tersebut dapat disusun neraca percobaan, atau langsung dibuat laporan neraca dan laporan laba rugi.

Laporan neraca dan laba rugi ditampilkan dalam bentuk yang terstruktur sesuai klasifikasi per masing-masing rekening.

8. Menyusun Laporan Aliran Kas

Pembuatan laporan aliran kas jauh lebih rumit daripada laporan Neraca dan Laba Rugi. Dimana harus diketahui necara bulan sebelumnya, menghitung perubahaannya, menghitung nilai penyusutan dan menyusunnya menjadi laporan sesuai aturan akuntansi yang berlaku.

9. Membuat analisa rasio dan grafik-grafik

Dari laporan keuangan yang sudah dibuat dapat dihitung rasio-rasio bisnis berdasarkan formula-formula yang baku. Serta dibuat pula dalam format grafik untuk memudahkan manajemen dalam menganalisa kinerja perusahaan.

Kebayangkan….. kalo semua proses ini dilakukan secara manual??

B. Menggunakan Sistem Komputerisasi

ada perbedaan proses akuntansi yang dikomputerisasi dgn yang manual. Laporan seperti daftar piutang, daftar utang dan laporan interim dapat disusun dan dicetak setiap saat dengan segera. Kalau data penyesuaian telah dimasukkan dalam komputer maka laporan keuangan akhir dapat segeradicetak. Oleh karena itu, dalam sistem komputer tidak diperlukan lagi kertas kerja seperti
pada sistem manual. Perlu dicatat bahwa konsep pelaporan keuangan tidak dapat diganti
oleh komputer, yang dapat diganti dengan komputer adalah proses pengolahan datanya.

Kalau dibandingkan dengan sistem manual, sistem komputerisasian memang jelas
mempunyai keunggulan (benefit) khususnya dalam hal kecepatan (speed), ketelitian
(accuracy) dan kapasitas (capacity) pemrosesan.
Kecepatan komputer dapat diandalkan karena komputer mengerjakan suatu perintah
dalam hitungan mikrodetik (microsecond). Perkembangan chip terakhir telah memungkinkan
kecepatan dalam seperbilliun detik (nanosecond) atau bahkan dalam sepertrilliun detik
(picosecond). Dengan kecepatan ini suatu transaksi dapat diproses dalam seketika.
Ketelitian jelas dapat diandalkan karena setelah data disiapkan dengan benar
komputer akan memroses tanpa campur tangan manusia lagi dan kalau komputer sudah
diprogram dengan benar kemungkinan kesalahan perhitungan dan klasifikasi menjadi kecil.
Itulah sebabnya sebelum suatu komputer dan programnya digunakan, suatu percobaan (trial
run) dengan data percobaan perlu dilakukan untuk memverifikasi program. Dalam sistem
manual, karena tiap langkah dikerjakan oleh manusia, kemungkinan kesalahan menjadi lebih
besar.

Kapasitas untuk menyimpan, mencatat dan mencetak data menjadi sangat besarkarena data disimpan dalam bentuk elektromagnetik. Oleh karena itu, di samping laporan utama komputer dapat diprogram untuk menghasilkan laporan-laporan tambahan lainnya termasuk rincian-rincian yang diperlukan.

Namun demikian, karena semua data tidak terekam dalam bentuk yang dapat dibaca oleh manusia, kegagalan komputer (computer failure) dapat merunyamkan perusahaan karena data dapat rusak atau hilang atau tidak dapat dibaca kembali. Itulah sebabnya diperlukan suatu mekanisme backup. Manipulasi dengan komputer dan kejahatan dengan komputer (computer crime) juga merupakan ancaman bagi perusahaan yang mengandalkan operasi dan pencatatan keuangannya dengan komputer

Bila dipelajari sifatnya, proses mulai dari penjurnalan sampai ke pelaporan sebenarnya
bersifat matematis (karena hubungan buku besar dapat ditunjukkan dalam persamaan
akuntansi, sistematis (karena urutan mengerjakannya jelas) dan logis (karena unsur
pertimbangan atau judgement tidak terlibat lagi). Dengan kata lain, proses tersebut sifatnya
adalah penambahan, pembandingan, penyortiran, pereklasifikasian, dan peringkasan dengan
cara tertentu yang sudah jelas atau pasti. Pekerjaan atau tugas yang demikian biasanya
menjadi objek komputerisasi.
Dengan sistem komputer seperti di atas maka langkah yang paling kritis adalah
langkah analisis transaksi karena kalau langkah ini salah, hasil pengolahan data oleh
komputer juga ikut salah.”
jadi, semua proses akuntansi dapat di komputerisasi.

Walaupun dengan penggunaan komputer kegiatan-kegiatan dalam siklus akuntansi
manjadi tidak ada lagi, konsep yang dipelajari dalam sistem akuntansi manual tetap
diperlukan karena apa yang dikerjakan oleh komputer tetap mengikuti konsep yang
digunakan dalam sistem akuntansi manual.
karena akan ada pelaporan yang disusun dan dicetak segera.

Secara garis besar proses akuntansi dengan sistem komputerisasi sbb :

1. Input transaksi pada formulir yang disediakan.
2. Seluruh laporan keuangan dan  Analisa Bisnis untuk menampilkan grafik dan analisa keuangan.

Seluruh proses pembuatan jurnal double entry, pencatatan kartu hutang dan piutang usaha, mencatat pemakaian barang dan menghitung harga pokok barang, serta perhitungan penyusutan dan pembuatan laporan, grafik dan analisa keuangan dilakukan secara otomatis.

Seluruh data yang telah diisi akan disimpan dan dapat digunakan kembali pada transaksi – transaksi yang lain.Seperti data pelanggan, pemasok dan data barang, cukup dibuat satu kali selanjutnya tinggal digunakan,begitu juga dengan laporan yang diinginkan,seluruh laporan dapat disajikan dikarenakansemua datasudah ke rekam dengan baik.Dengan cara ini histori transaksi pelanggan, pemasok dan barang persediaan dapat dianalisa dengan baik.

Bila dipelajari sifatnya, proses mulai dari penjurnalan sampai ke pelaporan sebenarnya
bersifat matematis (karena hubungan buku besar dapat ditunjukkan dalam persamaan
akuntansi, sistematis (karena urutan mengerjakannya jelas) dan logis (karena unsur
pertimbangan atau judgement tidak terlibat lagi). Dengan kata lain, proses tersebut sifatnya
adalah penambahan, pembandingan, penyortiran, pereklasifikasian, dan peringkasan dengan
cara tertentu yang sudah jelas atau pasti. Pekerjaan atau tugas yang demikian biasanya
menjadi objek komputerisasi.
Dengan sistem komputer seperti di atas maka hal yang paling penting dilakukan adalah
analisis transaksi karena kalau langkah ini salah, hasil pengolahan data oleh
komputer juga ikut salah,disinilah peran penting seorang akuntan
jadi, semua proses akuntansi dapat di komputerisasi sehingga dengan penggunaan komputer kegiatan-kegiatan dalam siklus akuntansi yang dilakukan secara manual manjadi tidak ada lagi, namun konsep yang dipelajari dalam sistem akuntansi manual tetap diperlukan karena apa yang dikerjakan oleh komputer tetap mengikuti konsep yang digunakan dalam sistem akuntansi manual karena akan ada pelaporan yang disusun dan dicetak segera…

Sumber : www.zahiraccounting.com , Atma Jaya Foundation

13 technology trend di tahun 2013

13 Top Tech Trends for 2013


The IEEE Computer Society, a membership organization for technology leaders, has peered into their crystal ball, so to speak, to foresee what the top tech trends of 2013 will be.

Considering IEEE members include professors, researchers, software engineers, IT professionals, employers, and students, it's a good group to look to for unbiased and sound opinions. Their predictions can prove helpful to businesses that are trying to plan their next IT expenditures and the overall direction for their company, and for consumers looking for the next great thing.

"The promise for the coming years is not just technology," said incoming IEEE Computer Society President David Alan Grier in a press release. "But technology and data -- how we get data from the right sources and get it to the right people in the right forms. That is the big issue that engages many of our members."

Below are just some of the technological advancements that the IEEE predicts for 2013. You can see an entire list of their predictions in the society's Top Trends for 2013 report.

What follows is a quick executive summary of the major advances that IEEE Computer Society experts forecast for 2013. Key terms have links for quick references to definitions for unfamiliar readers.

1. The Internet of Things will change how consumers and enterprises use technology: Promising to be the most disruptive technology since the World Wide Web, the Internet of Things is expected to result in up to 100 billion Internet-connected objects by 2020.

2. Researchers will develop new approaches to cybersecurity: With enterprises, governments, and consumers all depending on digital connections to function, new approaches to cybersecurity are becoming even more crucial.

3. Visualization will help solve challenges of big-data: In this data-driven era, the ability to make timely decisions based on data is crucial. As all fields confront the big-data problem in 2013, visualization will become an increasingly effective tool for presenting information and driving complex analyses.

4. Enterprises will deploy hybrid clouds, and consumers will embrace personal clouds: With the growth of services exceeding predictions, cloud computing will gravitate even further into the enterprise with hybrid clouds. Consumers, meanwhile, will embrace personal clouds.

5. Mobile computing will meet the cloud: In 2013, expect to see further intersections between mobile and cloud computing. The deployment of 3G and 4G networks, the rapid adoption of feature-rich smartphones, and the growing integration of computation into consumer products such as cars and home appliances, have brought these technologies into the mainstream.

6. Concern will increase over Internet censorship and control: Invented as a way to spread innovation and new ideas, the Internet has become a battleground for technical, social, and political control. In 2013, expect to see these battles continuing, in the form of Internet filtering versus circumvention; surveillance versus anonymization; denial-of-service attacks and intrusion attempts versus protection mechanisms; and, on- and offline persecution and defense of online activists.

7. Public interactive displays will become more common: With their prominent visibility and interactive features, interactive public displays offer new opportunities to enrich user experiences in public facilities such as museums, libraries, public plazas, or architectural facades.

8. The need will grow for next-generation mobile computing: enterprises, consumers, and government all rely on mobile computing for everything from disaster response and business continuity to simple communication. Yet, many of these systems operate within degraded network, power, or computing environments. Researchers in 2013 will tackle the challenge of maintaining quality-of-service in mobile computing environments.

9. New multimedia applications will emerge for 3D printing: From architecture to entertainment, manufacturing to security, 3D printing and multimedia has become increasingly incorporated into real-world applications. The extraction of 3D information has been studied in the field of computer vision for more than three decades, but remains challenging.

10. New approaches to securing safety-critical systems will emerge: With driverless cars, networked patient care, and personal apps on the horizon, and the advent of new control systems for air traffic, nuclear power plants, and military protection, researchers in 2013 will increasingly turn their attention to ensuring the security of safety-critical systems.

11. Reliability will become the biggest design challenge: Over the past decade, power, performance, and cost have been the biggest design priorities. But in the coming era, designers will turn their attention to creating robust and reliable systems. Without innovations in the areas of microprocessor and software reliability, researchers warn, future systems may face continuous failure.

12. Haptics will become more useful for rehabilitation: The science and technology of haptics has great potential to affect the outcomes of rehabilitation, as well as the adoption of advanced prosthetic and orthotic devices. Researchers are making great strides in using haptics to aid stroke and spinal-injury patients, and in creating more effective devices to enable mobility for lower- and upper-extremity amputees.

13. Use of shared memory will advance for multicore processing: Multicore processing has the potential to vastly increase computing speeds, but researchers are still exploring how to best allow for shared memory on a single node. This challenge must be resolved in order to move into a future where each node could hold up to 1,000 cores.

So, what do you think of these predictions? Do you see them coming, too? How will these technologies affect your business?

build-access-manage at dayaciptamandiri.com

Di belakangku ada wanita hebat

Pepatah 'dibalik pria hebat, ada wanita dashyat' sepertinya hampir selalu benar.

Mengenalnya semasa sama-sama menjadi GSM di Bektim sungguh anugrah.

Semangat dan keenerjikannya membuat siapa pun yang didekatnya merasa bersemangat.

Hangat diskusi dan canda berbobot melengkapi pribadinya yang tegas dan serius.

Kepasrahan dan penyerahan dirinya untuk keluarga tak diragukan lagi.

Telinga yang lebar, hidung besarnya menunjukkan kualitas pribadi totalnya.

Dukungan dan kesabarannya menjalani masa masa sulit kami menyemangati saya.

Itulah dia, istri tercantikku dan ibu anak-anakku.
build-access-manage at dayaciptamandiri.com

Gunakan Evernote untuk Project Management

Use Evernote for your information intensive IT projects

By Will Kelly

November 22, 2012, 5:46 AM PST

Takeaway: Will Kelly explains how to use Evernote for your IT projects natively or by integrating the app with Nozbe or Refinder.

Bring Your Own Device (BYOD) and Bring Your Own Cloud (BYOC) is helping the popular note-taking solution Evernote get more attention inside corporations. Some say Evernote isn’t for project managers, but I think Evernote is useful for projects and teams that are swimming in information. The app can also add a level of secure information sharing to such projects. Here are some ways you can use Evernote natively and how to integrate it with Nozbe and Refinder.

Go native with Evernote

Collaborative note-taking

I am not a fan of taking minutes during meetings. The task usually falls to one person, and the minutes are usually filed somewhere and never referred to again.

With the advent of Evernote Business (which is due to launch in December 2012) or a more relaxed environment for personal cloud apps, project managers and their teams can take notes in Evernote that deal with their segments of the meeting. Team members can then share their notes with the rest of the team at the end of the project meeting.

Share notes and notebooks

Sharing notes and notebooks is a way for sharing project information securely. It also does away with the need for paper notes and helps centralize project notes and your brainstorming.

To share notes, follow these steps:

1. Click Send. A drop-down menu appears.
2. In the drop-down menu that appears, click one of the following:
   a. Email to email a link to the selected note to a recipient. Optionally, you can add a short note.b. Link to create a link to the note. You can then cut and paste the link into an email or instant message.

If you establish a notebook for a project, you might want to share the entire notebook. Here’s how:

1. Right-click the notebook you want to share.
2. In the drop-down list that appears, select Share Notebook.
3. In the Sharing dialog box that appears (Figure A), perform one of these options:

a. Click Invite Individuals. Fill out the email address and permissions you want to grant an individual. Click Invite.

b. Click Create A Public Link. The public URL of the selected notebook appears. Click Invite Individuals. Enter the email addresses of the people you want to invite. Set access permissions in the Individuals who join can drop-down list. Click Invite.

Figure A

Sharing dialog box in Evernote. (Click the image to enlarge.)

Create task lists

You can create task lists in Evernote via the Web interface or through the Mac and Windows applications. Follow these steps to create a task list:

1. Open Evernote.
2. Click New Note.
3. Click the Insert To-do Checkbox.

Evernote creates a bare-bones checklist; there is no facility to put in dates, and Evernote doesn’t even cross out a completed task. You can share task lists just as you can any other note.

Integrate Evernote with third-party apps

Evernote integration with Nozbe

Nozbe is perhaps best known as a Getting Things Done (GTD) organizational system, though it is also a capable task management system for individuals and teams available in the cloud, PC desktop, or iOS app. I’ve used Nozbe to manage small projects, and the option to include Evernote notes in my Nozbe projects has given me a centralized view into my project research.

To integrate Evernote with Nozbe, follow these steps:

1. Create a Nozbe project.
2. Under More Content, click Evernote Notes.
3. Click Connect Nozbe to Evernote.
4. When the Allow Access: Nozbe page appears, click Authorize.

From within Evernote, you need to tag any project-related notes with the name of your Nozbe project in order for the Evernote notes to show up in Nozbe. Figure B shows Evernote notes as they appear in the Nozbe cloud app.

Figure B

Evernote notes in Nozbe. (Click the image to enlarge.)

Evernote integration with Refinder

Refinder is cloud-based project management application and a recent Evernote Devcup winner. Its integration with Evernote fits into where I see Evernote integration into a cloud-based application. In Refinder, you can add entire Evernote notebooks and add single notes by tags.

Here’s how to add Evernote notebooks to a Refinder collection:

1. Create a Collection.
2. Connect Evernote.
3. Click Start Authentication.
4. Click Authorize.
5. Select the Notebook you want to import.
6. Select the tags you want to import.
7. Click Save.
8. Click Continue.

Figure C shows Evernote notes as seen in a Refinder collection.

Figure C

An example of how you can access Evernote notes from Refinder. (Click the image to enlarge.)

Team members can add: comments and tags to the information; their own Evernote accounts to Refinder; and Dropbox folders, Google Drive, and Twitter feeds.

Evernote as project management tool

Evernote’s aggressive client app updates, impending release of Evernote Business, and third-party integrations are helping it gain more of a foothold inside corporate enterprises and increasing its availability to project managers. You should see whether Evernote can help you manage your IT projects.

Apa saja isi tweet yang wajib disebarkan para entrepreneur?

10 Tweet Ampuh bagi Pebisnis Pemula
Apa saja isi tweet yang wajib disebarkan para entrepreneur?



Entrepreneur harus bisa memanfaatkan teknologi Twitter untuk mendongkrak bisnisnya

Syahid Latif | Minggu, 25 November 2012, 06:55 WIB

VIVAnews - Di tengah gempuran jejaring media sosial yang makin kuat, tak ada satu pihak pun di dunia yang bisa lepas dari pengaruhnya. Tak terkecuali para pelaku bisnis, khususnya mereka yang tengah membangun bisnis, yang ingin mengembangkan usahanya.

Salah satu media sosial yang tak boleh dilupakan adalah Twitter. Entrepreneur harus mulai berpikir memiliki akun pribadi guna menancapkan citra produknya. Fans dan follower (pengikut) seringkali ingin terikat dengan orang yang berada di balik sebuah merek produk.

Kegiatan memberikan informasi dan prospek pada gaya hidup entrepreneur bisa membantu mereka menjalin hubungan yang lebih dalam, melampaui capaian yang bisa dibangun lewat sebuah merek.

Dikutip dari laman CNBC, berikut adalah 10 informasi yang bisa dituangkan entrepreneur dalam akun Twitter:

1. Informasi pribadi
Berbagilah informasi besar mengenai kehidupan pribadi seperti liburan, pernikahan, dan kelahiran yang biasanya Anda sebarkan pada teman terdekat. Cara ini bisa membantu follower merasa menjadi bagian dari kehidupan Anda.

2. Kesalahan dan hikmah
Berbagi kesalahan dan hikmah yang dipetik adalah ciri-ciri kemajuan bukan kelemahan. Cobalah membuat tweet "Apa yang saya pelajari pekan ini" dan lihat bagaimana respons para pengikut Anda.

3. Jawablah pertanyaan
Jika seorang pengikut mengajukan pertanyaan, jawab dan sebarkanlah. Cara ini bisa membuka jalan untuk mengembangkan fasilitas FAQ (frequented asked question) dalam industri Anda.

4. Link artikel
Kunci dari cara menyebarkan link sebuah artikel adalah memasukkan komentar Anda di dalamnya. Biarkan pengikut Anda tahu mengapa Anda suka atau tidak suka artikel tersebut.

5. Gambar atau hal aneh
Jika Anda melihat sesuatu yang menarik perhatian, bisa jadi hal itu juga menjadi perhatian orang lain. Jadi, kenapa tak mencoba menyebarkannya? Termasuk dalam cara ini adalah penyebaran gambar produk yang mengesankan, makanan, maupun arsitek.

6. Kata-kata bijak dari artikel
Ketika Anda menemukan kata-kata bijak dalam sebuah buku yang tengah dibaca, sebarkanlah. Cara ini tak hanya menunjukkan Anda termasuk kalangan yang doyan membaca, tapi juga pribadi yang memiliki nilai-nilai kebajikan. Kedua hal ini yang bisa membantu Anda membangun reputasi.

7. Iklan menarik
Ketika sebuah papan reklame atau apa pun jenis iklan menarik perhatian Anda, potret dan sebarkanlah. Setiap orang akan mendapat keuntungan dari cara pemasaran yang cerdas.

8. Belanjaan menarik
Berbagi informasi mengenai belanjaan seperti musik, video games, maupun peralatan olahraga bisa menggiring munculnya komentar dan percakapan dengan pihak lain. 

9. Berbagi kata bijak dari dunia di luar bisnis
Kata-kata bijak dari legenda olahraga, pemimpin militer, dan artis bisa membantu mengajarkan ilmu kepemimpinan dan inovasi. Hal inilah yang penting untuk kesuksesan bisnis Anda

10. Pekerjaan Anda
Link terbaik yang bisa Anda sebarkan kepada pengikut adalah link yang terkait pekerjaan pribadi Anda. Namun, jangan batasi pada pekerjaan profesionalitas saya. Jika Anda memiliki hobi dan minat dari sesuatu yang kreatif, sebarkanlah. (art)
build-access-manage at dayaciptamandiri.com

Memasuki tahun ke 10 dalam berbisnis di bidang IT di Indonesia, suka dan duka silih berganti. Kerumitan seperti biasanya selalu hadir dalam setiap solusi yang diberikan kepada konsumen. Di lain pihak, keberpihakan kepada layanan konsumen semakin baik setiap tahun.

Hal yang menarik untuk diamati adalah bagaimana membuat bisnis yang kita jalani dapat bertahan demikian lama dan terus memberikan keuntungan yang maksimal.

Di mulai awal kami berdiri, layanan dan kekuatan solusi berdasarkan hardware mendominasi solusi yang diberikan. Tapi dunia berubah demikian cepat. Seiring semakin baiknya infrastruktur jaringan dan jaringan distribusi IT Indonesia, maka infrastruktur software semakin banyak diperdagangkan dan lebih memberikan keuntungan.

Sekarang coba kita amati, apa yang dimaksud dengan 'infrastructure software'

Menurut Gartner, adalah

Infrastructure Software

This segment includes AD and application integration and middleware (AIM) software, information management software, storage management software, IT operations management and security software, and other infrastructure software.

 Application development and AIM software services — The AD software market comprises tools that represent each phase of the software development life cycle (application life cycle management [ALM], design, construction, automated software quality and other AD software). The Application Infrastructure and Middleware market segment includes business process management (BPM)-enabling technologies, integration-enabling middleware, platform middleware, portals and Web 2.0 infrastructure, and various additional products grouped together as "other AIM." Integration-enabling middleware is software that enables independently designed applications, software components or services to work together, by supporting data consistency, composite application and multi-step process styles of integration.

 Information management software services — This software market is defined by Data Management and Integration software and includes Data Integration Tools, Data Quality Tools and Database Management Systems. The discipline of data integration comprises the practices, architectural techniques and tools for achieving the consistent access and delivery of data across the spectrum of data subject areas and data structure types in the enterprise to meet the data consumption requirements of all applications and business processes. Traditionally aligned with cleansing of customer data (names and addresses) in support of CRM-related activities, the tools have expanded well beyond such capabilities, and forward-thinking organizations are recognizing the relevance of these tools in other data domains. A database management system (DBMS) is a product used for the storage and organization of data that typically has defined formats and structures. DBMSs are categorized by their basic structures and, to some extent, by their use or deployment.

 Storage management software services — The storage management software market includes all software products that are sold as value-added options to run on a server, storage network device or storage device to aid in managing the device or managing and protecting the data. Storage management software represents all the tools needed to manage capacity, performance and availability of data stored on disks, tapes and optical devices, as well as the networking devices that the data may pass through.

 IT operations management and security software services — IT operations management (ITOM) software is intended to represent all the tools needed to manage the provisioning, capacity, performance and availability of the computing, networking and application environment. Security software is included to control and monitor access to internal and external IT resources.

 Other infrastructure software services — Other infrastructure software includes, but is not limited to, clustering and remote control software, directory servers, OS tools, Java license fees, mainframe infrastructure, and mobile and wireless infrastructure, as well as other infrastructure software.

 Operating system software — An OS is software that, after being loaded into the computer by an initial boot program, manages a computer's resources, controlling the flow of information into and from a main processor. OSs perform complex tasks, such as memory management, control of displays and other input/output peripheral devices, networking and file management, and other resource allocation functions between software and system components. The OS provides the foundation on which applications, middleware and other infrastructure components function. OS usually provides user interfaces, such as command-line shell and GUI, for interaction between user and computer. The four most common subcategories of operating systems include Linux, Unix, Windows and mainframe OS.

OK, clear now. Inilah yang selama ini semakin banyak dijual dengan beragam nama , bentuk dan teknologi. Fokus kami selama ini ada di ITOM (IT Operation Management), sedangkan AD dan AIM semakin kami tinggalkan dan berfokus di software yang sangat benar kami kuasai dan dibutuhkan di pasaran.

Yah kurang lebih itulah yang akan kami fokuskan, ITOM..

Akhir Nov 2012,

Fanky Christian

Business Development Director

PT. DAYA CIPTA MANDIRI SOLUSI

IBEC Building 2nd Fl

Jl. KH Wahid Hasyim No.84-86

Jakarta Pusat, 10340, Indonesia

Telp: 62-21-3924716

Sales: 62-21-3907418

Fax: 62-21-3907417

mobile: 62-812-1057533 / 0881-8857333 / 081934102353

tw:@fankych

ym:dayaciptamandiri

www.dayaciptamandiri.com

Online Store: www.tokofc.com

visit:

- blog.dayaciptamandiri.com

- fankychristian.blogspot.com

- www.facebook.com/fanky.christian

[DataCenter]

GEADenco, MiraSaito, Goldbach, APC, PowerWare, FIKE, FirePro, CabloFil

[Structure Cabling]

AMP, R&M, LS, Netviel, Panduit

[Enterprise Management]

ManageEngine, PRTG, Nagios, Cimtrak

[Environment Monitoring]

AKCP

[SMS Gateway]

SendQuick, OZEKI NG

[Application Management]

finosSQM, finosMDS, finosHR, Globodox, FusionCharts, Navicat

[Network Solutions]

Draytek Vigor, WatchGuard, 3CX

Build-access-manage at dayaciptamandiri.com

10 Server/Network Monitoring Tools yang simple dan free

10 Free Server & Network Monitoring Tools that Kick Ass

When you have a website or a network, it’s helpful to be aware of any issues as soon as they occur. There are open source and freeware server/network monitoring tools that will supervise your infrastructure for any issues that may arise. These tools are meant to aid you in avoiding being taken offline and evaluating if your resource needs has outgrown your infrastructure.

In this article, we review our top 10 server/network monitoring tools. You will see a variety of server applications here so that you might find the tool (or tools) for your needs.

1. Monit

Monit not only monitors your server, but also attempts to remedy problems by taking predefined actions for certain situations. For example, if your database server crashes, Monit can automatically restart the service if this is the action that you want to take (hint: it usually is).

If you have more than one server that you need to monitor, then you can useM/Monit- an extended version of Monit that provides a simple way to monitor multiple machines.

There’s also an iPhone app available for M/Monit to help you conveniently check on your network without lugging around a laptop around.

2. Ganglia

When you have a cluster of machines, it’s difficult to see how the whole cluster is doing all at once. Ganglia, instead, presents an overview of the whole cluster. This is a great tool to have set up when you’re working with a server cluster; with that said, it may be overkill for single-machine set-ups.

3. Munin

Munin monitors and graphs system performance metrics. It can automatically produce daily/weekly/monthly/yearly performance graphs and reports of many important metrics. It comes with the ability to monitor core system resources, such as memory, disk space, CPU usage, server applications such as MySQL, Apache, and Squid.

One of Munin’s greatest strengths is how simple it is to extend. With just a few lines of code, you can write a plugin to monitor almost anything. Being so easy to extend means that Munin is also a good choice for graphing things unrelated to server performance, such as the number of user signups or website popularity.

4. Cacti

Cacti is similar to Munin in many ways. What is makes Cacti different though–and where it stands out in relation to Munin–is that it allows you to resize your graphs and view data for an arbitrary range. Whereas Munin has fixed daily, weekly, monthly and yearly graphs (unless you write a custom extension), Cacti lets you view your data however you want to: last 2 hours, last 4 days, last 6 months, out of the box. You can even visually select and zoom into regions on your graphs.

5. Nagios

Nagios is "the industry standard in IT infrastructure monitoring,"–well, at least that’s what it says on their website. Nagios can be complicated to install and configure, but its wealth of features are unmatched by any tool out in the market and is geared for the experienced IT network administrator. Nagios supports monitoring of multiple hosts and can send out alerts via email, pager (if you still use this ancient technology) or SMS/text messaging. Like Monit, it can also be configured to automatically respond to problems.

6. Zabbix

Zabbix is a feature-packed monitoring tool. It has great visualization support including user-defined views, zooming, and mapping. It can send out alerts via email, SMS or instant message. It also provides audible alerts, which can be useful when you’re physically near the monitoring machine.

7. Observium

Observium is geared towards Linux, BSD and Cisco networks. It supports auto discovery of your network infrastructure, finding the networks that you’re likely interested in monitoring; this feature can be compared to how your Wi-Fi software automatically finds signals in range that you can jack into. Observium provides detailed graphs, and can be set up alongside Nagios to provide alerts. It also integrates well with Collectd (featured below) for a more robust interface.

8. Zenoss

Zenoss is an open source version of the commercial server monitoring tool Zenoss Enterprise, written entirely in Python. It supports the Nagios plugin format, so many existing Nagios plugins can be used in Zenoss. One of the main highlights of Zenoss is its powerful yet simple to use user interface.

9. Collectd

Collectd is similar to Munin and Cacti in that it focuses on graphing system metrics. Where it excels in is that it is designed specifically for performance and portability; this ultimately means it’s great on rugged systems, low-end systems, and embedded systems. Being designed for performance and low-system resource use means that Collectd can gather data every 10 seconds without interfering with your server processes, providing extremely high-resolution statistics. You can write extensions for it in C, Perl or Java.

10. Argus

Argus focuses on the monitoring of network services, and supports IPv4 and IPv6. It has a nice alert escalation procedure: after sending out an alert and the problem still isn’t resolved within a fixed amount of time (because the systems admin is at home enjoying his sleep), another alert will be sent out to someone else.

What do you use?

Do you have experiences with any of the tools above? Do you use something else? Join our discussion in the comments.

About the Author

Ben Dowling is a passionate software developer who specializes in web and mobile application development. He currently works for Mendeley in London, UK, and regularly blogs about development at Coderholic. You can also find him on twitter.

Cara salah mengimplementasikan arsitektur LOAD balancing

2.5 bad ways to implement a server load balancing architecture

posted on Friday, October 24, 2008 7:55 AM 

Tweet 

I'm in a bit of mood after reading a Javaworld article on server load balancing that presents some fairly poor ideas on architectural implementations. It's not the concepts that are necessarily wrong; they will work. It's the architectures offered as a method of load balancing made me do a double-take and say "What?" 

I started reading this article because it was part 2 of a series on load balancing and this installment focused on application layer load balancing. You know, layer 7 load balancing. Something we at F5 just might know a thing or two about. But you never know where and from whom you'll learn something new, so I was eager to dive in and learn something.

I learned something alright. I learned a couple of bad ways to implement a server load balancing architecture.

TWO LOAD BALANCERS?

The first indication I wasn't going to be pleased with these suggestions came with the description of a "popular" load-balancing architecture that included two load balancers: one for the transport layer (layer 4) and another for the application layer (layer 7).

In contrast to low-level load balancing solutions, application-level server load balancing operates with application knowledge. One popular load-balancing architecture, shown in Figure 1, includes both an application-level load balancer and a transport-level load balancer.

Even the most rudimentary, entry level load balancers on the market today - software and hardware, free and commercial - can handle both transport and application layer load balancing. There is absolutely no need to deploy two separate load balancers to handle two different layers in the stack. This is a poor architecture introducing unnecessary management and architectural complexity as well as additional points of failure into the network architecture. It's bad for performance because it introduces additional hops and points of inspection through which application messages must flow. To give the author credit he does recognize this and offers up a second option to counter the negative impact of the "additional network hops."

One way to avoid additional network hops is to make use of the HTTP redirect directive. With the help of the redirect directive, the server reroutes a client to another location. Instead of returning the requested object, the server returns a redirect response such as 303.

I found it interesting that the author cited an HTTP response code of 303, which is rarely returned in conjunction with redirects. More often a 302 is used. But it is valid, if not a bit odd.

That's not the real problem with this one, anyway. The author claims "The HTTP redirect approach has two weaknesses." That's true, it has two weaknesses - and a few more as well. He correctly identifies that this approach does nothing for availability and exposes the infrastructure, which is a security risk. But he fails to mention that using HTTP redirects introduces additional latency because it requires additional requests that must be made by the client (increasing network traffic), and that it is further incapable of providing any other advanced functionality at the load balancing point because it essentially turns the architecture into a variation of a DSR (direct server return) configuration.

THAT"S ONLY 2 BAD WAYS, WHERE'S THE .5?

The half bad way comes from the fact that the solutions are presented as a Java based solution. They will work in the sense that they do what the author says they'll do, but they won't scale.

Consider this: the reason you're implementing load balancing is to scale, because one server can't handle the load. A solution that involves putting a single server - with the same limitations on connections and session tables - in front of two servers with essentially the twice the capacity of the load balancer gains you nothing. The single server may be able to handle 1.5 times (if you're lucky) what the servers serving applications may be capable of due to the fact that the burden of processing application requests has been offloaded to the application servers, but you're still limited in the number of concurrent users and connections you can handle because it's limited by the platform on which you are deploying the solution.

An application server acting as a cluster controller or load balancer simply doesn't scale as well as a purpose-built load balancing solution because it isn't optimized to be a load balancer and its resource management is limited to that of a typical application server. That's true whether you're using a software solution like Apache mod_proxy_balancer orhardware solution.

So if you're implementing this type of a solution to scale an application, you aren't going to see the benefits you think you are, and in fact you may see a degradation of performance due to the introduction of additional hops, additional processing, and poorly designed network architectures.

I'm all for load balancing, obviously, but I'm also all for doing it the right way. And these solutions are just not the right way to implement a load balancing solution unless you're trying to learn the concepts involved or are in a computer science class in college. 

If you're going to do something, do it right. And doing it right means taking into consideration the goals of the solution you're trying to implement. The goals of a load balancing solution are to provide availability and scale, neither of which the solutions presented in this article will truly achieve.

     

10 ways to make your business more efficient

By Jack Wallen | November 20, 2012, 5:12 AM PST

If your business isn't running at top efficiency, you're failing. In today's world of instant access, social networking, and constant connection, working with inefficient systems and software could quickly lead to a series of micro-fractures that can bring your company to its knees. Though you may not see it happening at first, at some point the failure will become obvious.

To avoid this, your company must be working at peak efficiency. But when you're already deeply embedded in your systems, software, and managerial practices, how can you retool your company for a more efficient environment? Here are 10 tips that can help.

1: Don't expand too quickly

I've seen this happen many times. Businesses start seeing dollar signs and think that the bigger they get, the better their bottom line. Those dollar signs blind them to the fact that expanding too quickly means the proper systems and training can't be put into place. When you're small, your workflow is designed accordingly. If you expand too quickly, you can't properly adjust workflow, the systems that support workflow, or the employees who must manage the workflow.

2: Don't employ technology until it is thoroughly tested and understood

This is another issue I have not only witnessed but have fallen victim to. Companies are often seduced by the idea that a piece of software or hardware will make their workflow infinitely easier. A PR-pro can easily sway them with numbers and user quotes. But you can't always tell whether that piece of software is well suited for your needs and staff. If you're thinking about new tech, get a demo of it and test it before you buy it or insist your employees start using something that will, in the end, cause serious inefficiencies.

3: Don't make technology decisions unless you have considered the users

I've been on both sides of this coin, and I know how frustrating this can be. There are users within your company who, in many ways, know how things work better than you. They're in the thick of the workflow every day. Those people need efficient tools and systems in place if they have any chance of getting their jobs done. If you're about to pull the trigger on a technology decision, make sure you have discussed this decision with those it affects.

4: Make communication a crucial component

One of the last aspects addressed within business is communication. When communication is poor, work is inefficient. Period. Communication could be as simple as an open door policy or as complex as a content management system designed to ensure every single piece of work is documented. Regardless of what you do, place the highest priority on communication. Make sure staff can easily communicate with their fellow workers. Make sure the company can communicate with clients. The second communication fails, efficiency fails.

5: Use secure and reliable technology

There are times I have been on the receiving end of technology that simply doesn't work. When I work within an office, I make sure I can use a Linux box for the majority of my day because I'm far more efficient with that platform than any other. When you deploy technology, make sure it is secure and reliable. Having to work with unreliable software (or hardware) is one of the prime reasons people can't get their work done. Viruses, malware, underpowered hardware… it all adds up.

6: Prepare for disaster

It doesn't take a natural disaster to bring down your business. A break-in, dead server hardware, a disgruntled employee — many issues can cause a company disaster. Unless you have an effective means of dealing with disaster, you will be dead in the water until the ship is righted. And even after the ship is righted, it may take awhile to get workflow back up to speed. Make sure your disaster plan continues through getting hardware back up and running and getting users working productively again.

7: Don't create redundant management tiers

Micromanaging is bad enough. But when you add redundant layers to management, you wind up with too many cooks in an already complicated kitchen. Those managers can often wind up in a war of egos, causing further roadblocks to efficiency. Make sure your chain of command isn't clogged to the point of confusion and paralysis. If you expect efficiency from your staff, make sure the managers above them can also work in an efficient manner.

8: Don't give your employees more work than they can handle

You know when an employee quits and you dump their work on another employee, thinking you're going to save a dollar? That is one of the single worst roadblocks to efficiency you can put in play. Once employees reach a certain saturation with duties, their efficiency drops exponentially. If you don't overload your employees, you should be able to expect efficient work from them.

9 Have a sufficient network pipe to handle your network load

How can your staff possibly work efficiently if you have insufficient or unreliable data pipes? With a constantly clogged pipe, your staff won't be getting much done. As a remote engineer, I have experienced plenty of instances where a data pipe was either too slow to do my job or a network connection was dropped. This is one of those issues that's simple to resolve: Just upgrade your pipe. Don't let those things that are easily controlled caused problems.

10: If an employee has an idea for a more efficient way of handling a task, listen!

Sometimes, those whose job titles don't start with the letter "C" might come up with a brilliant idea. Not only will you benefit from that great idea, but employee morale will get a nice bump from the understanding that you trust and respect your staff. Besides, those staff members are the ones who actually have to do the bulk of the work — they probably have some killer ideas on how to improve it.

Other tips?

Efficiency should be one of your top priorities if you want your business to thrive and grow. Without efficient systems in place, each phase of growth will only cause more issues, perpetuating the cycle of inefficiency. Take a close look at your company. If you can honestly say that everything was designed and built for the most efficient workflow, you're already miles ahead of your competition.

Have you experienced inefficient practices and environments with your own work? What suggestions would you add to this list?
build-access-manage at dayaciptamandiri.com