Quantcast
Channel: BLOG DAYA CIPTA MANDIRI GROUP
Viewing all 2824 articles
Browse latest View live

Smart Manufacturing di masa Covid19

$
0
0


 Salah satu industri terdampak pandemi Covid19 adalah manufacturing. Mungkin tidak semua bidangnya, tapi sebagian besar pasti terganggu. Pengalaman China yang hingga 3 bulan mematikan semua ‘mesin’ manufakturnya, dan harus bangkit kembali dalam waktu singkat.

Ada beberapa hal yang mungkin sama dengan kondisi China, yaitu kita masih memiliki manufaktur yang padat karya, masih banyak pekerja. Keduanya juga memiliki pasar yang besar, yang diyakini masih akan memerlukan produk manufaktur. Tapi seberapa cepat bisa bangkit dan pulih kembali, semua kegiatan produksi, target produksi, dan distribusi serta penjualan. Ini yang mungkin harus kita evaluasi.

Pemerintah kita telah mencanangkan Industri 4.0 sejak April 2018, dan disana menjadi tugas dan tanggung jawab dari kementerian Perindustrian untuk bisa memaksimalkan potensi manufaktur Indonesia dengan menggunakan teknologi informasi.

Beragam program telah dibuat, tapi masih saja ada kendala. Terutama terkait dengan implementasi teknologi informasi yang digunakan untuk mempercepat Industri 4.0 bisa digunakan dan terjadi di kalangan manufaktur. Kalau kita bicara manufaktur skala menengah hingga besar, maka hanya manufaktur besar saja yang telah memaksimalkan potensi ini. Dan ini memang umumnya ada di 5 industri target Making Indonesia 4.0. Lainnya, terutama IKM (Industri Kecil Menengah) masih harus bergelut dan bingung memulai dari mana. Tidak hanya karena faktor pengetahuan, tapi juga biaya investasi yang harus mereka lakukan.

Coba kita lihat apa yang bisa IKM mulai lakukan terkait Smart Manufacturing, terutama di kala pandemi ini. Kali ini kita akan melihatnya dari aspek konsumen.

  1. Konsumen merasa sulit berbisnis dengan manufaktur. Konsumen merasakan sulit mencari informasi tentang produk yang diproduksi, informasi lengkap produk, bagaimana menghubungi tim sales dan teknis yang mengerti. Belum lagi mereka juga kesulitan melakukan order. Dan ada juga keluhan konsumen karena mereka tidak tahu kapan produk yang mereka order akan selesai. Kapan produk akan diantar ke tempat mereka. Belum lagi konsumen komplain dengan kualitas produk.
  2. Konsumen inginnya memesan seperti di marketplace. Karena semua merasakan kemudahkan melakukan order, melihat produk, bahkan tahu kapan produk akan diantar, kapan akan siap, maka konsumen menganggap manufaktur bisa melakukan seperti yang marketplace lakukan. Mungkin dalam beberapa hal bisa, karena tetap ada pre-order yang harus dilakukan.
  3. Konsumen ingin self service portal. Dari self service portal, konsumen ingin bisa melihat semua. Mulai dari order, hingga komplain , serta informasi produk.
  4. Konsumen ingin order tepat waktu. Ini pasti keinginan konsumen, tapi apakah mereka bisa melihat semua proses nya, ada kendala apa, apa yang terjadi. Transparansi dituntut tinggi oleh konsumen saat ini.
  5. Konsumen komplain karena tidak bisa melihat inventori secara online. Ini kecenderungan baru, mereka ingin melihat semua termasuk stok, inventor yang ada.
  6. Konsumen ingin semua bisa online saja. Konsumen ingin mereka bisa lakukan semua secara online.

Lalu apa yang harus manufaktur lakukan ?

Perkuat kemampuan produksi dengan implementasi sistem TI. Saya menyebutnya sistem teknologi informasi, karena di dalamnya bisa banyak hal. Mulai dari infrastruktur teknologi informasi, mulai dari koneksi dari mesin produksi, perkabelan yang diperlukan, hingga implementasi sistem informasi, seperti Customer Relationship Management (CRM), Enterprise Resource Planning (ERP), dan perangkat sistem yang menghubungkan mesin produksi, peralatan di area produksi , yang bisa dimonitor , diintegrasikan satu dengan lainnya. Diintegrasikan dengan customer portal. Dari sini mereka bisa melakukan banyak hal.

Mungkin ada juga yang sudah punya ERP, atau minimal Sistem Akunting, maka tinggal buat Customer Portal. Beberapa memulai dalam konteks sebagai Customer Support Portal , atau Helpdesk System. Tapi di dalamnya sudah bisa melakukan order, bisa menerima komplain (Service Catalog), bisa melihat progress produksi (project management).

Lalu pertanyaan selanjutnya, lebih baik membuat sistem atau membeli yang sudah jadi ? Saya sangat menyarankan, membeli atau menyewa sistem yang sudah jadi. Mungkin kendala awal bisa terkait bahasa, atau proses bisnis. Tapi memang itulah seni-nya. Tapi kecepatan implementasinya lebih jelas. Dan investasi nya lebih murah, apalagi bila berbasis cloud. Maka tidak ada biaya infrastruktur TI yang tinggi.

Sudah saatnya, skala Industri Kecil Menengah pun bersiap, menghadapi pandemi tapi tetap produktif, dan kuncinya adalah penggunaan teknologi informasi.

Fanky Christian, PT Kota Cerdas Indonesia


Tips Sebelum memasang AC untuk Ruang Server

$
0
0
Tips sebelum memasang AC
Tahukah Anda? Sebelum memutuskan membeli atau memasang AC, anda perlu mempertimbangkan beberapa hal berikut agar AC tersebut bisa berfungsi maksimal dan efisien.

Penggunaan ruang berpengaruh terhadap suhu ruangan karena pada dasarnya manusia yang mengisi suatu ruangan mengeluarkan kalori yang cukup tinggi. Kamar tidur yang hanya diisi dua orang berbeda dengan ruang keluarga yang frekwensi keluar masuk penghuninya cukup tinggi. Semakin banyak pengguna maka semakin besar daya AC yang dibutuhkan.

👉Ukuran Ruangan

Ukuran ruangan menentukan berapa banyak BTU (british thermal unit) atau kecepatan pendinginan. BTU adalah kecepatan pendinginan untuk ruangan satu meter persegi dengan tinggi standar (umumnya tiga meter). Semakin besar satu ruangan tentunya akan semakin besar pula BTU yang dibutuhkan.

👉Beban pendinginan

Beban pendinginan berasal dari dalam ruangan (internal heat gain). Misalnya dari jumlah penghuni yang nantinya akan berada di ruangan AC. Selain itu juga penggunaan penerangan, seperti lampu. Beberapa jenis lampu mengeluarkan panas yang tinggi, artinya anda juga harus memilih AC dengan daya yang lebih tinggi. Selain dari dalam, beban pendinginan juga berasal dari luar. Seperti cahaya matahari yang mengeluarkan energi panas melalui dinding, atap atau jendela.

👉Banyaknya jendela kaca

Saat ini banyak rumah yang mempunyai jendela kaca atau menggunakan blok kaca (glass block). Apabila ruangan anda menggunakan kaca sebanyak 70% atau lebih, sebaiknya gunakan kaca film yang dapat menahan sinar ultraviolet untuk mengurangi beban pendinginan.

👉Penempatan AC

Untuk jenis AC split, anda harus memikirkan penempatan unit indoor dan outdoor atau kompresor. Pemasangan unit indoor perlu memperhatikan arus angin (air flow) dari blower AC. Penentuan arus angin atau hembusan yang tepat membuat udara yang dikeluarkan lebih merata dan tidak hanya berkumpul di satu titik.
UNTUK Layanan Pelanggan HUBUNGI KONTAK KAMI :
atau klik link di Bio @ruangserver_

#datacenter
#pusatdata
#ruangserver 
#DCMSOLUSI
#IT
#Informasiteknologi
#teknologiinformasi
#ACPresisi 
#acsplit 
#airconditioning 
#pendinginruangan

Perfect Monitoring – Combine PRTG’s Breadth with Flowmon’s Depth

$
0
0

 


Originally published on September 07, 2020 by Simon Bell
Last updated on September 07, 2020 • 14 minute read

PRTG provides a broad overview of the health and performance of networks of all sizes. By combining that breadth of monitoring, with the deep dive traffic analytics of Flowmon, administrators gain insight into what’s happening in their networks.

To find out more about getting insight into your IT with Flowmon and PRTG Network Monitor, sign up for our webinar by clicking this banner (and then read on below):

Free webinar "Integrating Flowmon and PRTG"

Introduction

As everyone knows, PRTG is a proven, all-round infrastructure monitoring tool - network performance, server health, storage availability, service state; we’ve got all that covered. We can even monitor your IoT, medical and industrial environments too.

But what if you need to go deeper – What’s causing that sudden spike in network traffic? Why are users complaining about poor application performance? For that you need a more specialised tool, and that’s where Flowmon comes in.

Now, please don’t make the same mistake I did. When I was asked to take a look at Flowmon’s tool set, I thought “OK, it’s JAFT (Just Another Flow Tool) like all the others out there”. I could not have been more wrong. Yes, the system is based around capturing and analysing flow records, but the Flowmon team have taken that tried and tested technology and done some very cool things with it.

The Flowmon architecture is similar to that of PRTG. There are two main components -

Flowmon Collector acts like PRTG’s Core Server, and is responsible for processing and analysing data, producing reports and providing web-based GUI access. But it also collects the raw flow data for processing, in a similar way to PRTG’s Local Probe.

Flowmon Probe, converts the raw flow data into enriched network telemetry, extracting the detailed metrics contained in the flows which the other components of the system convert into actionable information. This data enrichment is what sets Flowmon apart from standard flow tools.

1-flowmon-architecture-prtg-network-monitor

Both the Collector and Probe are available as physical or VM appliances, with various options for subscription or perpetual licensing that cover all deployment sizes from SME through to enterprise.

Flow Analysis

All the flow data collected by the system is collated and analysed through a centralised, web-based GUI known as the Monitoring Centre. It’s here you’ll find the more traditional xflow tools. The clear interface allows users to quickly create detailed analyses of the collected flow records – bandwidth utilisation, device-to-device conversations, protocol distributions and many other metrics can be added to dashboards. Sophisticated “profile” based filters can be used to focus the reports on specific devices, ports or protocols, including industrial protocols such as GOOSE and IEC 104. Monitoring Centre also allows alerts to created based on numerous conditions and thresholds. These can be chained together and combined with filter profiles to create sophisticated alarm-action relationships that can trigger various notification or remediation events.

2-flowmon-monitoring-centre-prtg-network-monitor

In addition to Monitoring Centre, additional software modules can be added to the system to fulfil specific tasks -

  • Anomaly Detection
  • Application Performance Monitoring
  • Packet Investigator
  • DDoS Defender

Anomaly Detection

Traditional signature & rule-based tools such as firewalls, IDS/IPS and anti-virus systems can be very effective in identifying and defeating compromises based on known malicious code or behaviours. But they mostly focus on securing the network perimeter and endpoints. But of course, not all threat vectors follow a North-South path. Research continues to highlight the risks of East-West, or “insider threats”, those that cannot be detected by network edge focused security tools.

Flowmon’s Anomaly Detection module combines signature-based detection methods with machine learning capabilities, adaptive baselining and advanced heuristics to analyse network traffic and identify potentially malicious activity, including common compromise indicators such as network surveillance activity, lateral movement attempts, exfiltration of data and connections to command & control networks.

3-flowmon-anomaly-detection-system-prtg-network-monitor

Application Performance Monitoring

The IT department exists to provide services to their users. Poorly performing systems and applications can cause frustration and aggravation for customers and employees alike, with corresponding financial and reputational implications. APM systems are the tool of choice for checking on the health and performance of the applications that businesses rely on. Most APM systems require agents to be installed right across network to collect data from devices using the monitored applications. With Flowmon, that extra administrative burden is removed. Because Flowmon APM passively collects and analyses flow traffic from the network, it can provide administrators, DBAs and DevOps teams with a deep understanding of how their applications are performing without having to deploy, patch and manage hundreds or even thousands of agents.

Flowmon’s APM module can measure the two key metrics that determine application performance –

  • Application Response Time (ART), which is the time difference between the last request packet (client – server) and the first response packet (server – client), taking place at layer 7 (application) of the OSI model.
  • Transport Time (TT), the time difference between the first and last packet of a request or a response (depending on conversation direction).

The analysis is further enhanced by capturing full details of SQL queries, URLs, server status codes and more, to provide a great insight on what actually happens as a user interacts with an application.

4-flowmon-application-performance-monitoring-prtg-network-monitor

Packet Investigator

One of the most frequently used utilities in the NOC / SOC analyst’s toolkit is a packet analyser - capable of pulling packets from the network, dissecting them and interpreting them to visualise what is happening on the network. Probably the most commonly used tool in this field is Wireshark, which has been around in various forms since the late ‘90s. While very powerful, Wireshark is a standalone tool, requiring manual configuration and expert knowledge to interpret the captured data.

Flowmon’s Packet Investigator does away with these problems. It’s an automated network traffic auditing tool that records and interprets full packet data from OSI layers 2 - 7. It provides automatic PCAP capture and a built-in expert “analytics engine” which can visualise the captured data and provide remediation suggestions to accelerate problem resolution and reduce downtime.

5-flowmon-packet-investigator-prtg-network-monitor

DDoS Defender

Massively disruptive but unfortunately easy to orchestrate, from the darker corners of the web, Distributed Denial of Service Attacks are a big problem for all network administrators, and especially ISPs. The most common DDoS method is the “volumetric attack” where an internet facing device is maliciously swamped with more traffic than it can process, thus inhibiting its ability to process genuine traffic. This leads to slow responses or even worse complete loss of the effected service. Once these volumetric attacks have reached their target, they are extremely difficult to counter, so the key is to detect the start of an attack as early as possible and take appropriate action.

Flowmon DDoS Defender automates the identification and response to DDoS attacks. The near real time nature of flow analysis allows the system to identify any abnormal increase in traffic in seconds. It can then trigger a variety of remedial actions, depending on the network design and features. This can include diverting traffic through policy-based routing, injecting blocking rules into next-gen firewalls via script or integrating with third party out-of-path mitigation systems.

6-flowmon-ddos-defender-prtg-network-monitor

Dashboards & Reports

Finally, the Dashboard and Reports module allows administrators to create detailed, widget-based dashboards that illustrate the status of the monitored network. The interface is tab based so different views of the data can be provided to different teams.

7-flowmon-dashboards-reports-prtg-network-monitor

The collected data can also be “sliced & diced” using the built-in reporting system. This allows both ad-hoc and scheduled reports to be created, combining data from user defined “chapters” which act as templates to quickly design new report layouts.

So Where Does PRTG Fit In?

I’m glad you asked. As we’ve seen, Flowmon provides superb deep-dive network traffic analytics, application performance and anomaly detection. Combining those capabilities with PRTG’s unrivalled ability for monitoring almost anything with an IP address; gives Sysadmins, NoC / SoC analysts and DevOps teams the best possible toolset for guaranteeing the performance of the network while maximising its security.

There are three ways that Flowmon and PRTG can work together. Flowmon have developed a set of Python based scripts, available through their Customer Portal, that retrieve data from the ADS and Monitoring Centre modules. Combined with PRTG Python Script Advanced Sensors, the collected data can be added to PRTG maps (dashboards) in the usual way. More information about the Python scripts can be found here - How can I integrate Flowmon into PRTG Network Monitor?

Next, as the Flowmon platform includes a REST based API (documentation available from the Flowmon Portal), you can use PRTG’s REST Custom Sensor to retrieve a huge variety of health, performance and analytics data from your Flowmon environment.

8-flowmon-and-prtg-network-monitor

Finally, as also described in the How can I integrate Flowmon into PRTG Network Monitor? Page, Flowman provide SNMP MIB files for their appliances, which can be used with standard PTRG SNMP sensors to monitor the health and performance of your Flowmon devices.

Summary

PRTG is a fantastic tool for keeping administrators informed about the overall health and performance of their systems, be they in traditional IT networks, sprawling IoT deployments or even medical or industrial environments. But, if there is a need to look deeper into the traffic traversing those networks to see how applications are performing, or to detect and mitigate security threats, then the Flowmon suite provides a powerful, tightly integrated set of tools to give administrators that additional insight.

SOURCE: https://blog.paessler.com/perfect-monitoring-combine-prtgs-breadth-with-flowmons-depth

Webinar Strategi Mencegah Kebocoran Data di Era Pandemi 23 Sep 2020

$
0
0

  Pandemi Corona dan pembatasan sosial berskala besar (PSBB) diwarnai bermacam kebocoran data di dunia siber. Kasus kebocoran data ini semakin mengkhawatirkan di Indonesia. Kian masifnya penggunaan internet, makin tinggi intensitas pengaksesan data perusahaan dengan sistem keamanan data yang lemah para sisi pengguna, dan lemahnya perlindungan hukum terhadap kasus kejahatan siber menjadi alasan mengapa kebocoran data semakin bertumbuh.

