Connect with us

Non classé

Modern Cost Engineering: The Promise and Peril of Process Change

Published

on

This is the third blog in a series of four on the adoption and implications of cost engineering, outlining the impact on people, processes, and technology. In the first, I outlined the compounding volatility in modern industrial markets due, in part, to increased digital hyperconnection, There clearly is a need for a kinetic, self-healing supply chain that shifts from solely backward-looking financial estimating to digital intelligence that enables real-time forward-looking methods, aka cost engineering, based on, for example, physics-based models. The second blog drilled into the implications for the human element, detailing the needed workforce transformation across key roles.

All good and fine. However, embedding the right people with the right knowledge, skills, and abilities (KSAs) into environments with outdated, rigid workflows will just lead to failure. Realizing the potential benefits of cost engineering requires industrial organizations to examine their processes. In this blog, I’ll discuss legacy silos and processes related to procurement methodologies, production practices, downstream logistics, and their connection to executing frictionless, informed supply chain orchestration.

Silo Deconstruction: Inevitable Doesn’t Mean Easy

Generally speaking, industrial supply chains have tended toward the linear and sequential. From a product perspective, design engineers created a product, handed it off to be priced, then procured, produced, and so on. This isolated structure inevitably created silos, with decision making confined to walled-off start and stop points. When processes worked well, it was perceived to be an outcome of strong relationships, experience honed over time, and effective judgment.

When things went poorly, it often resulted in catastrophic misalignment across business units and operating ecosystems. The misalignment often cascaded beyond the silo in which it was created, as it often was not identifiable in the moment. Simple examples range from creating little-to-no margin in design to forcing continuous rework due to unforeseen downstream constraints. In today’s hyperconnected business world, the consequences of misalignment aren’t sustainable.

De-siloing processes, such as cost engineering, and the attendant data is seen as an answer to these challenges. Yet, this tendency toward silos is exacerbated by many compounding realities of today’s work and operational environment. Spreadsheets and paper are still all too common. There remains an affordability and sophistication gap between larger tier-one and medium and small industrial organizations. The aging workforce is having a greater deleterious impact than the solutions designed to offset the retirement of knowledge, skills, and abilities (KSAs). I could go on all day.

Cost engineering processes cannot exist in a vacuum. The rewiring of how business gets done isn’t served by traditional change management. The magnitude and complexity are vast, especially as the work moves beyond the walls and immediate control of the organization. It requires an intelligent vision, value-based performance indicators, commitment to change in work across a diverse set of roles, new incentivization structures, and so on.

Processes must evolve to integrate specific expertise continuously throughout the entire product lifecycle. That change means uniting design, manufacturing, and procurement into a single, cohesive decision loop that accounts for business and operating strategies, material constraints, and regulations, to name just a few process inputs. For businesses reliant on supply chains as critical components of the value they deliver, de-siloing is an inevitability that must be addressed. However, it doesn’t make it easy.

Getting to Dynamic Collaboration

To break down internal barriers and rapidly solve complex manufacturing bottlenecks, leading organizations are abandoning the sequential handoff in favor of highly agile, cross-functional intervention teams. A prime example of this process innovation is the deployment of Supplier Operations Support (SOS) teams, pioneered by high-performing aerospace organizations like Rolls-Royce. When a critical supplier struggled to produce a component, the company didn’t default to an age-old punitive reaction, like simply issuing a contractual penalty every time it occurred. Instead, it deployed an SOS team, with decision-making autonomy, directly to the supplier’s factory floor.

With this deployment, the hard work began, based on what processes needed to improve continuously to achieve the necessary outcome. Despite that, the collaboration increased the value of the relationship for both organizations.

The concept and use of SOS groups, often referred to as tiger teams, certainly isn’t new or novel. However, the need for industrial data fabrics and the push toward autonomous AI have the potential to considerably modify the goals, responsibilities, and authority of these teams. Historically, these teams were constructed and deployed when reactive firefighting was necessary. They consisted of top-tier subject matter experts, so companies were very judicious in taking them away from their normal roles. Now, leaders in innovation view these teams with a very proactive mindset.

