Data Center is our focus

We help to build, access and manage your datacenter and server rooms

Structure Cabling

We help structure your cabling, Fiber Optic, UTP, STP and Electrical.

Get ready to the #Cloud

Start your Hyper Converged Infrastructure.

Monitor your infrastructures

Monitor your hardware, software, network (ITOM), maintain your ITSM service .

Our Great People

Great team to support happy customers.

Saturday, January 28, 2017

Company Now Offers Cloud-Based IT Management Apps Hosted in European Union

Company Now Offers Cloud-Based IT Management Apps Hosted in European Union

  • Major step toward cloud-based data security and privacy for organizations in the EU
  • Flagship ITSM offering, ServiceDesk Plus, now accessible at http://ow.ly/AZmN308cPwB; Mobile Device Manager Plus coming in February
PLEASANTON, Calif. - Jan.23, 2017 - ManageEngine, the real time IT management company, today announced the opening of its two new ISO 27001-certified data centers in the EU - one in Amsterdam, Netherlands and another in Dublin, Ireland. This announcement is a part of its efforts to help IT teams move operations seamlessly to the cloud while adhering to the data privacy and security standards of the EU.
With cloud adoption in Europe on a trend of high growth, software vendors are taking steps to protect customer data. To remove security concerns associated with the cloud, the new ManageEngine data centers are certified Service Organization Controls (SOC) Type II and reinforce the company’s efforts to facilitate cloud adoption by IT teams in the EU.
"Our European customers are subject to some of the world's strictest data privacy regulations, which apply to both on-premises and cloud applications," said Rajesh Ganesan, director of product management at ManageEngine. "Our on-premises apps have maintained the highest degree of data privacy and regulatory compliance for years. With our new EU data centers, we’ve set the same standard for our cloud apps and eliminated the privacy barrier to adopting our cloud-based IT management solutions."
"ManageEngine is popular across Europe for its breadth of solutions and value for the money," said Alexander Fillips, head of enterprise management at MicroNova, a long-time partner of ManageEngine in Germany. "Offering its cloud suite from data centers within Europe is a great move that ensures privacy and compliance to local regulations. Customers in this region who have been waiting to adopt ManageEngine's cloud offerings can now do so with confidence."
The company also announced the availability of ServiceDesk Plus, its flagship ITSM product, from its newly commissioned EU data centers. Accessible at sdpondemand.manageengine.eu, the service desk app is available in 12 major European languages.
Mobile Device Manager Plus, the company's enterprise mobility management software, will also be accessible from the EU data centers beginning February 2017. Mobile Device Manager Plus service will be available in 13 European languages and support iOS, Android and Windows operating systems. It will be accessible from mdm.manageengine.eu. Subscriptions start with monthly plans charged in euros.
ManageEngine, with 40+ IT management applications in its portfolio used by over 120,000 IT teams worldwide, has in the last decade emerged as a market leader and credible alternative to complex, expensive products from the Big 4. The company has an impressive array of IT management products available as on-premise and SaaS apps. ManageEngine has an extensive partner network of over 20 partners across the EU to support businesses regionally.
More information and contact details of the partners are available at https://www.manageengine.com/me_partners.html.

About ManageEngine

ManageEngine delivers the real-time IT management tools that empower IT teams to meet organizational needs for real-time services and support. Worldwide, established and emerging enterprises - including more than 60 percent of the Fortune 500 - rely on ManageEngine products to ensure the optimal performance of their critical IT infrastructure, including networks, servers, applications, desktops and more. ManageEngine is a division of Zoho Corporation with offices worldwide, including the United States, India, Singapore, Japan and China. For more information, please visit http://buzz.manageengine.com/; follow the company blog at http://blogs.manageengine.com/, on Facebook at http://www.facebook.com/ManageEngine and on Twitter @ManageEngine.
Media Contact:
Ahana Govinda
ManageEngine
ahana.g@manageengine.com
Follow us on Twitter: @manageengine

Monday, January 23, 2017

Mana yang duluan diimplementasikan dlm ITSM ?



PENDAHULUAN