Lalu, langkah apa yang harus diambil untuk mencegah terjadinya kebocoran data? Ungkap secara lugas di smartfren.BUSINESS konekt webinar series 9 x CISCO “Strategi Mencegah Kebocoran Data di Era Pandemi”



Daftarkan segera diri Anda di: 

https://bit.ly/smartfren23sep


Dapatkan free e-certificate dan berbagai door prize menarik dari Kami!

Mengenal DMARC

$
0
0

 Mencegah spoofing dan phishing dengan DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) adalah metode autentikasi email standar. DMARC membantu administrator organisasi mencegah peretas dan penyerang lain melakukan spoofing terhadap organisasi dan domain. Spoofing adalah jenis serangan yang memalsukan alamat Dari dalam pesan email. Pesan palsu seolah tampak berasal dari organisasi atau domain yang ditiru identitasnya.

DMARC juga memungkinkan Anda meminta laporan dari server email yang menerima pesan dari organisasi atau domain Anda. Laporan ini berisi informasi untuk membantu Anda mengidentifikasi kemungkinan masalah autentikasi dan aktivitas berbahaya untuk pesan yang dikirim dari domain Anda.

Spoofing dan phishing

Spammer dapat memalsukan domain atau organisasi Anda untuk mengirim pesan palsu yang meniru identitas organisasi Anda. 

Pesan palsu sering digunakan untuk tujuan jahat, misalnya untuk menyebarkan informasi palsu atau untuk mengirim software berbahaya. Pesan palsu juga digunakan untuk melakukan phishing, praktik scam yang menipu pengguna agar memasukkan informasi sensitif, seperti nama pengguna, sandi, atau data kartu kredit. Spoofing dapat memberikan pengaruh buruk yang berkepanjangan pada reputasi organisasi Anda dan memengaruhi kepercayaan pengguna dan pelanggan Anda.

Terkadang, spammer memalsukan pesan sehingga pesan tersebut seakan-akan berasal dari organisasi yang dikenal atau sah. Jika spammer menggunakan nama organisasi Anda untuk mengirim pesan palsu, orang yang mendapatkan pesan tersebut dapat melaporkannya sebagai spam. Jika ada banyak orang yang melaporkan pesan ini sebagai spam, pesan asli dari organisasi Anda mungkin juga akan ditandai sebagai spam.

Cara DMARC mencegah spoofing

DMARC memberi petunjuk kepada server email penerima ketika server tersebut menerima pesan yang seolah tampak berasal dari organisasi Anda, tetapi tidak lulus pemeriksaan autentikasi, atau tidak memenuhi persyaratan autentikasi dalam data kebijakan DMARC Anda. Pesan yang tidak diautentikasi mungkin meniru identitas organisasi Anda, atau mungkin dikirim dari server yang tidak sah.

DMARC selalu digunakan dengan dua metode atau pemeriksaan autentikasi email berikut:

  • Sender Policy Framework (SPF) memungkinkan pemilik domain memberikan otorisasi ke alamat IP yang diizinkan untuk mengirim email bagi domain tersebut. Server penerima dapat memastikan bahwa pesan yang seolah tampak berasal dari domain tertentu dikirim dari server yang diizinkan oleh pemilik domain.
  • Domain Keys Identified Mail (DKIM) menambahkan tanda tangan digital ke setiap pesan yang dikirim. Server penerima menggunakan tanda tangan tersebut untuk memastikan bahwa pesan tersebut asli, dan tidak dipalsukan atau diubah saat dikirim.

Mengautentikasi pesan (penyelarasan DMARC)

DMARC memutuskan untuk meluluskan atau tidak meluluskan pesan berdasarkan keselarasan header Dari: dalam pesan dengan domain pengirim ketika SPF atau DKIM memeriksa pesan tersebut. Tindakan ini disebut penyelarasan. Oleh sebab itu, Anda harus mengaktifkan SPF dan DKIM sebelum menyiapkan DMARC untuk domain.

Mengelola pesan yang tidak lulus autentikasi (kebijakan penerima)

Jika server email menerima pesan dari domain yang tidak lulus pemeriksaan SPF atau DKIM (atau keduanya), DMARC akan memberikan petunjuk penanganan pesan tersebut kepada server. Ada tiga opsi yang dapat diambil, yang ditentukan oleh kebijakan DMARC:

  • Kebijakan ditetapkan menjadi none--Tidak mengambil tindakan apa pun pada pesan dan mengirimnya seperti biasa.
  • Kebijakan ditetapkan menjadi quarantine--Menandai pesan sebagai spam dan mengirimnya ke folder spam penerima.
  • Kebijakan ditetapkan menjadi reject--Menolak pesan dan tidak mengirimkannya ke penerima.


Mengirim laporan sehingga Anda dapat memantau dan mengubah kebijakan

Siapkan data DMARC untuk mendapatkan laporan rutin dari server penerima yang menerima email dari domain Anda. Laporan DMARC berisi informasi tentang semua sumber yang mengirim email untuk domain Anda, termasuk server email Anda sendiri dan server pihak ketiga.

Laporan DMARC membantu Anda:

  • Mempelajari semua sumber yang mengirim email untuk organisasi Anda.
  • Mengidentifikasi sumber tidak sah yang mengirim email yang seolah tampak berasal dari organisasi Anda.
  • Mengidentifikasi pesan yang dikirim dari organisasi Anda yang lulus atau tidak lulus pemeriksaan autentikasi (SPF atau DKIM, atau keduanya).

Sebelum menyiapkan DMARC

  • Siapkan SPF dan DKIM untuk domain.
  • Siapkan grup atau kotak surat untuk laporan DMARC
  • Dapatkan informasi login host domain Anda
  • Periksa data DMARC yang ada (opsional)
  • Pastikan email pihak ketiga sudah diautentikasi

sumber: https://support.google.com/a/answer/2466580?hl=id

Menambahkan data DMARC

$
0
0

 

Menambahkan data DMARC

Anda menentukan fungsi DMARC dengan memasukkan data DMARC di setelan DNS domain.

Setelah menyiapkan teks data DMARC, tambahkan atau perbarui data TXT DNS di penyedia domain Anda. Untuk memperbarui data TXT DNS, masukkan baris teks yang menentukan data kebijakan DMARC di konsol pengelolaan untuk penyedia domain.

Setiap kali mengubah kebijakan DMARC dan memperbarui data, Anda harus memperbarui data TXT DNS di penyedia domain.

Subdomain atau domain tambahan

Jika Anda memiliki lebih dari satu domain, lakukan langkah-langkah di bawah untuk setiap domain. Setiap domain dapat memiliki kebijakan yang berbeda dan opsi laporan yang berbeda (ditentukan dalam data).

Jika Anda tidak membuat kebijakan DMARC untuk subdomain, subdomain tersebut akan mewarisi kebijakan DMARC domain induk. Untuk menentukan kebijakan DMARC bagi subdomain, gunakan sp tag kebijakan dalam data DMARC untuk domain induk.

Menambahkan atau memperbarui data

Lakukan langkah-langkah ini di konsol pengelolaan untuk host domain Anda, bukan di konsol Admin. Siapa host domain saya?

Penting: Konfigurasikan DKIM dan SPF sebelum mengonfigurasikan DMARC. DKIM dan SPF harus mengautentikasi pesan setidaknya selama 48 jam sebelum mengaktifkan DMARC.

  1. Siapkan baris atau file teks yang merepresentasikan data kebijakan Anda.
  2. Login ke konsol pengelolaan untuk host domain Anda.
  3.  Cari halaman tempat Anda memperbarui data DNS.
  4. Tambahkan data TXT DNS, atau ubah data yang ada, dengan memasukkan data Anda ke dalam data TXT untuk  _dmarc:
    1. Nama data TXT: Di kolom pertama, di bagian nama Host DNS, masukkan: _dmarc.solarmora.com
    2. Nilai data TXT: Di kolom kedua, masukkan teks untuk data DMARC Anda, misalnya:

      v=DMARC1; p=none; rua=mailto:dmarc-reports@solarmora.com

      Nama kolom mungkin berbeda untuk penyedia Anda. Nama kolom data TXT DNS antara satu penyedia dengan penyedia lainnya dapat sedikit berbeda. Domain yang digunakan di sini adalah domain contoh. Ganti solarmora.com dengan domain Anda sendiri.

  5. Simpan perubahan. 

Format data DMARC

Data DMARC dibuat dalam bentuk baris teks biasa. Teks ini adalah daftar tag dan nilai DMARC, yang dipisahkan dengan titik koma. Beberapa tag wajib diisi dan beberapa lainnya bersifat opsional.

Kebijakan DMARC memberi tahu server penerima tindakan apa yang harus diambil pada pesan yang tidak diautentikasi yang didapatkan dapatkan dari domain Anda. Tindakan yang harus diambil ditentukan dengan tag kebijakan (p) saat Anda menentukan data DMARC.

Ini adalah contoh data kebijakan DMARC. Tag v dan p harus dicantumkan terlebih dahulu, tag lainnya dapat dicantumkan dalam urutan apa pun:

v=DMARC1; p=reject; rua=mailto:postmaster@solarmora.com, mailto:dmarc@solarmora.com; pct=100; adkim=s; aspf=s

Tag data DMARC

TagWajib?Deskripsi dan nilai
v

Wajib

Versi DMARC. Harus berupa DMARC1.

p

Wajib

Menginstruksikan server email penerima tentang tindakan yang harus dilakukan terhadap pesan yang tidak lulus autentikasi.
  • none: Tidak mengambil tindakan terhadap pesan dan mengirimkannya ke penerima yang dimaksud. Mencatat pesan dalam laporan harian. Laporan dikirim ke alamat email yang ditentukan dengan opsi rua dalam data .
  • quarantine: Menandai pesan sebagai spam dan mengirimkan ke folder spam penerima. Penerima dapat meninjau pesan spam untuk mengidentifikasi pesan yang sah.
  • reject: Reject the message. With this option, the receiving server usually sends a bounce message  to the sending server.
pctOpsional

Harus berupa bilangan bulat dari 1 sampai 100. Jika opsi ini tidak digunakan di dalam data, kebijakan DMARC Anda akan diterapkan untuk 100% pesan yang dikirim dari domain.

Menentukan persentase pesan yang tidak diautentikasi tunduk pada kebijakan DMARC. Saat menerapkan DMARC secara bertahap, Anda dapat memulai dengan sebagian kecil pesan. Seiring makin banyak pesan dari domain Anda yang lulus autentikasi dengan server penerima, perbarui data dengan persentase yang lebih tinggi, hingga mencapai 100 persen.

Harus berupa bilangan bulat dari 1 sampai 100. Jika opsi ini tidak digunakan di dalam data, kebijakan DMARC Anda akan diterapkan untuk 100% pesan yang dikirim dari domain.

ruaOpsional

Alamat email untuk menerima laporan tentang aktivitas DMARC bagi domain Anda.

Alamat email harus menyertakan mailto:. Misalnya: mailto:dmarc-reports@solarmora.com

Untuk mengirim laporan ke lebih dari satu alamat email, pisahkan email dengan koma.

Opsi ini berpotensi menghasilkan email laporan dalam jumlah besar. Sebaiknya jangan gunakan alamat email Anda sendiri. Sebagai gantinya, pertimbangkan untuk menggunakan kotak surat khusus, grup, atau layanan pihak ketiga yang memiliki spesialisasi dalam laporan DMARC.

rufTidak didukungGmail tidak mendukung tag ruf, yang digunakan untuk mengirim laporan kegagalan. Laporan kegagalan juga disebut laporan forensik.
spOpsionalMenetapkan kebijakan untuk pesan dari subdomain dalam domain primer Anda. Gunakan opsi ini jika Anda ingin menggunakan kebijakan DMARC yang berbeda untuk subdomain Anda.
  • none: Take no action on the message and deliver it to the intended recipient. Log messages in a daily report. The report is sent to the email address specified with the rua option in the policy .
  • quarantine: Menandai pesan sebagai spam dan mengirimkan ke folder spam penerima. Penerima dapat meninjau pesan spam untuk mengidentifikasi pesan yang sah.
  • reject: Menolak pesan. Dengan opsi ini, server penerima harus mengirim pesan email tidak terkirim ke server pengirim

Jika Anda tidak menggunakan opsi ini di dalam data, subdomain akan mewarisi kumpulan kebijakan DMARC dari domain induk.

adkimOpsionalMenetapkan kebijakan penyelarasan untuk DKIM, yang menentukan seberapa ketat informasi pesan harus cocok dengan tanda tangan DKIM. Pelajari cara kerja penyelarasan.
  • s: Penyelarasan ketat. Nama domain pengirim harus sama persis dengan d=name yang sesuai di header email DKIM.
  • r: Relaxed alignment (default). Allows partial matches. Any valid subdomain of d=domain in the DKIM mail headers is accepted.
aspfOpsionalMenetapkan kebijakan penyelarasan untuk SPF, yang menentukan seberapa ketat informasi pesan harus cocok dengan tanda tangan SPF. Pelajari cara kerja penyelarasan.
  • s: Penyelarasan ketat. Header From pada pesan harus sama persis dengan nama domain di perintah SMTP MAIL FROM
  • r: Penyelarasan longgar (default). Memungkinkan pencocokan parsial. Semua subdomain yang valid dari nama domain dapat diterima.

Why CPU monitoring matters (and what PRTG can do for you)

$
0
0

 

Why CPU monitoring matters (and what PRTG can do for you)

Originally published on July 10, 2020 by Patrick Gebhardt
Last updated on July 10, 2020 • 6 minute read

The CPU is probably the most important component of any device in your network. And that is "probably" as in probably the earth is spherical. CPU obviously has the potential to affect network performance; not only somehow, but in some cases very seriously.

CPU monitoring is the difference between network stability and performance deterioration. Having no powerful and dependable way to monitor the CPU makes the life of every sysadmin quite difficult.

⚡ 3 examples of how a monitoring solution like PRTG can save your day

🦠 WHEN VIRUSES CRASH THE PARTY

IT networks are extremely susceptible to malware and viruses. Even sysadmins with the highest security standards are unable to protect their networks entirely. The same goes for medium-sized companies. Their computers get slower and slower, and it’s not long before the support desk receives its first complaints.

With our CPU monitoring tool, sysadmins can quickly tell if the CPU load is too high – even when few employees are actually working. They’ll also be able to recognize if data traffic is unusually high. As a result, they can immediately set out in search of malware, find it, and fix the damage.

🐌 WORK PROCESSES ARE GETTING TOO SLOW

It is not uncommon for certain areas of a company to detect disruption, but because the problems are not too big, IT is either not informed at all or is informed far too late. A snowball may have turned into an avalanche in the meantime. The result: gradually all the company's work processes become slower.

  • PRTG CPU monitoring software allows administrators to quickly diagnose their server CPU utilization.
  • You will see the effect new software has on CPUs as soon as it is installed.
  • This means you can act promptly.

🛍️ THE ONLINE STORE IS DOWN

A company launches a web campaign. Its website traffic increases dramatically. Consequently, CPU utilization on the web server soars. Within a few hours, the online store is running at a snail's pace. Few orders reach the final checkout stage.

The positive effect of the campaign is squashed as customers become frustrated with the slow website or find they can no longer use the service as their requests time out.

Here too, administrators are informed quickly about the increased CPU usage. PRTG comes with a built-in notification system that you can configure yourself. Choose to be notified by email, or in emergencies by SMS. Once notified, you can quickly get to work to find a solution.

🔥 Another very vivid example: CPU temperature.

  • Processor temperature: It's simple physics: When the load increases, the processor’s core gets hotter. Overheating can occur when certain loads are reached or when a fan malfunctions or goes down. Savvy sysadmins like to overclock the CPU to increase performance. But overclocking can lead to overloading and excessive heat. Most CPUs come with overheat protection. If they get too hot, they shut down automatically.
  • Checking the CPU temperature: The maximum recommended processor temperature is usually provided by the manufacturer. PRTG System Health sensors check the temperature of CPUs from a variety of different manufacturers. Sysadmins can also use the SNMP Custom Sensor to check the temperature of devices (provided they are compatible with SNMP), and define the temperatures which, when exceeded, will trigger an alarm. In other words, they define threshold values for themselves.
  • Stopping CPU failure in its tracks: If a critical value is reached, IT managers will immediately receive a notification. This lets them quickly take action before the CPU fails completely. CPU monitoring increases the stability of the entire network. The network crashes a lot less frequently – which saves the company considerable time and money.

🖥️ PRTG sensors for monitoring your CPU

PRTG features 200 preconfigured sensors. During installation, PRTG will scan your network and create appropriate sensors, saving you lots of time. Take charge of CPU utilization with PRTG and get to the root of problems. With PRTG you can easily

  • estimate load
  • identify problems
  • create reports
  • get the full picture
  • trust customizable upgrades

iAbout sensors In PRTG, “Sensors” are the basic monitoring elements. One sensor usually monitors one measured value in your network, e.g. the traffic of a switch port, the CPU load of a server, the free space of a disk drive. On average you need about 5-10 sensors per device or one sensor per switch port.

