BLOG DAYA CIPTA MANDIRI GROUP

The following information was contributed by the developers of the Help Desk Management Kit:

Achieving and maintaining a successful Help Desk operation can depend on a number of pre-requisites that need to be in place. These components have been identified from surveys covering a wide range of help desk facilities.

1. Set clear, realistic and quantifiable goals and objectives
Establish goals and objectives for the help desk operation that support and match the organizations overall aspirations. The key purpose of a Help Desk function is to provide effective support for the services being delivered to clients. The Help Desk usually provides the first level of support for a client and often co-ordinates the overall support process. The Help Desk delivers value to an organization by achieving the following goals and objectives:

- Provides strategic functionality in supporting the customer relationship objectives
- Helps ensure customer satisfaction
- Supports the retention of customers
- Identifies additional business opportunities
- Provides a managed and structured approach for the service support activities
- Enables identification of customer training requirements
- Monitors service activities and service performance levels
- Optimizes staff and other resources
- Enables early identification of service deficiencies

2. Understand your customers� requirements and carefully plan the Help Desk structure
A typical Help Desk structure providing various support levels to enable focused response to problems and system failures could be described as follows:

- Front Line Support
This unit is particularly key within the Help Desk structure. The front line personnel are the first people that the customer will contact in the event of a problem or incident. Their job is to record accurate information regarding the problem or incident, and to make an initial assessment of the classification level to be assigned to the problem. The front line support staff will then either identify potential solutions to the problem, or refer the matter directly to level two or level three support staff.

- Second Level Support
The second level support unit is usually staffed with a higher level of technical or specialised skills than the front line unit. The second level support unit is often located within the Help Desk premises, although this is not a mandatory requirement within this structure.

- Third Level Support
Usually staffed with highly technical specialists who will assess and advise the customer of the anticipated time for the resolution of the problem or incident, and then resolve the problem.

3. Establish and implement secure, practical and cost effective policies
Recent studies have shown that over 60% of Help Desk organizations have inadequate Information Security Policies and, as a result there is an inadequate basis upon which to build the appropriate safeguards to protect the life blood of the Help Desk � its information systems. You should research and obtain suggested baseline policies and rules to be applied to meet these requirements. Your organization should adopt only those policies that meet their own requirements and the organisation�s risk profile. Whilst Information Security Policies lay a solid foundation for the development and implementation of secure practices within your organization, the Policies themselves are not usually instructional or overly descriptive. They represent the rules which must be adhered to by the organization. Compliance will require an understanding by staff of not only the individual policies but also of the circumstances in which such compliance is expected in their day-today activities. Knowing the Policies is only one half of the equation - staff need to know how they should comply, from a procedural perspective.

4. Ensure adequate staffing levels
The following information requirements are provided to help to determine the number of personnel required to support the Help Desk function together with an assessment of the skill sets required:

- Service quality expectations
- Problem resolution expectations
- Complexity and age of the IT systems on which the services are dependant
- Available budget
- Number of customers being supported
- A profile of customers time support requirements ( i.e. 24/7 or 0800 � 1800 hours Monday to Friday )
- Foreign language requirements
- Type of incidents predicted
- Duration of resolution times
- Specialist expertise required
- Volume of incidents
- Work load graphs
- Service level agreements
- Existing skill levels of staff
- Adequacy of procedural documentation
- Automated support systems being used
- Cover for holidays, sickness or other employment contract entitlements

5. Provide ongoing comprehensive training to all levels of management and staff
Communication skills must be developed to a very high degree together with an understanding of the technical issues involved with the delivery of the organisation's products and services. It is not necessary for each Help Desk representative to have detailed knowledge of highly sophisticated technical systems, but they should have sufficient understanding of the technicalities involved to identify the correct level of technological support to be supplied by the organisation's technical staff. Areas for Help Desk training include:

- Telephone handling techniques
- Product and service orientation
- Communication skills development
- Complaint handling skills
- Listening skills
- Stress management
- Recording and note taking skills

