Internet Banking Research Survey

Tolong partisipasi survey yach..^_^..

Buat penelitian..:D..

Internet Banking Research Survey

Google Wallet si Dompet Elektronik di Ponsel bikin Bayar Tinggal Tekan Layar Hp

Tanggal 26 Mei 2011 di kantor Google di New York City, bersamaan dengan Citi, MasterCard, First Data dan Sprint, mereka memberikan demo dari Google Wallet, sebuah aplikasi yang akan membuat ponsel menjadi dompet Anda. Aplikasi ini memungkinkan Anda menekan tombol pada aplikasi untuk membayar dan menyimpan uang secara elektronik menggunakan ponsel Anda dan memanfaatkan teknologi near field communication (NFC). Kami, sedang melakukan uji lapangan Google Wallet dan berrencana untuk merilis segera.

Google Wallet merupakan bagian penting dalam upaya berkelanjutan kami untuk memperbaiki cara belanja bagi bisnis dan konsumen. Ini  ditujukan untuk membuat lebih mudah bagi pembeli untuk membayar barang yang anda inginkan, sementara pedagang memberikan lebih banyak cara untuk menawarkan kupon dan program loyalitas kepada pelanggan, serta menjembatani kesenjangan antara perdagangan online dan offline. Karena Google Wallet adalah aplikasi mobile, maka dapat  melakukan lebih dari dompet biasa. Anda akan dapat menyimpan kartu kredit Anda, penawaran, kartu loyalitas dan kartu hadiah, tapi tanpa memenuhi saku Anda. Ketika Anda menekan untuk membayar, ponsel Anda juga akan secara otomatis menebus penawaran dan mendapatkan poin loyalitas untuk Anda. Suatu hari, bahkan hal-hal seperti melewati boarding, tiket, ID dan kunci dapat disimpan di Google Wallet.

Pada awalnya, Google Wallet akan mendukung MasterCard Citi dan Kartu Prabayar Google, yang Anda dapat gunakan dengan hampir semua kartu pembayaran. Sejak awal, Anda dapat menggunakan ponsel untuk membayar dimanapun MasterCard PayPass diterima. Google Wallet juga akan sync Google Offers (www.google.com/offers) yang Anda bisa menebus melalui NFC di pedagang yang terdaftar pada program SingleTap, , atau dengan menunjukkan barcode saat Anda check out. Banyak pedagang yang sedang bekerja untuk mengintegrasikan penawaran dan program loyalitas dengan Google Wallet.

Dengan Google Wallet, kami membangun ekosistem perdagangan terbuka, dan kami berencana untuk mengembangkan API yang akan memungkinkan integrasi dengan sejumlah mitra. Pada awalnya, Google Wallet akan kompatibel dengan Nexus S 4G oleh Google, tersedia di Sprint. Seiring waktu, kami merencanakan untuk menambah dukungan untuk ponsel lebih luas lagi.

Untuk mempelajari lebih lanjut silahkan kunjungi situs web Google Wallet di www.google.com/wallet.  Artikel ini dikutip dari tulisan  Rob Behren von dan Wall Jonathan, Founding Engineers on Google Wallet

iPhone SLR Mount dari Photojojo Mengubah iPhone menjadi DSLR

Photojojo telah memperkenalkan SLR Mount untuk iPhone. Kombinasi dari casing iPhone dan mount mendukung baik lensa Nikon atau lensa Canon EOS SLR , yang juga dilengkapi dengan UV filter. Casing aluminium memiliki lubang yang memungkinkan strap kamera terpasang.

Ada dua versi dari  SLR Mount untuk iPhone, satu untuk Nikon dan satu untuk lensa Canon EOS. SLR Mount untuk iPhone ini memiliki bandrol harga $249 untuk iPhone 4 dan $190 utk iPhone 3.

OSI Model

The OSI Reference Model is founded on a suggestion developed by the International Organization for Standardization (ISO). The model is known as ISO OSI (Open Systems Interconnection) Reference Model because it relates with connecting open systems – that is, systems that are open for communication with other systems. OSI Model is a set of protocols that try to identify and homogenize the data communication practices. The OSI Model has the support of most computer and network vendors, many big customers, and most governments, including the United States. The OSI Model is a model that illustrates how data communications should take place. It segregates the process into seven groups, called layers. Into these layers are integrated the protocol standards developed by the ISO and other standards organization, including the Institute of Electrical and Electronic Engineers (IEEE), American National Standards Institute (ANSI), and the International Telecommunications Union (ITU), formerly known as the CCITT (Comite Consultatif Internationale de Telegraphique et Telephone). The OSI Model affirms what protocols and standards should be used at each layer. It is modular, each layer of the OSI Model functions with the one above and below it.
 

