Efisiensi Biaya dan Optimasi Data Rate pada Jaringan System Banking Online

Operasional dan pelayanan kepada nasabah suatu bank dengan system online sangat tergantung kepada kinerja dari jaringan komunikasi data, baik komunikasi data antara kantor pusat dengan kantor cabang maupun pelayanan langsung kepada nasabah melalui terminal atau channel transaksi.Biaya suatu bank untuk mengoperasikan jaringan komunikasi data merupakan salah satu biaya operasional bank yang terbesar. Usaha melakukan efisiensi biaya dan optimasi pemakaian data rate jaringan system banking online harus dilakukan guna menurunkan biaya operasional sekaligus peningkatan kinerja jaringan. Untuk itu digunakan kerangka kerja terukur berdasarkan e-TOM (Enhanced Telecom Operation Map).Untuk mendapatkan nilai-nilai Key Performance Indicators (KPI) dilakukan pengukuran terhadap besarnya data rate yang diperlukan oleh banking system, jumlah seluruh paket data yang ditransmisikan, besarnya data yang mampu ditransmisikan, dan banyaknya data yang tak dikehendaki pada segmen jaringan.Berdasarkan Key Performance Indicators (KPI) tersebut dilakukan perubahan setting data rate dan pengaturan alokasi port data komunikasi pada segmen jaringan hingga didapatkan nilai KPI terbaik.

A BPEL-Based Fault-Handling Architecture for Telecom Operation Support Systems

Exception handling is an important issue in dependable software computing. This paper presents a system architecture and explains the role of responsibility of each component that is introduced in the architecture. The design is used to ensure the constructed service-oriented applications remain in a stable state. Service-Oriented Architecture is a paradigm for constructing current enterprise applications. It uses service composition technology to induce existing service components to provide advanced services. The most important concept in this methodology is that of reusing existing components. Business Process Execution Language (BPEL) is widely used for achieving service composition, providing basic capability for developers to deal with faults using defined activities standard in BPEL. No sufficient design, however, supports developers in implementing fault-handling components efficiently. The architecture proposed in this paper provides the design approach to explain how to reuse the fault-handling components. Additionally, the paper also provides an empirical case study that illustrates how this design was used by the Chunghwa Telecom Company in an effort to improve efficiency in implementing fault-handling components and in constructing service-oriented applications. The number of fault-handling components required was reduced from 38 to 3, implying a 92.10% efficiency rate.