Availability and support
In the service level agreement (SLA), we agree on measured availability, the monitoring method, maintenance windows, response times and the outage procedure.
OPERATIONS NEED RULES
Data that lasts.
Trust we can demonstrate.
High availability is not a single marketing number. It requires monitoring, tested recovery and clear responsibility.
AVAILABILITY AND DATA PROTECTION
The passport must keep working for years.
Operations need specific rules.
We will design the production service for high availability. Storing files is not enough: we need to manage access, monitor operations, recover data and ensure it can be handed over if the provider changes.
Security and privacy
The proposal includes managed permissions, separation of client data, encryption and change logs. We will confirm the data storage location and subcontractors before launch.
Backup and recovery
We agree on backup frequency, retention period, recovery time objective and the acceptable loss of recent changes. Recovery has to be genuinely tested.
Continuity and the option to leave
We agree on export, data handover, keeping QR links working and a fallback procedure in case the operator or the client ceases to exist.
The service period is not governed by the subscription term alone.
For the battery passport, the law addresses availability even after the responsible company ceases to exist, as well as the end of the passport after recycling. We therefore set up long-term storage, handover and operational cover from the rollout. [1]
The specific availability percentage, scope of support and security parameters will be part of the agreed offer. The pilot environment does not automatically have the parameters of the live service.
A CONCRETE AGREEMENT
What we agree on before going live.
Where and who
Data location, infrastructure providers, subcontractors and their roles.
What is measured
Measured availability, support, outages, maintenance windows and incident escalation.
How recovery works
Backups, acceptable loss of changes, recovery time and a record of the test performed.
Who sees what
Client separation, roles, administrator access and change history.
How you can leave
Export scope, formats, transfer of identifiers and a handover plan.
What is actually verified
Operational and security tests. We do not claim any certification we cannot document.
WHAT WE SET UP BEFORE LAUNCH
Your data.
Clear rules.
Where the data runs, who can access it and how it is recovered. We will confirm the specific operating parameters for your delivery.
Data location clear in advance
We determine the hosting region, backups and involved suppliers before going live.
What we agree on
Primary data, documents, backups, operational logs and support access. We do not derive the specific location from where the marketing website is hosted.
Personal data protection
We set up responsibilities, access and contractual terms for processing.
What we agree on
The scope of personal data, controller and processor roles, subcontractors, retention period and incident handling. Server location alone does not settle this area.
Backup and a path to recovery
The handover will include an agreed backup procedure and its verification.
What we verify
Backup frequency and retention, the recovery procedure, the target recovery time and the acceptable loss of recent changes.
Availability without ambiguity
We agree on what is measured, who responds and how an outage is announced.
What we agree on
Measured services, support, maintenance windows, incident history and the method of data handover. The pilot does not automatically have production parameters.
We will confirm the scope, features and operating conditions in the pilot and in our offer.
Discuss security and operationsBATTERYPASSPORT
Security, operations and evidence
Before production launch, we agree the service scope, operational responsibilities and data handover.
What we agree and verify before handover
- Data locations and subprocessors.
- Access rights, account management and change records.
- Availability measurement, backups and recovery tests.
- Support, incident response and contract exit.
- Export, stable QR links and long-term continuity.
Evidence, programs and technology
Each entry states what it demonstrates, who holds it and the scope it covers.
ORGANIZATION CERTIFICATION
ISO/IEC 27001:2022
View evidenceMEMBERSHIP
Digital Product Passport Pro listing
View evidenceNEXT STEP
Let's start with one model.
We will go through your batteries and source data. We will propose the pilot scope, the cooperation required and the price. No automatic commitment to live operation.
Book an initial consultation