Tuesday, March 2, 2021

Technology and Context

cross-posted on medium and LinkedIn 

 This blog post will be the first installment of a multi-part series on technology, data, self-optimization, and context. Context is the often overlooked constant required for any level of optimization or understanding of a data-based problem.
I’ve worked in product capacities in the technology space for over ten years as a technologist and a go-to-market expert. I was taking products to the market and the market back to the product to create customer-centric solutions.
In that time I had the privilege of creating products and use cases to enhance the workflows used by tens of thousands of people every day and also creating products to create self-optimizing ecosystems. We will dive into the concept of context today to understand the importance of this often-overlooked variable in a contained system. Then look at it in other environments later. We will also talk about location and why location in many use cases is the ultimate in context.
Because this topic does come somewhat close to my day-to-day job, I should go ahead and say that this is my personal blog; the opinions are my own and may not represent my employer’s views. I hope to provoke you to look at more problems in terms of context and not just focus entirely on the data.’ Data is driven and explained by context.



 We live in a connected world. That’s nothing new; digitization powers almost every single action we take in the world today. Infrastructure has gone from many data centers across tens of thousands of offices to fewer, larger ones, run by companies with significant expertise and most likely their own scale requirements. Every single operation creates a well-orchestrated ballet of storage, compute, and infrastructure. These “cloud data centers” are little self-optimizing ecosystems. Some optimize for efficiency, and some for resilience and low management overhead.

Image for post
Photo by Taylor Vick on Unsplash
Image for post
Photo by Yuyeung Lau on Unsplash
PUE Formula

Goal Setting

Let us look at goal setting and how you prioritize what’s going on in optimizing technology. Are you optimizing to remove the human variables? Do you want an essentially lights-out facility? Well, then you want to standardize as much as you can. Reduce the number of vendors, understand the components’ life cycles, and understand how many of them may fail in a given them. Then put into place a fail-over plan that covers the intervals between planned maintenance. Congratulations, you just built a lights-out facility in the arctic circle, a high-tech facility whose only on-site employees are security.

Image for post

“If you think that 10% of shipments are late, it stands to reason that the majority of the other 90% are actually early, and that’s an entirely distinct problem.”

A shipment arriving early, many incur additional storage costs, there may be no one there to accept it/no available slots. It may incur inventory carry costs that are unanticipated. Hence, it’s crucial to hit that sweet spot exactly. People that know logistics know that it’s still very much an inexact science today. Hitting the sweet spot is a dream because, at least in logistics, we don’t always even have access to all the variables and data required to optimize. Honestly, probably any environment at this time. There is always more to learn.

Image for post
Photo by NASA on Unsplash

No comments:

Technology and Context

cross-posted on medium and LinkedIn    This blog post will be the first installment of a multi-part series on technology, data, self-optimiz...