I/O, I/O, it’s off to work I go

To the man who only has a hammer, everything he encounters begins to look like a nail.”
Abraham Maslow

In the case of OSS, our hammer is the computer monitor, keyboard and mouse, which are the weapons of choice for interacting with the OSS tools.

But are they the best I/O (Input / Output) devices for performing each of the different CSP operation tasks? A data entry operator will have vastly different needs than a NOC operator or a contracts (ie SLA) manager or a field service technician or an OSS application administrator, etc. Have OSS vendors considered custom I/O tools for the needs of each type of operator?

For example, any old OSS tool can register an alarm, show it in an alarm list, allow operators to acknowledge an alarm and create a ticket. In this case, they are designed to handle the most common tasks.

But where an OSS can really prove itself to be remarkable is how it assists an operator handle the outlier, such as when an alarm storm hammers the network.

“Noise” removal, information processing, understanding of alarm / network relationships, and root cause identification are the key functionality when handling these (hopefully) rare events. Are keyboard and mouse the best devices to assist with the speed of processing available information, recall of historical events and ultimately fault-prognosis? Or would touch and gesture computing allow faster prognosis? Would collaborative gesture computing speed prognosis even further? What would the interface look like?

Has anyone heard of a behavioural analyst or an industrial designer being used to create the GUI and I/O interfaces for an OSS product? If not, why not?

Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.