It’s the right move, but it’s not without tension. The transparency required both within and outside the organization (especially outside) is inherently uncomfortable, as it suggests sharing proprietary operational data. Uncovering hidden cost premiums and identifying specific inefficiencies won’t initially feel like a win for the supplier. The comfort of static purchasing and forecasting has to give way to continuous, real-time visibility of the entire production process.

This can cut two ways. On one hand, it can be seen as an intrusion on the ability of supplying businesses to generate revenue and maintain margin by the supplying businesses. On the other hand, it can deepen the value, reliability, and differentiation of the relationship. Those that understand that costing needs dynamic updating and employ experts to realign processes with that goal in mind will be able to manage price spikes, geopolitical and economic tensions, weather events, and all of the disruption inherent in competition in hyperconnected markets.

Leadership Via New Process Pathways

It is clear that AI has the ability to reason and execute at scale to help ensure autonomous optimization of many of the mundane, data-heavy tasks that used to consume organizational bandwidth. The question then becomes obvious: what to do with that bandwidth? Some downsizing is a reality, there’s no getting around that, particularly as AI transitions more directly into physical intelligence, with massive implications for supply chains. Processes that are transactional, repetitive, or dangerous will be the first targets. In these situations of human-to-digital migration, leadership needs to be exceedingly careful not to inadvertently get rid of critical expertise, as is an all-too-common mistake.

If done correctly, this expertise is retained and can then be shifted, proactively delivering competitively differentiating value by driving performance change aligned with modern market demand. Those experts become orchestrators, and there is a stark difference in progress between leaders and laggards. The latter continue to be unable to demonstrate the value of modernization. In contrast, leaders are gaining ground that they likely will never cede by proactively designing the business for autonomous operations.

Once this structure is in place and teams proactively drive business value using new processes underpinned by autonomous tools, the use cases for improvement are many. An example is building supply chain digital twins to integrate self-healing design and optimize network performance. Predictive maintenance, optimized energy/delivery, and sourcing/production risk management are also employed by leaders.

This move to collaborative teams proactively rewiring the process flows of the organization also allows critical, very complex, use cases to be tackled. Use cases related to sustainability, still a critical supply chain concern, can be addressed in new, highly effective ways. According to ARC’s annual survey, in 2026 energy transition and decarbonization are second only to cost reduction in industrial investment driver priorities. Turning this prioritization into actual business value has been challenging at best for industrial organizations, leading critics to continually and accurately raise the concern of greenwashing.

The combination of expert orchestration and autonomous tools, backed by access to and use of contextualized data, could ensure the execution and proof of regulatory compliance for something specific like a Corporate Sustainability Reporting Directive (CSRD) mandate or product carbon footprint lifecycle tracking requirement. When implementing cost engineering, the relationship between cost, risk, and benefit factors becomes much more transparent to all stakeholders. In turn, those elements can be factored more readily into decision lifecycle processes. The business, and its customers, can better understand what truly moves the needle. AI tools can be used to ensure that the movement occurs. In this way, sustainability becomes a crucial and appropriately weighted variable in every relevant decision. In addition to sustainability, these examples collectively demonstrate that the definition of high-value work is shifting away from traditional approaches such as manual intervention, reactively fighting fires, or leveraging financial threats.

Shift Left

The innovation modern cost engineering delivers entirely upends procurement and sourcing processes, of course, aiming to reduce and/or automate the transactional and minimize adversarial or negative ecosystem behavior. In industries where this is established, such as aerospace and defense, the benefits are in plain view. When effectively implemented, workflows inevitably move toward deep, transparent collaboration. As an example, conversations can occur with a mathematically defensible, highly granular baseline model of component cost at the center.

This injects fact-based transparency into the negotiation process in a way that can be beneficial to both parties. If the cost is out of line with expectations, the appropriate SMEs can enter conversations with the supplier to identify specific constraints or inefficiencies and move more quickly toward how they can be solved. The levers that can be pulled are more obvious to both parties. Approaches to volume uncertainty and other disruptions can be implemented so that, prior to or as they occur, they can be dynamically modeled, understood, and contractually accounted for without production whiplash.

