A process reference model suitable for all initiatives.
A best practice repository suitable for your business. Our goal has been to make processes more accessible. More specific. And ultimately more standardized. Business Flows covers details of an operating model from a business perspective. Packed in an simple process architecture suitable for small initiatives as well as for the standardization and transformation of large industrial enterprises.
> END-TO-END BUSINESS FLOWS
> SIMPLE PROCESS DESCRIPTION
> BPMN 2.0
End-to-End is the best way to describe business processes. To manage complexity define Process Domains that are sufficiently specific to cover details of an enterprise's operating models, such as Order to Cash, Procure to Order or Plan to Produce.
Don't just provide a list of business processes. Think about how your processes interact and address certain business cases. Compile a list of End-to-End Scenarios and comprehensive descriptions for each Domain. The scenarios should represent specific business cases fulfilling a specific business objective or represent a specific operating model.
Our Process Groups cluster individual processes in a functional representation similar to operational departments. In this sense, we offer a streamlined approach to gather the relevant business experts to review, adapt, and approve the reference model according to their business operations. We applied the SCOR framework across the supply chain: source, make, store, sell, and service and extend it by design, plan, service, integrated management system, enterprise management, and quality compliance management.
E2E PROCESS FLOWS
The End-to-End Processes represent the sequence of the involved business processes across functional silos providing the transparency to enable business readiness and requirements alignment. Mentioning the involved department is a key information worth highlighting on this level.
Build on BPMN 2.0 as the most common notation standard to describe processes from a business as well as from an IT perspective. Maintain complete descriptions in order to avoid unproductive process discussions, add reference model business rules, and mention IT-specific information as for example SAP transaction codes if you need them for your initiative. Of course all our processes are available in other industry standards, e.g. ARIS, Signavio, XML, etc.