A principal focus for customer handling skills is the building up of customer satisfaction levels. This is to support the objective of long term retention of customers through the building of effective and strong working relationships with the customer�s staff

6. Maximize automation of Help Desk operations on a cost-effective basis
Automation of the help desk operations should be maximized but care must be taken to ensure that this is done on a cost effective basis. There are a number of tools currently available which would assist the efficiency of the Help Desk, but these need to be properly analyzed to ensure that the technological investment is offset by a combination of lower costs of operation and improved customer service. Available Help Desk technology tools include:

- Help Desk management
- Advanced telephone systems including auto-routing, hunting, voice integration (CTI)
- Interactive voice response systems
- Electronic mail systems
- Network management tools
- E-mail operations management systems
- Analysis and diagnostic tools
- Remote diagnostic and resolution support systems
- Fax servers
- Internet technology

7. Manage and monitor service level performance through service level agreements
The service level agreement is the ideal vehicle to establish and agree metrics and benchmarks for measuring performance. A system must be set up to keep track of the volumes of calls and queries received. It must also monitor the resolution times for each of type of problem or incident so that improvements in service levels can be attained and measured. The type of information that could be included the following:

- Number of calls received
- Number of problems recorded
- Average resolution time per problem classification level - Number of problems resolved
- Number of unresolved problems
- Number of system changes requested
- Number of changes approved
- Number of changes implemented
- Frequency that escalation procedures have been evoked

It is necessary to monitor staff utilization and this is achieved through workload analysis. It is important to measure both average utilization and also peaks and troughs and monitor the periods in which they occur.

8. Control potential problem areas through effective change management procedures
Reduce potential problem areas through application of change management disciplines. The objective of the change management process is that standardized procedures and controls are applied to all proposed changes to the systems, product or service deliveries to the customer. The procedures are prepared for the people who are responsible for making such changes in order that they can handle such activities in a structured manner. The change management procedures are normally applied to proposed changes within the following areas:

- System software
- Application software
- Documentation
- Operational procedures
- Hardware
- Communications
- Support systems
- Maintenance procedures

If change management is not standardized then changes are likely to occur in an uncoordinated and uncontrolled manner.

9. Ensure effective problem management and escalation
The main goal of problem management is in the detection of the underlying reasons for a particular incident and the resolution and prevention of future recurrences of that incident through problem elimination methodology. Effective problem identification is dependant on a formal incident management process. In the first instance the emphasis should be on problem and error control processes, particularly where specialized resources are in scarce supply.

Escalation management is the involvement of increasingly senior levels of management at preset intervals whenever a problem remains unresolved. The level of problem or incident classification is a critical feature within the escalation management process. For example, a priority 1 or mission critical problem could be automatically notified to a senior management level within the supplier�s organization very shortly after the customer notifies the Help Desk about the problem. On the other hand a priority 4 problem that merits a low priority rating would only be notified to the supplier�s senior management after a significant time had lapsed

10. Hold regular service review meetings
On a regular basis the service quality levels need to be reviewed with the customer. This is normally handled by holding periodic service review meetings between the customer�s representatives and Help Desk staff or other supplier representatives nominated for this task. These meetings can be at regular intervals or they can be triggered by a significant problem experienced by the customer or simply because the customer has requested a meeting to discuss concerns that they may have. The key document to form the basis of these meetings is the service level agreement and these meetings will tend to use this document as a basis for discussing service expectations and actual delivery. At these meetings it is important to discuss whether the services being delivered are in full conformity with the agreement and whether any deviations that have occurred that need to be rectified.

The service review meetings can be either formal or informal. This is a matter to be agreed between the two parties at an early stage in the discussions. If it is agreed that a high degree of formality is required then minutes should be kept in sufficient detail to satisfy the needs of both parties. It is also beneficial in these more formal gatherings for there to be a detailed agenda with advance notice of some of the more critical issues being discussed. If the meeting is to proceed on an informal basis then formal minutes would not normally be necessary although it is always advisable for the main findings and agreements reached during the meeting to be communicated in writing after the meeting has concluded

