Operational Efficiency Concepts

"Service reliability math that every engineer should know" I think it's useful for engineers to understand what uptime and reliability mean in practice. These numbers paint a good picture of what's involved :) Now while service reliability is often reduced to a simple percentage, the reality is far more nuanced than those decimal points suggest. First, not all downtime is created equal. A single 8-hour outage has dramatically different business implications than 480 one-minute outages, even though both sum to the same annual downtime. This distinction is particularly relevant when considering service level agreements (SLAs) and how they’re measured. The impact of downtime also varies significantly based on when it occurs. Five minutes of downtime during peak business hours might cost more than an hour of downtime during off-hours. This temporal aspect of reliability is often overlooked in simple percentage calculations. Each additional nine of reliability typically requires an order of magnitude more engineering effort and operational complexity. Moving from 99.9% to 99.99% isn’t just a matter of being "10 times more reliable" – it often requires fundamental architectural changes: At 99.9% (8h 45m downtime/year), you might get away with single-region deployment and basic failover At 99.99% (52m 35s), you’re typically looking at multi-region deployment, sophisticated health checking, and automated failover At 99.999% (5m 15s), you need redundancy at every layer, real-time monitoring, and likely some form of active-active deployment At 99.9999% (31s), you’re dealing with advanced techniques like chaos engineering, automated canary deployments, and sophisticated traffic management While understanding the basic math of service reliability is crucial, the real engineering challenge lies in understanding the context, trade-offs, and business implications of reliability decisions. The next time you see a reliability requirement, don’t just think about the percentage – think about the entire socio-technical system required to achieve and maintain that level of service. The numbers are simple. The engineering reality behind them is anything but. #softwareengineering #programming

Our research center in Princeton has become a magnet for healthcare AI expertise. Every time I catch up with Dorin Comaniciu and the team there, conversations quickly move from what’s possible to what really matters in healthcare delivery. Take for instance, our work on what we call the Operational Twin, an advisory service. It starts with creating a virtual representation of a clinical department, reflecting how patients, staff, and equipment interact in everyday operations so that different scenarios can be explored more safely and at scale. By simulating billions of scenarios representing dynamic conditions, AI agents learn how operational decisions shape outcomes. They can begin to anticipate bottlenecks and understand the long-term impact of short-term choices. The goal is more efficient planning of patient schedules, staffing, and equipment use, aligning daily decisions with broader clinical and organizational priorities. This becomes even more relevant as clinical innovations accelerate workflows. Faster scanning technologies such as Deep Resolve can shorten patient timeslots and an Operational Twin can help organizations adapt by optimizing schedules and resources to fully realize gains in speed and throughput. At its core, this work is about creating clarity in complex systems so that action becomes more precise and more purposeful. We see a similar principle in clinical innovation. With photon counting CT, we can visualize the heart in extraordinary detail, including structures inside the left ventricle that were previously difficult to see clearly. That deeper insight is captured by a Foundation Model that could help physicians guide ablation therapies with greater precision and confidence, especially when combined with live ultrasound to support real-time decision making in the procedure room. In both cases, whether in clinical imaging or in operations, the ambition is the same: better insight leading to better decisions at the moments that matter most for patients. 𝘋𝘪𝘴𝘤𝘭𝘢𝘪𝘮𝘦𝘳: 𝘛𝘩𝘦 𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘴/𝘧𝘦𝘢𝘵𝘶𝘳𝘦𝘴 𝘢𝘯𝘥/𝘰𝘳 𝘴𝘦𝘳𝘷𝘪𝘤𝘦 𝘰𝘧𝘧𝘦𝘳𝘪𝘯𝘨𝘴 𝘮𝘦𝘯𝘵𝘪𝘰𝘯𝘦𝘥 𝘩𝘦𝘳𝘦 𝘢𝘳𝘦 𝘯𝘰𝘵 𝘺𝘦𝘵 𝘢𝘷𝘢𝘪𝘭𝘢𝘣𝘭𝘦 𝘪𝘯 𝘢𝘭𝘭 𝘤𝘰𝘶𝘯𝘵𝘳𝘪𝘦𝘴. 𝘐𝘧 𝘵𝘩𝘦𝘴𝘦 𝘴𝘦𝘳𝘷𝘪𝘤𝘦𝘴 𝘢𝘳𝘦 𝘯𝘰𝘵 𝘮𝘢𝘳𝘬𝘦𝘵𝘦𝘥 𝘪𝘯 𝘤𝘦𝘳𝘵𝘢𝘪𝘯 𝘤𝘰𝘶𝘯𝘵𝘳𝘪𝘦𝘴 𝘧𝘰𝘳 𝘭𝘦𝘨𝘢𝘭 𝘰𝘳 𝘰𝘵𝘩𝘦𝘳 𝘳𝘦𝘢𝘴𝘰𝘯𝘴, 𝘵𝘩𝘦 𝘴𝘦𝘳𝘷𝘪𝘤𝘦 𝘰𝘧𝘧𝘦𝘳𝘪𝘯𝘨𝘴 𝘤𝘢𝘯𝘯𝘰𝘵 𝘣𝘦 𝘨𝘶𝘢𝘳𝘢𝘯𝘵𝘦𝘦𝘥. 𝘍𝘰𝘳 𝘮𝘰𝘳𝘦 𝘪𝘯𝘧𝘰𝘳𝘮𝘢𝘵𝘪𝘰𝘯, 𝘱𝘭𝘦𝘢𝘴𝘦 𝘤𝘰𝘯𝘵𝘢𝘤𝘵 𝘺𝘰𝘶𝘳 𝘭𝘰𝘤𝘢𝘭 𝘚𝘪𝘦𝘮𝘦𝘯𝘴 𝘏𝘦𝘢𝘭𝘵𝘩𝘪𝘯𝘦𝘦𝘳𝘴 𝘳𝘦𝘱𝘳𝘦𝘴𝘦𝘯𝘵𝘢𝘵𝘪𝘷𝘦.