The short form used to memorize the layer names of the OSI Model is “All People Seem To Need Data Processing”. The lower two layers are normally put into practice with hardware and software. The remaining five layers are only implemented with software. The layered approach to network communications gives the subsequent advantages: Reduced intricacy, enhanced teaching/learning, modular engineering, accelerated advancement, interoperable technology, and standard interfaces.


The Seven Layers of the OSI Model
 

The seven layers of the OSI model are:

• Application (7)
• Presentation (6)
• Session (5)
• Transport (4)
• Network (3)
• Data Link (2)
• Physical (1)

The easiest way to remember the layers of the OSI model is to use the handy mnemonic "All People Seem To Need Data Processing":

• Application All (7)
• Presentation People (6)
• Session See (5)
• Transport T (4)
• Network Nee (3)
• Data Link Dat (2)
• Physical Processin (1)

The functions of the seven layers of the OSI model are:
 

Layer Seven of the OSI Model
The Application Layer of the OSI model is responsible for providing end-user services, such as file transfers, electronic messaging, e-mail, virtual terminal access, and network management. This is the layer with which the user interacts.

Layer Six of the OSI Model
The Presentation Layer of the OSI model is responsible for defining the syntax which two network hosts use to communicate. Encryption and compression should be Presentation Layer functions.

Layer Five of the OSI Model
The Session Layer of the OSI model is responsible for establishing process-to-process commnunications between networked hosts.

Layer Four of the OSI Model
The Transport Layer of the OSI model is responsible for delivering messages between networked hosts. The Transport Layer should be responsible for fragmentation and reassembly.

Layer Three of the OSI Model
The Network Layer of the OSI model is responsible for establishing paths for data transfer through the network. Routers operate at the Network Layer.

Layer Two of the OSI Model
The Data Link Layer of the OSI model is responsible for communications between adjacent network nodes. Hubs and switches operate at the Data Link Layer.

Layer One of the OSI Model
The Physical Layer of the OSI model is responsible for bit-level transmission between network nodes. The Physical Layer defines items such as: connector types, cable types, voltages, and pin-outs.

The OSI Model vs. The Real World
 

The most major difficulty with the OSI model is that is does not map well to the real world! The OSI was created after many of todays protocols were already in production use. These existing protocols, such as TCP/IP, were designed and built around the needs of real users with real problems to solve. The OSI model was created by academicians for academic purposes. The OSI model is a very poor standard, but it's the only well-recognized standard we have which describes networked applications. The easiest way to deal with the OSI model is to map the real-world protocols to the model, as well as they can be mapped.

Layer Name Common Protocols
7 Application SSH, telnet, FTP
6 Presentation HTTP, SMTP, SNMP
5 Session RPC, Named Pipes, NETBIOS
4 Transport TCP, UDP
3 Network IP
2 Data Link Ethernet
1 Physical Cat-5
 

The difficulty with this approach is that there is no general agreement as to which layer of the OSI model to map any specific protocol. You could argue forever about what OSI model layer SSH maps to. A much more accurate model of real-world networking is the TCP/IP model:

TCP/IP Model
Application Layer
Transport Layer
Internet Layer
Network Interface Layer
 

The most significant downside with the TCP/IP model is that if you reference it, fewer people will know what you are talking about! For a better description of why the OSI model should go the way of the dodo, disco, and DivX, read Kill the Beast: Why the Seven-Layer Model Must Die. 2 nodes.

1. For sending a packet or in more easy words we can say that Message to the intended Node we need its Address which would be globally known(i.e IP Address).Network Layer Protocols like IP(Internet Protocol)provides that information.
2. Network Layer also helps in finding the best path to that destination node among the various available paths over the network in order to transmit the packet(Part of Complete Message) to the final Destination.
3. Internet consists of various small-small Networks,if we 2 nodes are communicating over the Internet then in that we have to traverse various different Networks to finally get that particular node,In that case also Network Layer helps by taking information from one network and putting it on another network.

Bandwidth VS Troughput

A Guide to Bandwidth and Throughput

