Frequently asked questions
Entergaia builds two connected technologies: EntergaiaOS, our energy infrastructure intelligence platform, and long-range wireless charging for machines.
Here are the questions customers most often ask about what we do, how it works and how Entergaia fits into the infrastructure they already operate.
EntergaiaOS is an energy infrastructure intelligence platform.
It connects to the equipment and systems you already operate, brings their data together and helps you understand:
Instead of giving operators another screen full of alarms, EntergaiaOS is built to help answer a much more useful question:
What matters, why does it matter, and what should we look at next?
Most critical infrastructure already produces huge amounts of data.
The problem is that the data is often spread across different machines, vendors, control systems, dashboards and databases.
EntergaiaOS brings that information into one operational picture and turns it into useful intelligence about the physical infrastructure behind the business.
That can include generators, UPS systems, batteries, transformers, substations, switchgear, ATS systems, chillers, pumps, compressors, telecom power systems and other critical assets.
EntergaiaOS is an operating platform for physical and energy infrastructure.
It does not replace Windows, Linux, PLC firmware or the control system inside a machine. Those systems continue doing their jobs.
EntergaiaOS sits above them and provides a common intelligence layer for connecting assets, understanding their condition, modelling dependencies, managing evidence and presenting operational decisions across sites and fleets.
Critical infrastructure is full of information but often short of answers.
A generator may have its own controller. A UPS has another monitoring system. A transformer has another. The building has a BMS. The site has SCADA. Historical information is somewhere else.
Each system may know about its own equipment.
EntergaiaOS is built to understand the system around the equipment. That means moving from:
UPS 3 has an alarm.
to:
UPS 3 is deteriorating, it supports this critical load, the available resilience has changed, and this is the evidence behind the finding.
EntergaiaOS is designed to go beyond displaying measurements and alarms.
It combines the data with knowledge of the physical equipment and the relationships between assets. That allows the platform to ask questions such as:
The result is intelligence that is tied back to the infrastructure itself rather than an unexplained score.
Yes, where it is useful — but EntergaiaOS is not built around asking AI to guess what is happening to critical equipment.
The platform combines engineering models, statistical analysis, system relationships, operational evidence and machine reasoning.
AI can help operators interact with and understand that information, but important conclusions are designed to remain connected to the underlying evidence.
Yes. Explainability is a core part of the product.
A customer should be able to see what changed, why the platform considers it important, which asset is involved, what may be affected and the evidence associated with the finding.
We do not want customers to have to accept:
The AI says this machine is risky.
The objective is to provide an operational conclusion that people can examine and challenge.
It should say so.
Critical infrastructure is not the place for software to silently invent missing engineering information.
Where an assessment depends on information that is unavailable, EntergaiaOS can identify the missing evidence rather than present an unsupported conclusion.
That may mean asking for an equipment rating, commissioning baseline, runtime measurement, load measurement or another relevant input.
Knowing when there is not enough evidence is part of the intelligence.
EntergaiaOS is designed around critical physical infrastructure, including assets such as:
The exact assets available at a site determine which forms of intelligence EntergaiaOS can provide.
No.
Vendor neutrality is an important part of the EntergaiaOS proposition.
A site may contain equipment from several manufacturers and several generations of technology.
EntergaiaOS is designed to work above those individual systems so that customers can understand the infrastructure as a whole rather than being limited to one manufacturer’s product family.
No.
EntergaiaOS is specifically designed to work with infrastructure customers already own. It is not a rip-and-replace product.
Entergaia adds an intelligence layer above them.
Not necessarily.
Many organisations already collect far more operational data than they currently use effectively.
Entergaia normally starts by understanding what data is already available.
Additional instrumentation may be useful where important information is missing, but installing new sensors everywhere is not a requirement for getting started.
The standard approach is Entergaia Connect.
Entergaia Connect is lightweight software that runs inside the customer’s environment and reads approved data from existing systems. It then sends permitted information securely to EntergaiaOS.
The objective is simple:
Use the data you already collect before asking you to install anything else.
Entergaia Connect is the bridge between customer infrastructure and EntergaiaOS.
It can run on a server the customer already owns.
Its role is to connect approved operational data sources, organise the information for EntergaiaOS and maintain the secure outbound relationship with the platform.
For many customers, no new Entergaia hardware is required to get started.
Normally inside the customer’s own network, close to the systems containing the operational data. For example:
Equipment → SCADA / Historian → Entergaia Connect → EntergaiaOS
or:
Equipment → MQTT / OPC UA / database → Entergaia Connect → EntergaiaOS
The exact architecture is agreed with the customer’s IT, OT and security teams.
The standard Connect deployment is designed around an outbound connection from the customer’s environment.
That means the customer does not normally need to expose industrial equipment directly to the public internet or create an inbound route for Entergaia to control equipment.
Entergaia Connect supports common industrial and enterprise data interfaces including:
The best connection route depends on what the customer already operates.
SCADA stands for Supervisory Control and Data Acquisition.
It is commonly used to monitor and supervise industrial equipment and processes.
EntergaiaOS does not try to replace SCADA.
Instead, where appropriate, Entergaia can use information already available through SCADA or the systems behind it and add a higher level of infrastructure intelligence.
A historian is a system used to store operational measurements over time.
It may contain months or years of information about temperatures, loads, pressures, fuel levels, equipment states, alarms and other measurements.
Historical data can be extremely valuable because Entergaia can use it to understand how equipment behaved before the platform was connected live.
Yes. This is one of the easiest ways to start an Entergaia engagement.
A customer can provide an approved historical export — commonly a CSV or historian extract — and Entergaia can analyse the available operating history before any permanent live connection is introduced.
This can help both sides understand the available data, identify gaps and demonstrate the value of the platform with very little disruption to the customer’s environment.
That is normal.
Industrial environments rarely use one universal naming convention.
EntergaiaOS is designed to organise customer-specific names and measurements into a consistent view of assets and operational information.
Where something is ambiguous, it can be confirmed during commissioning rather than guessed.
That can make deployment even simpler.
Where a customer already centralises data from many sites into an approved historian, MQTT platform, database or other system, Entergaia may be able to connect at that aggregation point rather than installing software at every individual site.
The right architecture depends on the customer’s network, security and operational requirements.
Through a secure web browser.
Customers sign in to the EntergaiaOS Client Console and access the sites, assets, findings and evidence they are authorised to see.
No specialist desktop application is required for normal use.
No.
The cloud service is designed as a multi-tenant platform with customer and site access separated by permissions.
A user should only see the organisation, sites and information they are authorised to access.
Dedicated deployment architectures can also be discussed where customer security, sovereignty or isolation requirements demand them.
Depending on the customer’s deployment and available data, the platform can provide views across areas such as:
The objective is to move from thousands of individual data points to a manageable view of what matters.
It is a representation of how assets depend on one another.
Knowing that a machine has a problem is useful.
Knowing what else stops working if that machine becomes unavailable is far more useful.
EntergaiaOS can represent relationships between sources, equipment and downstream services so operators can understand consequences rather than looking at assets in isolation.
Where the required infrastructure relationships and evidence are available, EntergaiaOS can help identify assets or dependencies whose loss may create significant downstream consequences.
These findings should be confirmed against the customer’s engineering documentation and site knowledge.
EntergaiaOS can translate engineering scenarios into business exposure using customer-provided commercial information or clearly identified planning assumptions.
This helps connect infrastructure condition to questions executives care about:
The platform does not present an assumption as a known financial fact.
No.
EntergaiaOS is designed to strengthen engineering and operational decision-making, not replace qualified people.
It helps teams see more, connect information faster, preserve evidence and prioritise attention.
Safety-critical decisions, authorised engineering decisions and statutory responsibilities remain with the appropriate people and organisations.
No.
EntergaiaOS can help collect, organise and present evidence relevant to engineering, audit and compliance reviews.
It does not replace a regulator, competent person, Authorising Engineer or other authorised professional, and it does not turn software output into automatic certification.
The production posture is read-only.
EntergaiaOS observes, analyses and explains.
It is not positioned as an autonomous controller of safety-critical infrastructure.
That separation is deliberate.
Because customers can gain intelligence without giving an external analytics platform authority to start, stop, switch or energise critical equipment.
It reduces deployment risk and allows EntergaiaOS to sit alongside established operational and safety systems rather than replacing them.
Access is based on authenticated users, organisations, sites and permissions.
Customer deployments also use controlled device enrolment and auditable activity records.
Specific security and network architecture can be reviewed with customer IT, OT and security teams during deployment.
Entergaia Connect is designed to tolerate temporary connectivity interruptions by retaining data locally and forwarding it when the connection is available again.
For environments with additional offline, sovereignty or local-processing requirements, alternative deployment architectures can be discussed.
EntergaiaOS is currently packaged around seven major critical-infrastructure sectors:
The same core platform sits underneath them.
What changes by sector is the equipment, operating context and the questions customers need answered.
EntergaiaOS can bring together critical-power assets such as utility supplies, generators, UPS systems, batteries, transformers, ATS systems, switchgear and critical loads.
The aim is to help operators understand not only whether an individual asset is healthy, but what that condition means for the resilience of the wider power chain.
Telecom sites combine grid supply, generators, batteries, rectifiers, fuel and increasingly hybrid energy systems across large distributed fleets.
EntergaiaOS can help operators understand site energy, generator readiness, battery condition, abnormal fuel behaviour and the issues that deserve attention across the fleet.
EntergaiaOS can bring operational data around transformers and associated infrastructure into a common view of loading, condition, ageing, dependencies and emerging operational exposure.
The objective is to help asset teams make better-informed maintenance and investment decisions.
Mines depend on electrical infrastructure to support much more than production.
Power may ultimately support pumping, dewatering, ventilation and other critical services.
EntergaiaOS helps connect equipment condition to those wider operational dependencies so the importance of a problem can be understood in context.
Industrial sites often rely on combinations of generators, UPS systems, batteries, transformers, switchgear, pumps, motors and other standby or production equipment.
EntergaiaOS helps bring those assets into one operational intelligence environment and identify issues before hidden weakness becomes operational disruption.
EntergaiaOS provides a common platform for bringing together operational measurements, equipment state, power infrastructure and supporting evidence across distributed pipeline and terminal assets.
The platform is designed to help operators move from fragmented information toward a clearer view of asset condition, change and operational consequence.
Ports are increasingly dependent on complex electrical infrastructure supporting cranes, reefers, shore power, substations, charging and terminal operations.
EntergaiaOS helps bring those assets and their operational data into a common infrastructure view so teams can understand condition, loading and emerging constraints more clearly.
Entergaia is building long-range wireless charging for machines.
The objective is to deliver energy where running a cable, repeatedly replacing batteries or manually connecting equipment creates unnecessary cost or operational limitation.
The initial opportunity includes industrial sensing, monitoring, instrumentation and other machine applications where access to power is itself the constraint.
No.
Conventional consumer wireless charging normally works across very short distances.
Entergaia is addressing applications where power needs to reach equipment across meaningful working distances and where traditional cabling or repeated battery maintenance creates a real operational problem.
The exact wireless technology, configuration and deployment are determined by the application.
The strongest opportunities are machines and devices for which power access is difficult, expensive or maintenance-intensive. Examples include:
Each application is assessed according to its energy requirement, environment, safety requirements and operating conditions.
EntergaiaOS is the operating intelligence backbone.
Wireless charging provides the energy relationship.
EntergaiaOS provides the digital relationship around it — including the identity of the machine, its condition, the energy session, operational information, metering and evidence.
That creates something more valuable than a wireless charger alone:
Energy and intelligence around the machine in one system.
No.
EntergaiaOS is designed to deliver value on the infrastructure customers operate today — grid power, generators, UPS systems, batteries, transformers and conventional electrical systems.
Wireless charging extends the Entergaia platform into new ways of delivering energy to machines.
One does not have to wait for the other.
No.
No software platform should be the final safety authority for energy delivery.
Entergaia’s architecture keeps final safety authority in the appropriate local hardware and safety systems.
EntergaiaOS provides orchestration, identity, monitoring, evidence and intelligence around the energy relationship.
No.
Energy delivery and data communications are separate engineering problems.
A machine may receive energy through one technology while communicating through an existing network such as Ethernet, Wi-Fi, cellular, private wireless or another approved communications system.
EntergaiaOS brings the two relationships together at the intelligence layer.
The simplest first step is usually to understand the infrastructure and data you already have.
That can begin with historical operating data before any live connection is introduced.
From there, a standard deployment can use Entergaia Connect on an existing customer server to establish the live data relationship.
The process is designed to minimise disruption to operational systems.
No.
Entergaia Connect can run as software on existing customer infrastructure.
Other local, virtual or dedicated deployment architectures can be discussed where the customer requires additional isolation, offline operation or specific infrastructure arrangements.
Yes.
The same platform is designed to work from an individual facility through to organisations operating many sites.
A local team may care about one generator or UPS.
A fleet operator may care about which 20 assets across 5,000 sites deserve attention first.
EntergaiaOS is designed to support both perspectives.
The production architecture supports secure cloud deployment together with customer-site Entergaia Connect components.
Google Cloud is the primary cloud platform for the Entergaia production deployment.
Customer-specific requirements around data location, network architecture, security and deployment model are agreed during onboarding.
Customer environments vary.
Where security, sovereignty, network isolation or operational requirements call for a different architecture, local or virtual deployment options can be scoped with the customer.
The objective is to fit Entergaia into the customer’s infrastructure rather than force every customer into the same topology.
It depends mainly on the quality and accessibility of the existing data, the number of sites and the complexity of the infrastructure.
A historical-data assessment can begin before a permanent live deployment.
The standard Connect architecture is deliberately lightweight so live deployments can use customer infrastructure that is already available rather than beginning with a new hardware installation programme.
Usually:
We then determine the most appropriate way to connect and what can be assessed from the available evidence.
That is useful information in itself.
EntergaiaOS assesses the information it receives and can separate instrumentation problems from equipment-condition concerns.
If a sensor is unreliable, stuck or incomplete, the platform should identify that limitation rather than treat bad data as a genuine machine event.
Commercial arrangements depend on the number of sites, assets, data sources, deployment architecture and the scope of intelligence required.
For larger estates, fleet-wide deployments and specialist infrastructure, we structure the commercial model around the scale and value of the deployment.
Contact Entergaia to discuss your infrastructure and the problem you want to solve.
Yes.
We can demonstrate the platform and discuss an assessment using your infrastructure context or approved historical data.
The objective is to show how EntergaiaOS would work against a real operational problem rather than ask customers to buy from a generic presentation.
Still have a question?
Whether you operate one critical facility or thousands of distributed assets, tell us what infrastructure you run, what data you already have and what problem you are trying to solve.
