The challenge

Xingfa Aluminium needed to coordinate process management across multiple manufacturing locations and business activities. Standards, process knowledge and access responsibilities were difficult to keep aligned as the organization operated across sites. The challenge included both the definition of work and the handoffs needed to run it.

The published case identifies inconsistent process standards, scattered knowledge, unclear responsibility boundaries and repeated manual actions between systems. It also describes limited end-to-end visibility. Without a reliable connection between process design, execution and data, improvement depended too heavily on experience and local observations.

The approach

Xingfa adopted a staged programme spanning the AlphaFlow process lifecycle. EBPA provided process architecture and assets; BPA supported online workflow execution; integration robots supported defined cross-system actions; and BPI provided analysis of actual execution.

The sequence established a process foundation before adding further execution and analysis capabilities. It brought process documents, responsibilities and access rules into the same overall programme as workflow automation.

Implementation in stages

The EBPA process design platform entered trial operation on January 5, 2023. Formal deployment followed on September 20, 2023, with process architecture, position-based views and document archiving forming the foundation.

The execution platform was deployed on October 28, 2023. It brought core business workflows online and supported routing through a process engine. A robot platform followed on January 14, 2024, extending coordination across systems through configured repetitive actions, connectors and interfaces.

BPI was deployed on July 18, 2024. This added a way to reconstruct operational paths and examine process behavior. Each stage built on the process foundation and capabilities established earlier in the programme.

Examining purchasing work

BPI reconstructed paths in the purchase requisition process and examined activity durations and process variants. This gave the team a way to identify frequent paths and investigate waiting across the request journey.

Process owners could use this evidence to evaluate variations and decide where changes to the workflow would be useful.

What was delivered

Xingfa connected maintained process assets, online execution, cross-system automation and operational analysis. Teams could query process knowledge, run business workflows and investigate actual execution data.

The staged implementation linked the standards used to define work with the operational evidence needed to improve it after deployment.

KEY TAKEAWAYS

Takeaways for your team.

  • Sequence design, execution, integration and analysis around the readiness of the process.
  • Distinguish templates, running instances and event samples when reporting platform use.