Section
Case Studies & Reflections
Cases and methodological reflections grounded in real business problems.
Why did a project to generate BOMs from drawings begin by redefining the product?
The customer initially wanted AI to generate BOMs automatically from drawings. After reassessing the underlying need, we first clarified the product definitions and parameter-to-material configuration rules for six standard models, then built a small tool and put it into use. The technical department reported an improvement of approximately 25%–30% in efficiency for this work.
Why are equipment records still hard for people and AI to use as more fields are added?
Sales, asset management, maintenance, and quality teams all keep adding fields to the same equipment table. Each request makes sense in isolation, yet the page grows longer and the information becomes harder to use. The problem is not merely the number of fields: different business domains, perspectives, and purposes have been compressed into one representation.
Why must ‘approval’ be unpacked before an agent can automate it?
Many OA systems treat form records, notifications, object creation and change, and decisions that truly require judgment as the same thing: approval. Before an agent can participate, the first step is not to make it run the workflow faster, but to distinguish what these actions really are.