Question 1

What exactly does Gita 50001 do?

Accepted Answer

Gita 50001 collects energy consumption data from meters, bills and existing systems, calculates energy baselines and performance indicators, flags deviations from expected consumption patterns, and keeps the documentation needed for various ISO 50001 clauses — from energy review to internal audit and certification readiness — in one platform. It's built to replace scattered spreadsheets with a single, auditable source of data.

Question 2

Is this software only suitable for companies that already hold ISO 50001 certification?

Accepted Answer

No. Many organisations use Gita 50001 purely to manage energy consumption better, well before pursuing certification. The baseline, monitoring and report-builder modules work independently of the certification process. If you later decide to pursue certification, the required documentation already exists in the system, leaving little extra work for audit preparation.

Question 3

Does this software replace an energy consultant or auditor?

Accepted Answer

Not entirely. The software automates data collection, calculations and documentation, but decisions such as defining system boundaries, choosing the variables that affect consumption, or interpreting an unusual deviation still require engineering judgment. In practice, consultants and auditors spend less time gathering data and more time on analysis and decisions.

Question 4

Does implementing ISO 50001 guarantee energy savings?

Accepted Answer

No, the standard is a management framework, not a technical guarantee. Real savings depend on execution quality: whether significant energy uses are correctly identified, whether targets are realistic, and whether improvement actions are actually followed through. Continuous monitoring and deviation alerts improve the odds that results stick, but they don't replace organisational commitment to executing improvement plans.

Question 5

What if we don't have meters or a measurement system yet?

Accepted Answer

You can start with whatever data already exists — monthly bills, manual log sheets, or main incoming meters. Gita 50001's energy review module identifies which significant energy uses need more precise measurement first, so investment in metering is targeted and staged rather than blanket and unprioritised.

Question 6

How is Gita 50001 different from a BMS or SCADA system?

Accepted Answer

BMS and SCADA systems are built for real-time equipment control and monitoring, not for analysing energy performance over time. Gita 50001 can pull data from those systems, but what it adds is baseline calculation, normalising consumption against relevant variables, and turning raw data into indicators that management and auditors can actually report on.

Question 7

Can the software run on-premise, or is it cloud-only?

Accepted Answer

Both are supported. The cloud version suits faster deployment and automatic updates; the on-premise version is used where data must stay inside the local network, for example under the security policies of sensitive industries. The choice between the two is usually driven by the client's IT policy, not a technical limitation of the software.

Question 8

Which protocols and meter types are supported?

Accepted Answer

Common industrial protocols such as Modbus (RTU and TCP), OPC UA, and direct connections to SCADA databases are supported, along with manual entry and spreadsheet upload for sites that don't yet have smart meters. Proprietary protocols or older equipment are assessed and scoped case by case for integration.

Question 9

What happens when a meter has a data gap or an interruption?

Accepted Answer

The system automatically detects data gaps and flags them in reports so they aren't mistakenly treated as zero or valid consumption in EnPI calculations. Depending on the gap's length, the system either interpolates based on similar consumption patterns or excludes that period from the analysis dataset; the final decision is always visible and adjustable by the user.

Question 10

How is the EnPI regression model built and validated?

Accepted Answer

Variables that affect consumption, such as production output, degree-days or operating hours, are first tested against historical data, and one or more linear or multivariate regression models are built. Model quality is assessed using the coefficient of determination (R²) and the coefficient of variation of the root-mean-square error (CV(RMSE)) against common thresholds like ASHRAE's; the model chosen is the one with random, non-systematic residuals.

Question 11

How is the baseline updated after a significant change in the production process?

Accepted Answer

Changes such as adding a new production line, replacing major equipment, or changing product mix count as a 'static factor' and require re-baselining. The user logs the change in the system, a new period of post-change data is collected, and the regression model is rebuilt; the old baseline is archived for historical comparison rather than deleted.

Question 12

How much data volume is generated, and how long is it retained?

Accepted Answer

Real-time meter data is typically logged at 1 to 15-minute intervals and kept for short-term analysis, while daily and monthly aggregated data is archived for longer periods to keep the database manageable. The exact retention policy is set based on the number of measurement points and client requirements in the deployment agreement.

