erp_transformation_discovery
ERP transformation with an incomplete requirement
Iterative discovery of integrations and user needs is relevant when the target solution cannot be specified responsibly before market engagement.
Methodology / model 2.3.0
A comparison method without a built-in result direction
The model separates legal compliance, procurement workflow design, contract design, execution channel and system support. Each decision remains visible in the record.
- 01
Set the shared boundary
Select the legal and governance boundary, procedure family and initiation date. Context outside the supported scope is rejected rather than completed by assumption.
- 02
Design both maps
For each alternative, define activities, predecessors, active work, waiting, roles and non-labour cost. Duration follows the longest path through the dependency graph.
- 03
Lock legal rules
Required periods are resolved from a versioned ruleset, retain explicit provenance and cannot be shortened by system support.
- 04
Calculate each alternative
Total cost comprises role effort, non-labour cost, elapsed time multiplied by the declared daily cost of inaction, and explicitly priced contract-design elements.
- 05
Record the result boundary
The decision record preserves axes, both designs, monetisation coverage, non-monetised dimensions, assumptions, sources, legal provenance and migration history.
When adaptation adds value and when it is unnecessary
The scenarios illustrate mechanisms rather than recommendations or observed outcomes. They show conditions to test before designing the procurement workflow.
Conditions that justify adaptive work
logistics_service_redesign
Logistics service redesign
Adaptation helps when the operating model, service levels and allocation of responsibility need joint validation. The scenario does not establish lower cost.
public_it_open_with_market_consultation
Public IT with preliminary market consultation
Consultation can clarify the need before an open procedure. Statutory submission and standstill periods remain identical for both alternatives.
discovery_solution_codesign
Solution co-design
Learning with the market can deliberately add time and effort. It is justified only when the value of information exceeds the cost of that additional work.
Conditions where more adaptation does not address the problem
stable_private_standard_service
Stable standard service
With a known requirement and repeatable market, simplify workflow and controls before adding discovery without a defined risk.
stable_capex_replacement
Replacement capital investment
A known specification and material investment gates may justify sequential decisions. System support does not remove the value of accountable control.
catalog_calloff_control / mrp_release_control
Catalogue or MRP execution
Supplier, price and terms are already contracted. The relevant problem is efficient transaction execution and exception handling, not redesigning sourcing.
Comparison identity
ΔC = cost of the formal sequential alternative − cost of the adaptive compliant alternative
Swapping the alternatives reverses the delta and its outer range. The test imposes no quota on either side of zero.
Low, central and high values form a declared scenario range, not a confidence interval or probability forecast.
Legal boundary
The model supports the stated classic procurement contexts. Sectoral, defence and security contexts fail closed. Selecting a special procedure still requires assessment of its legal grounds by an authorised person.
Practitioner-material boundary
Observations from Procurement&Beyond episode 8 inform questions about process friction, ownership, requirements, TCO and responsible automation. They are not evidence of implementation effectiveness and do not calibrate the cost model.