Artikel ini saya tulis dengan maksud berbagi tentang layanan yang dimiliki Equine Advisory Services yaitu IT Service Management (ITSM) berbasis Information Technology Infrastructre Library (ITIL) , dimana di dalamnya akan secara spesifik membahas mengenai incident, problem & change management.

Apakah IT SERVICE MANAGEMENT (ITSM)?

IT Service Management (ITSM) adalah suatu metode pengelolaan aktivitas teknologi informasi yang fokus memberikan layanan prima kepada para pengguna/pelanggannya.
Tujuan utama ITSM adalah menyelaraskan layanan IT dengan kebutuhan pengguna, memperbaiki kualitas layanan TI, dan mengefektifkan penggunaan biaya untuk pengelolaan TI.
“Penerapan ITSM dapat membantu organisasi untuk meningkatkan kinerjanya”
Artikel ini akan membahas sebagian kecil proses-proses yang ada di dalam ITSM, yaitu:
1. Incident Management;
2. Problem Management;
3. Change Management.

APAKAH INCIDENT, PROBLEM & CHANGE MANAGEMENT?

Tidak pernah ada cara yang baku memulai ITSM dalam organisasi. Melalui artikel ini saya akan memberikan panduan mengimplementasikan ITSM dengan 3 proses yaitu incident, problem & change management.
ITSM
Incident Management
Problem Management
Change Management
Incident, Problem & Change Management

1. INCIDENT MANAGEMENT

Incident Management adalah proses pencatatan, penelusuran, penugasan, dan pengelolaan insiden untuk dikomunikasikan dengan pengguna layanan IT. Pengertian insiden menurut ITIL adalah gangguan terhadap layanan IT atau penurunan kualitas dari layanan IT, contohnya seperti: printer error, tidak bisa login ke aplikasi, kegagalan server, dan hal-hal lain yang mengganggu suatu layanan IT dapat dikategorikan sebagai insiden.
Incident Management dijalankan dengan suatu prosedur. Dimulai pada saat User melaporkan terjadi insiden/gangguan, kemudian Helpdesk akan mencatat ke dalam log insiden den membuat tiket insiden. Setelah insiden dicatat, Helpdesk akan mengidentifikasi gangguan yang terjadi, jika insiden dapat diselesaikan oleh Helpdesk maka Helpdesk akan memandu langkah-langkah untuk segera melakukan perbaikan/resolusi terhadap insiden tersebut atau Helpdesk langsung mendatangi User yang melaporkan untuk langsung menangani insiden/gangguan tersebut. Namun jika gangguan/insiden tidak dapat ditangani maka Helpdesk akan melakukan eskalasi ke Tehnical Support yang kompetensinya lebih tinggi. Selanjutnya Tehnical Support akan mengidentifikasi insiden/gangguan yang terjadi dan melakukan penanganan secepat mungkin. Setelah insiden/gangguan selesai ditangani maka Helpdesk akan menutup tiket laporan dan memutakhirkan status insiden menjadi CLOSED.
Incident, Problem & Change Management

2. PROBLEM MANAGEMENT

Problem Management adalah proses yang bertanggung jawab menangani problem lifecycle. Pengertian Problem menurut ITIL adalah penyebab lebih dari sebuah atau lebih insiden. Jika dikaitkan dengan insiden maka biasanya problem terjadi sesudah insiden, penyebab ini umumnya tidak diketahui ketika tiket problem dibuat, dan proses Problem Management bertanggung jawab terhadap investigasi lebih lanjut. Contoh penanganan problem seperti ini disebut dengan Reactive Problem Management dimana investigasi dilakukan setelah insiden terjadi, sebaliknya penanganan problem juga dapat dilakukan sebelum insiden terjadi dengan cara mencari gejala-gejala yang mungkin dapat menimbulkan insiden, proses ini disebut dengan Proactive Problem Management.
Contoh problem management adalah pada hari Senin terjadi server error yang menyebabkan aplikasi hang, setelah dicari penyebabnya incident management team tidak menemukan masalah apapun kemudian server direstart dan aplikasi berjalan normal kembali. Selang seminggu terjadi lagi error yang sama, kemudian incident management team merestart server dan aplikasi pun berjalan normal kembali. Pada saat selesai penanganan insiden yang kedua, incident management team melakukan eskalasi masalah ke problem management. Server yang berulang kali direstart menunjukkan bahwa insiden itu telah berubah menjadi problem, masalah tidak benar-benar tuntas pada saat server hanya direstart.
Pada kejadian di atas maka insiden sudah menjadi problem dan perlu dilakukan investigasi lebih mendalam terhadap error yang terjadi. Metode mencari akar masalah yang menjadi penyebab error di proses problem management dinamakan dengan root cause analysis. Pada saat akar masalah telah ditemukan maka perlu ditentukan perbaikan/resolusi permanen terhadap problem tersebut.
Incident, Problem & Change Management
Gambar berikut merupakan contoh cara mencari akar masalah suatu problem yang disebut dengan 5 Why.
Setelah ditemukan akar masalah pada server, dilakukanlah resolusi permanen berupa penambahan memori untuk mengatasi agar tidak terjadi lagi server error. Akar masalah dan resolusi yang telah dilakukan akan didokumentasikan ke dalam Known Error Database (KEDB) untuk memastikan problem dapat dilihat historinya dan dapat menjadi sumber informasi apabila problem yang sama terjadi lagi di masa mendatang.