Lesson Learned Dari Insiden Email Spamming

$
0
0

  

Salah satu stakeholder kami mengalami insiden berupa email spamming dan meminta bantuan Gov-CSIRT Indonesia, kami pun langsung merespon insiden tersebut dan memberikan asistensi untuk tindakan korektif dengan men-setting mail filtering dan otentikasi email, melakukan test konfigurasi, test kirim terima email biasa dan email mengandung virus, serta memberikan rekomendasi teknis lainnya. Selengkapnya disampaikan pada artikel ini.


Terjadi Insiden Siber berupa Email Spamming

Suatu ketika masuk laporan insiden siber berupa spamming pada email server di stakeholder kami,. Untuk mendeteksi bahwa terjadi insiden berikut adalah ciri-ciri dari insiden email spamming :

  1. kirim terima email terganggu. Ada kalanya tidak bisa mengirimkan email atau menerima email, bahkan keduanya sekaligus;
  2. dari log diketahui bahwa terdapat alamat email tertentu yang melakukan spamming yaitu mengirimkan email dalam jumlah yang besar dalam waktu yg singkat. Hal ini berarti kemungkinan besar pengiriman email dilakukan menggunakan engine.

Kami selaku Tim Gov-CSIRT Indonesia pun bergegas melakukan penanganan secara onsite. Setibanya di lokasi, kami diterima dengan baik oleh tuan rumah selaku pelapor dan langsung diantar ke data center dan diperkenalkan dengan staf teknis TIK yang menangani infrastruktur dan server. Kami pun langsung melakukan observasi.

Observasi Awal

Adapun email server yang dimaksud memiliki spesifikasi berikut :

Sistem OperasiAplikasi Email Server
Ubuntu versi 18Kolab Community versi 1.8

Setelah melakukan observasi awal kami mendapatkan fakta-fakta sebagai berikut :

  1. Insiden email spamming terjadi pada beberapa alamat email saja dan pemilik alamat email sudah dihubungi oleh administrator untuk berkoordinasi namun bersikap kurang kooperatif. Hal ini menyebabkan administrator bingung menentukan penyebab insiden : apakah email spamming terjadi karena komputer pemilik alamat email di-hack atau penyebab lainnya;
  2. Staf teknis TIK sudah berusaha menangani insiden ini dengan cara me-reset password, namun email spamming tetap terjadi;
  3. Kirim terima email tidak berjalan dengan baik, yaitu seringkali email yang dikirimkan tidak sampai tujuan;
  4. Kirim terima email merupakan bagian dari proses bisnis aplikasi yang digunakan instansi tersebut. Sehingga proses bisnis aplikasi menjadi terganggu;
  5. Administrator sering melakukan akses secara remote ke server menggunakan SSH, namun ketika ditanya mengenai konfigurasi SSH rupanya sudah menerapkan konsep hardening namun belum memadai. Hardening ini penting dilakukan guna mencegah serangan brute force/dictionary attack ke port SSH. Namun apakah SSH ini yang menyebabkan terjadinya insiden? Belum diketahui juga.

Sebenarnya selain melakukan observasi di atas, bisa juga dilakukan analisis melalui test secara online atas konfigurasi email server. Berikut adalah beberapa website gratis yang bisa melakukan test atas konfigurasi email server :

  1. Email Server Test – Online SMTP Diagnostic Tools pada tautan https://mxtoolbox.com/diagnostic.aspx;
  2. Test Your SMTP Mail Server (MX) pada tautan https://www.wormly.com/test-smtp-server.

Akhirnya setelah melakukan observasi lebih lanjut ternyata email server tersebut memiliki topologi yang kurang ideal, yaitu email server tersebut terkoneksi begitu saja ke internet tanpa perangkat pengamanan apapun. Berikut adalah gambaran dari topologi yang dimaksud.

Gambar 1. Topologi jaringan di email server.

Tindakan Korektif untuk Insiden Email Spamming

1. Mail Filtering

Setelah Tim Gov-CSIRT Indonesia melakukan analisis terhadap file log di server, didapatkan kesimpulan bahwa email server ini tidak memiliki konfigurasi email filtering. Rupanya inilah penyebab utama terjadinya insiden email spamming. Maka staf teknis TIK kemudian melakukan konfigurasi email server dengan panduan tutorial pada tautan : https://help.ubuntu.com/lts/serverguide/mail-filtering.html.en. Kemudian dilakukan restart atas email service.

2. Menambah Trust Dengan Otentikasi Email

Otentikasi email membantu meningkatkan pengiriman dan kredibilitas email dengan menerapkan protokol yang memverifikasi domain yang mengirimkan pesan. 
a. SPF (Sender Policy Framework) 
SPF adalah cara bagi penerima untuk mengkonfirmasi identitas pengirim email yang masuk. SPF berupa entri teks DNS yang menunjukkan daftar server yang dizinkan untuk mengirimkan email ke domain tertentu. Berikut adalah alur otentikasi email menggunakan SPF :

  1. Setelah menerima pesan HELO dan alamat pengirim diambil oleh server surat penerima;
  2. Email server penerima menjalankan kueri TXT DNS terhadap entri domain SPF yang diklaim;
  3. Data entri SPF kemudian digunakan untuk memverifikasi server pengirim;
  4. Seandainya cek gagal, pesan penolakan diberikan ke server pengirim.
Gambar 2. Otentikasi email menggunakan SPF.

b. DKIM (Domain Key Identified Mail) 
DKIM adalah metode untuk identifikasi email “palsu” tetapi menggunakan 2 (dua) kunci pada kriptografi asimetrik: kunci publik dan kunci privat. Kunci privat ditempatkan di lokasi yang aman yang hanya dapat diakses oleh pemilik domain. Kunci privat ini digunakan untuk membuat tanda tangan terenkripsi yang ditambahkan ke setiap pesan yang dikirim dari domain itu. Menggunakan tanda tangan, penerima pesan dapat memeriksa terhadap kunci publik DKIM, yang disimpan dalam catatan DNS yang menghadap publik. Jika record-nya “cocok”, maka email hanya bisa dikirim oleh orang yang memiliki akses ke kunci privat, alias pemilik domain. Adapun panduan untuk melakukan konfigurasi pada DKIM dan SPF dapat dilihat pada tautan : https://www.linuxbabe.com/mail-server/setting-up-dkim-and-spf.

  1. Saat mengirim pesan keluar, server terakhir dalam infrastruktur domain memeriksa terhadap pengaturan internal jika domain yang digunakan dalam header “From:” termasuk dalam “Signing table“. Jika tidak prosesnya berhenti di sini;
  2. Header baru, yang disebut “DKIM-Signature“, ditambahkan ke pesan email dengan menggunakan bagian pribadi dari kunci pada konten pesan;
  3. Konten utama email tidak dapat diubah, jika tidak maka header DKIM tidak akan cocok lagi;
  4. Pada penerimaan, server penerima akan membuat DNS TXT query untuk mengambil kunci yang digunakan di DKIM-Signature field;
  5. Hasil pemeriksaan header DKIM kemudian dapat digunakan ketika memutuskan apakah suatu email dapat dipercaya atau curang.
Gambar 3. Otentikasi email menggunakan DKIM.

c. DMARC (Domain-based Message Authentication, Reporting, and Conformance) 
Sementara SPF dan DKIM dapat digunakan sebagai metode yang berdiri sendiri, DMARC harus mengandalkan SPF atau DKIM untuk memberikan otentikasi. Berikut adalah skema otentikasi email menggunakan DMARC :

  1. Pada saat penerimaan, server surat penerima memeriksa apakah ada kebijakan DMARC yang ada yang diterbitkan dalam domain yang digunakan pada pemeriksaan SPF/DKIM;
  2. Jika pemeriksaan pada salah satu atau keduanya (SPF dan DKIM) berhasil, kemudian hasil pemeriksaan akan disejajarkan dengan kebijakan yang ditetapkan oleh DMARC. Hasil pemeriksaan apabila sesuai maka dianggap berhasil, namun jika tidak sesuai maka ditetapkan sebagai gagal;
  3. Jika hasil pemeriksaan gagal, maka berdasarkan tindakan yang dilakukan berdasarkan kebijakan DMARC.
Gambar 4. Otentikasi email menggunakan DMARC.

Adapun panduan konfigurasi DMARC berdasarkan pada tautan : https://www.esecurityplanet.com/applications/how-to-set-up-implement-dmarc-email-security.html.

3. Test Konfigurasi

Setelah staf teknis TIK melakukan konfigurasi email filtering, dilakukan test secara online dan didapatkan hasil sebagai berikut :

Gambar 5. Hasil test konfigurasi SMTP pada email server.
Gambar 6. Alamat IP email server yang masuk dalam beberapa blacklist.

Dengan demikian, dapat disimpulkan bahwa :

  1. Tindakan korektif sudah tepat sehingga email server tersebut bukan merupakan open relay yang sangat rentan terjadi email spamming. Open Relay maksudnya mail tersebut memperbolehkan pihak luar (di luar network yang telah didefenisikan) untuk mengirim email via email server tanpa otentikasi. Akibatnya, ketika email server menjadi Open Relay adalah :
    • Email server tersebut akan digunakan untuk mengirim email-email spam. Dampaknya kemudian alamat IP dari email server akan di-block karena terindikasi melakukan spamming;
    • Email server diambil datanya dan digunakan untuk tujuan yang tidak seharusnya. Saat ini alamat IP dari email server masih di-block oleh beberapa blacklist. Oleh karena itu perlu menyampaikan permohonan ke blacklist terkait agar alamat IP tersebut dapat di-release.
  2. Saat ini alamat IP dari email server masih di-block oleh beberapa blacklist. Oleh karena itu perlu menyampaikan permohonan ke blacklist terkait agar alamat IP tersebut dapat di-release.

4. Test Kirim Terima Email Biasa

Pada pengujian ini, email server bisa menerima email yang dikirimkan dari domain lainnya. Namun email server belum bisa mengirimkan email ke domain lainnya karena alamat IP dari email servermasih di-block, butuh waktu untuk me-release block tersebut.

5. Test Kirim Email Mengandung Virus

Ketika melakukan konfigurasi mail filtering, terdapat engine ClamAV yang berfungsi untuk mem-filter apabila terdapat virus yang dikirimkan melalui email. Untuk menguji hal ini dilakukan pengiriman email yang mengandung virus berdasarkan tutorial pada tautan : https://easyengine.io/tutorials/mail/server/testing/antivirus, kemudian dilakukan pengecekan terhadap log dan didapatkan bahwa engine sudah bisa mem-block email tersebut :

Gambar 7. Log pada email server.

Rekomendasi Keamanan Lainnya

Selain melakukan tindakan korektif, kami juga memberikan beberapa rekomendasi teknis untuk meningkatkan keamanan siber yaitu :

  • Diperlukan topologi jaringan yang lebih baik sehingga dapat mencegah serangan siber dan menjaga kontinuitas bisnis. Berikut adalah topologi jaringan yang disarankan :
Gambar 8. Topologi jaringan yang disarankan.
  • Apabila email server tidak dilindungi oleh firewall perangkat keras, maka diperlukan firewall perangkat lunak pada dengan network policy yang ketat namun sesuai kebutuhan. Network policy yang dimaksud diantaranya membuat whitelist terhadap koneksi inbound dan outbound, selain itu di-deny.
  • Selama ini staf TIK sering mengakses server secara remote menggunakan SSHTerkait hal tersebut diperlukan hardening pada SSH untuk meminimalisir risiko terhadap dictionary/brute force attack yaitu dengan menambahkan konfigurasi :
PermitRootLogin noTidak mengizinkan login dengan akun root
MaxSessions 2Session maksimal 2 user
PubkeyAuthentication yesMengaktifkan otentikasi dengan public key
PasswordAuthentication noMenonaktifkan otentikasi dengan password
  • Perlu personil yang menguasai IT Security, sehingga bisa melakukan identifikasi terhadap celah-celah keamanan(vulnerability)dan melakukan hardening terhadap vulnerability yang ditemukan. Personil dapat mengikuti pelatihan yang berelasi dengan IT Security, seperti Certified Ethical Hacker (CEH) untuk memahami teknik hacking yang dilakukan oleh hackerCertified Hacking Forensic Infestigator (CHFI) untuk dapat mengetahui teknik investigasi forensik apabila terjadi hacking, serta pelatihan IT Security lainnya   
  • Diperlukan edukasi dan sosialisasi kepada pengguna TIK mengenai penggunaan layanan TIK (seperti internet dan e-mail) secara aman.

 sumber: https://csirt.bppt.go.id/2019/05/28/lesson-learned-dari-insiden-email-spamming/





Webinar How to deliver a seamless customer service experience while staying compliant - 20 Okt 2020 - 2 pm

$
0
0

MotadataWebinarDCM

