Common questions about Report Zero
Practical answers to the questions most often raised by operations, IT, sustainability and governance teams when evaluating or deploying Report Zero.
This FAQ focuses on common topics such as setup, reporting, standards alignment, security and integration. It is not intended to be exhaustive. As Report Zero evolves, and as regulatory and operational requirements change, this library will continue to expand. If you are looking for clarification on a specific use case or environment, just ask.
01 -What is Report Zero?
Report Zero is a metrics platform for data-centre environments. It collects measured operational data from existing facility and infrastructure systems and converts it into consistent, standards-aligned energy, water and environmental metrics that can be used across individual sites or entire portfolios.
02- What problem does Report Zero solve?
Many organisations already collect large volumes of operational data from data-centre systems to support the facility statbility and operationl status. Electricity and efficiency are rarely reported directly from systems with manual metrics being prepared on a site by site basis historically. The consistency of manual metrics is often questioned and can vary between sites due to calculation methodology, inaccurate calculation of M&E overhead and differant tools supplying the base information in differant formats. If efficiency and consumption reporting relies heavily on spreadsheets and manual reconciliation, teams spend time debating numbers rather than acting on them. Consistent reliable data is required to accurately assess each facility across a portfolio.
Report Zero addresses this by providing a single, standardised metrics layer across all sites and systems. By applying consistent calculation logic to measured data, it ensures everyone is working from the same figures. This removes ambiguity, reduces reporting effort, and enables clearer operational, financial and sustainability decisions at site, portfolio and executive level. Report Zero also collects data in real-time providing acurate consumption information as it happens providing actionable data that supports both the DC operational team and the IT teams to take action.
03 - How is Report Zero different from dashboards or reporting tools?
Most dashboards and reporting tools focus on visualising data from individual systems. While useful for local monitoring, they often rely on site-specific configurations, manual adjustments or inconsistent assumptions, which makes portfolio-level comparison and external reporting difficult.
Report Zero is designed to enforce consistency across entire data-centre portfolios. The data collection at site level is site specific, we map Report Zero to secific systems and only collect data that supports the metrics. Report Zero then applies a single, standardised calculation model across all sites, aligned to recognised global standards such as ISO 30134, EN 50600 and regulatory frameworks including EED and CSRD. This ensures that energy, water and carbon metrics are calculated the same way everywhere, producing outputs that are comparable, auditable and suitable for governance, regulatory reporting and executive decision-making, not just operational dashboards.
04 -Is Report Zero a replacement for DCIM or BMS tools?
No. Report Zero is designed to work alongside your existing DCIM, BMS, EMS and other facilities or infrastructure systems, not replace them. Those systems remain the systems of record for operational control, monitoring and alarms. Report Zero does not attempt to replicate their functionality or introduce additional operational tooling.
Instead, Report Zero consumes selected data from these systems and applies a consistent, standards-aligned calculation layer across sites and portfolios. This removes the need for manual reconciliation, spreadsheets or bespoke reporting logic, and ensures that metrics used for reporting, benchmarking and decision-making are comparable, auditable and defensible, without disrupting day-to-day operations
05 - How do we assess if Report Zero is a good fit?
Report Zero is designed for organisations operating one or more data centres that need consistent, auditable energy, water and carbon metrics across sites or portfolios. It is typically a strong fit where organisations already have BMS, EMS, DCIM or other facilities systems in place, and are under pressure to move beyond spreadsheets, manual reconciliation or inconsistent reporting — whether driven by cost reduction, regulation, audit, executive scrutiny or cost and efficiency objectives.
An initial assessment focuses on three practical areas: the operational data already available, the reporting and decision-making requirements across teams, and the size and complexity of the data-centre estate. This allows us to quickly determine whether Report Zero will deliver meaningful value, which metrics can be enabled immediately, and how capability can scale over time. If it is not a good fit, we will say so early.
06 - How do we start a conversation?
Contact us via our web form or pick up the phone to discuss your data-centre estate, reporting requirements or partner model. We are happy to help.
07 - Who typically uses Report Zero?
Report Zero is used by data-centre operations teams, IT infrastructure teams, IT leadership, sustainability and ESG teams, and finance functions. Each role uses the same underlying metrics for different purposes.
08 - Does Report Zero optimise data centres automatically?
No. Report Zero does not make automated optimisation decisions or apply control actions within data centres. Its role is to provide accurate, standardised metrics and clear visibility into performance across sites and portfolios.
By producing consistent, decision-ready insight, Report Zero enables customers and their partners to identify inefficiencies, evaluate options and take informed action using their existing operational processes and tooling. This ensures accountability and control remain with those responsible for design, operations and change.
09 - Does Report Zero replace sustainability strategy or consulting?
No. Report Zero provides a reliable data foundation that supports these activities rather than replacing them. We aim to provide the intelligence to enable better and more consistent decisions.
10 - What types of data does Report Zero collect?
Report Zero works with measured operational data including power, energy, water and fuel consumption. The specific data points depend on what is available in existing customer systems.
11 -Does Report Zero rely on estimates or proxies?
Where measured data is available, Report Zero uses it directly. Where data gaps exist, assumptions can be clearly defined and documented to maintain transparency and auditability.
12 - Which standards do the metrics align to?
Metrics are aligned to recognised industry and regulatory frameworks, including ISO 30134, relevant EN standards, and requirements associated with EED and CSRD reporting.
13 - Can metrics be compared across sites and regions?
Yes. Report Zero is designed to support direct comparison across sites, regions and entire portfolios. All metrics are calculated using a single, consistent calculation model, regardless of location, facility design or underlying systems. This removes variation caused by local configuration differences, manual adjustments or site-specific assumptions.
Because the same inputs, formulas and standards are applied everywhere, results can be compared reliably across sites and regions. This supports benchmarking, identification of underperforming facilities, and portfolio-level analysis without the need for manual normalisation or caveats.
14 - Does Report Zero calculate carbon emissions?
Yes. Report Zero calculates Scope 1 and Scope 2 carbon emissions using measured energy and fuel consumption data sourced directly from facility systems. Emissions are calculated using defined emission factors and consistent calculation logic, rather than estimates or spend-based proxies.
Where available, Report Zero applies near real-time, location-based electricity carbon intensity data to reflect actual grid conditions. Customer-specific emission factors can also be applied where required, ensuring alignment with internal ESG policies, corporate reporting methodologies, and regulatory requirements. This produces site-level and portfolio-level carbon figures that are auditable, comparable and suitable for use in EED, CSRD and internal governance reporting.
15 - How are water metrics handled?
Water consumption and efficiency metrics are derived from measured facility data where available and can be used for both operational monitoring and regulatory reporting.
16 - Can Report Zero support regulatory reporting?
Yes. Report Zero is designed to support regulatory and governance reporting by producing consistent, auditable metrics aligned to recognised data-centre and environmental standards. Calculations are based on measured facility data and standardised methodologies, rather than site-specific interpretations or manual adjustments.
Regulatory reports can be generated automatically from live facility data, reducing manual preparation and reconciliation effort. This supports repeatable reporting cycles for frameworks such as the EU Energy Efficiency Directive (EED), CSRD and internal governance, while maintaining a clear audit trail across sites and portfolios.
17 - Does Report Zero generate EED or CSRD outputs?
Report Zero supports the generation of metrics and data inputs used in EED and CSRD reporting processes. It does not replace wider organisational compliance workflows.
18 - Are the metrics audit-ready?
Yes. Metrics in Report Zero are derived directly from measured facility data and calculated using documented, standardised calculation logic. Inputs, assumptions and formulas are defined and applied consistently across sites, removing ambiguity caused by local interpretation or manual adjustment.
This provides a clear audit trail that supports internal review, external audit and assurance activities. Because the same methodologies are used across the portfolio, results can be repeated, explained and validated over time, which is essential for regulatory reporting, governance and formal assurance processes.
19 - How does Report Zero reduce manual reporting effort?
By removing the need to manually reconcile data from multiple systems and spreadsheets, Report Zero reduces time, effort and reporting risk.
20 - How is Report Zero licensed?
Report Zero is licensed per data centre, based on site size and operational complexity. Each site has an annual subsciption to Report Zero which is aligned to the clients portfolio view within Report Zero.
21 - Are there per-user licences?
No. Pricing does not vary based on user numbers, dashboards or standard reporting use cases. We also provide a be-spoke reporting service that designs reports for use accross a client portfolio.
22 - Are additional metrics charged separately?
No. Subscriptions include access to the full metrics set supported by the platform.
23 - How does pricing work for multi-site estates?
Multi-site estates use the same pricing structure across portfolios, with commercial terms agreed upfront.
24 - Can Report Zero be resold or embedded by partners?
Yes. Report Zero is used by resellers, systems integrators and technology partners as part of their own offerings.
25 - Who owns the customer relationship in partner deployments?
Partners retain ownership of the customer relationship. Report Zero provides the metrics platform and technical support.
26 - How is Report Zero deployed?
Report Zero uses a lightweight deployment approach designed to integrate with existing environments. Deployment models align with customer security and architecture requirements.
27 - Can we start with a pilot or limited scope?
Yes. Many customers begin with a subset of sites or metrics before expanding coverage across their estate.
28 - Can Report Zero be rolled out gradually?
Yes. Many organisations begin with a small number of sites in a single region and expand coverage over time using the same metrics framework.
29 - Does Report Zero require access to production systems?
Report Zero requires access only to the data needed for metrics calculation, using access models designed to minimise operational and security risk.
30 - How long does implementation take?
Implementation timelines depend on data availability and scope. You will instantly have access to Report Zero for manual data uploads. Full integration is typically completed 3-4 months depending on security approvals.
31 - What does a typical implementation involve?
Implementation typically involves identifying relevant data sources, configuring secure data access, validating calculations, and confirming reporting outputs. The scope depends on the number of sites, systems and metrics required. We have a 3-phase deployment plan;
Phase 1: Mobilisation – Report Zero is deployed immediately for manual data uploads, this gives you access to consistent metrics based on your existing consumption data.
Phase 2: System Integration & Implementation – We design the integration for security sign off and implement near-real-time data flows from the facility to Report Zero
Phase 3: Test and Go Live – All data feeds are tested against the expected results ahead of transition to near-real time data in your Report Zero instance
32 - How is implementation managed?
Your Customer Sucess Manager will provide access to the Report Zero Site onboarding portal. This collabouration space guides the whole team through the site implementation and keeps everyone up to date with the site implementation.
33 - Does Report Zero require agents on production systems?
No. Report Zero does not require agents to be installed on production systems. Data is accessed through existing systems and interfaces, using controlled integration methods agreed during onboarding.
This approach avoids introducing additional software into operational environments and reduces security and operational risk. Integrations are designed to align with existing architecture, access controls and change-management processes, ensuring minimal impact on live systems.
34 - Can Report Zero work with different systems at different sites?
Yes, Report Zero is system agnostic. Many estates operate different DCIM, BMS or facilities systems across sites. Report Zero is designed to normalise data from heterogeneous environments into a consistent metrics framework.
35 - How much internal resource is required during implementation?
Internal effort is typically focused on system access, validation and review rather than ongoing manual data handling. Requirements vary depending on environment complexity.
36 - How are data quality issues handled?
Data quality is assessed during onboarding. Where gaps or inconsistencies exist, they are documented and addressed transparently rather than hidden through assumptions.
37 - What happens if our systems change over time?
Report Zero is designed to operate alongside evolving environments. Changes to source systems are managed as part of ongoing service and support.
38 - How is data secured?
Report Zero is designed with security as a core requirement. Data is transmitted securely from customer environments using encrypted connections, and access to the platform is tightly controlled through role-based permissions. Customer data is logically segregated to ensure isolation between organisations.
The platform follows established enterprise security practices across data handling, access control and operational processes. This approach supports use in regulated environments and ensures data can be managed in line with internal security policies and governance requirements, without introducing unnecessary risk or exposure.
39 -What security standards does Report Zero follow?
Report Zero follows established enterprise security practices aligned with customer and regulatory expectations. Specific controls are addressed during security review and onboarding. Report Zero is ISO / IEC 27001 : 2022 acredited.
40 - Who owns the data?
Customers retain ownership of their data. Report Zero processes data solely to provide metrics and reporting services.
41 - Is customer data isolated from other customers?
Yes. Customer data in Report Zero is logically segregated to ensure isolation between organisations. Each customer’s data is processed and accessed within its own controlled environment, preventing visibility or access by other customers.
This segregation is enforced through platform design and access controls, supporting use in regulated and multi-tenant environments while maintaining clear boundaries between customer datasets.
42 - Does Report Zero process personal data?
Report Zero is designed to work with operational infrastructure data. It does not require personal data to deliver its core functionality.
43 - How is access to data controlled?
Access to Report Zero is managed through role-based permissions, ensuring users only see the data and functions relevant to their role. Permissions are assigned deliberately rather than broadly, following the principle of least privilege.
This approach supports separation of duties between operational, sustainability and executive users, and helps organisations align access with internal security policies and governance requirements. Access controls can be reviewed and adjusted as roles or responsibilities change.
44 - Is data encrypted in transit and at rest?
Yes. Data handled by Report Zero is encrypted both in transit and at rest using industry-standard encryption mechanisms. This ensures data is protected as it moves between systems and while it is stored within the platform.
Encryption is applied as part of the platform’s baseline security design and supports use in regulated environments where protection of operational and environmental data is required under internal security and governance policies.
45 - Can Report Zero align with customer security policies?
Security controls and deployment models are designed to align with customer security, risk and compliance requirements.
46 - Where is data processed and stored?
Data processing and storage arrangements are agreed during onboarding and aligned to regulatory and customer requirements.
47 - How are security incidents handled?
Security incidents are managed through established incident management processes, including investigation, containment and communication where required.
48 - Can customers restrict or audit access?
Yes. Access controls and audit mechanisms can be configured to support customer governance requirements.
Still have a question?
Every organisation operates in a slightly different context, with its own mix of infrastructure, regulatory obligations and internal processes. Not every question fits neatly into a predefined list.
If you need clarification on a specific metric, integration, reporting requirement or deployment model, you can ask us directly or request a walkthrough tailored to your environment.