Documents & integrations
Keep information and documents connected to operations.
Operations often involve several applications. The business record needs to retain useful references, track document stages and send events to partners. Here are integrations and controls we have developed.
- EWC & ADR
- Trackdechets waste tracking
- APIs & notifications
Examples from vehicle and battery projects. Document obligations and integration capabilities must be checked for each country, activity and system involved.
EWC and ADR: separate information, separate purposes.
Waste classification codes and transport information need to be recorded in the right place. Grouping them under a compliance label does not explain what the tool actually does.
What the application does
- The EWC code is linked to the declaration and can be suggested from the reference battery type.
- Battery condition is recorded separately with the required diagnostic documents.
- The interface displays the ADR information defined for that condition. Teams define input rules, supporting documents and required approvals.
The detail that matters
The application organizes data and applies defined rules. It does not automatically turn an EWC code into authorization for transport or treatment.
What the team gets
Distinct, accessible information that helps qualified stakeholders review the record.
Include the waste tracking form in declaration tracking.
For relevant French operations, the waste tracking form (BSD) has its own statuses. Teams need to know whether it is created, signed and ready for the next step.
What the application does
- The application creates or updates a form through Trackdechets and stores its identifier with the declaration.
- It checks status and distinguishes a missing producer signature from a missing collector signature.
- The workflow can condition receiving on these signatures, then transmit receiving and treatment information.
The detail that matters
A blocked step should explain why and who needs to resolve it. This describes a control in the developed workflow, not a universal legal rule.
What the team gets
The form and declaration remain linked; the user sees document status and required actions.
Link signatures to the right record.
A document sent for signature should remain connected to the vehicle or operation that generated it.
What the application does
- In the relevant vehicle workflows, transfer and destruction documents are generated within the process.
- The DocuSign electronic signature service is integrated into the workflow.
- The business record provides access to the documents and signature progress.
The detail that matters
Signatories, documents and signature timing are defined by the procedure. The project also accounts for incomplete steps.
What the team gets
Continuity between the request, prepared documents and signature tracking.
Exchange business objects, not just files.
A provider may already manage operations in its own system. Requiring every change to be entered again in a portal adds work instead of removing it.
What the application does
- A provider API supports operations including battery data exports and imports and price proposals.
- Outgoing notifications report specific events: a battery assigned, ready for pickup, received or processed; an offer created or accepted.
- Access is authenticated and limited to the partner’s scope. Interfaces and exchange formats are defined for the relevant operations.
The detail that matters
A connection to your ERP or logistics software needs assessment: available data, exchange direction, access rights and error handling. We do not assume a universal connector exists.
What the team gets
A partner can update tracking from its system and receive events relevant to its operations.
FDTI
Show us a real flow, its participants and the tools already in place.