Composability is a system design principle that deals with the inter-relationships of components. A highly composable system provides components that can be selected and assembled in various combinations to satisfy specific user requirements. 1 Wikipedia “Composability”
In the context of business processes, composability describes the ability to flexibly design process supporting applications by assembling existing system capabilities according the respective process flow as needed.
Examples for composable business capabilities:
Any element of business logic that is needed in multiple processes or process variants should be made accessible as a composable component, as a “microservice” to be available in any process context where needed.
Take “Order confirmation / ATP” as an example. This capability may sit in your ERP or e2e planning, but it needs to be accessible from various “order entry” channels: e-business, customer service, inbound EDI, VMI etc. etc.
Composability requires two prerequisites:
- Systems that make these logical components accessible as a “service”
- A smart process orchestration engine like OpenPlatform powered by PointOut®.AI
The advantages are obvious:
- Avoidance of redundancies – any logical component is built / implemented only once
- Flexible fulfillment of fast changing business requirements w/o increasing system complexity
- Enablement of process-centric design, e2e and lean, replacing system-centric design