Bandwidth and throughput are two networking concepts that are commonly misunderstood. System administrators regularly use these two concepts to help plan, design, and build new networks. Networking exams also include a few bandwidth and throughput questions, so brushing up on these two subjects is a good idea before exam day.

What is Bandwidth ?

You probably already have a fairly good idea on what bandwidth is. It is technically defined as the amount of information that can flow through a network at a given period of time. This is, however, theoretical- the actual bandwidth available to a certain device on the network is actually referred to as throughput (which we’ll discuss further on in this section). Bandwidth can be compared to a highway in many respects. A highway can only allow for a certain amount of vehicles before traffic becomes congested. Likewise, we refer to bandwidth as finite- it has a limit to its capability. If we accommodate the highway with multiple lanes, more traffic could get through. This also applies to networks- we could perhaps upgrade a 56K modem to a DSL modem and get much higher transfer speeds. Bandwidth is measured in bits per second (bps). This basic unit of measurement is fairly small, however, and you’ll more than likely see bandwidth expressed as kilobits, megabits, and gigabits.

Make sure you make the distinction between bits and bytes. A megabyte is certainly not the same as a megabit, although they are abbreviated quite similarly. Since we know there are 8 bits in a byte, you can simply divide the number of bits by 8 to find the byte equivalent (or to convert from bytes to bits, multiply by 8).

Lastly, it’s important to also make the distinction between speed and bandwidth. Bandwidth is simply how many bits we can transmit a second, not the speed at which they travel. We can use the water pipe analogy to grasp this concept further. More water could be transported by buying a larger pipe- but the speed at which the water flows is less affected.

The Difference between Throughput and Bandwidth

Although bandwidth can tell us about how much information a network can move at a period of time, you’ll find that actual network speeds are much lower. We use the term throughput to refer to the actual bandwidth that is available to a network, as opposed to theoretical bandwidth.

Several different things may affect the actual bandwidth a device gets. The number of users accessing the network, the physical media, the network topology, hardware capability, and many other aspects can affect bandwidth. To calculate data transfer speeds, we use the equation Time = Size / Theoretical Bandwidth.

Keep in mind that the above equation is actually what we use to find the “best download.” It assumes optimal network speeds and conditions since we use theoretical bandwidth. So to get a better idea on the typical download speed, we use a different equation: Time = Size / Actual Throughput.

Organizational Memory

Controversies In OM

• Can organizations be said to have memories, or is OM essentially anthropomorphism?
• What is the relationship between the research fields of OM and KM?
• Does OM reside in the minds of individual organizational members, or elsewhere?Is OM appropriately modeled in terms of static storage bins, or should it be treated as a dynamic socially constructed process?
• How are OM systems operationalized?
• Is OM functional or dysfunctional in terms of organizational performance and effectiveness?

Learning in a Knowledge Environment

• Learning and development are essential activities in a knowledge-intensive community
• Knowledge workers innovate and adapt as they explore and integrate new knowledge and experiences
• Social, intellectual and technical capital need to be nurtured and valued across the community

• Training: learning processes guided by an expert
• Learning: changes in skills, knowledge and abilities which influence how people think and operate in the future
• Development: ongoing process of growth and change which occurs as new influences are encountered

• Competencies: areas of knowledge and skills which contribute to job-related behaviours
• Capabilities: the range of skills and competencies which enable the individualto meet the challenges associated with performing complex work roles

Learning approaches

• There is no single best learning approach
• Different methods suit different purposes
• Individuals may learn best through different approaches
• Different forms of learning need different support approaches
• Organisations need to provide opportunities which reflect these different needs

CES 2011 Lanjutan

CISM Binus

Tugas Individu Mata Kuliah Managing Corporate Information System and Technology

Nama     :    Geraldy Jonathan Doodoh

NIM        :    1112200213

Halaman 53 No.4

• Yang membedakan kita dengan kompetitor serta pengganti adalah nilai lebih atau more value yang ada pada produk maupun service yang bisa berupa nilai dalam harga, segmen pelanggan, dan lebih radikal lagi adalah business models. 
• Yang sulit ketika pemain baru masuk kedalam pasar kita adalah subtitusi produk dan layanan karena bukan tidak mungkin permain tersebut memiliki segmentasi produk serta layanan yang berbeda dengan kita atau bisa jadi sama persis.
• Lebih sulit mengganti pemasok karena pada dasarnya pemasok merupakan rantai dari produksi suatu produk atau layanan dengan demikian bukanlah tidak mungkin akan terjadi perubahan dalam proses bisnis yang ada.