What's the best methodology for operational excellence—Lean, Six Sigma, or Theory of Constraints? Lean eliminates waste. Six Sigma reduces variation. Theory of Constraints addresses bottlenecks. Three distinct approaches to operational excellence. The usual question: which one wins? The question itself is flawed. These aren't competing philosophies—they're complementary disciplines that address different sources of loss in operations. No single methodology has all the answers. Lean keeps flow moving. TOC shows where it stops. Six Sigma makes it stable and predictable. Grounded in respect for people and rigorous data analysis, these disciplines create a system that continuously improves—higher throughput, fewer defects, less waste, driven by both people and process. The real skill isn't picking one. It's knowing when to use each. When integrated effectively, the results speak for themselves: higher throughput, fewer defects, sustainable margins. I'm curious: How do you blend these methodologies in your operations? Do you lead with one and layer in the others, or do you approach them as an integrated system from the start? And if you're struggling to build a cohesive continuous improvement culture—or finding that your methodologies work in silos rather than in concert—let's talk. I offer a complimentary 30-minute consultation to help organizations create an integrated approach that fits their unique operational challenges. Because the right answer isn't Lean or TOC or Six Sigma. It's knowing how to orchestrate all three.

OT Detection Use Cases for your OT SOC When it comes to building an OT SOC, there’s a big misconception: many assume success is about collecting every log or integrating every system In reality, the key is focusing on operationally meaningful visibility — the detections that actually help you understand what’s happening inside your control network >> In industrial environments, context defines everything > The same Modbus write command could mean two very different things: > a maintenance engineer performing a scheduled update — or an attacker changing control logic. > Without context, both look identical in your SIEM. >> An OT SOC must speak the language of process, assets, and operations, not just alerts. It should tell you when something changes, who initiated it, and whether it threatens safety, reliability, or integrity >> Below are 10 detection use cases I always recommend as a starting point. They’re mapped to MITRE ATT&CK for ICS and NCA OTCC, but more importantly, they’re grounded in what actually happens inside real plants and industrial networks 1. Unauthorized PLC Programming Detect logic or configuration changes outside scheduled maintenance windows 2. ICS Protocol in IT Zone Flag Modbus, DNP3, or BACnet traffic on IT networks — strong evidence of segmentation drift or misconfiguration 3. PLC Stop or Mode Change Command Detect STOP or PROGRAM mode changes — an event that can halt production and indicate malicious control 4. Remote Access to HMI from Unapproved Source Identify RDP, VNC, or TeamViewer sessions from IT zones targeting OT HMIs — a common lateral movement path 5. New Device in Control VLAN Catch unauthorized or rogue devices joining deterministic control networks where new assets should rarely appear 6. PLC Firmware Downgrade or Version Change Detect unauthorized firmware rollbacks — a subtle but serious method of tampering or hiding malicious code 7. OPC UA Anonymous Session Identify untrusted or anonymous OPC UA sessions that bypass normal authentication or encryption 8. Engineering Software on Non-Engineering Host Detect the execution of TIA Portal, Control Builder, or similar tools on unauthorized systems — often a sign of credential misuse or insider activity 9. PLC Configuration Upload Monitor FTP/TFTP uploads to PLCs — an activity that could replace control logic or inject malicious configuration 10. Abnormal HMI Behavior Spot rapid screen changes, tag edits, or command spamming from operators — signs of misuse, automation, or compromise They aren’t just security detections — they’re process integrity safeguards. Each one gives the SOC visibility into the exact actions adversaries use during real OT incidents — often before physical impact occurs When combined with contextual data (authorized engineers, maintenance schedules, device baselines) and network telemetry , these detections evolve from simple alerts into actionable operational intelligence #OTSOC #OTsecurity #ICSsecurity

