Severity Levels– how they work with business rules

The Genkiosk developer team has spent the past few years working on not just getting lots of useful kiosk data for analysis, but also developing ways in which the system can best work for organisations using automated processes. Why not make things as slick, effective and efficient as possible – adding maximum value?

This methodology is based on the premise that it’s “not only what data you get, but what you do with it that counts”.

Whilst you might say that this is a no-brainer, you are to a degree led by the system architects who develop management systems.

GWD Media uses Agile and Scrum processes to solicit feedback and turn real world customer based requirements into tangible roadmaps – adding real value to the whole process. New capabilities that are really powerful include:

Business Rules

Severity Levels

and Notifications

Business Rules are a way in which you can specify automated events to take place depending on the status of information. For example, kiosks might be considered to require attention if they haven’t reported any usage for a specified period of time (e.g. 2hrs. Or 3. It is up to you to decide).

Severity Levels allow for the setting of degrees of significance. For example, if a bill acceptor can hold 250 notes before it’s full and unusable:

on a journey from empty to 250 notes ….

at 125 notes it is 50% full which may be the threshold set before the first notification that it requires emptying ….

and if it gets as far as 80% full, a high priority alert should be sent out: top severity, before you go out of service.

Using severity levels to specify what happens at these various levels creates a simple and maintainable escalation process which can be: