Insights & tools
Problems that keep recurring in projects, written up as judgments you can use.
A useful question can change the next operating meeting. Explore practical ideas, use the checklists with your team, and connect what you learn to a business improvement or AI scenario.
Contents
- ·Featured series: one complete reading path
- ·Articles: judgment, method and practice
- ·Tools: downloadable checklists and templates
Featured series
More Systems, Yet Operations Still Get Stuck?
The first series in our long-running theme on the real breakpoints of manufacturing operations. It arranges three articles, two tools and three services into a reading order rather than reposting the articles.
ABOS Agent Insights
How AI can support real manufacturing work.
Practical perspectives on how AI can support real manufacturing operations - with clear business context, evidence, governance, and human responsibility.
The single chain behind delivery, inventory and operational visibility: promise, change, readiness, execution and exception handling - where each one breaks, who owns it, and what data settles it.
Which work fits AI, which operational facts it needs, how people and rule tools divide the work, and what always needs human approval. Explore the built-in L0–L2 controls in ABOS Suite and the agent articles.
The order in which a business problem moves through diagnostic, blueprint and capability build, and the conditions each step requires. Currently spread across the service pages and articles rather than a separate series.
Articles
Judgment for deciding, method for acting.
Articles focus on judgment and method and do not disclose client names or identifying detail. Each link below is labelled Chinese Edition.
Business judgment
Questions for deciding where the operating problem really sits.
- 01Read in 中文 →
Why a digital project has to start from a business problem
When a project starts from a system shortlist rather than a business problem, there is no way to decide afterwards whether it worked.
- 02Read in 中文 →
The five most common breakpoints from order to delivery
Losing control of delivery is rarely a scheduling problem. It is the absence of one operating thread across order, demand, material, production and exception handling.
- 03Read in 中文 →
Four conditions to meet before AI enters real operations
The value of AI is not decided by a model demo. It depends on whether data, process, accountability and measurement can carry a recommendation into real action.
AI delivery & technology
Conditions, controls and architecture for bringing AI into operations.
- 01Read in 中文 →
Rules before tools: agent levels L0–L4 and a registry
Decide what an agent is allowed to do, who signs off and how far data may travel - before choosing any architecture.
- 02Read in 中文 →
A prompt is not control: the deterministic kernel and three red lines
Any number or judgment that reaches a customer, an audit or a label must come from a traceable deterministic kernel. The model explains; it does not manufacture truth.
- 03Read in 中文 →
Three questions that decide agent selection
Source of truth, consequence and step determinism decide the engineering form - not the other way round.
Tools & guides
Two tools you can run yourself first.
Each tool page states what it helps you judge, what falls outside it, and its version and language.
Order-to-delivery checklist
Five breakpoints and 20 statements - enough to locate where delivery loses control in a single management meeting.
PDF in Chinese · v1.0 · 2026-09-01
Obsolescence definition & RACI
Definition rules and data fields for five inventory classes, plus a six-function by four-step responsibility matrix.
PDF in Chinese · v1.0 · 2026-09-01Methods
Two methods connecting direction, capability and operations.
Each method sets out a shared working process and the basis for its judgments.
ABOS Framework
From reading the strategy and checking the current state to building capability and driving operations - closing the gap between planning and implementation.
View method →Zao Agentic Operations
Design the controlled collaboration of agents, processes, tools, knowledge, permissions and observability.
View framework →Use 30 minutes to align your stage and smallest starting scope
The first discussion is not a pitch for an all-in-one package. Bring a delivery, readiness, inventory or legacy-integration problem. Together we identify your stage and an initial scope you can verify.
Book a focused discussion →