Something interesting is happening that some leaders are not talking about publicly. While companies make headlines about downsizing in their home countries many of these same organizations are quietly establishing significant operations in Manila. JPMorgan takes over 2nd Uptown BGC tower which doubled Manila workforce to 20,000. Amazon also inaugurated its first operations services office in Cebu City which created hundreds of employment opportunities. According to Business World Online, office sector net absorption of 281,000 sq.m. in H1 2024 is driven by return-to-office mandates and office expansion. The numbers actually do not lie. Indeed, major tech companies, financial services firms, and consulting organizations are building substantial teams in the Philippines while maintaining different narratives in their public communications. This goes beyond cost-cutting anymore. It speaks about competitive advantage. The real reasons behind this quiet expansion reveal strategic thinking. The Philippines offers something unique. There is a mature business ecosystem with Western-compatible work culture, timezone flexibility for global operations, and a talent pool that scales with quality. Companies are not just finding cheaper resources. They are finding better operational models. The Philippines has become the preferred destination for serious business growth because it solves multiple problems simultaneously. English proficiency eliminates communication friction. Cultural compatibility reduces management overhead. Government support creates favorable business conditions. And the talent infrastructure can absorb rapid scaling without quality degradation. But what people often most miss is that companies are keeping this expansion quiet because it represents a competitive approach. While competitors struggle with domestic hiring challenges and inflated salary expectations, these organizations are building efficient and high-performing teams that operate seamlessly across global markets. Companies that figured this out early are scaling faster, operating more efficiently, and building sustainable competitive advantages while others debate the future of work. The Philippines is not just another offshore destination. It has become the operational backbone for companies that understand global talent strategy.

“SAP has slowed our operations.” That’s what a frustrated COO told me recently. And I get it — on the surface, it feels true. Before SAP, the team had more “freedom.” They could make decisions quickly, enter data loosely (or not at all), skip steps if needed, and keep things moving. But here’s the question I asked him: “Were you truly fast… or just unstructured?” Let’s break it down. 📝 Before SAP: Sales orders came in through email, phone, or sticky notes. Approvals were verbal. Everyone had their own version of the truth. Finding information took longer than acting on it. There was flexibility… but no accountability. And it worked — until the business grew. Then it started breaking. ⚙️ After SAP: Users are asked to enter structured, consistent data. Processes follow defined flows with approvals, checks, and validations. Every decision is traceable. Reports update in real-time. There’s a system — not guesswork. So yes, some steps take a bit longer. But that extra 30 seconds at the start saves hours of confusion, firefighting, and rework later. 🧠 The COO paused. He realized SAP didn’t slow them down. It forced discipline. It made inefficiencies visible. It replaced tribal knowledge with traceability. And that’s the foundation for scale. You can’t scale chaos. You can only scale the structure. Have you heard similar complaints from any of your customers or business users? Please share your experience! #SAP #ERP #DigitalTransformation #COO #OperationalExcellence #ProcessDiscipline #Leadership

A bank CEO just told me his $2B asset bank outperforms a $20B competitor in efficiency ratio. I asked him about M&A and the race to scale that seems to be a central theme for 2025. He laughed. "That's old math." While banks are rushing to merge their way to scale, the rules of banking have fundamentally shifted.  Sure, M&A can spread fixed costs across a bigger balance sheet. But merging two inefficient operations just creates a bigger inefficient operation.  His secret? They stopped trying to be everything to everyone. Instead, they invested heavily in modernizing their tech stack and focused on specific customer segments they could serve profitably. Their loan officers spend 80% of their time with customers instead of paperwork and these conversations are data driven. Everything is captured in their CRM that they’ve finally gotten cultural buy in to leverage so follow ups are automated and there are more data to drive more insights. This isn't about having fancy tools. It's about fundamentally rethinking how banking works. The old playbook: gather deposits, make loans, buy a competitor, repeat. Growth meant more branches, more people, more overhead. The new playbook? Use technology to reduce friction, increase productivity, and create scalable processes that don't require an army of people. M&A isn't dead, but technology is the new scale game. The winners won't be determined by asset size but by operational efficiency. Ironically, focusing on The New Rules makes a bank more attractive in M&A either as a target or an acquirer. Ted R., Managing Director at Stephens, drove this home in a conservation about M&A before the holidays. His point: banks need to build a unique asset such as focus or a scalable growth engine to command a premium.   What old rules and assumptions about scale are holding your bank back?

💡 Smart tilt-down street lights 🛠️ = Bringing SMED to the streets Why are we still sending technicians 12 meters into the air just to change a light bulb? High-mast maintenance is a safety and logistics nightmare. It requires crane trucks, lane closures, and extreme working-at-height risks Tilt-down mechanism with counterbalanced swing-down design allows to lower the entire fixture to chest height quick and easy Look at the lean and safety metrics this unlocks: ➡️ No Elevation Risk: Eliminates falls from height ➡️ Zero Heavy Equipment: No cherry pickers or traffic blocks required.Standard service vehicle is enough. ➡️ SMED Execution: The bulb swap happens at ground level in a few minutes. The asset downtime drops to near zero. Why solving physical friction with digital complexity. True lean innovation is just smart mechanical engineering. Design the infrastructure to adapt to the worker, not the other way around. 🎥 @stem_feed