Halaman 79 No.3

• Ya tentu saja. Karena dengan mengidentifikasi dan memanajemen resiko yang ada dalam teknologi informasi akan membantu kita dalam menentukan produk, pasar, jaringan bisnis, posisi bisnis, serta menambah kapabilitas dalam bisnis yang ada.

Halaman 95 No.9

• Ya harus. Karena dengan menciptakan budaya dalam membagi nilai dan sifat dari sebuah organisasi dengan rekannya akan membentuk sebuah kolaborasi yang memiliki kekuatan bisnis tersendiri dan hal ini semata-mata untuk menuju pada tujuan bersama.

Halaman 119 No.8

• Dalam hal operasional TI diperusahaan saya berjalan selama 24 jam 365 hari non-stop dan 2 kali dalam seminggu dilakukan maintain untuk sistem yang ada.
• Untuk implementasi TI yang menyangkut bisnis biasanya rata-rata 2-6 bulan tergantung skala prioritas yang ada dengan pengeluaran yang bervariasi tergantung dari proyek TI itu sendiri.
• Yang menjadi kunci utama penyebab lambatnya implementasi inovasi TI dalam bisnis serta meningkatnya pengeluaran yaitu kurangnya sinkronisasi antara strategi, kapabilitas, dan nilai untuk TI itu sendiri.

Untuk selengkapnya tugas CISM individu dapat di-download :

Download Tugas Individu CISM

CES 2011

Cara Upload Video Youtube ke Blog

Cisco Catalyst 6500 Family

Flagship Platform of the Catalyst Family

With more than 35,000 customers, the Cisco Catalyst 6500 Series Switch is the benchmark for innovation and investment protection in networking. To support Borderless Networks, the switches deliver high performance and a broad feature set suitable for campus, data center, WAN, and Metro Ethernet deployments.

Increased Uptime

Catalyst 6500 E-Series Switches support modular Cisco IOS Software to decrease unplanned downtime and simplify software changes through in-service software upgrades.

Security

The Cisco Catalyst 6500 E-Series integrates the Cisco Catalyst 6500 Series Supervisor Engine 720 and the Cisco Catalyst 6500 Series Adaptive Security Service Module to take advantage of the existing infrastructure and deliver integrated security services with increased VPN session counts and efficient power consumption in a single blade.

Mobility

Catalyst 6500 E-Series Wireless Service Module 2 easily integrates wired and wireless networks and provides security, mobility, and redundancy for business-critical WLANs.

Network Management

The Catalyst 6500 E-Series Network Analysis Module 3, optimized for 10 Gb performance, improves resource utilization, troubleshooting, and the end-user experience.

Application Performance

The Catalyst 6500 E-Series Application Control Engine 30 increases availability, accelerates performance, and enhances security.

Virtualization

The Catalyst Virtual Switching System (VSS) increases operational efficiency by simplifying the network with a single point of management, while still providing redundancy. VSS activates all available bandwidth across redundant Catalyst 6500 Series Switches and eliminates asymmetric routing.

ITSM (Information Technology Service Management)

ITSM (Information Technology Service Management, Manajemen Layanan Teknologi Informasi) adalah suatu metode pengelolaan sistem teknologi informasi (TI) yang secara filosofis terpusat pada perspektif konsumen layanan TI terhadap bisnis perusahaan. ITSM merupakan kebalikan dari pendekatan manajemen TI dan interaksi bisnis yang terpusat pada teknologi. Istilah ITSM tidak berasal dari suatu organisasi, pengarang, atau pemasok tertentu dan awal penggunaan frase inipun tidak jelas kapan dimulainya. ITSM berfokus pada proses dan karenanya terkait dan memiliki minat yang sama dengan kerangka kerja dan metodologi gerakan perbaikan proses (seperti TQM, Six Sigma, Business Process Management, dan CMMI). Disiplin ini tidak memedulikan detil penggunaan produk suatu pemasok tertentu atau detil teknis suatu sistem yang dikelola, melainkan berfokus pada upaya penyediaan kerangka kerja untuk menstrukturkan aktivitas yang terkait dengan TI dan interaksi antara personil teknis TI dengan pengguna teknologi informasi. ITSM umumnya menangani masalah operasional manajemen teknologi informasi (kadang disebut operations architecture, arsitektur operasi) dan bukan pada pengembangan teknologinya sendiri. Contohnya, proses pembuatan perangkat lunak komputer untuk dijual bukanlah fokus dari disiplin ini, melainkan sistem komputer yang digunakan oleh bagian pemasaran dan pengembangan bisnis di perusahaan perangkat lunak-lah yang merupakan fokus perhatiannya. Banyak pula perusahaan non-teknologi, seperti pada industri keuangan, ritel, dan pariwisata, yang memiliki sistem TI yang berperan penting, walaupun tidak terpapar langsung kepada konsumennya. Sesuai dengan fungsi ini, ITSM sering dianggap sebagai analogi disiplin ERP pada TI, walaupun sejarahnya yang berakar pada operasi TI dapat membatasi penerapannya pada aktivitas utama TI lainnya seperti manajemen portfolio TI dan rekayasa perangkat lunak.