Question 13

How are user roles and audit trails managed?

Accepted Answer

Access is defined by role; for example, a site operator can only log data, an energy manager has full access to reports and analysis, and an internal auditor has read-only access to historical records. Every change to data, baselines, or target settings is logged with a timestamp, user, and previous value so it can be traced during an audit.

Question 14

Can it integrate with ERP, CMMS or Power BI?

Accepted Answer

Yes, a REST-based API can push consumption data, indicators and alerts to external systems such as ERP or Power BI, or pull production and maintenance data from a CMMS. For each integration, the data structure and update frequency are defined during the implementation phase.

Question 15

How long does a full implementation usually take?

Accepted Answer

For a single site with existing metering, it typically takes 4 to 8 weeks: initial configuration, connecting data sources, building the baseline, and training users. If new meters need to be installed or several systems need to be integrated, this can stretch to a few months. Multi-site rollouts are usually done in stages, site by site.

Question 16

What does the client need to provide during implementation?

Accepted Answer

Access to existing consumption data (bills or meter output), technical specifications of existing meters and systems for integration assessment, an internal technical point of contact for coordination, and, if available, any prior energy management documentation such as previously identified significant energy uses or targets.

Question 17

How many measurement points are enough to start?

Accepted Answer

The exact answer depends on the organisation's significant energy uses, but in practice you can start by measuring at the main electricity or gas intake and expand metering onto significant energy uses based on the energy review's findings. Starting with a small but accurate set of meters beats broad, unprioritised metering.

Question 18

What training is provided for users?

Accepted Answer

Training happens on two levels: operational users for data logging and daily monitoring, and energy managers for interpreting indicators, setting targets, and using the report builder. Training sessions come with user guides and ongoing Q&A support during the first weeks after go-live.

Question 19

How is a multi-site rollout managed?

Accepted Answer

Typically, one pilot site is fully implemented and validated first, then the configuration pattern is repeated for subsequent sites. The multi-site module enables performance comparison and benchmarking across sites from the start, even if sites go live at different times.

Question 20

How is historical data in spreadsheets migrated into the system?

Accepted Answer

Historical data is imported through standard spreadsheet upload templates; during import, automatic validation flags outliers and inconsistent units. Having at least 12 to 24 months of historical data allows the initial baseline to be built with greater statistical confidence.

Question 21

What is the pricing and licensing model?

Accepted Answer

Licensing is typically an annual subscription based on the number of sites, active measurement points, and selected modules, rather than the number of users. This lets small organisations start with one site and a few modules, then expand later without changing infrastructure.

Question 22

What does a demo session include?

Accepted Answer

The demo is a 45 to 60-minute session that walks through the modules relevant to your industry — such as baseline, monitoring, or the report builder — using sample data, and answers your team's technical questions. If you'd like, some of your organisation's real data can also be reviewed in a follow-up session.

Question 23

How are support and software updates handled?

Accepted Answer

Technical support is provided through tickets, email, and phone calls during business hours, and product updates are released periodically at no extra cost for active subscribers. Significant changes are communicated to clients before release so their audit or reporting schedule isn't disrupted.

Question 24

Who owns the data entered into the system?

Accepted Answer

All consumption data, baselines, and generated reports belong to the client organisation. In the cloud version, data is hosted on the infrastructure but can be fully exported at any time; in the on-premise version, data never leaves the organisation's internal network.

Question 25

Is the software multi-language?

Accepted Answer

Yes, the interface supports Persian and English, and depending on the deployment region — Iran, Türkiye, or Canada — adding an additional local language is assessed through the regional partner team and considered for the product roadmap.

Question 26

Can the software be deployed in all three group regions (Iran, Türkiye, Canada)?

Accepted Answer

Yes. Domestic deployment runs through Gita in Iran, regional delivery in Türkiye and neighbouring markets through Metachain, and North American support through Shan. The product core is identical across all three regions; the difference is only in the deployment team, local support, and language.

Technical answers to the questions energy and IT managers actually ask

General

Technical

Implementation

Commercial

Have another question?