In fact, cost engineering shifts the analytical processes as far upstream as they can go. And that is well beyond procurement and sourcing. At its most effective, cost engineering gets beyond “autopsy” thinking limits and even “what if” intelligence (though it does retain those principles) to “exactly what now” autonomous decision making. Nowhere is this more evident than product design.

After all, the redesign loop is reactive, sequential, and ripe for inaccuracy to find its way in. Cost engineering sits at the front of design so that cost is a property of R&D. When these processes are also then informed by autonomous agents monitoring the real-time environment, across its expanse no matter how large the footprint is, implications are made transparent and decisions obvious. Constraints and impractical product tolerances are actively baked out of design. By starting from an optimized design state, all downstream decisions begin from that raised product lifecycle floor.

Integrity is a Process, Too

Of course, the discussion isn’t complete without raising the specter of trust issues inherent in adopting cost engineering that is heavily reliant on digital methods and AI. Integrity isn’t born; it is behavior-based and nurtured over time. Let me try to phrase it another way. If one is a supply chain, engineering, product, or other SME professional, many forms of today’s AI must seem like forms of tribal knowledge. After all, AI is positioned as consisting of KSAs that human experts can’t really match. It informs its KSAs via whatever information sources it can access, whether they are good or bad. Over time, that is, as it gains experience, its expertise will surpass those SMEs. While it can be designed with the mission to share, its most valuable and efficient state is thought to be autonomous action. It’s a keeper of knowledge, and based on the ability applied to a task, its assessments are often unexplainable. It can also be inconsistent or dreadfully wrong while confidently certain in its misinformation. It also has motive, or at least the keepers of the revenue who deploy it do.

Listen, I’m not trying to say they are the same things, but the point makes itself, I believe. Integrity of output requires trust, and AI is no different. That doesn’t just mean behavior guardrails and cybersecurity. Going back to where I started in this blog, inevitable is not the same as easy. As traditional estimating processes are increasingly automated via various digital and AI techniques, organizations must build new processes to ensure human operators can trust the machine’s output, and that’s not a straightforward task, no matter what the selling market says. For cost engineering, this means ensuring AI is only scaled into production processes where it demonstrably improves and explains outcomes, rather than simply adding layers of technological complexity and obfuscation.

In the fourth and final blog, I’ll explore the technology aspect of cost engineering. The discipline has a massive impact on systems, particularly as it flows downstream into the supply chain needed to take cost engineering from concept to reality.

The post Modern Cost Engineering: The Promise and Peril of Process Change appeared first on Logistics Viewpoints.

Continue Reading

Non classé

Before the Vendor Shortlist: How to Structure the Decision Intelligence Market

Published

on

By

A Decision Intelligence shortlist should not begin with vendor demos. Providers are arriving from planning, optimization, visibility, risk, networks, enterprise suites, orchestration, and AI-native architectures, and without a category framework a shortlist can become a collection of impressive but fundamentally different products.

Inventory the decisions that are slow, fragmented, poorly contextualized, or overly dependent on manual coordination. For each one, document frequency, consequence, time horizon, required data, systems touched, decision rights, and the action that follows. This creates a demand-side map before the supply-side market is introduced. The physical logistics intelligence-layer discussion also explains why superficially similar providers can occupy very different architectural positions depending on where they sense, interpret, decide, and act.

The eligibility test is decision impact. Generic BI, horizontal AI, reporting, and transactional systems do not qualify by default; the technology must materially improve a real supply-chain decision That gate prevents the market from expanding into every product with a dashboard, copilot, optimization engine, or AI claim.

A useful structure distinguishes planning and optimization-led; visibility, event, and risk-led; decision-orchestration and AI-native; and suite, network, or enterprise-led approaches. These approaches can all create value, but they often solve different decision problems and operate at different levels of depth and reach.

Decision depth asks whether the platform interprets context, models tradeoffs, and changes the quality of the decision. Operating reach asks how broadly that capability spans functions, workflows, systems, partners, and time horizons. Buyers can add governance, execution connectivity, evidence quality, and implementation fit as additional criteria.