Kerangka Kerja 

Kerangka kerja (framework) yang dianggap dapat memberikan contoh penerapan ITSM di antaranya:

• Information Technology Infrastructure Library (ITIL)
• Control Objectives for Information and Related Technology (COBIT)
• Software Maintenance Maturity Model
• PRM-IT IBM's Process Reference Model for IT
• Application Services Library (ASL)
• Business Information Services Library (BISL)
• Microsoft Operations Framework (MOF)
• eSourcing Capability Model for Service Providers (eSCM-SP) dan eSourcing Capability Model for Client Organizations (eSCM-CL) dari ITSqc for Sourcing Management.

ITIL (Information Technology Infrastructure Library)

ITIL atau Information Technology Infrastructure Library adalah suatu rangkaian konsep dan teknik pengelolaan infrastruktur, pengembangan, serta operasi teknologi informasi (TI). ITIL diterbitkan dalam suatu rangkaian buku yang masing-masing membahas suatu topik pengelolaan TI. Nama ITIL dan IT Infrastructure Library merupakan merek dagang terdaftar dari Office of Government Commerce (OGC) Britania Raya. ITIL memberikan deskripsi detil tentang beberapa praktik TI penting dengan daftar cek, tugas, serta prosedur yang menyeluruh yang dapat disesuaikan dengan segala jenis organisasi TI. Walaupun dikembangkan sejak dasawarsa 1980-an, penggunaan ITIL baru meluas pada pertengahan 1990-an dengan spesifikasi versi keduanya (ITIL v2) yang paling dikenal dengan dua set bukunya yang berhubungan dengan ITSM (IT Service Management), yaitu Service Delivery (Antar Layanan) dan Service Support (Dukungan Layanan).

Pada 30 Juni 2007, OGC menerbitkan versi ketiga ITIL (ITIL v3) yang intinya terdiri dari lima bagian dan lebih menekankan pada pengelolaan siklus hidup layanan yang disediakan oleh teknologi informasi. Kelima bagian tersebut adalah:

1. Service Strategy
2. Service Design
3. Service Transition
4. Service Operation
5. Continual Service Improvement

Kelima bagian tersebut dikemas dalam bentuk buku, atau biasa disebut sebagai core guidance publications. Setiap buku dalam kelompok utama ini berisi:

1. Practice fundamentals – menjelaskan latar belakang tahapan lifecycle serta kontribusinya terhadap pengelolaan layanan TI secara keseluruhan.
2. Practice principles – menjelaskan konsep-konsep kebijakan serta tata kelola tahanan lifecycle yang menjadi acuan setiap proses terkait dalam tahapan ini.
3. Lifecycle processes and activities – menjelaskan berbagai proses maupun aktivitas yang menjadi kegiatan utama tahapan lifecycle. Misalnya proses financial management dan demand management dalam tahapan Service Strategy.
4. Supporting organization structures and roles – proses-proses ITIL tidak akan dapat berjalan dengan baik tanpa defini roles dan responsibilities. Bagian ini menjelaskan semua aspek yang terkait dengan kesiapan model dan struktur organisasi.
5. Technology considerations – menjelaskan solusi-solusi otomatisasi atau software ITIL yang dapat digunakan pada tahapan lifecycle, serta persyaratannya.
6. Practice Implementation – berisi acuan/panduan bagi organisasi TI yang ingin mengimplementasikan atau yang ingin meningkatkan proses-proses ITIL.
7. Complementary guideline – berisi acuan model-model best practice lain selain ITIL yang dapat digunakan sebagai referensi bagian tahapan lifecycle.
8. Examples and templates – berisi template maupun contoh-contoh pengaplikasian proses.