3. CHANGE MANAGEMENT

Change Management adalah proses yang bertanggung jawab mengendalikan siklus dari setiap perubahan (change). Tujuan utama dari change management adalah merealisasikan manfaat perubahan dengan meminimalisasi gangguan terhadap layanan.
Change Management dilakukan untuk 2 (dua) alasan, yaitu:
1. Proaktif dengan tujuan mencari benefit yang digunakan untuk mendukung kepentingan bisnis dan/atau peningkatan layanan IT dan/atau peningkatan kemudahan sehingga layanan IT menjadi lebih efektif;
2. Reaktif dengan tujuan untuk menyelesaikan suatu masalah atau adaptasi terhadap lingkungan yang berubah.
Incident, Problem & Change Management
Contoh change management yaitu pada saat melakukan perubahan fungsi pada aplikasi bisnis, langkah yang harus dilakukan adalah mengajukan form Request For Change (RFC), setelah diajukan akan dianalisa dampak, risiko, dan alasan pengajuan perubahan serta dibuat rencana apa yang harus dilakukan apabila perubahan gagal. Setelah RFC disetujui maka harus dibuat perencanaan implementasi perubahan sedetail mungkin untuk memastikan RFC dapat berhasil sesuai tujuan awal. Risiko-risiko yang mungkin terjadi pada RFC yang tidak dikelola dengan baik seperti:
 Perubahan yang tidak/belum disetujui
 Tingkat keberhasilan perubahan yang rendah
 Jumlah perubahan darurat yang tinggi
 Pembengkakan biaya dan waktu
 Ketidaksesuaian requirement dengan hasil perubahan
“Tidak ada perubahan yang tidak berisiko, maka siapkan rencana yang matang”

4. HUBUNGAN INCIDENT, PROBLEM & CHANGE MANAGEMENT

Incident, problem, dan change management adalah proses-proses yang berhubungan dalam pengelolaan ITSM. Insiden yang berulang membuat insiden itu menjadi problem, dan untuk problem yang sudah diketahui akar masalahnya diperlukan change management untuk resolusi/perbaikannya. Sehingga dapat dilihat ketiga proses ini saling terkait dan dapat dengan mudah diterapkan untuk memulai ITSM dalam suatu organisasi IT.
Incident, Problem & Change Management

KESIMPULAN

Dari pemaparan di atas dapat disimpulkan ITSM adalah konsep pengelolaan layanan dengan menjalankan proses-proses seperti area incident, problem & change management, dengan cara memastikan pencatatan dan penanganan insiden; melakukan analisa insiden-insiden berulang; dan menjalankan mekanisme change management jika diperlukan perubahan untuk perbaikan insiden/problem. Penerapan ITSM yang konsisten akan memberikan banyak manfaat bagi suatu organisasi IT dalam mendukung pencapaian tujuan bisnis.

Apa beda ITSM dan ITIL ?

ITSM vs. ITIL: What’s the Difference?

1.5K491103

Free Download: ITIL 5 Book Set Get the booklets

