Sustainability data creates enterprise value only when it enters the same decisions, controls and workflows that run the business.
Many organisations discover their sustainability-data problem at reporting time.
Teams search spreadsheets, reconcile conflicting definitions, request missing supplier information, manually assemble indicators and then attempt to explain why the numbers do not align with finance, operations or procurement. The visible problem appears to be reporting. The underlying problem is usually integration.
A 2017 paper by Chofreh, Goni and Klemeš developed a roadmap for implementing Sustainable Enterprise Resource Planning systems, or S-ERP. Their central premise was that sustainability processes, information and data should be integrated across the extended value chain rather than managed in isolated tools. The proposed master-plan concept separated a roadmap, which identifies implementation stages, a framework, which defines important perspectives, and guidelines, which describe actions.
The paper is conceptual and explicitly calls for further evaluation of the roadmap's usability. It should not be treated as proof that one implementation model guarantees success. Its strategic value lies elsewhere: sustainability information becomes useful when it is part of the enterprise operating system, not a parallel reporting system.
The Strategic Context
ERP systems exist because organisations need common processes and data for functions such as finance, procurement, inventory, production, projects and sales. Sustainability cuts across many of the same processes.
Carbon can depend on energy, materials, freight and product volume. Waste can depend on production orders, yield and disposal routes. Social indicators may depend on workforce and supplier data. Product sustainability can depend on bill-of-materials structures, sourcing and lifecycle assumptions.
If sustainability data is collected outside the systems that create these transactions, several problems emerge:
- data arrives late;
- definitions drift;
- reconciliation becomes manual;
- accountability is unclear;
- audit trails weaken;
- sustainability teams become dependent on periodic requests rather than operational signals.
The transformation challenge is therefore not simply to buy sustainability software. It is to decide where sustainability information belongs in the architecture of enterprise decisions.
What Leaders Commonly Misread
The problem is assumed to be a dashboard problem
A dashboard cannot repair fragmented source processes.
If sites classify waste differently, suppliers use inconsistent units or product data lacks required attributes, a visualisation layer simply presents the inconsistency more elegantly.
Transformation should begin with data ownership, process design and decision use cases.
Sustainability is treated as a specialist workflow
When environmental or social information sits entirely with a sustainability team, operational owners can see it as someone else's reporting obligation.
But many sustainability outcomes are created by decisions in procurement, engineering, operations, logistics and capital investment. The relevant data should therefore enter those workflows where practical.
For example, a sourcing decision can include environmental attributes before a purchase order is raised, not months later when the annual footprint is calculated.
Implementation is treated as a technology project
The S-ERP paper draws heavily on project-management concepts and organises implementation across pre-implementation, implementation and post-implementation phases. This is useful because technology changes processes, roles, data structures and behaviour.
A system can technically go live while the transformation fails because people maintain shadow spreadsheets, definitions remain contested or executives do not use the information in decisions.
Go-live is a transition state, not benefit realisation.
More data is assumed to create better decisions
Integration can generate vast quantities of sustainability data. The objective is not maximum collection.
Each field should have a reason to exist. Does it support compliance, a management decision, a customer requirement, an environmental budget, an investment choice or a risk control? If no decision or obligation uses the information, collection may create cost without value.
Reframing the Issue
S-ERP should be framed as enterprise decision integration.
The question becomes:
Which sustainability information must be embedded into which business processes so that better decisions occur routinely?
This reframing changes implementation priorities.
Instead of starting with a sustainability data catalogue, start with decisions:
- Which supplier should we select?
- Which product design should advance?
- Which plant needs intervention?
- Which capital project should be funded?
- Which environmental hotspot is consuming the portfolio budget?
- Which compliance threshold requires escalation?
Then determine what data, workflow and governance those decisions require.
Related article: Relative Efficiency Can Still Be Unsustainable: The Executive Case for Environmental Budgets
Strategic Analysis: Integrate the Decision, Not Just the Data
Architecture follows accountability
Every material sustainability metric needs an operational owner and a data owner.
The operational owner is accountable for the outcome. The data owner is accountable for definition, quality and availability. These may be different people.
Without this distinction, sustainability functions often become de facto owners of outcomes they cannot control.
The roadmap needs gates, not only phases
Chofreh et al. proposed three broad lifecycle phases and mapped project-management process groups across them, including initiating, planning, executing, monitoring and controlling, and closing at relevant points.
Executives can strengthen this idea by introducing decision gates.
A pre-implementation gate should confirm strategic purpose, process ownership, data readiness and benefit logic.
An implementation gate should test configuration, integration, controls and user adoption.
A post-implementation gate should test whether the system is producing decision value, not merely whether technical defects are closed.
Post-implementation is where value is tested
The source roadmap includes post-implementation activities related to go-live and continued monitoring and control. This is strategically important because enterprise systems often create a temporary illusion of completion at deployment.
The real questions come later:
- Are users entering data correctly?
- Are legacy spreadsheets disappearing?
- Are decisions changing?
- Can the organisation trace a reported metric back to transactions?
- Are suppliers providing usable information?
- Are benefits visible in risk, cost, compliance or environmental outcomes?
If not, the organisation has installed a system but not institutionalised a capability.
Integration creates new dependencies
Sustainability data may rely on finance, master data, supplier portals, production systems, project systems and external datasets. This increases complexity.
Program governance should therefore manage dependencies explicitly. A sustainability module can fail because the bill of materials is wrong, supplier IDs are inconsistent or production quantities are not trustworthy.
The transformation cannot be owned solely by IT or sustainability.
Data quality should be prioritised by decision criticality
Not every sustainability field requires the same assurance level.
A figure used for statutory reporting, capital approval or external customer commitment deserves stronger controls than an exploratory internal metric.
This avoids an expensive attempt to perfect all data at once.
Related article: Environmental Decisions Need Confidence Ranges, Not Just Precise Scores
Decision Framework
A practical S-ERP investment test can be organised around six questions.
| Dimension | Executive question |
|---|---|
| Strategic purpose | Which enterprise decisions or obligations will improve? |
| Process ownership | Which business process creates the outcome? |
| Data architecture | Where will the data originate, and who owns quality? |
| Integration | Which systems and master-data structures must connect? |
| Adoption | What behaviour must change for the system to work? |
| Benefits | How will leadership know the capability is producing value? |
Before funding a major implementation, every proposed metric should be mapped to a process and a decision.
If a sustainability indicator has no operational owner, the design is incomplete.
If a decision requires data that the organisation cannot reliably capture, the roadmap should include capability development before automation.
From Strategy to Execution
Immediate action
Inventory the highest-value sustainability decisions and identify how information currently reaches them. Look for manual spreadsheets, duplicate definitions, missing owners and delayed data.
Select a small number of use cases where integration can materially improve a recurring decision. Avoid attempting to automate the entire sustainability universe in the first release.
Medium-term capability building
Create common sustainability data definitions, ownership rules and control standards. Integrate high-value fields into existing enterprise processes where this reduces duplication and improves accountability.
Run the work as a transformation program with business, sustainability, IT, finance, procurement and operations representation. Manage dependencies and adoption as program risks.
Use post-implementation reviews to identify shadow systems and decisions that have not changed despite the new data.
Long-term strategic positioning
Build an enterprise information architecture capable of connecting sustainability constraints with portfolio and operational decisions.
For example, environmental budgets could inform product portfolios, supplier selection and capital planning rather than appearing only in annual reports.
Related article: Carbon Is a System Property: Why Emissions Strategy Must Follow Economic Linkages
The mature outcome is a business in which sustainability information travels with the transaction and is visible at the point of decision.
Signals to Monitor
Watch for:
- recurring manual reconciliation at reporting time;
- sustainability metrics with no operational owner;
- multiple definitions of the same indicator;
- a new platform recreating old spreadsheet processes;
- go-live celebrated without evidence of changed decisions;
- sustainability teams becoming data administrators rather than strategic advisers;
- critical metrics depending on poor master data;
- users bypassing workflows because the system increases friction;
- growing data volumes without clear management use.
Questions for the Leadership Team
- Which decisions should become better because of this system?
- Which sustainability outcomes are created by processes outside the sustainability function?
- Where is the authoritative source for each critical metric?
- What shadow systems should disappear after implementation?
- How will we test adoption and decision value after go-live?
- Which data deserves the highest assurance because it drives external commitments or capital decisions?
- Are we integrating sustainability into the operating model or simply automating reporting?
Closing Perspective
Sustainability reporting problems often reveal deeper operating-model problems.
When data is fragmented, ownership is weak and processes are separate, a new dashboard cannot create integration. Enterprise systems become valuable only when they connect sustainability information to the transactions and decisions that generate the outcome.
The S-ERP roadmap concept is therefore useful not because it offers a universal implementation recipe, but because it frames the work as a staged enterprise change.
The leadership objective should be clear: make sustainability information part of how the business runs, not a parallel system that explains the business afterwards.
Source References
- Chofreh, A.G., Goni, F.A. & Klemeš, J.J. 2017, 'Development of a roadmap for Sustainable Enterprise Resource Planning systems implementation (part II)', Journal of Cleaner Production, vol. 166, pp. 425-437, doi:10.1016/j.jclepro.2017.08.037.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.