Di samping buku-buku dalam core guidance publications, ada juga complementary guidance. Dimana buku-buku dalam kategori nantinya dimaksudkan untuk memberikan model, acuan dan panduan bagi penerapan ITIL pada sektor-sektor tertentu seperti jenis industri tertentu, tipe organisasi serta arsitektur teknologi. Dengan demikian, ITIL akan dapat lebih diterima serta diadaptasi sesuai dengan lingkungan serta behaviour dari setiap organisasi TI.

Siklus Layanan ITIL

Kelima bagian ITIL yang seperti tersebut di atas biasanya disebut juga sebagai bagian dari sebuah siklus. Dikenal pula dengan sebutan Sikuls Layanan ITIL. Secara singkat, masing-masing bagian dijelaskan sebagai berikut :

A. Service Strategy 

Inti dari ITIL Service Lifecycle adalah Service Strategy. Service Strategy memberikan panduan kepada pengimplementasi ITSM pada bagaimana memandang konsep ITSM bukan hanya sebagai sebuah kemampuan organisasi (dalam memberikan, mengelola serta mengoperasikan layanan TI), tapi juga sebagai sebuah aset strategis perusahaan. Panduan ini disajikan dalam bentuk prinsip-prinsip dasar dari konsep ITSM, acuan-acuan serta proses-proses inti yang beroperasi di keseluruhan tahapan ITIL Service Lifecycle. Topik-topik yang dibahas dalam tahapan lifecycle ini mencakup pembentukan pasar untuk menjual layanan, tipe-tipe dan karakteristik penyedia layanan internal maupun eksternal, aset-aset layanan, konsep portofolio layanan serta strategi implementasi keseluruhan ITIL Service Lifecycle. Proses-proses yang dicakup dalam Service Strategy, di samping topik-topik di atas adalah:

1. Service Portfolio Management
2. Financial Management
3. Demand Management

Bagi organisasi TI yang baru akan mengimplementasikan ITIL, Service Strategy digunakan sebagai panduan untuk menentukan tujuan/sasaran serta ekspektasi nilai kinerja dalam mengelola layanan TI serta untuk mengidentifikasi, memilih serta memprioritaskan berbagai rencana perbaikan operasional maupun organisasional di dalam organisasi TI. Bagi organisasi TI yang saat ini telah mengimplementasikan ITIL, Service Strategy digunakan sebagai panduan untuk melakukan review strategis bagi semua proses dan perangkat (roles, responsibilities, teknologi pendukung, dll) ITSM di organisasinya, serta untuk meningkatkan kapabilitas dari semua proses serta perangkat ITSM tersebut.

B. Service Design 

Agar layanan TI dapat memberikan manfaat kepada pihak bisnis, layanan-layanan TI tersebut harus terlebih dahulu di desain dengan acuan tujuan bisnis dari pelanggan. Service Design memberikan panduan kepada organisasi TI untuk dapat secara sistematis dan best practice mendesain dan membangun layanan TI maupun implementasi ITSM itu sendiri. Service Design berisi prinsip-prinsip dan metode-metode desain untuk mengkonversi tujuan-tujuan strategis organisasi TI dan bisnis menjadi portofolio/koleksi layanan TI serta aset-aset layanan, seperti server, storage dan sebagainya. Ruang lingkup Service Design tidak melulu hanya untuk mendesain layanan TI baru, namun juga proses-proses perubahan maupun peningkatan kualitas layanan, kontinyuitas layanan maupun kinerja dari layanan. Proses-proses yang dicakup dalam Service Design yaitu:

1. Service Catalog Management
2. Service Level Management
3. Supplier Management
4. Capacity Management
5. Availability Management
6. IT Service Continuity Management
7. Information Security Management

C. Service Transition 

Service Transition menyediakan panduan kepada organisasi TI untuk dapat mengembangkan serta kemampuan untuk mengubah hasil desain layanan TI baik yang baru maupun layanan TI yang diubah spesifikasinya ke dalam lingkungan operasional. Tahapan lifecycle ini memberikan gambaran bagaimana sebuah kebutuhan yang didefinisikan dalam Service Strategy kemudian dibentuk dalam Service Design untuk selanjutnya secara efektif direalisasikan dalam Service Operation. Proses-proses yang dicakup dalam Service Transition yaitu:

1. Transition Planning and Support
2. Change Management
3. Service Asset & Configuration Management
4. Release & Deployment Management
5. Service Validation
6. Evaluation
7. Knowledge Management

