Carbon Footprint
Collection of activity data, emission factors, calculation of product-related emissions and management of result versions.
Activatable modules
From Carbon Footprint and LCA to BMS data.
NexusDPP can integrate specialised microservices to calculate, collect and update environmental and technical data, connecting the results to the product’s Digital Product Passport.
Three microservice families
Environmental data, lifecycle analysis and dynamic information.
Each module operates within a defined scope and returns structured data that can support the DPP, internal controls and business documentation.
LCA
Organisation of the data required for Life Cycle Assessment, including study boundaries, scenarios and environmental indicators.
BMS
Acquisition of battery technical data such as state of charge, state of health, cycles, temperatures, alarms and usage events.
Product Carbon Footprint
From business sources to a traceable indicator.
The Carbon Footprint microservice can collect consumption, materials, transport, production processes and supplier data while preserving the connection with the sources used and the relevant product version.
- Configuration of calculation boundaries and lifecycle stages.
- Guided collection of primary data and management of emission factors.
- Retention of calculation evidence and revisions.
- Publication in the DPP of the value and authorised supporting information.
Life Cycle Assessment
LCA becomes a coordinated data process.
NexusDPP can organise the inventory, scenarios and results of a lifecycle assessment, supporting collaboration between the company, environmental consultants, laboratories and verifiers.
Study boundaries
Definition of the product, functional unit, lifecycle stages and reference scenarios.
Data inventory
Materials, energy, processes, transport, use, maintenance, end of life and partner data.
Quality and provenance
Data origin, reference period, collection method, reliability level and linked documents.
Results and scenarios
Environmental indicators, comparison of alternatives and updated versions when the product or value chain changes.
DPP connection
Selective publication of results and controlled access to the complete supporting evidence.
Battery Management System
BMS data brings the battery’s dynamic condition into the DPP.
For batteries and energy-storage systems, NexusDPP can connect BMS data to the battery’s digital identity while separating public data, technical data and confidential information.
- State of Charge and State of Health.
- Cycle count, temperatures, voltages and diagnostic parameters.
- Alarms, anomalies, maintenance and technical updates.
- Data supporting service, warranty, second life and end of life.
“The DPP can combine static product data with dynamic usage information while applying different access rules for customers, service teams, manufacturers and verifiers.”
NexusDPP operating modelActivation model
Independent microservices coordinated by the same DPP.
A company can start with one module and add further capabilities as more data becomes available or project objectives evolve.
Configuration
Definition of scope, required data, roles, update frequency and expected outputs.
Connectors
Connection with business systems, structured files, calculation tools, IoT systems, BMS and document sources.
Governance
Completeness checks, approvals, versions, change traceability and role-based access.
Evidence
Datasets, documents, factors, reports and attachments remain linked to the result generated by the microservice.
Updates
Results can be recalculated when materials, suppliers, processes, usage or technical condition change.
DPP view
The passport displays only the information authorised for each user and project configuration.
Modular roadmap
From the first indicator to a complete product-data system.
Carbon Footprint, LCA and BMS can be adopted separately or combined to create a progressive data foundation for sustainability, compliance, service and lifecycle management.
Phase 1
Select the priority microservice and map available data sources.
Phase 2
Configure the data model, collect evidence and complete the first processing cycle.
Phase 3
Internal validation, optional specialist review and connection to the DPP.
Phase 4
Automate updates and activate additional microservices.