If you’re not sure whether you need ITSM or ITIL®, then I’m pretty sure you’re asking the wrong question. It’s not an “either/or” decision. IT service management (ITSM) is what you do to manage the services you deliver to your customers, even if you don’t actually use that term. ITIL is a best practice framework for ITSM, and you should think about adopting some ideas from ITIL to help you work more effectively.
difference between ITIL and ITSM
Here’s what you need to know about ITSM and ITIL, and how each can contribute to the success of your IT organization.

Difference between ITSM & ITIL

Let’s start with a quick overview of what these terms stand for:
  • ITSM is an acronym for IT service management. It simply means how you manage the information systems that deliver value to your customers. Even if you’ve never heard the term ITSM, if you’re running IT systems, then you are doing ITSM. ITSM could include activities like planning and managing changes so they don’t cause disruption to the business, fixing things when they go wrong, or managing a budget to ensure you can pay the bills when they arrive. People who use the term ITSM tend to think of IT as a means of delivering valuable services to their customers, rather than as a way to manage technology—but even if you have a completely technical focus, your work still needs to be managed, and that’s what we call ITSM.
  • ITIL is the name of the world’s most widely recognized framework for ITSM. ITIL is a registered trademark of AXELOS, which owns a range of best practice solutions and their corresponding publications and exams. ITIL has been adopted by many organizations, and there are millions of certified ITIL practitioners worldwide.

Benefits for ITIL

It is likely that some—probably many—of the ITIL best practices would prove beneficial to your organization. Organizations that adopt ITIL often find that they:
  • Improve the alignment of IT to their business, providing services that better meet the needs of their customers.
  • Improve the quality of the IT services they deliver by understanding the required levels of availability, security, capacity, and continuity, and then planning solutions that are able to deliver these.
  • Lower the cost of delivering IT by reducing wasted effort and focusing on getting things right the first time.
You don’t have to adopt ITIL to manage your IT services effectively and efficiently, but it can certainly help. Some organizations simply create their own set of processes for running IT, and this can work. But it’s hard to develop something original that matches the years of experience that have gone into the development of the ITIL best practice framework that has now been adopted by many thousands of organizations.
Adopt and Adapt to Fit Your NeedsIT organizations that make use of ITIL decide for themselves which aspects to adopt. Many IT organizations choose to adopt only the operational processes, such as incident management and change management. On their own, these do provide some value, of course, but they are only a small part of the whole ITIL framework. However, you’ll get the best value from ITIL by taking a lifecycle approach to ITSM. This covers everything from your overall IT strategy through the design, transition, and operation of services; and it incorporates continual improvement into everything you do.
When your organization has made the decision to adopt a best practice framework, a smart strategy is to understand which approach will be a good fit for your organizational culture and to incorporate it into your own management system in a sympathetic way. I have worked with many organizations that start our relationship by telling me they tried ITIL a few years ago, but it didn’t deliver any value. When I investigate what happened, I usually discover they attempted to adopt a rigid set of processes, with no understanding of how they would fit within the culture of their organization. As a result, people would ignore the new processes—so the money spent on the project ended up being wasted. The right way to use ITIL is summarized in the phrase “adopt and adapt.” You only adopt the parts that you need, and you adapt the ideas to fit your environment rather than slavishly following the guidance.

Additional Frameworks to Explore


The smartest organizations tend to use other standards or best practice frameworks in combination with ITIL. This can be very effective as each approach brings something different to the mix. For example:
  • COBIT is a very good framework for governance, audit, and compliance. It is much stronger than ITIL in these areas, and the two work very well together.
  • Agile and DevOps help to ensure the IT organization quickly delivers new business functionality. They often conflict with ITIL because of cultural differences between the people who adopt them, but they can fit together very well if the organization understands the value provided by each.
  • Lean can be used to drive continual improvement and elimination of wasted effort. It is a great fit with ITIL continual improvement.
If you run IT services, you owe it to your customers to adopt ideas that will make you effective, efficient, and agile. So maybe it’s time you had another look at ITIL to see what it has to offer.

Here are practical methods for developing a best practice framework


ITIL Guides
Each “Best Practice Insights” booklet highlights important elements from the latest version of ITIL so that you can quickly understand key changes and actionable concepts for your organization.