A common workflow layer across enterprise applications.

The challenge

Changan Mazda operated a landscape of enterprise applications supporting human resources, finance, manufacturing, quality and other activities. Employees needed to move work through those systems, but separate entry points and approval experiences made coordination difficult. Workflow information and attachments also needed to remain available during the transition to a new platform.

The project addressed the relationship between a common employee experience and the systems that held business records. It required process routing and application integration, alongside the identity, permissions and operational controls needed to make the platform usable across departments.

The approach

The company implemented AlphaFlow BPA for workflow management and automation. A common portal and single sign-on brought workflow access together. A unified permission model and consolidated task experience supported the way employees found and handled work.

Connecting the application landscape

The implementation connected applications including human resources, Oracle EBS, manufacturing and vehicle quality systems, as well as travel, email, directory and supplier-related services. The source reports integration with twelve heterogeneous systems, illustrating the breadth of the application landscape involved in the project.

Workflow use extended beyond a single approval form. The source describes document, meeting and vehicle-related activities alongside other enterprise processes. Structured data and system connections helped carry the result of an approval into the relevant business application instead of leaving it as an isolated workflow record.

The platform supported Chinese, English and Japanese use and mobile approvals. These capabilities formed part of this customer’s reported implementation. The project also included interface monitoring and workflow permission administration, with controls such as watermarks and restrictions on mobile attachment downloads described in the source.

Moving existing work and records

The migration covered historical forms, routes, comments and attachments. Preserving those elements mattered because completed and ongoing workflow records were part of the organization’s operational history.

Identity and permissions were addressed together with the workflow experience. System actions, employee access and the visibility of records needed to fit the roles involved in each business process. Those relationships are especially relevant when a common workflow platform spans several application owners.

A dated view of use

For the first quarter of 2020, the source reports 9,520 initiated workflows and 8,682 completed workflows, with a reported completion rate of 91.2%, as of March 31, 2020. These are historical operating counts for the platform population described in that account. They are not measures of improvement against a previous system.

The case describes a delivered common workflow layer, application integrations and migrated process records. Its relevance is the coordination pattern: connect employee tasks, approval responsibility and system actions while retaining the business context of the request. A new implementation would need its own scope, data mappings, exception handling and operational baseline.