Integrate AKCP sensorProbe devices with Nagios® XI™ 5 to be alerted when temperature, humidity, or other environmental variables exceed specific thresholds.

In this example, we’ll demonstrate how to monitor AKCP Dual Temperature and Humidity Sensors connected to the AKCP sensorProbe platform. All of AKCP’s Intelligent Sensors connect using plug and play RJ45 connectors and can be monitored from Nagios using similar steps. For more information on other sensors please contact our support team.

Prerequisites for monitoring a sensorProbe device via SNMP Traps in Nagios XI 5

It is possible to monitor the AKCP sensorProbe actively OR passively within Nagios XI 5. This integration guide assumes that you have already set up your Nagios XI 5 system to receive SNMP traps. If you have not already configured Nagios to receive SNMP traps use the following guides provided by Nagios.

Integrating SNMP Traps with Nagios XI

Step 1 : Download the AKCP MIB for use within Nagios XI

Monitoring a temperature sensor via SNMP requires an AKCP MIB definition file. The first step is to download and install the correct MIB file. You can download the AKCP MIB for monitoring temperature sensors via SNMP at the following link :

AKCP MIB File Download

Once you have downloaded the AKCP MIB file for monitoring your temperature sensor, you need to unzip the archive and install the akcp.mib from the Nagios Web Interface.

You can do this by navigating to Admin > System Extensions > Manage MIBs

Click on the Browse button and locate the akcp.mib

Select Process trap and then click Upload MIB.

To verify that your MIB file was processed correctly by Nagios XI, on your Nagios server check that the akcp.mib file is located in

/usr/share/snmp/mibs

Run the addmib command from the command line of your Nagios XI server as the root user. The command will look like :

addmib /usr/share/snmp/mibs/akcp.mib

Step 2 : Run the SNMP Wizard to set up Active Checks

The next step is to run the SNMP Wizard by navigating to the Configure > Run the Monitoring Wizardpage via the top navigation bar, and select SNMP Wizard.

In Step 2 enter the IP address for the AKCP sensor in the Device Address box and click Next.

Step 3 requires you to enter a SNMP Community string (it is not suggested to use the default of “public”) and also the SNMP version. For this example we used version 1. The SNMP Authentication section does not apply to this set up because we are using SNMP v1.

The SNMP Authentication section does not apply to this set up because we are using SNMP v1.

Finally, you will need to enter information in to the SNMP Service section. Create a row for each sensor. For example the SNMP OID for the temperature sensor on RJ45#1 is:

1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0

The SNMP OID for the humidity sensor on RJ45#1 is:

1.3.6.1.4.1.3854.1.2.2.1.17.1.3.0