Everyday IT processes in banks and financial institutions are met with complicated challenges that need to be resolved with exceptional precision and consistency. In order to satisfy the needs of customers who use the online and mobile financial services, banks and financial firms need to employ an effective ITSM platform to provide smooth service delivery while strictly complying with regulatory requirements.

    Register Now

    In this webinar, you will discover the following benefits of ITSM in BFSI:

    • Software Compliance with Security Guidelines
    • IT Operations Automation for Internal Services
    • Process Optimization for Customer Experience & Satisfaction
    • SLA Management for Efficient Service Delivery

      Webinar Agenda

      • Motadata Company Overview & ServiceOps Platform
      • Common service management challenges faced by BFSI 
      • How ServiceOps can help you deliver a seamless customer  service experience while staying compliant
      • Demo of BFSI Use Cases by Expert
      • Q/A
      Network MonitoringITSMLog MonitoringLog Monitoring
      www.motadata.com
      Follow Us:   
      © 2020 Mindarray Systems Pvt. Ltd., All right reserved.

      APTIKNAS CYBERSECURITY CHAPTER - PHISING & CREDENTIAL BREACH PROTECTION 21 OKT 2020

      $
      0
      0

       APTIKNAS CYBERSECURITY CHAPTER - PHISING & CREDENTIAL BREACH PROTECTION 21 OKT 2020 kembali menyapa para pecinta CYBERSECURITY INDONESIA, dengan membahas :

      - Bagaimana proteksi domain anda dari email pishing ?

      - Bagaimana melindungi data kredensial anda ?  

      Semua dalam webinar di 21 Okt 2020, jam 14-16 WIB, segera daftar di https://s.id/acsc21okt



      Ditunggu kehadirannya


      ITSM vs ITIL

      $
      0
      0

      When implementing an IT service management platform in an organization, there's this common confusion between ITSM and ITIL. You must have asked yourself, "What is needed, ITSM or ITIL?"
      #ITSM and #ITIL aren't the same things.

      ITSM is a #software solution used by #IT teams to implement, manage, and deliver #ITServices to meet the needs of an organization.

      On the contrary, ITIL (IT Infrastructure Library) is a popular ITSM #bestpractice#framework designed to standardize the selection, planning, delivery, and maintenance of IT services within a #business. ITIL has 5 core volumes such as Service Strategy, Service Design, Service Transition, Service Operation, and Continual Service Improvement.

      Even though the end-goal for both is to improve #efficiency and achieve reliable service delivery, it's good not to confuse the two terms, and absolutely wrong to use them interchangeably because as far as ITSM is concerned, it is not technology-focused rather the focus is on customers.

      ITSM is the 'What' and ITIL is the 'How' of IT service delivery. To know more, check our blog:

      https://www.motadata.com/blog/difference-between-itil-and-itsm/

      We are #Motadata partner offer a unified ITSM platform#ServiceOpss which is PinkVERIFY certified and ITIL compliant.

      #Motadata#dcmsolusi#itsm#itam#service#servicedesk

      4 Ways to reduce alert noise in enterprise IT

      $
      0
      0

       

      4 Ways to reduce alert noise in enterprise IT

      Originally published on October 02, 2020 by Shaun Behrens
      Last updated on October 02, 2020 • 9 minute read

      Enterprise IT — which we (Paessler) loosely define as infrastructure with over 1,000 devices — is a special beast to manage, with many challenges to overcome. One of the biggest issues that IT teams in these large environments face is alert noise. This happens when you're monitoring your infrastructure, network, storage, cloud services and other elements of your IT, and generating alerts and notifications for failures or impending failures. Too much alert noise makes it downright difficult to identify serious problems, and it might even mean ignoring alerts and missing what really matters. Your monitoring efforts are compromised, and the quality of your service goes down.

      If you've got the feeling that your alerting situation is out of hand, I've got some suggestions for you to try out. And if you want other ideas of how to effectively monitor your infrastructure, download our free guide to monitoring enterprise IT.

      New call-to-action

      But before we get into the suggestions of reducing alert noise, let's consider why there are so many alerts in the first place.

      What causes alert noise, and why it's dangerous

      Enterprise IT environments are complex and heterogenous, with hundreds and thousands of devices and applications from many different vendors. Usually you end up with a variety of different monitoring tools, each of them monitoring separate aspects of your IT and each sending a lot of notifications and alerts for every detail within their monitoring range. Because there are so many alerts from so many different tools, it’s almost impossible to match an alert to the responsible team member. All alerts end up in a central IT inbox, and it's easy to lose the overview.

      Another problem is assigning the correct importance of an alert. Just a simple example: Getting the alert that a server is running out of memory is helpful when you’re only running five servers in your server room. If you have 5.000 servers in your data center, this alert is not helpful. You need to be able to prioritize and focus on the most important alerts for issues that will cause major failures and outages. 

      Another common characteristic of large infrastructure is distributed networks, where the enterprise is spread over various locations, often with more than one data center. If you're managing the networks in a central location, all alerts are probably being sent to the central team.

      All of this means that it's easy for alerts to get out of hand. And the fact is: if you have too many alerts, they might become meaningless. Either that, or the noise means that important indications of failure are missed. Or both.

      How to reduce alert noise

      Reducing alert noise in your organization takes a combination of careful, strategic planning and the right monitoring tool. Here are some ways to reduce alert noise.

      1) One monitoring tool

      003183-prtg-plusConsolidating your monitoring into one tool has benefits beyond alerting, but for this article we'll only focus on alerting. Instead of multiple tools with different ways of alerting you when there are problems, you should aim to have a single tool. This means that when there are alerts, you have one source to go to in order to find the underlying problem.

      Additionally, because different tools handle alerting and notifications differently, a single tool means that you can apply the same philosophy across the board.

      2) Set the right thresholds

      Alerts are based on thresholds: when a device gets hotter than a certain temperature, or when available storage drops below a certain number of gigabytes, then alerts must be triggered. So it stands to reason that good alert management is based on setting the right thresholds. Set them too low, and you'll get inundated with alerts; set them too high, and you won't get notified when there's an issue until it's already too late.

      That might sound easy, but how do you manage this when you have thousands monitored devices and applications? That’s exactly why it is crucial to have a monitoring solution that offers automation and other mechanisms like inheriting thresholds for groups of devices.

      3) Define response teams and filter alerts

      This one requires that you have a monitoring tool with comprehensive rights and roles functionality. This will let you easily create roles and responsibilities for specific teams (or even individuals), and to filter alerts accordingly.

      For your monitoring concept, define the user groups according to the areas that they focus on. Then, you define notifications for failures in those areas to go to the specific teams that need to know. For example, you might have an IT team that handles your online store, and another team that handles the E-mail services. In this example, you would configure that the team handling the online store only receives alerts relevant to that area, and the same for the team handling the E-mail services.

      This way, alerts get sent only to the relevant teams.

      4) Define high-level alerts for management and business stakeholders

      Not everyone in your organization needs to know what's going on behind the scenes of your infrastructure. Your IT teams do, sure, but quite often decision makers, management, and other business stakeholders only need to know the health of the network at a very high level.

      A good strategy is to organize your infrastructure into IT services according to business processes. For example: your company’s E-mail service, the licensing system, or software build processes are all IT services provided by several connected bits of hardware, software and connectivity.

      Let's take the E-mail service as an example. You would map the mail server, storage servers, and the internet connection components of your infrastructure to the "E-mail" business service. Now, if there is a minor failure to one of those components — such as a redundant mail server has performance problems — the E-mail service itself is not endangered because there are fail-over mail servers available. In this instance, only the IT teams responsible get alerted about the performance issues of the server. Management does not need to be alerted.

      However, if there is a service-critical problem — maybe a crash of the core switch all mail data passes through — then the E-mail service itself is endangered, and an alert can be sent to relevant management members or stakeholders.

      How to monitor large scale infrastructure

      Managing alerts is just one piece of monitoring enterprise IT. To get the full guide, which includes tips on how to segment your network and a checklist for selecting a monitoring tool, click on the banner below.

      And I'd love to hear about your biggest challenge with monitoring enterprise IT! Let me know in the comments below.

      Hadiri TEMU UMKM 14 Okt 2020

      $
      0
      0

      TEMU UMKM akan hadir pada hari Rabu, 14 Oktober 2020 yang terdiri dari 3 sesi: Sesi PLENARY, Sesi Temu SATU dan Sesi Temu DUA. Kita bahas satu-satu yuk masing-masing sesinya
      .
      Pada sesi pertama yaitu ada Sesi Plenary, akan dibahas mengenai "Transformasi Digital sebagai Solusi UMKM Hadapi Era Normal Baru" yang akan diselenggarakan pada pukul 14.00 hingga 15.25
      .
      Terdapat banyak sekali pembicara yang merupakan pakar dari pemerintah dan juga dari berbagai industri seperti eCommerce, logistik dan juga asosiasi UKM yang akan memberikan beragam informasi berharga seputar perkembangan UKM di Indonesia
      .
      Hadirilah Webinar TEMU UMKM dengan cara klik link http://bit.ly/temuumkm_web 

      Magic Quadrant for IT Service Management Tools - 2020

      $
      0
      0

       

      Magic Quadrant for IT Service Management Tools

      Published 6 October 2020 - ID G00451024 - 35 min read


      IT service management tools are vital for infrastructure and operations organizations to deliver business value in the services they provide. This research profiles vendors in the enterprise ITSM tool market to help I&O leaders align them against their current and future IT roadmaps.

      Market Definition/Description

      ITSM tools help infrastructure and operations (I&O) organizations manage the consumption of IT services, the infrastructure that supports the IT services and the IT organization’s responsibility in delivering business value with these services. These are most heavily used by IT service desks and IT service delivery functions to support the tasks and workflows for processes including incident, request, problem, change, service level, knowledge and configuration management.
      ITSM tools are classified based on ITSM capabilities and integration with IT operations management (ITOM) solutions, and include:
      • Basic ITSM tools that have core ITSM capabilities such as incident, request and change management, and limited integration with ITOM solutions.
      • Intermediate ITSM tools that have broad ITSM capabilities such as configuration, problem and service-level management, and provide some basic ITOM functions or integrate with intermediate third-party ITOM solutions.
      • Advanced ITSM tools that have a full range of ITSM capabilities, provide advanced workflow support, and, increasingly, AITSM and collaboration capabilities. They also provide broad ITOM functionality natively or integrate with advanced third-party ITOM solutions.
      In response to digital disruption, ITSM tools are beginning to address integration requirements with the DevOps toolchain and support for agile workflows across ITSM processes.
      Vendors are increasingly concentrating product development on non-I&O use cases as market saturation of ITSM tools continues. The adaptation of enterprise service management capabilities outside of ITSM functionality (such as for HR case management or facilities management) are not evaluated in this research.

      Magic Quadrant

      Figure 1. Magic Quadrant for IT Service Management Tools

      Source: Gartner (October 2020)

      Magic Quadrant for IT Service Management Tools

      Vendor Strengths and Cautions

      Axios Systems

      Axios Systems is a Niche Player in this Magic Quadrant.
      Its assyst product is focused on extending ITSM across multiple channels, augmented by a broader set of ITOM and IT business management (ITBM) extensions. It is targeted at organizations with a basic to intermediate level of I&O maturity. Since the last publication of this Magic Quadrant, the vendor has introduced new product bundling for its self-service offerings, updated mobile support features and added integrations into Azure Cognitive Services.
      Strengths
      • ITSM Focus: Axios’ primary revenue source is ITSM tools, which allows it to focus its resources and attention on ITSM products more than competitors that concentrate on different use cases.
      • Customer Engagement: Axios actively leverages numerous customer communication channels to foster user communities, build advocacy and drive most of its product enhancement roadmap.
      • Emerging Markets: Axios has a growing presence in emerging markets, including Latin America and the Middle East, with a broad distribution of revenue across the major geographies.
      Cautions
      • Size: Axios has the smallest market share of the vendors in this Magic Quadrant, and growth in customer numbers and revenue has lagged behind that of its competitors.
      • Product Investment: While Axios focuses on new functionality, some core components are showing their age. Customers have cited the UX and self-service portal as feeling dated compared with other products in the market.
      • Churn Risk: Axios’ strategy of focusing on a smaller number of enterprise customers, rather than on the midmarket, exposes it to higher risk in the case of renewal challenges with these customers.

      BMC

      BMC is a Leader in this Magic Quadrant.
      BMC offers four ITSM products; its flagship product, BMC Helix ITSM, is focused on providing deep ITSM capabilities with integrations into other BMC ITOM solutions on its BMC Helix platform. It is targeted at organizations with intermediate to advanced levels of I&O maturity. Since the last publication, of this Magic Quadrant, BMC released an automation dashboard, introduced ChatOps integrations into third-party collaboration tools, and updated both discovery and AITSM functionality.
      Strengths
      • Advanced ITSM: Gartner’s Critical Capabilities research determined that BMC Helix ITSM scored highest for the advanced I&O maturity use case, indicating it is strongly suited to meet the requirements of highly mature I&O organizations.
      • Partner Network: BMC has built a robust set of channel and technology partnerships that broaden its ability to reach its target customers and integrate adjacent and complementary technology into its platform.
      • ITOM Depth: BMC has a broad ITOM software portfolio, making it a viable partner for mature I&O organizations that need to extend their ITSM tools.
      Cautions
      • Legacy Perception: BMC’s rebranding of its Remedy product and broader BMC Helix platform messaging has yet to resonate with customers that still associate the product with legacy experiences. Gartner clients still commonly see Helix ITSM as a point solution rather than embracing BMC’s broader Helix platform value proposition.
      • Recent Acquisitions: BMC’s 2020 acquisitions of Compuware and RSM Partners reflect its recent investment in the mainframe, rather than acquisitions that directly result in complementary ITSM functionality. In addition, BMC relies on partnerships and integrations for some of its newer features. These have resulted in a perception among some BMC customers of a shifting focus to the mainframe rather than ITSM.
      • Virtual Agent Adoption: Despite its ongoing investment in the feature, BMC has only a small number of customer deployments around its ITSM chatbot technology. Gartner regularly receives calls from clients about virtual agents, but not from clients deploying BMC Helix Chatbot.

      Broadcom

      Broadcom is a Niche Player in this year’s Magic Quadrant.
      Its CA Service Management product is focused on providing core ITSM capabilities integrated into Broadcom’s broader suite of enterprise software products. It is targeted at organizations with intermediate to advanced I&O maturity. Since the last publication of this Magic Quadrant, Broadcom released its chatbot, Aria, Docker container-based deployment and updated APIs.
      Strengths
      • Global Presence: Broadcom’s ecosystem of value-added resellers, system integrators and regional offices provides a far broader global presence than many of its competitors.
      • Product Portfolio: Broadcom has a large software portfolio, creating opportunities for both cross-selling to its core target accounts as well as DevOps alignment through integration with CA Release Automation, Clarity PPM and Rally.
      • MSP Deployments: Broadcom has many managed service provider (MSP) customers on CA Service Management. Its multitenant architecture has enabled Broadcom’s MSPs and hosting providers to support multiple customers on a single implementation of its product.
      Cautions
      • Innovations: The pace of innovation and release cadence for new features lags behind the other advanced ITSM tools in this Magic Quadrant. Broadcom provides limited AITSM support and lacks DevOps integration outside of its own products.
      • SaaS: Customers rarely opt for on-premises ITSM tools, but Broadcom lacks a SaaS-based ITSM tool. Instead, it relies on MSP- and partner-hosted versions of its on-premises product for customers looking for a cloud-based ITSM tool offering.
      • Customer Interest: Broadcom’s focus on marketing CA Service Management directly to a small number of strategic accounts limits its visibility to potential prospects. CA Service Management was very rarely included in Gartner clients’ ITSM tool shortlists over the past two years.

      Cherwell Software

      Cherwell Software is a Challenger in this Magic Quadrant.
      Its Cherwell Service Management product focuses on providing ITSM capabilities built on a low-code platform and extended into other business workflows. It is targeted at organizations with intermediate levels of I&O maturity. Since the last publication of this Magic Quadrant, Cherwell has released a new UI, Slack Integration, sentiment analysis and virtual agent updates.
      Strengths
      • Low-Code Platform: Cherwell demonstrates a platform-style solution that many customers find more easily upgradable and lower maintenance compared with other intermediate to advanced ITSM solutions.
      • Buyer Mind Share: Cherwell continues to enjoy significant mind share among Gartner clients looking at intermediate ITSM tools. It was the second most frequently shortlisted vendor by Gartner clients in 2019, as with past years.
      • Product Extensibility: Cherwell maintains a large and growing set of integrations and community-driven extensions to its platform via its Mergeable Applications (mApp) Exchange.
      Cautions
      • Technical Support: Several Cherwell customers have advised Gartner that the quality and responsiveness of support they’ve received from the vendor have declined over the past year.
      • New Features: Cherwell’s innovation in ITSM has lagged behind many of its closest competitors. Several new features released were incomplete, lacking capabilities found standard in other tools (for example, live chat integration lacking basic presence detection, and walk-up support lacking appointment scheduling).
      • Global Presence: Cherwell’s SaaS data center and direct sales presence is limited to North America, Western Europe and Australia. It only has a small customer footprint outside of these locations.

      EasyVista

      EasyVista is a Niche Player in this Magic Quadrant.
      Its EV Service Manager product is focused on providing a low-overhead ITSM tool with guided knowledge management to support both business and IT consumers. It is targeted at organizations with various levels of I&O maturity. Since the last publication of this Magic Quadrant, EasyVista introduced a new report builder, updated its virtual agent, and added several IT and business-consumer-facing UI updates.
      Strengths
      • Customer Retention: EasyVista maintains a good relationship with its customers, including providing a direct channel for them to vote on new capabilities and enhancements. It achieved strong customer retention in 2019.
      • Total Cost of Ownership (TCO): EasyVista maintains one of the lowest overheads for the products evaluated, with concurrent licensing, quick-start implementation options and bundled asset management.
      • Growth: EasyVista saw strong annual revenue growth over the past two years for its size, driven particularly by operations in the U.S. and France.
      Cautions
      • Sales Channels: A significant portion of EasyVista’s sales are direct rather than through partner channels. This will limit its global outreach, particularly in emerging markets where it has little presence, such as Asia, the Middle East and Latin America.
      • Brand Awareness: EasyVista does not regularly appear on Gartner client shortlists and rarely is shortlisted outside of the U.S. and France.
      • Emerging Features: EasyVista’s rate of innovation in the integration and adoption of machine learning technologies to augment IT staff, as well as the use of live collaboration to enable new support models, is not as advanced as its competitors.

      Freshworks

      Freshworks is a Niche Player in this Magic Quadrant.
      Its Freshservice product focuses on providing a low-overhead ITSM tool that is easy to use and configure. It is targeted at customers with basic to intermediate I&O maturity. Since the last publication of this Magic Quadrant, Freshworks released several updates to core ITSM functionality in its product, introduced new conversational interfaces, and acquired AnsweriQ and Flint in early 2020 for AI and ITOM functionality.
      Strengths
      • Growth: Freshworks achieved the highest percentage of year-over-year growth in its ITSM tool business of all the vendors evaluated in this Magic Quadrant. Its Freshservice product has a large and growing installed base among small and midsize businesses (SMBs).
      • Rapid Updates: Freshworks has an agile approach to product updates, with a rolling release model that allows it to offer weekly product updates. Feature flags on the updates enable customers to select the new capabilities they would like to adopt or exclude.
      • Global Expansion: Freshworks opened five new offices across North America, Europe and India, and grew its partner network across North America, Europe and the Middle East, in 2019.
      Cautions
      • Advanced Functionality: As Freshworks targets larger and more mature customers, Gartner’s Critical Capabilities research shows its product lacks the level of ITOM integration and ITSM functionality that advanced-maturity customers expect from ITSM tools.
      • Upmarket Aspirations: Freshworks’ attention to enterprise customers risks its predominantly SMB and midmarket customer base, as the vendor devotes support and development resources to go after the more advanced needs of the enterprise.
      • Market Focus: The majority of Freshworks’ 2019 revenue is derived from its other products, such as those for customer service management and sales force automation.

      IBM

      IBM is a Niche Player in this Magic Quadrant.
      Its Control Desk product is focused on extending IBM’s ITSM capabilities to IBM Global Technology Services customers, along with those looking for deeper enterprise asset management integration. It is targeted at organizations with advanced I&O maturity. Since the last publication of this Magic Quadrant, IBM enabled container-based deployment and out-of-the-box integration into Watson Assistant, and updated integration into IBM Maximo Asset Management.
      Strengths
      • EAM Support: By offering a shared platform between Maximo Asset Management and Control Desk, IBM provides a structured approach to managing both IT and enterprise assets to its customers.
      • Global Network: In addition to traditional North American and European markets, IBM has extensive global partnerships and resources in Asia, where many other ITSM vendors lack a significant local presence.
      • Native Integration: The vendor offers significant technology integration options across the IBM estate of solutions, including its automation, monitoring, cloud management, reporting and development products.
      Cautions
      • Market Presence: IBM’s ITSM offerings have limited appeal outside of its existing customer base because the vendor typically gears its pricing and marketing around selling Control Desk as part of a larger managed service outsourcing, ITOM or IT/OT purchase. Gartner clients rarely consider IBM on their shortlists when choosing a new ITSM tool.
      • Watson: Given the strength and breadth of the Watson AI brand, IBM has been slow to exploit it on its ITSM platform to expand its AITSM and virtual agent capabilities, and is still far behind market competitors in integrations of Watson technology.
      • Customer Deployments: Despite targeting enterprise customers, IBM has a disproportionately high number of small volume deals compared with similarly-focused vendors. This suggests, in many cases, that Control Desk customers are not using it as their primary ITSM tool.

      Ivanti

      Ivanti is a Leader in this Magic Quadrant.
      Its Service Manager product is focused on driving more support automation for edge devices through a combination of automation and self-service capabilities. It is targeted at intermediate to advanced I&O maturity organizations. Since the last publication of this Magic Quadrant, Ivanti released its self-healing automation bots, Ivanti Neurons for Healing, as well as new IT-focused mobile applications.
      Strengths
      • Edge Support Innovation: Ivanti extends its ITSM product with a deep set of integrated solutions for discovery, endpoint automation and self-enablement. Its newly released Ivanti Neurons for Healing provides a unique differentiation in this market to proactively monitor and remediate common issues on an end user’s device.
      • Market Awareness: Ivanti has marketed effectively through channels that cater to organizations with intermediate I&O maturity, and regularly appears on customer shortlists.
      • Regulatory Compliance: Ivanti Service Manager meets a number of regulatory standards, including HIPAA and FedRAMP. By attaining Federal Risk and Authorization Management Program (FedRAMP) certification for its Service Manager product in 4Q19, Ivanti is one of only a few vendors in this Magic Quadrant to meet this designation and, as a result, better positions itself to expand its public-sector business.
      Cautions
      • Product Portfolio Messaging: Ivanti’s portfolio has appeared disjointed to customers rather than telling a cohesive story across its products. As a result, customers often perceive Ivanti as a point solution rather than a strategic solution provider.
      • Back-End Configuration: Despite the vendor providing graphical workflow design capabilities, Ivanti customers have cited challenges with the initial configuration of Service Manager.
      • Emerging Markets: Ivanti has a lesser presence in emerging markets, such as those countries with emerging market economies in the Asia/Pacific region, Latin America and the Middle East, challenging its growth ambitions in those regions.

      ManageEngine

      ManageEngine is a Niche Player in this Magic Quadrant.
      Its ServiceDesk Plus is focused on providing a low-overhead ITSM tool with integration to its broader suite of products. It targets midsize and basic I&O maturity organizations. Since the last publication of this Magic Quadrant, ManageEngine released several updates to the core ITSM functionality in its product, introduced a release management module and expanded its graphical workflow support.
      Strengths
      • Installed Base: ManageEngine has a large and geographically distributed customer base. The vendor is particularly strong among SMBs.
      • Midmarket Pricing Strategy: ManageEngine’s low-cost and flexible pricing tiers align well to the needs of low-maturity and midsize organizations.
      • Product Portfolio: ManageEngine offers a broad portfolio of complementary products, including endpoint management, network monitoring, application monitoring and Active Directory management solutions that integrate into ServiceDesk Plus and provide cross-selling opportunities.
      Cautions
      • Innovation: Innovation has lagged behind the competition targeting similar customers. Many of the newer enhancements come from integration with other Zoho (ManageEngine is a division of Zoho) microservices and stand-alone tools.
      • Feature Parity: ManageEngine lacks feature parity between the SaaS and on-premises versions of its ITSM product. For example, on-premises customers do not have access to release management support and not all out-of-the-box integrations are available across both on-premises and SaaS offerings.
      • Branding: ManageEngine’s marketing and branding of its ITSM product as a help desk tool rather than a full ITSM solution limits its appeal to larger enterprise customers because it focuses on only a basic subset of ITSM needs.

      Micro Focus

      Micro Focus is a Niche Player in this Magic Quadrant.
      Its Service Management Automation X (SMAX) is focused on providing core ITSM capabilities on a no-code platform integrated into Micro Focus’ broader suite of enterprise software products. It is targeted at organizations of intermediate to advanced I&O maturity. Since the last publication of this Magic Quadrant, Micro Focus added a SaaS offering, natural language understanding to its virtual agent and the ability to extend SMAX with custom apps.
      Strengths
      • Bundled AI: Micro Focus includes its embedded AI/ML capabilities as part of its standard license, which can lower the barrier of entry for customers looking to explore the use of this technology to enhance ITSM processes.
      • Product Portfolio: Micro Focus has a broad portfolio of software including ITOM and development products for customers looking to extend their ITSM investments.
      • Codeless Configuration: Micro Focus has designed its product around a codeless workflow configuration. This addresses a key challenge of buyers to reduce implementation time and ongoing administrative resource requirements.
      Cautions
      • Buyer Mind Share: Among Gartner clients, Micro Focus has not generated increased interest around its SMAX product. Based on Gartner client inquiries, Micro Focus seldom appears on shortlists for ITSM tools.
      • Decreased Revenue: While SMAX as a new product is gaining customers, both Micro Focus and its overall ITSM portfolio had decreased year-over-year revenue in 2019.
      • Limited SaaS Experience: Although Microfocus has a SaaS offering, it lacks an established customer base. Customers looking for the convenience of a SaaS implementation may be concerned that this service is currently only available in North America and Europe.

      ServiceNow

      ServiceNow is a Leader in this Magic Quadrant.
      Its IT Service Management product is focused on providing a single platform connecting ITSM and non-IT workflows, augmented by a set of native AIOps and ITOM extensions. It is targeted at organizations with intermediate to advanced I&O maturity. Since the last publication of this Magic Quadrant, ServiceNow made platform-level acquisitions to add native AI, ML and natural language processing functionality, and added workspaces for service owner and vendor manager roles.
      Strengths
      • Market Presence: ServiceNow has global reach with local sales and support organizations, and strong brand recognition. It dominates customer shortlists and its ITSM tool revenue market share has grown to more than four times that of its closest competitor.
      • Partner Ecosystem: As a result of ServiceNow’s dominant market position, its platform has helped build a strong partner ecosystem, including professional services and integrations. In 2019, ServiceNow made significant updates to its partner program to help customers identify the right partners and to drive more consistent experiences when working with them.
      • AITSM Investment: ServiceNow’s acquisition of several AI- and ML-focused companies provides it with not only native IP to engineer into its platform, but also in-house expertise to innovate these features over time. Many of the vendor’s competitors rely on third-party partnerships for this extended functionality.
      Cautions
      • Pricing Model: ServiceNow lacks the license model flexibility of many of its closest competitors. Customers with large numbers of occasional users struggle to justify its role-based named user licensing model and Gartner has observed low adoption of its all-user licensing model alternative.
      • I&O Maturity of Buyers: Interactions with Gartner clients indicate that organizations that have not yet achieved high levels of I&O maturity struggle to demonstrate substantial value from their ServiceNow investments. Functionality to track improvement initiatives that drive maturity requires an ITSM Professional license, which comes at a significantly higher cost than the entry-level Standard edition.
      • Renewals: Some Gartner clients are concerned that ServiceNow’s market position is hurting their ability to negotiate their contract or reduce their footprint without heavy impacts to their current discount. This is significant for organizations looking to reduce or optimize spend through downsizing their ITSM footprint in response to adverse financial impacts resulting from compulsory COVID-19 response measures.

      Vendors Added and Dropped

      We review and adjust our inclusion criteria for Magic Quadrants as markets change. As a result of these adjustments, the mix of vendors in any Magic Quadrant may change over time. A vendor’s appearance in a Magic Quadrant one year and not the next does not necessarily indicate that we have changed our opinion of that vendor. It may be a reflection of a change in the market and, therefore, changed evaluation criteria, or of a change of focus by that vendor.

      Added

      ManageEngine was added to this Magic Quadrant.

      Dropped

      No vendors were dropped from this Magic Quadrant.

      Inclusion and Exclusion Criteria

      To qualify for inclusion, vendors need to meet the following:
      • Sell and market an ITSM product that includes native functionality for IT incident management, problem management, change management, release governance, IT user self-service (for knowledge and request management), IT knowledge management, IT service support analytics and reporting, and SLA management with regard to incident and service requests. Also, a graphical process designer must be used to modify at least one-third of the above workflows.
      • Have demonstrated ongoing development of the product with at least one major update/release (not including security updates and minor feature update) over the past 12 months (since 1 April 2019).
      • Have at least 35% of customers using versions of software across the ITSM product portfolio that are less than 18 months old (released after 1 October 2018).
      • Have at least $40 million in annual revenue derived from ITSM products during the calendar year of 2019 or at least $30 million in annual revenue derived from ITSM products during the calendar year of 2019, with at least 20% year-over-year growth when compared to 2018.
        • At least half of ITSM product revenue must be derived outside of bundled outsourced and managed workplace service agreements.
      • Have at least six new customers added during 2019 with either a contract value of $300,000 for purchase of perpetually licensed ITSM tool software or an annual contract value of $150,000 for subscription to ITSM tool software
      • Have a sales presence or partner network that includes at least two offices (regional office or reseller partner) in each of three or more of the following regions: North America, Latin America, Europe (Western, Eastern and Eurasia), Middle East and North Africa (including Sub-Saharan Africa), Asia/Pacific (mature, emerging, Greater China and Japan).
      The product versions considered as part of this evaluation must have been generally available by 1 April 2020.
      Vendors may have multiple products in the ITSM solution market. In these cases, each vendor was evaluated as a whole for this Magic Quadrant and for the subsequent Critical Capabilities for ITSM, and either their large-enterprise-focused product was evaluated or any product appearing on over 3% of Gartner client ITSM shortlists was evaluated. The products are described separately in the companion Critical Capabilities research.

      Honorable Mentions

      There are over 400 vendors in the market for ITSM tools. While this research identifies 11 vendors that have met our inclusion criteria, the exclusion of a vendor does not mean that the vendor and its products lack viability. Gartner regularly advises clients to also consider ITSM vendors not found in this Magic Quadrant. Below are several noteworthy vendors that did not meet all inclusion criteria but could be appropriate for clients, contingent on requirements. All vendors below were of interest to Gartner clients, as evidenced by number of times shortlisted in Gartner client inquiry discussions in 2019:
      • Alemba — Alemba is exclusively focused on its ITSM tool, Alemba Service Manager (formerly vFire). It aims to simplify the request fulfillment process and offer ITSM capabilities at a low TCO. Its customers are primarily located in the U.K., U.S., and Australia. Alemba lacks the ITSM tool revenue required to satisfy Gartner’s inclusion criteria for this Magic Quadrant.
      • Atlassian — Atlassian complements its portfolio of development and collaboration tools with its ITSM product, Jira Service Desk. It aims to drive deeper collaboration across development and ITOM workstreams with a low-cost ITSM tool. Its customers are primarily midsize organizations. Atlassian did not meet the individual customer revenue contribution requirement to satisfy Gartner’s inclusion criteria for this Magic Quadrant.
      • SolarWinds — SolarWinds complements its portfolio of IT operations management and security tools with its ITSM product, SolarWinds Service Desk (after acquiring Samanage in 2019). It aims to provide an easy-to-use ITSM tool that is integrated into its broader software portfolio. Its customers are primarily midsize organizations. SolarWinds did not meet the individual customer revenue contribution requirement to satisfy Gartner’s inclusion criteria for this Magic Quadrant.
      • SysAid — SysAid is exclusively focused on its ITSM tool of the same name. It aims to provide a flexible, easy-to-use ITSM product with integrated ITAM and automation features. Its customers are primarily midsize organizations. SysAid did not meet the ITSM tool revenue required to satisfy Gartner’s inclusion criteria for this Magic Quadrant.
      • TOPdesk — TOPdesk is exclusively focused on its ITSM tool. Its TOPdesk Enterprise aims to drive ease of use and quick implementation, while offering support for other non-IT workflows. TOPdesk’s customers are primarily located in Europe. TOPdesk lacks some of the graphical process designer capabilities required to fully satisfy Gartner’s inclusion criteria for this Magic Quadrant.

      Evaluation Criteria

      Ability to Execute

      Product/Service: Core goods and services offered by the vendor for the defined market. This includes current product/service capabilities, quality, feature sets, skills and so on, whether offered natively or through OEM agreements/partnerships as defined in the Market Definition/Description and detailed in the subcriteria.
      Overall Viability: Viability includes an assessment of the overall organization’s financial health, and the financial and practical success of the business unit. It also assesses the likelihood that the individual business unit will continue investing in the product, continue offering the product and advance the state of the art within the organization’s portfolio of products.
      Sales Execution/Pricing: The vendor’s capabilities in all presales activities and the structure that supports them. This includes deal management, pricing and negotiation, presales support, and the overall effectiveness of the sales channel.
      Market Responsiveness/Record: Ability to respond, change direction, be flexible and achieve competitive success as opportunities develop, competitors act, customer needs evolve and market dynamics change. This criterion also considers the vendor’s history of responsiveness.
      Marketing Execution: The clarity, quality, creativity and efficacy of programs designed to deliver the organization’s message to influence the market, promote the brand and business, increase awareness of the products, and establish a positive identification with the product/brand and organization in the minds of buyers. This “mind share” can be driven by a combination of publicity, promotional initiatives, thought leadership, word of mouth and sales activities.
      Customer Experience: Relationships, products and services/programs that enable clients to be successful with the products evaluated. Specifically, this includes the ways customers receive technical support or account support. This can also include ancillary tools, customer support programs (and the quality thereof), availability of user groups, service-level agreements and so on.
      Operations: The ability of the organization to meet its goals and commitments. Factors include the quality of the organizational structure, including skills, experiences, programs, systems and other vehicles that enable the organization to operate effectively and efficiently on an ongoing basis.

      Table 1: Ability to Execute Evaluation Criteria

      Evaluation Criteria
      Weighting
      Product or Service
      High
      Overall Viability
      Medium
      Sales Execution/Pricing
      High
      Market Responsiveness/Record
      Medium
      Marketing Execution
      Medium
      Customer Experience
      Medium
      Operations
      Not Rated
      Source: Gartner (October 2020)

      Completeness of Vision

      Market Understanding: This criterion assesses the ability of the vendor to understand buyers’ wants and needs, and to translate those into products and services. Vendors that show the highest degree of vision listen to and understand buyers’ wants and needs, and can shape or enhance those with their added vision.
      Marketing Strategy: This criterion looks at whether the vendor has a clear, differentiated set of messages consistently communicated throughout the organization and externalized through the website, advertising, customer programs and positioning statements.
      Sales Strategy: This criterion evaluates the strategy for selling products that uses the appropriate network of direct and indirect sales, marketing, service, and communication affiliates that extend the scope and depth of market reach, skills, expertise, technologies, services and the customer base.
      Offering (Product) Strategy: This criterion assesses the vendor’s approach to product development and delivery that emphasizes differentiation, functionality, methodology and feature sets as they map to current and future requirements.
      Business Model: This criterion evaluates the soundness and logic of the vendor’s underlying business proposition.
      Vertical/Industry Strategy: This is an assessment of the vendor’s strategy to direct resources, skills and offerings to meet the specific needs of individual market segments, including vertical markets.
      Innovation: This criterion assesses whether the vendor has direct, related, complementary and synergistic layouts of resources, expertise or capital for investment, consolidation, defensive or preemptive purposes.
      Geographic Strategy: This is an assessment of the vendor’s strategy to direct resources, skills and offerings to meet the specific needs of geographies outside the “home” or native geography, either directly or through partners, channels and subsidiaries as appropriate for that geography and market.

      Table 2: Completeness of Vision Evaluation Criteria

      Evaluation Criteria
      Weighting
      Market Understanding
      High
      Marketing Strategy
      High
      Sales Strategy
      Medium
      Offering (Product) Strategy
      High
      Business Model
      Medium
      Vertical/Industry Strategy
      Not Rated
      Innovation
      High
      Geographic Strategy
      Medium
      Source: Gartner (October 2020)

      Quadrant Descriptions

      Leaders

      Leaders have executed well with broad market reach, strong customer awareness of their participation in this market and adoption (as evidenced by Gartner client interaction data, as well as their growth and market presence). The Leaders in this Magic Quadrant jointly account for more than 70% of the market share for 2019. These vendors have a clear vision that addresses relevant challenges for I&O teams. They exhibit the levels of product, marketing and sales capabilities required to drive market acceptance.

      Challengers

      Challengers have executed well, growing market revenue, retaining good customer awareness and improving their ITSM product and overall viability levels enough to participate in the general-purpose market with competitive products. In general, however, Challengers are not seen as driving the market as strongly as Leaders or Visionaries.

      Visionaries

      Visionaries appearing in this quadrant deliver innovative products that address operationally important I&O organizational challenges — namely, optimizing operational efficiency, creating more agile ITSM processes and enhancing the experiences offered to business consumers — but have yet to gain significant market or mind share. This year, no vendors fit this description, as many have focused on innovation outside the scope of ITSM tools.

      Niche Players

      Niche Players have strengths in particular areas of ITSM and often offer solid products for a specific use case, but generally have not invested in satisfying all the requirements to demonstrate Completeness of Vision and the Ability to Execute. The Niche Players in this Magic Quadrant focus on a small segment or are in the process of ramping up go-to-market efforts, and have yet to develop the vision to break out; or they are scaling down their offerings by retiring products.

      Context

      The Magic Quadrant for ITSM tools assesses the viability of vendors and their competitive strength in the ITSM tool marketplace. The vendors featured here produce ITSM tools that are of interest to large I&O organizations, however, the depth of out-of-the-box integration support and ITSM process support can significantly vary by product. It is important to note that this is not a direct evaluation of the ITSM products that these vendors offer. This analysis is complemented by Critical Capabilities for IT Service Management Tools, which analyzes 13 capabilities that differentiate these products, weighted into three I&O-maturity-related use cases and one use case for supporting heavy agile and DevOps environments. The use-case filter helps prioritize the capabilities that will have the greatest beneficial impact from ITSM products offered by these vendors.
      Gartner strongly recommends that organizations use this research in conjunction with the Critical Capabilities companion research, the selection best practices included in the 6 Smart Steps for ITSM Tool Selection Success, inquiries with Gartner analysts and other Gartner research to define their requirements and select solutions that match their needs.
      Gartner recommends that you plan to select a vendor that you believe will be in a position to support your organization’s needs for at least five years, and one that demonstrates its commitment to invest in developing the tool capabilities to remain viable in the ITSM market. While the core features within these tools are fairly well-defined, a number of shifts in this market are impacting vendor roadmaps and should be considered while evaluating them. These include:
      • Broader AITSM support to drive the application of context, advice, actions and interfaces of AI, automation and big data
      • DevOps initiatives that require a deeper integration into the DevOps toolchain
      • Enabling more flexible and agile ITSM processes
      • Omnichannel and multiexperience support that create more consistent and engaging experiences across different support channels (for example, walk-up, roaming or P2P support) and interfaces (for example, mobile, web)
      • Enabling greater self-service and automated request and incident resolution
      • Supporting highly collaborative support models (for example, swarming)
      For further insight around these key shifts in ITSM, see  2019 Strategic Roadmap for IT Service Management.
      While many vendors are also looking at opportunities to expand into other business workflows, capabilities for processing workflows such as HR, facilities, project management and others that are not associated with ITSM are not evaluated in this research (see The Reality of ITSM Tools as Enterprise Service Management Tools).
      Finally, prioritize skills, training, process optimization and proper product implementation, because these factors will influence your experience with a product more than the specific functional capabilities (see How to Successfully Implement Your ITSM Tool). The key opportunity for a new ITSM tool is the use of this technology to support gains in delivery maturity that ultimately drive better experiences for IT’s customers.

      Market Overview

      The ITSM tool market is mature and is composed of hundreds of products that claim to provide IT organizations with the ability to track and resolve issues affecting the IT production environment. While the products have evolved with new capabilities to help ITSM vendors differentiate themselves and their forward visions, the market itself has been stable for several years. Several developments have impacted the ITSM market over the last year, including:
      • As I&O organizations have an increased focus on experience management, ITSM tool vendors have been challenged to evolve their solutions to meet this change. This includes not only providing enhanced experiences delivered by the platform itself to both the business and IT users who access it, but also providing better ways of measuring and improving the customer sentiment around the experiences.
      • As I&O leaders increasingly adopt agile and DevOps practices, a growing number of ITSM vendors are providing bidirectional visibility and integration between native and third-party development and ITSM tools.
      • Several ITSM vendors are partnering with AIOps platforms and investing in developing or acquiring native machine learning and big data analytics technologies to provide I&O leaders and practitioners with greater insights around their environments.
      • SaaS is still the most commonly desired model for ITSM vendors, but some larger vendors are adopting containerized deployment approaches over public cloud infrastructure to provide additional flexibility and more choices for their customers.
      • A growing number of vendors are developing, marketing and, in some cases, rebranding their products to support enterprise workflows such as HR and facilities management. This potentially threatens stagnation in their ITSM roadmaps as these companies spend limited R&D and marketing budgets outside of their core market.
      In addition, the COVID-19 pandemic has highlighted the need for robust ITSM tooling to enable I&O to effectively respond to significant disruption in several ways, including:
      • Supporting remote collaboration that enables service desk agents, change managers and other IT staff to coordinate the response to the disruption. This is often in the form of native live chat, forums and wikis, or through integrating into common platforms such as Microsoft Teams and Slack.
      • Enabling Level 0 self-service support to deflect common contacts into the service desk and relieve pressure.
      • Enabling remote agents to effectively share knowledge with each other through a robust knowledge base.
      • Providing a platform based on industry-accepted best practices that enables the growth of ITSM process maturity. COVID-19 and the resulting economic impact is providing a stress test that quickly exposes gaps and, in some cases, inefficiencies in current practices.
      There are over 400 products in the market, but most of them are basic or intermediate tools that focus on IT service desk and ticketing functions targeted at lower-maturity I&O organizations. Vendors focused on basic- to intermediate-maturity use cases can be expected to emphasize core ITSM competencies (for example, incident management, change management and request management). They will find novel ways to leverage emerging technologies and selectively pursue non-ITSM use cases to differentiate themselves in an already crowded landscape. I&O organizations with these limited requirements should consider basic and intermediate tools to avoid overspending on license and deployment costs, and increased demand on resources to successfully manage these tools.
      I&O organizations intent on achieving higher levels of maturity within 18 months should consider advanced ITSM tools to gain value from solutions focused on a broader, end-to-end context of IT service support and delivery. Vendors focused on advanced-maturity use cases can be expected to develop and execute platform strategies to distinguish themselves from simple SaaS applications, providing more flexibility and product capabilities. These vendors also tend to invest more heavily in innovative features like AI and ML, as their customers can leverage their scale and data quality to achieve higher results than less mature organizations. Given the increases in capability and complexity, advanced ITSM tools will be more costly and require more resources for deployment than an intermediate or a basic tool.
      The market for ITSM tools continues to grow; however, the top three vendors by ITSM revenue — BMC, Ivanti and ServiceNow — combined had 70% of the market share in 2019. Gartner has seen some significant vendors consolidate their offerings over the past few years through mergers, spinoffs and product retirement, but there has been no major consolidation in the past 12 months. However, as vendors may look to boost market share, increase global footprint or realign their portfolios, Gartner anticipates that additional consolidation in this mature market is likely.

      Acronym Key and Glossary Terms

      AITSM
      AITSM is not an acronym. It is a term that refers to the application of context, assistance, actions and interfaces of AI, automation and big data on ITSM tools and practices to improve the overall effectiveness, efficiency and error reduction for I&O staff. AITSM is important for intermediate and advanced use cases to automate and support complex environments.

      Evidence

      Gartner’s Market Share: Enterprise Infrastructure Software, Worldwide, 2019 analyzes market share data for ITSM vendors as part of overall IT operations software revenue. This market has grown from an estimated $1.3 billion in 2010 to $4.3 billion in 2019.
      Gartner’s community of more than 1,200 analysts engages in more than 250,000 one-on-one client interactions each year. Conclusions are based on Gartner interaction data with Gartner clients purchasing ITSM tools collected during the past 18 months (as of 1 July 2020).
      Gartner collects ITSM tool statistics from anonymized client inquiries detailing ITSM tools in use, scheduled for replacement and on shortlists for selection.

      Evaluation Criteria Definitions

      Ability to Execute

      Product/Service: Core goods and services offered by the vendor for the defined market. This includes current product/service capabilities, quality, feature sets, skills and so on, whether offered natively or through OEM agreements/partnerships as defined in the market definition and detailed in the subcriteria.
      Overall Viability: Viability includes an assessment of the overall organization's financial health, the financial and practical success of the business unit, and the likelihood that the individual business unit will continue investing in the product, will continue offering the product and will advance the state of the art within the organization's portfolio of products.
      Sales Execution/Pricing: The vendor's capabilities in all presales activities and the structure that supports them. This includes deal management, pricing and negotiation, presales support, and the overall effectiveness of the sales channel.
      Market Responsiveness/Record: Ability to respond, change direction, be flexible and achieve competitive success as opportunities develop, competitors act, customer needs evolve and market dynamics change. This criterion also considers the vendor's history of responsiveness.
      Marketing Execution: The clarity, quality, creativity and efficacy of programs designed to deliver the organization's message to influence the market, promote the brand and business, increase awareness of the products, and establish a positive identification with the product/brand and organization in the minds of buyers. This "mind share" can be driven by a combination of publicity, promotional initiatives, thought leadership, word of mouth and sales activities.
      Customer Experience: Relationships, products and services/programs that enable clients to be successful with the products evaluated. Specifically, this includes the ways customers receive technical support or account support. This can also include ancillary tools, customer support programs (and the quality thereof), availability of user groups, service-level agreements and so on.
      Operations: The ability of the organization to meet its goals and commitments. Factors include the quality of the organizational structure, including skills, experiences, programs, systems and other vehicles that enable the organization to operate effectively and efficiently on an ongoing basis.

      Completeness of Vision

      Market Understanding: Ability of the vendor to understand buyers' wants and needs and to translate those into products and services. Vendors that show the highest degree of vision listen to and understand buyers' wants and needs, and can shape or enhance those with their added vision.
      Marketing Strategy: A clear, differentiated set of messages consistently communicated throughout the organization and externalized through the website, advertising, customer programs and positioning statements.
      Sales Strategy: The strategy for selling products that uses the appropriate network of direct and indirect sales, marketing, service, and communication affiliates that extend the scope and depth of market reach, skills, expertise, technologies, services and the customer base.
      Offering (Product) Strategy: The vendor's approach to product development and delivery that emphasizes differentiation, functionality, methodology and feature sets as they map to current and future requirements.
      Business Model: The soundness and logic of the vendor's underlying business proposition.
      Vertical/Industry Strategy: The vendor's strategy to direct resources, skills and offerings to meet the specific needs of individual market segments, including vertical markets.
      Innovation: Direct, related, complementary and synergistic layouts of resources, expertise or capital for investment, consolidation, defensive or pre-emptive purposes.
      Geographic Strategy: The vendor's strategy to direct resources, skills and offerings to meet the specific needs of geographies outside the "home" or native geography, either directly or through partners, channels and subsidiaries as appropriate for that geography and market.

      source: 

      Gunakan FreshService untuk ENTEPRISE SERVICE MANAGEMENT

      $
      0
      0

       


      Apakah Anda perlu HELPDESK yang bisa digunakan oleh beragam departemen di perusahaan anda, seperti IT, HR, Finance, Maintenance, Legal, Marketing dan Sales . Ya konsep itu namanya ENTERPRISE SERVICE MANAGEMENT.

      Bila anda perlu yang berbasis CLOUD , dan bisa diakses dari mana saja, anda bisa gunakan FRESHSERVICE. Berikut videonya.



      Vaccine Cold Storage Rooms – How They Work and are Maintained

      $
      0
      0

       

      Vaccine Storage and Handling

      Vaccines and other medical products are essential parts of a healthy society. They provide relief from diseases and suffering. They are designed to improve the quality of life for people. As with any other product, they are manufactured in facilities located near urban centers.

      When shipped elsewhere, transportation is provided by a cold chain process in place to safeguard the quality of the medical products. Typically, cold chain operations employ of refrigeration units to maintain ideal conditions for vaccines or other life science products.

      Vaccine Cold Chain

      The purpose of the vaccine cold chain is to maintain product quality from the production of the product until the point of administration, by guaranteeing that vaccines are stored and transported within World Health Organization (WHO) recommended temperature ranges.

      The cold chain is sometimes also known as the vaccine supply chain, or the immunization supply chain. The cold chain consists of various links that are designed to keep vaccines within WHO-recommended temperature ranges. Following this strategy ensures that cold chain performance is properly monitored and that necessary information is gathered for vaccine quality forecasting.

      A cold chain is a temperature-controlled supply chain that includes all vaccine-related equipment and procedures. The cold chain begins with the cold storage unit at the manufacturing plant, extends to the transport and delivery of the vaccine and proper storage at the provider facility, and ends with the administration of the vaccine to the patient.

      In order to maintain a reliable vaccine cold chain at the optimum level, the following key protocols must be followed:

      • Store vaccines and diluents within the required temperature range at all sites
      • pack and transport vaccines to and from outreach sites according to recommended procedures
      • keep vaccines and diluents within recommended cold chain conditions during immunization sessions.

      immunization and vaccine supply chain

      Temperature requirements for vaccines

      Vaccines are biological products that are vulnerable when exposed to conditions outside their safety parameters. Some of them are sensitive to freezing, some to heat, and others to light. Vaccine potency is the ability to protect the vaccinated patient. It can diminish when the vaccine is compromised by temperature excursions. Once potency is lost, it cannot be restored. To preserve its quality, vaccines must be stored away from temperature extremes by using a cold chain that meets specific temperature requirements. It is essential that all those who handle vaccines and diluents know the temperature sensitivities and the recommended storage temperatures for all the vaccines being shipped.

      Strive for Five

      The vaccine cold chain immunization

      The vaccines are classified into six categories. Within these six categories, vaccines are arranged in alphabetical order, and not according to their sensitivity to heat. The most heat-sensitive vaccines are in Group A and the least heat-sensitive vaccines are in Group F.

      It is worth noting that the heat stability information shown for freeze-dried vaccines applies only to unopened vials. Freeze-dried vaccines can rapidly lose potency if mixed with saline solution. Also, it is imperative to keep opened multi-dose vaccine vials, with no preservative, cooled at temperatures between +2 °C and +8 °C (32 °F and 46.3°F) during the injection session, or within six hours after opening.

      Sensitivity to light

      There are some vaccines that are sensitive to light and lose potency when exposed to it. They should always be shielded against sunlight or any strong artificial light, and exposure should be minimized. Vaccines that are sensitive to light include Bacille Calmette-Guerin (BCG), measles, measles-rubella, measles-mumps-rubella, and rubella. The vaccines are often stored in dark glass vials that give them some protection from light damage, but they should be kept in their boxes for as long as possible to protect them during storage and transportation.

      Controlled Temperature Chain (CTC)

      An increasing number of vaccines are tested to see if they are compatibile with a Controlled Temperature Chain (CTC) at ambient temperatures. WHO defines a CTC as the on-label use of a WHO-prequalified vaccine out of the traditional +2 °C and +8 °C (32 °F and 46.3°F) cold chain for a limited period of time with temperature variable of up to 40 °C, just before administration. The CTC approach can be adopted by countries under special circumstances, such as for special strategies, or mass vaccination campaigns at the health center or peripheral health facility level.

      As such, health workers can adequately protect vaccines by doing the following:

      • Keep vaccines in prescribed vaccine refrigeration equipment.
      • Use a temperature monitoring device to ensure temperatures remain between +2 °C and +8 °C (32 °F and 46.3°F).
      • Transport vaccines to immunization sessions in a vaccine carrier, correctly packed, using coolant packs where necessary.
      • During immunization sessions, fit a foam pad (if available) at the top of the vaccine carrier, to ensure insulation from the outside temperature.

      At the health facility, one person will be the supervisor for managing the vaccine cold chain. A second person can be the back-up personnel if the primary person is absent. Their responsibilities are:

      • checking and recording vaccine temperatures twice daily; typically, in the morning and at the end of the session or day
      • properly storing vaccines, diluents, and water packs
      • handling preventative maintenance of the cold chain equipment. All health workers in a facility must have the knowledge to monitor the cold chain and what to do if temperatures are out of range.

      pharmacist checking temperature of vaccines

      Manufacturers, distributors, public health staff, and health care providers are all responsible to ensure the cold chain is maintained once the vaccines are manufactured until they are delivered to the final user.

      Vaccine Coordinator

      To ensure proper storage and handling of medical products, there should be a primary vaccine coordinator who will be responsible for overseeing the process. An alternate coordinator should be appointed to serve in the absence of the primary coordinator. These individuals should be fully trained in routine and emergency policies and procedures. Coordinator responsibilities may be completed by the coordinator or delegated to appropriate staff. The coordinator must ensure the delegate has documented training, demonstrating competency for the specific tasks assigned and must confirm that tasks are completed.

      Some of the coordinator responsibilities include:

      • Ordering vaccines
      • Supervising proper receipt and storage of vaccine deliveries
      • Documenting vaccine inventory information
      • Organizing and monitoring vaccines within storage units, including rotating stock and removing expired vaccines
      • Setting up temperature monitoring devices (TMDs) and recording daily temperatures
      • Responding to temperature excursions (out-of-range temperatures) and equipment failures
      • Overseeing vaccine transport (when necessary)
      • Overseeing emergency preparations

      Vaccine Storage and Handling Standard Operating Procedures (SOPs)

      Facilities must develop and maintain clearly written, detailed, and up-to-date storage and handling standard operating procedures (SOPs) recommended by the CDC. SOPs must be familiar with all staff and revised by the vaccine coordinator yearly.

      SOPs should contain information for three major areas:

      General information – include contact numbers for vaccine manufacturers, equipment service providers, and important facility staff, as well as their job descriptions, regularly used forms, and staff qualifications.

      Routine storage and handling – include information on vaccine inventory management, from ordering to monitoring temperature conditions. 

      Emergency vaccine storage, handling, and transport – procedures to be taken in the event of equipment breakdowns, power failures, natural disasters, or other emergencies that could compromise vaccine storage conditions.

      Vaccine Storage and Temperature Monitoring Equipment

      It is important for a storage area to have proper monitoring and refrigeration equipment that is set up correctly, maintained appropriately, and repaired as needed. These procedures ensure the protection of patients from receiving compromised vaccines. and prevent the pharma companies against the costs of revaccinating patients, replacing expensive vaccines, and losing brand reputation.

      Refrigerators and Freezers

      Here are the recommended types of refrigerators and freezers:

      Purpose-built or pharmaceutical-grade units designed to either refrigerate or freeze biologics, including vaccines, are used recommended. These units can be compact, under-the-counter style, or larger units.

      If a pharmaceutical-grade unit is unavailable, a stand-alone, household unit may be an acceptable option in some practice settings. The freezer compartment must be used, with caution, for storing vaccines. The reason is that these units have cold spots and temperature fluctuations, and air circulating from the freezer could expose refrigerated vaccines in the same unit, to freezing temperatures.

      Temperature Monitoring Devices (TMDs)

      Every vaccine storage unit must have good TMD. CDC recommends the use of a continuous monitoring and recording device called a “digital data logger” (DDL), set at least every 30 minutes interval for recording. Many DDLs use a buffered temperature probe. Temperatures measured by a buffered probe match vaccine temperature more closely than those measured by standard thermometers, which tend to reflect air temperature. DDLs show details on how long a unit has been operating outside the recommended temperature range. Each DDL should have a current and valid Certificate of Calibration Testing (also known as a “Report of Calibration”) to certify it is accurate.

      CDC recommends DDLs with the following characteristics:

      • A detachable probe that best reflects vaccine temperatures
      • Alarm for out-of-range temperatures
      • Low-battery indicator
      • Current, minimum, and maximum temperature display
      • Recommended uncertainty of +/-0.5°C (+/-1°F)
      • Logging interval (or reading rate) that can be set by the user to measure and record temperatures every 30 minutes

      Temperature data from a DDL can be downloaded to a computer using an application or retrieved from a website for user review, which is crucial to vaccine safety. The app or website may also allow the user to preset the frequency of temperature readings.

      AKCP provide such temperature monitoring devices suitable for use in pharmaceutical industry and monitoring of medical refrigerators.

      The AKCP Wireless Tunnel™ NIST2 and NIST4 type sensors are used with a glycol jar attachment to fulfill the requirements and guidelines from CDC, FDA and The WHO. Temperature data is graphed, reports can be generated, temperature alerts sent and vaccine batches tracked for temperature excursions.

      Glycol and air temperature 2

      Each facility should have a recommended TMD for:

                  Each vaccine storage unit

                  Each emergency transport unit

                  A backup TMD in case the primary device malfunctions or is out for calibration testing

      Health facility cold chain equipment

      Different levels within the national cold chain system require different types of equipment for transporting and storing vaccines and diluents within the prescribed temperature range.

      • Primary level (national): the primary level generally uses cold or freezer rooms, freezers, refrigerators, cold boxes, and refrigerated trucks for transportation.
      • Intermediate level (province or district): intermediate level generally uses cold and freezer rooms and/or freezers, refrigerators and cold boxes, and refrigerated trucks for transportation.
      • Peripheral level (health center/facility or health post): health facilities generally need refrigerators (in certain instances with water pack freezing/cooling compartments), cold boxes, and vaccine carriers. In some countries, cold boxes alone may be used for monthly or weekly immunization sessions.

      To ensure optimal performance, cold chain equipment used for immunization programs at any level must comply with the latest technological specifications, as prescribed with WHO prequalification standards or standards set by national regulatory authorities.

      Cold chain equipment needed at peripheral-level health facilities. 

      Refrigerators

      Health facility refrigerators are powered by electricity, solar energy, or gas (or kerosene). A health facility refrigerator should be chosen based according to the mode of power usage in the area and the combined capacity needed for vaccine and water pack storage.

      Health facility refrigerator must never be tightly packed– always provide some space around the vaccines and diluents to allow air circulation, and easy access to the vaccine.

      A health facility refrigerator must be able to hold:

      • at least one month’s supply of vaccines and diluents in the refrigerator
      • a one- or two-week reserve stock of vaccines and diluents (usually an additional 25–50% of the one-month supply)
      • a minimum of four water packs in the freezer/cooling compartment

      Cold boxes

       A cold box is an insulated container that is lined with water packs to keep vaccines and diluents within the prescribed temperature range during transport. Cold boxes can store vaccines for periods of up to two days or more if there is no ready source of power. Once stored, cold boxes should not be opened until the vaccine is needed.

      Pelican Cold Boxes for pharmaceutical products

      Monitoring cold chain temperatures

      The data gathered from temperature monitoring devices must be recorded and analyzed on a regular basis to demonstrate that vaccines are being stored and transported at the correct temperatures.

      In refrigerators, a standard manual temperature-recording chart is attached to the door of every vaccine refrigerator. Readings are taken twice a day, at least five days per week, preferably every day, including weekends and holidays. Daily readings should be taken from the same temperature monitoring device each time. Recording temperatures provides evidence that the refrigerator is being checked regularly. This identifies performance trends, sometimes even before automatic alarms pick them up.

      AKCP provides a solution to monitor the complete cold chain, from manufacturer, through transportation, warehousing and last mile delivery.

      live tracking of cold chain with AKCP

      Taking action when a vaccine refrigerator’s temperature is not within the prescribed limit;

      If the temperature of the refrigerator is below +2 °C (32 °F), a report should be made to the supervisor.

      Corrective action includes the following protocols:

      • Turn the thermostat knob so the arrow points to a setting that will make the refrigerator warmer.
      • Check whether the door of the freezer closes properly. The seal may be damaged. If broken, repair it.
      • If the temperature has fallen below 0 °C for any length of time, check freeze-sensitive vaccines to see if they have been damaged by freezing, using the Shake Test.

      Corrective action includes the following procedure:

      • Make sure that the refrigerator is working. If it is not working, check whether the power supply is working.
      • Check whether the door of the refrigerator or the freezing compartment closes properly; if the seal is broken, the temperature will fluctuate. Correct it.
      • Check whether frost is preventing cold air in the freezing compartment from entering the refrigerator compartment. Defrost if necessary.
      • If the power supply, door seal, and frost levels are all in working order, turn the thermostat knob so that the arrow points to a setting that will make the refrigerator cooler.
      • If the temperature cannot be maintained between +2 °C and +8 °C (32 °F and 46.3°F), replace the equipment with another that can maintain the temperature range until the refrigerator is repaired.

      Remember: to avoid freezing vaccines, do not adjust the thermostat to a cooler (higher number) setting after a power cut or when vaccines arrive.

      Conclusions

      Vaccine cold storage rooms have the latest technologies in cooling temperature to ensure the safety of the life science products. These temperatures are prescribed by the WHO or the concerned government agencies to safeguard the health of users.

      Vaccines must be arranged inside cold chain equipment in a way that helps ensure that they remain in good condition, with minimum risk of exposure to damaging temperatures.

      More details on AKCP solution specifically designed for the pharmaceutical industry can be found on https://www.parma-mon.com

      Komponen Panel Listrik

      $
      0
      0

      Komponen sangat banyak untuk membentuk sebuah panel listrik, disini anda akan mempelajari sebuah komponen listrik yang lengkap dan sangat terperinci.

      Komponen listrik nantinya terdiri dari komponen power, komponen indicator, komponen control, dan komponen pengaman.

      1. Miniatur Circuit Breaker (MCB)
      MCB atau Miniature Circuit Breaker adalah sebuah komponen listrik yang berguna untuk mengamankan beban lebih
      Atau hubung singkat (Short Circuit) yang disebebkan oleh lonjakan listrik yang tidak disengaja maupun  disengaja.
      Contoh Short Circuit yang disengaja, Memasukan 2 buah kabel phase dan netral pada stok kontak dan di sambungan kabel tersebut.
      Maka akan keluar sebuah percikan api jika MCB msh belum trip, jika MCB bagus makan percikan api tidak sebesar dengan MCB yang kurang bagus atau sudah lama dipakai.
      Contoh Short Circuit tidak disengaja seperti, anda mempunyai pompa air tiba-tiba pompa air tersebut tidak bisa jalan dan keluar sebuah asap atau bau terbakar.
      Kemudian MCB dirumah anda trip atau turun, membuktikan mcb tersebut bekerja ketika ada short circuit pada pompa anda.
      MCB berfungsi sebagai pengaman beban lebih Overload dan hubung singkat short circuit yang disebabkan oleh ketidak sengajaan manusia dan disengaja oleh manusia.

      2. Moulded Case Circuit Breaker (MCCB)
      MCCB adalah singkatan dari Moulded Case Circuit Breaker, sebagai pengaman terjadinya hubung singkat short circuit dan beban lebih overload agar tidak terjadi

      kerusakan pada motor listrik maupun kebakaran yang disebabkan oleh short circuit yang selalu menimbulkan bunga api.
      MCCB biasanya digunakan oleh industri karena MCCB hanya untuk pengaman listrik 3 phase, dan motor listrik industri juga menggunakan listrik 3 phase
      Jadi jika anda ingin bertemu apa itu namanya MCCB dan digunakan untuk apa mampir deh ke pabrik terdekat dan minta tolong untuk dilihatkan apa itu MCCB.

      3. Pilot Lamp atau Lampu Panel
      Pilot Lamp disini berfungsi untuk menunjukan jika ada arus atau tegangan yang masuk dengan tanda bahwa pilot lamp tersebut menyala.
      Pilot lamp sendiri memiliki beberapa warna biasanya untuk tegangan distribusi seperti phase R, S, T menggunakan warna Biru, Kuning, Merah,
      Tergantung sebuah perusahaan jika menganut PUIL (Persyaratan Umum Instalasi Listrik) lama biasanya menggunakan Merah, Kuning, Hijau.
      Tetapi ada juga yang pilot lampnya sama antara phase R, S, T menggunakan hijau yang membedakan adalah lebel dari penel listrik tersebut.

      4. Push Button
      Push Button adalah komponen penting berada pada panel listrik sebagai komponen kontrol.
      Fungsi dari Push Button ini adalah untuk menghubungkan arus jika ditombol akan nyambung N/O ( Normaly Open), biasanya Push Button ini berwana hijau.
      Jika ditombol lepas atau N/C (Normaly Close) maka tegangan akan lepas, push button ini biasanya identik dengan warna merah.
      Push button mempunya beberapa tipe pada gambar diatas adalah tipe 1 kontak jadi pilih NC atau NO.
      ada juga push button 2 tipe NC dan NO jadi bisa wiring 2 kabel di 1 push button,
      Prinsip kerja push button adalah sebuah mekanik spirng atau peer ya jadi dia ditombol itu di tekan
      Ketika dilepas push button akan kembali lagi seperti semula.

      5. Selector Switch
      Selector Switch adalah Komponen listrik yang berfungsi sebagai memilih atau select sebuah mode di panel listrik, selector switch memiliki kontak yaitu berupa kontak N/O atau N/C.
      Perbedaan dengan push button adalah dalam hal posisi jika push button bekerja ketika ditombol sedangkan Selector Switch  bekerja ketika diputar ke kiri atau ke kanan.
      Contoh sebuah Selector Switch dipakai pada panel listrik untuk menggerakan conveyor maju mundur, jadi Selector Switch ini akan memilih maju atau mundur.
      Ketika Selector Switch sudah dipilih baru bisa ditombol push button motor akan berjalan sesuai Selector Switch yang dipilih.

      6. Emergency Stop
      Emergency Stop adalah komponen yang berfungsi untuk memberhentikan mesin secara cepat (emergency), kontak emergency stop ini biasanya menggunakan kontak N/C.
      Prinsip kerja Emergency adalah memutus tegangan utama control pada mesin, untuk mengaktifkan emergency stop ini tinggal di pencet dengan telapak tangan.
      Jika ingin melepas emergency tinggal di putar ke kanan emergency akan kembali normal.

      7. Kontaktor 3 Phase atau 1 Phase
      Pengertian Fungsi dan Wiring Dari Kontaktor bisa disebut Magnetic Contactor karena prinsip kerja dari kontaktor tersebut menggunakan medan magnet yang timbul oleh arus listrik.
      yang didalam kontaktor tersebut ada sebuah kumparan untuk menjadi magnet karena dialiri oleh arus listrik.

      Kontaktor menimbul kan magnet yang bisa disebut Coil yang menarik kontak - kontak NO (Normaly Open) menjadi NC (Normaly Close) bahasa indonesia menutup.

      8. Timer Listrik
      Timer atau kepanjanganya Time Delay Relay adalah sebuah komponen elektronik yang dibuat untuk menunda waktu yang bisa disetting sesuai range timer tersebut
      Dengan memutus sebuah kontak relay yang biasanya digunakan untuk memutus atau menyalakan sebuah rangkaian kontrol.
      Timer ini biasanya digunakan sebagian besar dunia industri, yang dirangkai dengan berbagai komponen elektronik juga seperti kontaktor, TOR / Overlaod , dan juga push button untuk rangkian kontrol pendukung. 

      9. TOR ( Thermal Overload Relay)
      Thermal Overload Relay (TOR) adalah sebuah alat elektronik untuk mengamankan beban lebih Overload bedasarkan suhu Thermal yang mempunyai relay untuk memutuskan sebuah rangkaian kontrol
      Seperti direct online dan start delta untuk mengoperasikanya biasanya hanya menggunakan push button Start / Stop.
      Thermal Overload Relay bekerja saat suhu pada dalam TOR tersebut terpenuhi, jadi TOR ini terdapat sebuah settingan berapa maksimum amper untuk melakukan trip jika ampere tersebut sudah terpenuhi. Didalam TOR tersebut ada sebuah Bimetal Element yang menjadi panas saat ampere beban sudah melebihi ampere settingan TOR.
      Mangkanya disebut Thermal yaitu suhu, gampangnya seperti kabel yang hanya mampu dilewati arus 5A tetapi bebanya 10A maka kabel tersebut akan panas
      Seperti halnya TOR ini prinsip kerjanya sama tetapi bedanya ketika suhu tersebut terpenuhi maka akan menggerakan sebuah coil untuk menutup atau membuka kontak yang ada di TOR tersebut.

      10. Capacitor Bank
      Mengapa Capacitor bank banyak di pasang pada dunia industri pabrik, karena itu tadi pabrik sekarang banyak menggunakan electro motor yang menimbulkan beban induktif yang mempengarui pada faktor daya atau cos phi.
      Industri sangat berhati-hati dengan faktor daya sebab jika sebagian besar pabrik tersebut memakai listrik dari PLN ( Tidak mempunyai pembangkit listrik sendiri ) maka faktor daya perlu diperhatikan,
      PLN telah menentukan nilai minimum dari faktor daya tersebut dengan nilai 0.85.

      11. Terminal Block
      Komponen Terminal Block ini berfungsi sebagai tempat penyambungan kabel (terminal) antara kabel dalam panel listrik dengan kabel yang keluar di panel listrik.
      Terminal block ini juga membuat panel menjadi tampak prefesional dan ramping karena tidak memakan banyak tempat.





      12. Omega Rails atau Din Rails
      Omega Rails ini berfungsi sebagai sebuah freme atau tatakan untuk menempelnya seperti kontaktor, mcb, terminal block, power supply, plc, dan komponen lainya yang mendukung untuk diletakan pada omega rails ini.

      13. Relay Control 
      Komponen Listrik Relay adalah suatu peranti yang menggunakan elektromagnet untuk mengoperasikan seperangkat kontak N/O atau N/C. terdiri dari kumparan kawat penghantar yang dililit pada inti besi.
      Bila kumparan ini dienergikan, medan magnet yang terbentuk menarik armatur berporos yang digunakan sebagai pengungkit mekanisme sakelar magnet.





      14. Power Supply 
      Komponen Power Supply berfungsi sebagai penyearah tegangan dari 220V ke 24V DC maupun 12V DC tergantung kebutuhan anda.
      Power Supply ini ada yang bisa diletakan pada Omegra Rails maupun langsung di baut pada base plate panel listrik.







      15. Programmable Logic Control (PLC)
      PLC (Programmabel Logic Control) adalah perangkat yang dibuat untuk menggantikan Cirkuit relay sekuensial yang diperlukan untuk kontrol alat berat.
      PLC bekerja dengan melihat inputnya dan tergantung pada keadaannya, menyalakan / mematikan outputnya. Pengguna memasuki suatu program, biasanya melalui software, yang memberikan hasil yang diinginkan.

      16. Ampere Meter Digital
      Ampere Meter Digital ini berfungsi untuk menampilkan sebuah beban ampere pada mesin listrik yang saat ini digunakan secara realtime.

      Komponen ini juga perlu pendukung sensor yaitu CT atau bisa disebut Current Transformer.







      17. Volt Meter Digital
      Volt Meter Digital ini berfungsi untuk menampilkan sebuah voltase atau tegangan 1 phase maupun 3 phase pada mesin listrik maupun panel distribusi secara realtime.








      18. Power Meter Digital
      Power Meter Digital berfungsi seperti halnya amper meter, volt meter tetapi ini lebih lengkap, semua ada didalam power meter digital ini.

      Mulai dari watt yang terpakai, berapa jumlah kWH yang terpakai, Cos Phi atau faktor daya ditampilkan juga.
      Jadi lebih effisien 1 untuk semua power meter digital ini, fungsinya sangat penting untuk panel distribusi listrik.



      19. Human Machine Interface (HMI)
      Human Machine Interface (HMI) adalah komponen dari perangkat tertentu yang mampu menangani interaksi manusia-mesin.

      HMI terdiri dari perangkat keras dan perangkat lunak yang memungkinkan input pengguna untuk diterjemahkan sebagai sinyal untuk mesin, pada gilirannya, memberikan hasil yang diperlukan kepada pengguna.
      Teknologi antarmuka manusia-mesin telah digunakan di berbagai industri seperti elektronik, hiburan, militer, medis, dll.

      Antarmuka manusia-mesin membantu dalam mengintegrasikan manusia ke dalam sistem teknologi yang kompleks.

      Antarmuka manusia-mesin juga dikenal sebagai antarmuka manusia-mesin (MMI), antarmuka manusia-komputer atau antarmuka manusia-komputer.

      Semoga bermanfaat untuk artikel "Komponen Panel Listrik" jika anda suka bisa dishare ketemenya dan jika ada pertanyaan mengenai seputar artikel ini tinggalkan komentar atau bisa juga kirim email.

      Kami memastikan data center dan ruang server anda bekerja optimal.
      Silahkan hubungi Tim kami untuk mendapatkan penawaran Terbaik terkait kebutuhan anda.
      CONTACT US : dcim@dayaciptamandiri.com

      FirePro Aerosol Fire Extinguishant System

      $
      0
      0

      FirePro adalah sistem pemadaman api kebakaran dengan menggunakan gas aerosol. Dengan menggunakan bahan condensed aerosol solid compound yang sudah di mendapatkan sertifikasi dari Underwriter Laboratories (UL). Yang mampu bertahan selama 15 tahun. Dengan hampir tidak ada penambahan biaya perawatan, karena kita hanya perlu mengadakan pemeriksaan jalur eketrikal saja.


      Komponen Generator aerosol FirePro

      Sistem aktifasi generator ada 3 yaitu :
      1. Secara Elektrik : menggunakan koneksi dengan BTA atau koneksi dengan panel kontrol rilis.
      2. Secara thermal : dihubungkan dengan Linear Heat Detector (LHD)
      3. Aktifasi sendiri : pada suhu 300°C Electrical Activator akan mengaktifasi generator. Ini adalah skema backup jika rangkain elektrikal tidak terputus baik karena aliran listrik terputus atau karena jalur perkabelan terputus.
      Setelah itu FPC mengalami proses tranformasi secara Exothermic menjadi gas aerosol. Proses ini mengakibatkan suhu yang panas sekali hingga sekitar 800°C. Media pendingin dari bahan keramik akan menurunkan suhu gas aerosol hingga mendekati suhu ruangan. Sebelum akhirnya melewati discharge outlet untuk memadamkan api.

      Keunggulan FirePro Aerosol Fire Extinguishant System.

      A. Ramah Lingkungan (Green Technology)
      Bahan FPC condensed aerosol yang bahan dasarnya Garam Potasium (Potassium Salts) tidak menimbulkan bahaya. Baik itu bahaya terhadap manusia maupun lingkungan. Oleh karena itu FirePro sudah mendapatkan telah disertitifikasi, terdaftar dan disetujui oleh Lembaga Sertifikasi Internasional.
      – Tidak mengurangi lapisan Ozone
      – Tidak menyebabkan global warming.
      B. Pemadaman Cepat (Metode Memutus Reaksi Kimia)

      Api dibentuk oleh 3 unsur utama yaitu : Bahan bakar, Oksigen dan Panas. Bahan pemadam api yang ada dipasaran saat ini umumnya memadamkan api dengan mengurangi salah satu unsurnya, seperti :
      • Mendinginkan : pemadam dengan bahan dasar air. Prinsip kerjanya dengan menyemprotkan air berusaha untuk mendinginkan panas hingga dibawah titik bakar dari bahan bakarnya.
      • Mengurangi Kadar Oksigen : pemadam bahan dasar gas. Prinsip kerjanya adalah dengan menambahkan gas yang akan menekan kadar O2 sehingga api padam.
      • Memutus Rantai Reaksi Kimia : FirePro Aerosol. Dengan menggunakan unsur Kalium yang merupakan unsur kimia yang stabil, maka akan mengikat radikal bebas dalam api, sehingga api cepat padam.
      Untuk lebih jelasnya marilah kita perhatikan digram dibawah ini.

      Bagian pertama kita lihat bahan bakar dan oksigen yang dipicu oleh panas yang menyababkan kebakaran. Kandungan dari api tidak lain adalah unsur radikal bebas yang teridiri dari, O, H dan OH.

      Bagian kedua Generator FirePro yang diaktifkan menimbulkan 2 aksi : secara fisik gas akan menekan api, secara kimia bereaksi dengan unsur radikal bebas. Sementara itu energi dari api dimanfaatkan oleh unsur K yang akan menarik unsur OH yang merupakan unsur utamanya.

      Bagian ketiga : Setelah unsur OH yang ada dalam api ditarik oleh unsur K dan membentuk KOH (Potassium Hydroxide), maka api sudah padam dalam hitungan detik. Selanjutnya senyawa KOH melakukan reaksi lanjutan menghasilkan O2 dan  K2CO3 (Potassium Carbonate) kembali.

      C. Hampir Tanpa Residu. Garam potasium hasil akhir dari proses pemadaman sangat sedikit sekali, sehingga kita bisa menyapu atau mengelap property yang dilindungi. Bandingkan dengan gas FM200 yang perlu penanganan khusus untuk membersihkan.

      Pemasangan FirePro Aerosol Fire Extinguishant System

      1. Stand Alone (Berdiri sendiri)
      Sistem ini digunkan untuk melindungi area yang perluasannya sempit. Seperti pada panel listrik yang merupakan sumber utama kebakaran dari korsleting. Sistem stand alone ini belum bisa dilakukan oleh media pemadam lain. Generator yang digunakan berbentuk silinder dengan aktifasi menggunakan Bulb Thermal Activator (BTA). Bola kaca air raksa akan pecah pada suhu tertentu (varian dari 57°C – 182°C), dan mengaktifkan generator secara elektrik. Pemasangan sangat mudah karena FirePro menyediakan breket serta magnet yang kekuatannya sudah mendapat sertifikasi dari UL. Sehingga tinggal ditempelkan saja pada bahan besi pada panel tersebut.

      2.System (Total Flooding System)
      Prinsip dasar dari sistem total flooding adalah baham pemadam harus memenui ukuran dari volume ruangan agar pemadaman maksimal. Digunakan untuk area perlindunga yang lebih luas, seperti ruang produksi atau gudang. Generator yang dipasang pasti lebih dari 1 unit, dan semua generator tersebut harus rilis atau discharge secara bersamaan.
      FirePro Total Flooding System

      Sertifikasi, Listing dan Approval FirePro Aerosol Fire Extinguishant System

      Sedangkan untuk aplikasi Marine atau kelautan berikut ini adalah sertifikasi, listing dan approvalnya :

      Dimana saja Generator FirePro ini bisa di pasang?
      1. Panel listrik : mayoritas kebakaran untuk daerah pabrik adalah adanya korsleting listrik dari dalm panel listrik. Sehingga dengan pemadaman yang cepat akan menyelamtkan aset Anda.
      2. Ruang Trafo : Ruangan ini dengan panas yang tinggi dan bahan bakar minyak tentu rawan terhadap terjadinya kebakaran.
      3. Ruang Arsip : tempat penyimpanan dokumen penting dari perusahaan Aanda harus mendapatkan perlindungan. Karena bahan kertas yang mudah terbakar.
      4. Ruang server : Banyaknya intalasi kabel di ruangan ini tentu saja resikonya sangat tinggi terjadi korsleting listrik.
      5. Ruang produksi : terutama adalah area sekitar mesin.
      6. Ruang Gudang
      7. Dan seluruh hampir seluruh ruangan lainnya bisa diaplikasikan
      PT DAYA CIPTA MANDIRI SOLUSI Memberikannya Solusi Untuk :
      - Pemasangan Fire Extinguisher (FirePro / FM200)
      - Perawatan / Maintenance FirePro / Aerosol System

      Staf penjualan kami siap menjawab pertanyaan apa pun dan memberi Anda Quotation.
      Hubungi :
      dcim@dayaciptamandiri.com

      PRTG Solusi Cepat dan Efisien Bagi Perusahaan di Masa Pandemi Covid-19

      $
      0
      0

       



      PRTG merupakan produk dari Paessler (www.paessler.com)

      PRTG telah banyak digunakan di berbagai perusahaan dan instansi , baik dari skala kecil hingga enterprise. Penggunaan PRTG dimulai dari tahun 2009 semenjak kami memegang produk ini.

      Kami merupakan Platinum Partner PRTG sejak 2009, dengan prestasi implementasi di berbagai perusahaan dan instansi.

      PRTG dihitung berdasarkan Sensor, bukan device. PRTG hanya mengambil informasi yang diperlukan sehingga penggunaan bandwidth lebih hemat. Itulah sebabnya perusahaan ISP , Telco memilih PRTG.


      PRTG hanya menghitung Sensor, tidak ada Add-On. Semua sangat simple dan tepat dengan PRTG.
      GET YOUR FREE TRIAL (klik disini)

      Alat Monitoring Jaringan Populer

      Terdapat banyak network monitoring tool yang dapat dijadikan pilihan network engineer. Pemilihan network monitoring tool harus disesuaikan dengan kebutuhan.

      Aplikasi monitoring jaringan berkembang pesat di seluruh dunia. Perangkat lunak maupun utilitas baru dirilis setiap tahun untuk memfasilitasi manajemen jaringan dan infrastruktur IT. Ada banyak Network monitoring tool (alat monitoring jaringan) yang dapat menjadi pilihan network engineer. Pemilihan Network monitoring tool harus disesuaikan dengan kebutuhan.
      Berikut adalah  Network monitoring tool paling populer yang kami sarankan :

      PRTG Network Monitor dari Paessler

      PRTG merupakan sebuah aplikasi monitoring jaringan yang dikenal karena kemampuannya yang canggih dalam mengelola insfrastruktur IT. Semua perangkat, sistem, traffic, dan aplikasi dalam jaringan bisa dengan mudah ditampilkan dalam hierarki antarmuka yang sangat mudah digunakan.

      PRTG menggunakan teknologi seperti SNMP, WMI, SSH, Flows / Packet Sniffing, HTTP Request, REST API, ping, SQL. Hal ini dapat dikatakan, PRTG network monitoring application adalah pilihan ideal untuk perusahaan yang masih kurang pengalaman dalam network management.

      Fitur paling unggul dari PRTG adalah kemampuannya untuk memonitor perangkat ke pusat data yang menggunakan aplikasi seluler. Sebuah QR code yang cocok dengan sensor label cetak akan dipasang ke pangkat fisik. Lalu, untuk memindai kode dan melihat informasi perangkat, gunakan aplikasi seluler dan kemudian ringkasan informasi perangkat akan segera muncul pada layar seluler.

      Silahkan hubungi Tim kami untuk mendapatkan penawaran Terbaik terkait kebutuhan anda.
      CONTACT US : dcim@dayaciptamandiri.com

      Pengertian dan Fungsi Optical Distribution Point Atau ODP

      $
      0
      0


      Memahami ODP Jaringan Akses Fiber Optik. Dikala ini telkom sudah gencar melaksanakan realisasi jaringan indihome fiber, yang mana teknologi yang digunakan oleh produk indihome merupakan teknologi jaringan GPON dengan mengadopsi media penghantar informasi suatu serat optik ataupun yang lebih diketahui dengan nama Fiber Optic( FO).

      Hanya menegaskan kembali, kalau saat sebelum bergeser ke indihome, telkom mempunyai produk layanan internet yang diucap Speedy dengan memakai teknologi jaringan ADSL serta masih menggunakan media suatu suatu kawat tembaga bagaikan media penghantar informasi dan mempunyai kecapatan optimal sampai 5 Mbps.

      Serta buat dikala ini pihak telkom sudah melaksanakan revolusi digital dengan mengusung produk yang bernama Indihome yang mencampurkan layanan Internet, IPTV, serta Telepon Rumah ataupun yang sering di dengar dengan layanan Triple Play Fiber Optic.

      Share postingan kali ini hendak mangulas sebagian fitur jaringan yang digunakan buat menunjang layanan fiber optik sehingga secara tidak langsung bila perlengkapan ataupun fitur ODP tersebut telah terpasang di dekat tempat tinggal kamu, hingga di yakinkan kalau daerah kamu telah tercover oleh layanan internet dengan bandwidth kecepatan besar sampai lebih dari 100 Mbps.

      Didalam jaringan fiber optik kita hendak memahami sebutan Fiber To The Home ataupun di pendek dengan sebutan FTTH yang ialah sesuatu akses jaringan yang menghubungkan antara pusat layanan dengan perlengkapan pelanggan dengan memakai fiber optik. 

      Pengertian dan Fungsi ODP

      ODP merupakan singkatan dari Optical Distribution Point yang ialah suatu fitur pendukung layanan fiber optik yang berperan bagaikan titik terminasi kabel drop optik ataupun tempat buat membagi satu core optic ke sebagian pelanggan( halte), serta ODP dibagi dalam sebagian tipe, ialah.

      Optical Distribution Point merupakan tempat terminasi kabel yang mempunyai sifat- sifat tahan korosi, tahan cuaca, kokoh serta kuat dengan konstruksi buat dipasang diluar. ODP berfungsi bagaikan tempat instalasi sambungan jaringan optik single- mode paling utama buat menghubungkan kabel fiberoptik distribusi serta kabel drop. Fitur ODP bisa berisi optical pigtail, connectoradaptor, splitter room serta dilengkapi ruang manajemen fiber dengan kapasitas tertentu.

      ODP dipasang wajib cocok dengan peruntukannya, ODP Pole cuma boleh dipasang pada tiang, ODP Pedestal dipasang pada permukaan tanah, ODP Wall dipasang pada bilik serta ODP Clousure cuma boleh dipasang pada kabel SCPT serta kabel SSW baik pada pertengahan gawang ataupun di dekat Tiang.Metode pemasangan ODP dengan metode memetik salah satu core dari kabel distribusi secara urut. Setelah itu core tersebut dimaskukan kedalam pasif, pasif yang biasa digunakan pada ODP ialah pasif 1/ 8. Sehingga pasif tersebut di split jadi 8.

      Macam-Macam Jenis ODP

      ODP Closure
      ODP Closure merupakan suatu kotak gelap yang terpasang pada kabel jaringan telepon utama SCPT serta kabel SSW, serta buat letak pemasangan dapat terletak dekat dengan tiang telepon atapun terpasang pada pertengahan kabel diantara 2 tiang telepon.

      ODP Pole

      ODP Pole merupakan suatu kotak halte kabel fiber optik yang di pasang pada tiang kabel telepon yang berperan bagaikan tempat buat membagi core serat optic dari kabel utama ke pelanggan sehingga bila rumah kamu dekat dengan kotak ODP Pole/ ODP Wall hingga hendak lebih gampang bila mau mengajukan pemasangan jaringan indihome.

      Gimana bila tempat tinggal kamu jauh dari ODP Pole ataupun berjarak lebih dari 100 m, hingga buat jadi pelanggan indihome kamu wajib membeli sendiri bonus kabel fiber
      ( bila rumah kamu berjarak lebih dari 100 m dari Box ODP Pole).

      ODP Pedestal
      ODP Pedestal merupakan suatu tabung yang berisi sambungan kabel fiber optik yang di taruh di atas tanah, serta biasanya ODP Pedestal ataupun ODP tanah di pasang di dekat komplek perumahan maupun zona perkantoran.

      Itulah artikel yang dapat saya sampaikan mengenai pengertian dan fungsi Optical Distribution Point atau ODP pada kesempatan kali ini, jangan lupa untuk share artikel ini ke media sosial kalian terima kasih.

      Kami memastikan Kabel anda terstruktur dan bekerja optimal.
      Kami Melayani Perapihan Cabling.
      Produk yang kami gunakan : Tyco AMP, Panduit, Netviel, LS-Cable, Rosenberger, Belden.

      Silahkan hubungi Tim kami untuk mendapatkan penawaran Terbaik terkait kebutuhan anda.
      CONTACT US : dcim@dayaciptamandiri.com
      Viewing all 2824 articles
      Browse latest View live