In an opinion piece published by InformatiqueNews, Guillaume Faugère, a technical leader at Constellation Group, presents ERP modernisation as a strategic decision connecting data, operations and sustainability. This source represents a vendor perspective. It helps structure the questions but is not, by itself, proof of economic or environmental benefits for a particular business.
Start with data and workflows, not the word cloud
The author emphasises the need for reliable, available and usable data. The first leadership question is therefore not a hosting choice. It concerns the workflows the ERP must support, the quality of reference data, interfaces with business applications and responsibility for each data item.
A hybrid or cloud-native architecture may facilitate integration and evolution. It may also add dependencies, usage costs and monitoring requirements. Compare the choice with an internal baseline: incidents, processing times, maintenance workload, data quality and continuity constraints.
Assess AI uses within their operational chain
The opinion piece mentions visual inspection, predictive maintenance and knowledge-base enrichment. These uses do not demonstrate a universal result. Rather, they show where an ERP may connect an observation, business data and an operational action.
- Identify input data and its level of quality.
- Define the assisted decision and required human approval.
- Trace the action triggered within existing systems.
- Plan degraded operation and recovery after an error.
- Compare results with the business’s own baseline.
Integrating AI and cybersecurity within a platform does not remove the need for governance. Access rights, logs, interface security and knowledge maintenance must remain explicit.
Measure resource efficiency instead of assuming it
The author argues that shared, more efficient infrastructure can reduce the environmental footprint of digital technology. This proposition must be checked within the actual scope: consumption, location, utilisation, equipment lifetime, data transfers and additional services.
FinOps and CarbonOps are useful precisely because they turn an intention into measurement. The former helps make usage costs visible and attributable. The latter aims to track energy performance. Without a baseline indicator, calculation rule and monitoring frequency, an efficiency promise remains a hypothesis.
Use standards without erasing the business
The opinion piece presents a return to standard processes as a way to facilitate adoption and upgrades. This direction may reduce complexity, but the decision must be made process by process. A specific variation is justified only if it supports a genuinely differentiating business rule or an obligation that cannot otherwise be met.
Useful standardisation does not mean forcing every team into an abstract model. It means distinguishing what should remain common, what can be configured and what merits a documented exception. This discipline facilitates evolution and limits dependence on customisations that are difficult to maintain.
Decide using evidence specific to the business
Prudent scoping connects each choice with a workflow, an owner, data, a risk and a measurement. Leadership can then compare scenarios without assuming that cloud, AI or shared infrastructure will automatically produce the benefits claimed in the opinion piece.
Before any broad rollout, the right deliverable is a decision report: scope, target architecture, process impacts, full costs, resilience criteria, environmental measurement method, internal skills and reversibility conditions. Robinswood can help connect the ERP with critical workflows and establish this internal evidence.