Skip to main content

Do no harm


Having endured another restless night, Oscar reaches for the alarm.   His mind wanders as he recalls the nightmare which seems to be top of mind, even as the sun peaks through the windows.   Their service company,  WeHelpU was in court defending their position regarding the data breach at the "TrustMe nuclear plant".   They,  like many other service providers, WeHelpU jumped on the IoT bandwagon a couple of years ago.  It didn't take long for Oscar to become overwhelmed, current situation aside, what about the thousands of our other customers?



A couple of years ago, in 2018, we established  rules of engagement to prevent us from being in this situation, where did we fail?



  • Air Gap | at first we were very disciplined to only install non-intrusive monitoring.  As our skills and knowledge broadened we started making exceptions.   Hey, we can save some capital if we just connect to the existing control system?
  • Cellular | while very tempting we stood our ground and never connected to the clients network,  sensors to the  gateway and gateway to the cloud.
  • Anonymized | this was the trickiest of all.  Fact is we have lots of sensors and actuators which all tie to assets,  which belong to sites,  sites which belong to clients.   Whether structured data sets or metadata tags, they are all vulnerable.   The short term recall of data is powerful for scheduled and unscheduled activity and needs to relate to the customer.   Long term data is helpful for models and AI, this data should be anonymous.



Our discipline, or lack thereof, will impact our organizations and our clients.   We simply don't know what we don't know, be curious but cautious.



-----

Next post:  who's data is it?

Thoughts?  feel free to leave replies or direct message

See all of the "last mile worker" posts here:  http://lastmileworker.com

-----


Comments

Popular posts from this blog

entusiastic about preventative maintenance

Why do I really care if my field technicians are enthusiastic or not? When you look at a person's work output, as directly related to workforce sciences, you come up with three primary ingredients required to achieve your desired results.   These ingredients are; attitudes, attributes, and capabilities and when mixed properly with enabling tools can yield unbelievable outputs. So what does any of this have to do with routine maintenance? If your maintenance routines actually become way too routine then pretty soon performance will be replaced with complacency. In order to keep any piece of equipment running as trouble-free as possible the maintenance performed, and the thoroughness of the inspection and tasks at hand, have a direct impact on the asset's life expectancy.   There are some strategies that help service organizations keep the enthusiasm at all-time highs. Switch techs from time to time :   One of the best ways to ensure maintenance is being performed...

It's the little details

As overwhelmed Oscar sits in his office, surrounded by piles of overdue work order tickets to review and material orders to procure, his heart yearns to give the customer anything they want, yet the tools at his disposal make it difficult. On this relatively ordinary day Oscar receives a phone call from a marquee customer. This new customer has multiple locations and has asked for just three pieces of information every time a person visits their sites to perform service or maintenance. Oscar gathers his thoughts as he prepares to discuss this seemingly small challenge with reluctant Ruth, the dispatcher who has been with the organization for decades, Ruth can be a bit of a curmudgeon. Oscar does appreciate the inconvenience of gathering unexpected information both for the field worker as well as the back office.   A seemingly great example of ending up between a rock and a hard place. In a world of perfect harmony where all customers, work orders, and requests are exactly...

why transform?

Why do I want to change, who said anything was wrong with my stack of papers and sea of Excel files?   We solve problems, that is a key characteristic of any successful service organization, if it isn't broke why fix it?   Often, when discussing a transformation from paper or cobbled together systems to a cohesive digital approach, folks struggle with the gap between what they currently do and how digital tools can help.   You really need to look at where the pain points are in your organization and how these compare to your business objectives.   Consider writing down these points on the whiteboard in no particular order, spend a few days shuffling and consolidating into a prioritized list.   Once you have the "why" and the "what" identified, the old remaining step is "how".   Some of the most popular observations over the years have been; Slipping through the cracks :   you know, not the major muscle movements, instead those little i...