Method
Who builds, who owns, what you pay for
Delivery divides into four layers: the specification platform, process building, the runtime environment, and cloud, security and compliance architecture. Once the layers are separated, each one can be decided separately: what is bought as a service, what is built in-house and what is tendered.
Delivery defines who builds and owns what
Delivery divides into layers, from the specification platform to the cloud architecture. Typically we supply all layers at the start and hand them over as the client matures. The target state is that the client's own small team builds the processes, with Managentics providing the platform and technical consulting.
The layers in brief
The specification platform is the tool for describing and governing processes; it is our product and stays with us. Process building turns specifications into working processes; it shifts step by step to the client's own team. The runtime environment is in the client's own cloud, on the client's own accounts, from day one. Cloud, security and compliance architecture secures the foundations of security, access control and compliance, and it is designed together with the client's IT.
Why the division of layers is worth making visible
Once the layers are separated, costs can be compared and decisions made layer by layer: what is bought as a service, what is built in-house and what is tendered. Without the division, programmes are bought as a lump, comparison becomes impossible and vendor dependency forms unnoticed.
Frequently asked questions
Q:How big does our own team need to be?
In the target state a few developers are enough to build and maintain an entire process portfolio, because the specifications and the platform make the work repeatable.
Q:Can the layers be bought from different vendors?
Yes, and the division is designed for it. The specification ties the layers together regardless of who supplies each one.