Once the structure is clear, evaluate decision fit, decision depth, operating reach, context quality, scenario and tradeoff capability, workflow and execution connectivity, governance, explainability, evidence quality, and referenceable outcomes. A large suite may be attractive when enterprise reach and installed-base integration dominate; a specialist may be stronger where one high-value decision requires deeper intelligence. The framework makes those tradeoffs explicit.

A disciplined market structure is therefore not academic taxonomy. It reduces evaluation noise, prevents false comparisons, and makes the shortlist defensible before vendor marketing begins to shape the requirements.

Market structure should follow the decisions buyers need to improve

A useful shortlist starts by inventorying the decisions that are currently slow, fragmented, poorly contextualized, or dependent on manual coordination. Planning tradeoffs, disruption response, inventory allocation, logistics exceptions, supplier risk, and cross-functional balancing may all require different forms of intelligence and different time horizons.

Only after those decision domains are explicit should buyers compare provider types. That prevents a broad suite, a planning specialist, an event-intelligence platform, and an AI-native orchestration layer from being treated as interchangeable simply because each uses similar language. The category framework should make the operating model visible before the vendor list is allowed to dominate the evaluation.

Translate the market structure into a decision inventory

Before scheduling provider demonstrations, buyers should document a small set of decision classes that matter economically: for example, responding to a logistics disruption, reallocating constrained inventory, balancing service against cost, interpreting supplier risk, or coordinating a cross-functional response to changing demand. For each decision, record the data required, the time horizon, the people or systems with authority, the actions that follow, and the cost of delay or error. That inventory turns an abstract software category into a practical evaluation model and makes it much easier to see which provider archetypes belong on the shortlist. The 2026 Market Map is designed to help organizations understand the structure of the Decision Intelligence market, evaluate provider differences, and identify the capabilities most relevant to their operating environment. If your organization is evaluating Decision Intelligence platforms or clarifying where decision intelligence fits within the broader technology architecture, I would be glad to provide the Market Map brochure and discuss the evaluation questions and provider differences most relevant to your requirements.

Request the Decision Intelligence Market Map Brochure

For technology providers

Providers may request the brochure, discuss the research framework, or contact me to confirm how their capabilities are represented in the market assessment.

Discuss the research or confirm your profile

Continue Reading

Non classé

Transportation Leaders See AI Moving From Experiment to Operating Model at the Descartes Innovation Forum

Published

on

By

For the past few years, transportation executives have had to manage through one disruption after another: excess capacity, collapsing rates, driver shortages, rising fuel costs, fraud, cargo theft, shifting regulations, and increasingly demanding customers.

What struck me during the transportation management discussion I moderated at the Descartes Innovation Forum was how quickly another issue has moved to the center of the conversation: technology, and particularly AI, is becoming part of the operating model rather than a separate innovation initiative.

The freight market itself remains complicated. Demand remains relatively soft, yet capacity has tightened significantly as trucking companies and drivers have exited the system. That creates an unusual dynamic in which rates can increase without a corresponding demand surge. It also changes the shipper conversation from simply negotiating lower rates to ensuring access to dependable capacity and managing greater pricing uncertainty.

For shippers, the response increasingly starts upstream. Better forecasting, inventory optimization, dedicated transportation, and network planning can reduce exposure to the spot market and prevent costly expedites. The objective is to make an emergency become an inconvenience. That is a useful way to think about transportation management because some of the largest transportation costs are created long before anyone tenders a load.

Technology is also becoming an increasingly important tool for protecting margins. One example discussed involved a repetitive process performed approximately 750,000 times each month. When converted into labor, the activity consumes roughly 1,500 employee hours every day. Automating work at that scale is not a marginal productivity improvement. It changes the economics of the operation.

Agentic AI was therefore not discussed as something sitting five years over the horizon. The conversation included active use cases involving workflow automation, voice agents, email automation, decision support, and software development. The challenge increasingly becomes deciding what should be automated, where humans should remain in the loop, and how quickly organizations can absorb the rate of technological change.

One of the most striking examples involved a proprietary transportation management system containing more than 30 million lines of code and accumulated over approximately 20 years of development and acquisitions. A 12-person team was given six weeks to recreate the system using AI-native development methods and reportedly replicated the core system in that period.

