The customer and project context
Dynabook Technology (Hangzhou) was formerly Toshiba Information Equipment (Hangzhou). The customer’s official history records the company name change in April 2019. The earlier AlphaFlow account describes the implementation under its former name; a later update covers procurement workflows under the Dynabook name.
The challenge
The earlier implementation required Chinese, English and Japanese interfaces alongside connections with existing Oracle and HR systems. Teams needed more flexible workflows and a shared way to manage documents, training, assets and financial activities. The later procurement account describes duplicated data entry and coordination across separate operational systems.
A shared workflow environment
The historical account describes multilingual collaboration and integration requirements. The later AlphaFlow BPA implementation update reports a common login and workflow entry point, connecting office automation, customs declaration and HR systems. Asset purchases, new-item registration and related operational requests could be initiated through the platform.
Connecting purchasing to receipt
For non-raw-material items, the procurement project linked requests with supplier delivery, customs declaration, warehouse receipt and inventory. Shared rules and templates organized the handoffs. The update also describes automatic selection of electronic seals during approval, based on the person handling the workflow.
Connected procurement at the Hangzhou company
The Hangzhou company built on its multilingual collaboration environment to connect procurement workflows and operational systems. Teams gained a shared entry point for requests and a clearer connection between procurement records and the applications used to manage them.
KEY TAKEAWAYS
Takeaways for your team.
- Carry multilingual access and existing system requirements into workflow design.
- Define purchasing responsibilities through receipt and inventory, not only the initial request.
