Skip to main content

Improving the cost effectiveness of operating ATMs


When an ATM fails in is most likely to be one of the following causations:
  • the utility power such as that supplied by the municipality or Eskom has failed;
  • the ATM hardware has failed; and
  • the network connectivity to the ATM has failed.
In all cases a network management tool does not provide causation. The loss of connectivity to the ATM and the ATM infrastructure does not provide any measure of realtime diagnosis. Should power be restored the network management tool can potentially determine whether ther has been a power outage by referencing the system clock on the network equipment and determining if it has been reset.
Some network equipment have a "last gasp" functionality, but in most deployment cases this does not function. The equipment failure is combined upstream with a service provider failure and the alerts are not received.
The DS solution is to use a Powalert.
The Powalert is an Internet of Things sensor that interoperates with the wider range of sensors and gateways in the PowaINFRA range. The range addresses a number of uses cases in Information Technology, food processing, medical, building and real estate management and the financial sector.
The Powalert provides:
  • Provides up time Service Level Agreement (SLA) metrics for the utility feed which is directly connected;
  • Provides up time SLA metrics for attached equipment;
  • Reports energy usage in kW/h;
  • Provides a historical record of power quality;
  • Remote Power On Reset (POR) of the attached equipment;
  • Ability to monitor life of battery attached to inverter; and
  • Ability to monitor SLA metrics for utility feed into inverter.
The Powalert is able to provide causation to any outage as was described in the opening statements of this post.
The bank's operations centre will dispatch a resource to an ATM to determine the cause of an outage. The cause is unknown until the resource is on site. The cost of the rolling wheels visit to the ATM also involves the provision of suitable security which is an additional expense. Dependent on the skills of the resource, they might not be able to address the cause of the outage and re-institute service. If this is the case, then multiple rolling wheels are required to bring the ATM back online. The Powalert allows the operations centre to determine causation in realtime and thus the operations centre can dispatch the most appropriate resource. Additionally, if a network or equipment failure is suspected the operations centre can implement a standard operating procedure to reset the equipment with a remote power down. Should the service automatically recover using this process, then a rolling wheels dispatch is negated. The measures described here reduce the operational costs of ATM management.
Visit the website of DS or email info@ds.co.za to discover awesome #IoT solutions and services. We are proud South African innovators!

Comments

Popular posts from this blog

Using OPENDNS on a Mikrotik

At the office we use a Mikrotik which is connected via fibre to Cool Ideas.  We use OpenDNS as a Information Security tool.  It prevents ransomware and bots from becoming major incidents within the office.

The router is scheduled to do a daily update via script of the OpenDNS settings.  Below is the example:

:local opendnsuser "user@domain.co.za";
:local opendnspass "itsprivate";
:local opendnshost "office";

:log info "OpenDNS Update";
:local url "https://updates.opendns.com/nic/update";
/tool fetch url=($url . "\3Fhostname=$opendnshost") user=("$opendnsuser") password=("$opendnspass") mode=https dst-path=opendnsupdate.txt
:local opendnsresult [/file get opendnsupdate.txt contents];
:log info "OpenDNS: Host $opendnshost - $opendnsresult";

The importance of the major incident process

ITIL mentions the Major Incident process as a special case of the incident management process as well its close relationship to problem management.  However, the Major Incident process requires greater clarity and specification as in many large enterprises the process is crucial for overcoming a crisis. A Major Incident typically defined as an incident with severe negative business consequences and an important duty of any designated Information Technology (IT) resources is to deal with Major Incidents in a structured manner.  We will address this important topic in a series of articles that specifically addresses the process and crisis management in general.

Read the full article here.

Checklist of the information a manager of a NOC needs to have close at hand

This is a checklist devised by DS of the information a manager of a Network Operations Centre (NOC) needs to have close at hand:
Command and controlDate and time of current shift including start, finish and handover.NOC manager on dutyShift leadersService Delivery Manager on duty/standbyMajor Incident Manager on duty/standby Tiger Team status (refer here for process) echowhiskydeltaromeobravoalpha Red-Amber-Green (RAG) of the trenchesSecurityData centreAppsSupportInfrastructure NotificationsOngoing Service Level Agreement (SLA) or contract violationsAll Major Incidents All failures and outages Last 10 maintenance tasks completedNext 10 maintenance tasks scheduledPlanned continuity tests scheduled (inverter/generator tests, network path protection tests, business continuity or application high availability tests)Resources available to the NOCResources unavailable to the NOCChanges completed during the past week (includes the status on whether they were successful or failed)Changes sch…