Whether every organization can reproduce that result is almost beside the point. The more important message is that assumptions about software development timelines, technical debt, and what constitutes a realistic transformation project may need to be reconsidered.

At the same time, the discussion was hardly techno-utopian. Fraud, cargo theft, cybersecurity, insurance exposure, driver qualification, and litigation all figured prominently. Transportation may be becoming more automated, but the consequences of a bad decision remain very physical.

That tension may define the next stage of transportation technology.

AI can increasingly do the work. The harder questions will be deciding which work we want it to do, which decisions still require human judgment, and how quickly our organizations can adapt to what is suddenly possible.

The post Transportation Leaders See AI Moving From Experiment to Operating Model at the Descartes Innovation Forum appeared first on Logistics Viewpoints.

Continue Reading

Non classé

Descartes Takes Agentic AI Into the Logistics Workflow at the Descartes Innovation Forum

Published

on

By

The AI discussion in logistics is quickly moving beyond copilots, chatbots, and better search. At the Descartes Innovation Forum today, Descartes demonstrated something considerably more interesting: agents working across multiple logistics applications and organizations to execute parts of a representative end-to-end supply chain process.

That distinction matters.

Descartes described one of the persistent problems in logistics as the “swivel chair tax.” A shipment may move physically from origin to destination, but the information required to manage it still moves through transportation systems, compliance applications, carrier portals, email inboxes, messaging platforms, spreadsheets, and people. The applications themselves are often perfectly capable. The problem is everything that happens between them.

Descartes’ emerging answer is what it calls its Agent Control Plane. In the keynote demonstration, an order moved through four representative companies and 15 Descartes products, with 28 individual process steps occurring behind the scenes. Agents performed tasks ranging from compliance checks and information gathering to disruption detection and replanning, while the underlying Descartes applications continued to perform the operational work they were built to do.

But the most important part of the demonstration may have been what the agents did not do. At several points, humans remained responsible for consequential decisions. When a compliance issue appeared, the agent gathered the relevant information and escalated the decision. Later, when a disruption created an opportunity to rebook transportation at an 8% savings, the alternative carrier carried a trust score of just 32. The agent surfaced the option; the human rejected it.

That is a much more realistic model of logistics automation than the idea of simply turning operations over to autonomous AI. Descartes summarized the philosophy particularly well: autonomy is a dial, not a switch.

This is where agentic AI starts becoming operationally interesting. Consider what normally happens when an international shipment is disrupted. Someone discovers the change, someone determines which shipments are affected, and other people begin checking capacity, appointments, customer commitments, carrier options, and downstream consequences. Emails and phone calls start moving among multiple organizations, and by the time the problem is fully understood, hours may have passed.

In the Descartes demonstration, agents detected the disruption, evaluated its downstream impact, investigated alternatives, and coordinated information across the participating companies. Instead of simply alerting the shipper that something had gone wrong, the system could potentially deliver something much more valuable: the problem and the proposed resolution together. That represents a meaningful change in the role of supply chain software.

For decades, enterprise applications have largely waited for people to operate them. Agentic systems introduce the possibility that applications can increasingly initiate work themselves—within defined permissions and with humans inserted at the appropriate decision points. Descartes also emphasized that this is not merely a future concept. The company said it has already executed approximately 3.25 million agent operations and is opening an early-access program for the Agent Control Plane.

Just as important, Descartes is building governance around the model. Agents have identities, actions are logged and attributable, and activity can be reviewed and replayed. That may ultimately prove as important as the AI itself because enterprises will want different levels of human oversight depending on the decision, risk, and business context. They may be very willing to let agents do the investigative work, coordinate routine activities, react to predefined conditions, and bring humans the relatively small number of decisions that actually require judgment.

That was my biggest takeaway from the keynote.

The next generation of logistics automation may not be about removing humans from the process.

It may be about removing humans from all the work they never needed to be doing in the first place.

The post Descartes Takes Agentic AI Into the Logistics Workflow at the Descartes Innovation Forum appeared first on Logistics Viewpoints.

Continue Reading

Trending