D. Service Operation 

Service Operation merupakan tahapan lifecycle yang mencakup semua kegiatan operasional harian pengelolaan layanan-layanan TI. Di dalamnya terdapat berbagai panduan pada bagaimana mengelola layanan TI secara efisien dan efektif serta menjamin tingkat kinerja yang telah diperjanjikan dengan pelanggan sebelumnya. Panduan-panduan ini mencakup bagaiman menjaga kestabilan operasional layanan TI serta pengelolaan perubahan desain, skala, ruang lingkup serta target kinerja layanan TI. Proses-proses yang dicakup dalam Service Transition yaitu:

1. Event Management
2. Incident Management
3. Problem Management
4. Request Fulfillment
5. Access Management

E. Continual Service Improvement 

Continual Service Improvement (CSI) memberikan panduan penting dalam menyusun serta memelihara kualitas layanan dari proses desain, transisi dan pengoperasiannya. CSI mengkombinasikan berbagai prinsip dan metode dari manajemen kualitas, salah satunya adalah Plan-Do-Check-Act (PDCA) atau yang dikenal sebagi Deming Quality Cycle

The Eight Essential Elements

ITIL FUNCTIONS & PROCESSES - Figure A

As stated above, some ITIL processes are essential to every IT organization because you’re doing them regardless of whether you have an efficient process in place to help you or not. Let’s take stock now of the essential ITIL processes and why they’re essential to IT Service Management success.

If you compare the bullet list that follows to the list of ITIL v3 functions and processes in Figure A you’ll quickly see that, while it’s obvious that some of these processes are clearly essential to ITSM, it is difficult to decide exactly which processes and functions to include because there are many sub-processes in v3. Figure A illustrates the large range of elements that need to be addressed from the v3 perspective.

Leveraging the collective ITIL guidance with an eye toward “first steps” and foundational aspects, here are the eight essential ITSM processes that are required by all IT departments:

1. Service Desk
2. Event Management
3. Problem Management
4. Service Asset & Configuration Management
5. Change Management
6. Incident Management
7. Request Fulfillment
8. Release & Deployment Management

Recent research supports calling these processes out as essential. For example, the IT Process Institute, in its research on Identifying Key Performance Drivers, found seven sets of control practices that predict top levels of performance. From highest to lowest impact, they are:

• Release scheduling and rollback (Release & Deployment Management)
• Process culture
• Pre-release testing (Change Management)
• Process exception management (Incident Management and Problem Management)
• Standardized configuration strategy (Service Asset & Configuration Management)
• Change linkage (Change Management)
• Controlled production access

Looking at these control practices you can see that most of them map closely to five of the ITIL essentials. Process culture is a management initiative and not an ITIL element per se, and therefore is not covered by the essential elements. This leaves Controlled Production Access, which the essential ITIL processes will contribute by highlighting and supporting resolution of various security issues, as well as ensuring that new services are secure. Similarly, the eight ITIL essentials encompass much of what is in the ITIL Service Transition and Service Operation phases, which have been well-quantified in terms of their impact to IT performance.

Cisco Nexus 7000 Series

Build the network foundation you need for your next-generation data center. Cisco Nexus 7000 Series Switches are a modular switching system designed to deliver 10 Gigabit Ethernet and unified fabric in the data center.

Single End-to-End Platform

The Cisco Nexus 7000 Series offers an end-to-end solution for data center core, aggregation, and high-density end-of-row and top-of-rack server connectivity in a single platform.

The Cisco Nexus 7000 Series platform is run by Cisco NX-OS software. It was specifically designed for the most mission-critical place in the network, the data center.

Design Principles

The Cisco Nexus 7000 was designed around three principles:

• Infrastructure scalability
• Operational continuity
• Transport flexibility

Infrastructure Scalability

These switches use virtualization, efficient power and cooling, density, and performance to support efficient growth in data center infrastructure.

Operational Continuity

The Cisco Nexus design integrates hardware, software, and management to support zero-downtime environments.

Transport Flexibility

You can incrementally and cost-effectively adopt new innovations and technologies, such as:

• Cisco Overlay Transport Virtualization (OTV)
• Cisco FabricPath
• Fibre Channel over Ethernet (FCoE)
• Cisco Locator/ID Separation Protocol (LISP)
• Cisco IOS Multiprotocol Label Switching (MPLS)