If you added an additional sensor in the second port (#2) their OID would be very similar to the temperature and humidity sensors.

You will have to change the 0 (zero) at the end of the OID to 1 (one). These sensors would be added to the SNMP service section as:

1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1

and

1.3.6.1.4.1.3854.1.2.2.1.17.1.3.1

Continue to fill in the remaining fields in the SNMP Service section. It is important to note the warning and critical values in this example are set up as ranges.

A critical alert occurs when the temperature is outside of the range 60-85 degrees. Finally, select the check boxes next to the temperature sensor and humidity sensor OIDs and click Next.

If you are willing to accept the default monitoring settings, you can click Finish. Otherwise continue to enter your preferences for monitoring these service checks through each step of the wizard and clickFinish.

Once complete, you can navigate to Home > Services, and verify that your checks are working. The active checks are the Humidity Sensor 1 and Temperature Sensor 1 listed below.

Configuring The Dual Sensor To Send Passive Checks Via SNMP To Nagios XI

Sending Passive Checks to Nagios requires some set up on the AKCP sensorProbe2. To do this we need to log into the AKCP Web interface by entering the IP address in to your browser. The web interface will require you to enter your user account and password.

First you will want to set up your check thresholds on each sensor, and for this example we will set up the Temperature sensor on Port 1. Click on the Sensor tab, then under Environmental select Temperature, and finally select the Temperature sensor on port 1. From this screen enter your threshold information for critical events.

Next click on the Traps tab to enter pertinent information for sending SNMP traps to Nagios XI. Enter the IP of your Nagios server for the Destination IP. Next enter a community string. It is always a good idea to change the default community string from “public” to something else. language translate For our example, we set the Send Keep Alive Traps to Off. Click on the Save button and you are done with the set up required for the AKCP sensor.

Note: The AKCP sensorProbe2 allows you to send SNMP traps to two different destination IP addresses if needed.

Configuring Nagios XI To Receive Passive Checks Via The SNMP Trap Wizard

Once you have your Nagios server set up to receive SNMP Traps as outlined in the Prerequisite section, you will be able to set up Nagios XI to receive passive checks from the AKCP sensorProbe2.

To start, run the SNMP Trap Wizard by navigating to the Configure > Run the Monitoring Wizard page via the top navigation bar, and select SNMP Trap Wizard.

Click Next for Step 2. Then select the host you wish to enable SNMP traps for in Step 3 and click Next.

You can now select Finish if the default notifications options suit your needs, otherwise continue to set up notification and group options as you see fit.

You should now be able to see traps coming in from the Temperature and Humidity sensors. The passive check is listed below as the SNMP Traps check.

If for some reason you don’t see SNMP traps changing the status of your service check in Nagios XI, check your Unconfigured Objects page (accessed via Admin > Monitoring Config > Unconfigured Objects).

Also, reviewing the logs created by SNMPTT can help you troubleshoot the issue as well.

tail /var/log/snmptt/snmptt.log 
tail /var/log/snmptt/snmpttunknown.log 
tail /var/log/messages

PRTG Cloud Sensors - Part 1: Monitor Google Analytics & Drive, Microsoft OneDrive and Dropbox

New Sensor Types to Monitor Your Favorite Cloud Services

Google Analytics Sensor

Google Drive Sensor

Microsoft OneDrive Sensor

Dropbox Sensor

Sensor of the Week:MongoDB System Health Sensor

Monitor the Health Status of Your MongoDB Server via HTTP

Automatically Convert Network Alarms into Tickets. Restore Services Sooner.

10 Components to Simplify Help Desk Management

Application Discovery and Dependency Mapping (ADDM)

Discover resources faster

Design a business service dependency map.

View the status of applications, and troubleshoot quickly.

CMDB integration and updates made effortless.

Healthcare IT Monitoring

HEALTHCARE IT MONITORING WITH PRTG NETWORK MONITOR

FREE HEALTHCARE IT INFRASTRUCTURE MONITORING SOFTWARE

Basic upload

Multiple-files upload

1. 'View as' Custom

Check box field code

Text box field code

2. List page Javascript OnLoad code

3. Validation part

Monitor your Datacenter Performance from OpManager's unified web console

Physical and virtual server monitoring

In-depth Application Monitoring

Flow-based bandwidth monitoring

Datacenter environment monitoring

Prerequisites for monitoring a sensorProbe device via SNMP Traps in Nagios XI 5

Step 1 : Download the AKCP MIB for use within Nagios XI

Step 2 : Run the SNMP Wizard to set up Active Checks

Configuring The Dual Sensor To Send Passive Checks Via SNMP To Nagios XI

Configuring Nagios XI To Receive Passive Checks Via The SNMP Trap Wizard

Keep Your Network on the Safe Side!

1. Install the Temperature Sensor at each cold isle.

2. Notification Wizards alert users to changes in Sensor Status.

3. Receive real-time sensor alerts to your phone or PC.

Sensor of the Week:
MongoDB System Health Sensor