Home/ Platform/ ElecTwin®
Field capture  ·  Electrical network twin  ·  ElecTwin®

The study is the easy part.
Getting the data is not.

ElecTwin® replaces the clipboard. Your survey team captures every nameplate, setting, cable run and panel on a tablet, against templates built for power system modelling, with photographs attached and each asset tagged where it stands. It works with no network at all · substation basements included · and publishes a structured model that ETAP, SKM, CYME and EasyPower take straight in.

Enquire now Get the Android app
Fully offline capture
Modelling-grade templates
Exports a model, not a PDF
// CAPTURING · PCC-01 / FDR-07
ACB · 630A · LSI
// NETWORK
OFFLINE · queued 214
// FIELDS COMPLETE
18 / 18  ·  PHOTO ✓
0 bars
Network needed to survey a substation basement
1 pass
Captured, photographed and validated where it stands
0
Re-typing from a notepad into a spreadsheet
ETAP
SKM · CYME · EasyPower · as a model, not a report
In 30 seconds

What ElecTwin® does.

Every power system study · arc flash, short circuit, load flow, protection coordination · begins with someone walking a plant and writing on paper. That walk is where the schedule slips, where the errors enter, and where the cost actually sits. ElecTwin is built for that walk and for what happens to the data afterwards.

// 01

Captures in the field

Templates per equipment class, built from what a power system model actually needs rather than a generic inspection checklist. Photograph, tag, GPS stamp and validate at the panel, on a tablet, with no signal.

// 02

Validates before it leaves site

A missing %Z, a transformer with no secondary voltage, a feeder with no parent bus · flagged while the engineer is still standing in front of the panel, not three weeks later when the model will not converge.

// 03

Publishes a model, not a report

A structured, connected electrical network that ETAP, SKM, CYME and EasyPower ingest directly. And it stays alive afterwards, so the next survey is a delta rather than a repeat of the whole exercise.

The real bottleneck

Nobody's study is late
because of the maths.

Data collection and modelling routinely take more effort than the study itself.

This is not our opinion, it is the consensus of the people who sell these studies. Published industry guidance puts field data collection and scheduling at one to two weeks, engineering and modelling at one to two weeks, and the report and labels at three to five days · then adds another one to two weeks of slippage caused by out-of-date diagrams, missing breaker settings and equipment nobody can get into. The calculation is the fastest part of the whole project.

Drawn from published arc flash study guidance from independent engineering practices, 2026.
// Failure 01

The notepad to spreadsheet gap

Data is written by hand at the panel, then typed into a spreadsheet days later by someone who was not there. Every transposed digit survives all the way into the incident energy result, and nothing downstream will catch it.

// Failure 02

The unreadable nameplate

Faded, painted over, or facing a wall with 200 mm of clearance. The engineer writes “check later”, and later never comes. The bus gets a default value and nobody records that it was a default.

// Failure 03

The second site visit

The model will not converge, three fields are missing, and the plant is four hundred kilometres away with a shutdown window that closed last Tuesday. This single event is the most common reason a study slips a month.

The pattern behind all three is the same. The data is validated at the wrong time, in the wrong place, by the wrong person. ElecTwin moves validation to the moment and place of capture, which is the only point at which a gap is cheap to close.

Have a survey coming up?

Tell us the site, the approximate bus count and which package the model has to land in. We will tell you what the capture would look like and how many field days it should take.

Enquire now
Capture templates

Built from what the model needs.
Not from a checklist app.

This is the difference between ElecTwin and a generic forms tool. Fifteen component classes, each carrying exactly the fields a power system study consumes, in the order an engineer actually reads a panel, with the mandatory ones enforced before the record can be closed.

Equipment classCaptured fieldsEnforced before close
Utilityincomer / grid tie Voltage, fault level or short-circuit MVA, X/R ratio, feeder arrangement, utility reference, protection at the point of supply. fault level · voltage
GeneratorDG, standby, parallel Rating, voltage, subtransient reactance, earthing, changeover arrangement and interlock, run mode · standby, parallel or island. rating · reactance · changeover
Busthe connectivity spine Designation, voltage, bus rating, short-circuit bracing, incomer source, every outgoing feeder with its device and destination, panel condition and working clearance. designation · source · feeder list
Bus ductits own class, deliberately Type, rating, material, length, routing, from-bus and to-bus, enclosure and support arrangement. rating · length · both ends
Transformerpower & distribution kVA rating, primary and secondary voltage, percent impedance, tap position and range, vector group, winding configuration, neutral earthing method, cooling class, temperature rise, make and serial. kVA · %Z · both voltages · vector group
Cablethe field's least favourite Conductors per phase, size, material (copper or aluminium), insulation, length, installation method, raceway type and size, from-bus and to-bus. size · material · length · both ends
FuseHRC and switch-fuse Type and class, ampere rating, switch rating, short-circuit rating, manufacturer curve reference. class · rating
Contactorstarters and feeders Make, type, rating, utilisation category, coil voltage, associated overload relay and its setting. rating · overload setting
HV circuit breakerVCB, SF6 Make, type, rated current, interrupting rating, operating mechanism, associated CTs, and the protection relay that drives it. rated current · interrupting rating · relay
LV circuit breakerACB, MCCB Make, type, frame size, sensor or plug rating, trip unit type, long-time pickup and delay, short-time pickup and delay, instantaneous setting, ground fault setting, interrupting rating, and a photograph of the dial or display. frame · trip unit · every set point
Switchisolator, changeover Type, rating, short-circuit withstand, interlocking, normal operating position. rating · normal position
Relaynumerical or electro-mech Make and model, CT and PT ratios, characteristic curve, pickup, time multiplier, every enabled function and its setting, relay setting sheet photographed as found. CT / PT ratio · curve · pickup · TMS
Motorand drive kW or HP, voltage, full-load current, power factor, starting method, direct-on-line or through a VFD, locked-rotor contribution, driven equipment and criticality. rating · voltage · starting method
Loadlumped and static Connected and demand load, voltage, power factor, load type, diversity, and the feeder it hangs from. load · voltage · parent feeder
CapacitorAPFC banks, often missed kVAr per step, number of steps, switching device, detuning reactor, controller make and setting. kVAr · steps

Fifteen component types, and a count against each one.

This is the capture screen as the surveyor sees it. Utility, generator, bus, bus duct, transformer, cable, fuse, contactor, HV and LV circuit breaker, switch, relay, motor, load and capacitor · each with a live count of what has been captured and what state it is in.

Note that HV and LV breakers are separate classes, that bus duct is its own type, and that contactor sits beside fuse. That granularity is not cosmetic · it is what stops a surveyor forcing a component into the wrong template and producing a model that will not grade.

Counts update as the team works. A survey manager opening this screen can see the shape of the capture without asking anyone for a status.

ElecTwin app capture screen listing utility, generator, bus, bus duct, transformer, cable, fuse, contactor, HV and LV circuit breaker, switch, relay, motor, load and capacitor with captured counts
// Select component · live capture counts

Templates are configurable per project, because a distribution utility survey and a chemical plant survey do not want the same fields. What is not configurable is that a mandatory field cannot be skipped silently · it is either filled, or it is recorded as a declared gap with a reason and a photograph, which is a very different thing from a blank cell in a spreadsheet.

Offline first

A substation basement
has no signal. Ever.

This is not a degraded mode or a sync-later compromise. The app is built to run an entire survey campaign with the device in flight mode, because that is the normal condition of the places this work happens: LT rooms below grade, switchyards inside steel structures, plants that do not permit a cellular device on the floor at all.

// In the field

Everything works, unplugged

Templates, validation, the growing single-line, search across what the team has already captured, photographs at full resolution. None of it asks for a network.

  • Full multi-day campaign with no connectivity
  • Validation runs locally, at the panel
  • Photographs held at capture resolution
  • Device battery is the only real constraint
// Back at the guest house

Publishes when it finds a connection

The queue uploads in order over whatever it gets · hotel wifi, a phone hotspot, the site office in the morning. Interrupted uploads resume rather than restart.

  • Resumable, ordered upload
  • Photographs uploaded after data, so the model is usable first
  • Nothing is deleted from the device until the server confirms it
// Across the team

Several surveyors, one model

Three engineers can work three areas of the same plant on three tablets. Each holds its own portion, and the merge happens server-side against the asset hierarchy rather than by someone reconciling spreadsheets on a Sunday.

  • Area or feeder assignment per surveyor
  • Conflicts surfaced, never silently overwritten
  • Live progress against the planned asset count
Get the app

It is on Google Play.
Put it on a tablet and try it.

Collect field data, online and offline, anytime and anywhere.

That is the app's own description, and it is the whole product in one line. Install it on any Android tablet or phone your survey team already carries, sign in, and capture against your templates · in a switchyard, in a basement LT room, in a plant that does not allow a connected device on the floor.

There is nothing to procure and no hardware to specify. The devices your engineers are holding today are the devices this runs on.

  • // Platform
    Android phone or tablet
  • // Publisher
    Vijaya Bhanu Digital Transformations
  • // Category
    Business · field data capture
  • // Works
    Fully offline, syncs when it can
Get it on Google Play Enquire now

Downloading it is free and tells you in ten minutes whether the capture flow suits how your engineers actually work. Templates are configured per project, so what you see on a first install is the standard set rather than yours · tell us your conventions and we will shape it to them.

// Scan on site
Point a camera at this and the app opens on Google Play. Useful when you are standing in the panel room rather than at a desk.
Download onGoogle Play
Capture status

Six states, and one of them
is the whole argument.

Every component carries a state from the moment it is captured to the moment it is signed off. This is what separates a survey tool from a forms app: the data has a lifecycle, a reviewer, and a way back when something is wrong.

In progress

Saved locally on the device and waiting to be submitted. Editable by the surveyor until it goes up.

This is the offline state · a full day's capture can sit here with no network and nothing at risk.

Source component required

Saved without its source component selected. Still editable, but flagged as incomplete until the source is set.

The state that proves this is a network, not a list · a component with no source is an orphan, and the app will not let it pass quietly.

Submitted

Sent up and awaiting approval. The surveyor can no longer change it; the reviewer can see it.

The handover point between the field and the engineer, timestamped rather than remembered.

Approved

Accepted by the reviewer. Locked from editing, open for viewing. This is data the model can be built on.

Your model is assembled only from approved records, so nothing unreviewed reaches a study.

Re-survey

Sent back. The reviewer has flagged something that has to be looked at again, with the reason on the component.

The second-site-visit problem, handled while the team is still on site rather than three weeks later.

Submitted by others

Captured by a different surveyor on the same project. Visible to you, and selectable as the source component for what you are capturing.

How three engineers in three areas build one connected network instead of three disconnected spreadsheets.

The red state is the one worth dwelling on. Every other survey method discovers a bad record when the model refuses to converge, by which point the plant is four hundred kilometres away and the shutdown window has closed. A re-survey flag raised the same week costs an hour.

See the workflow on your own site.

One substation, your templates, your reviewer in the approval seat. You will know within a day whether the states match how your team actually signs work off.

Enquire now
Evidence, not recollection

Every record carries
the photograph it came from.

A number typed into a spreadsheet is an assertion. A number with the nameplate it was read from attached is evidence · and six months later, when the model disagrees with the plant, that is the difference between an argument and a two-minute check.

// Capture

Photograph bound to the field

Nameplate, relay setting sheet, breaker dial, panel front, cable marking. Each image is attached to the specific asset and the specific field it evidences, not dumped into a folder named after the site.

// Unreadable nameplate

The honest path, made easy

Where the plate is faded, painted or inaccessible, the surveyor records what is legible, photographs it, and marks the remainder as a declared gap with a reason. The gap travels into the model as a flagged assumption rather than a silent default.

// Back office

Verified without a site visit

The engineer building the model opens the photograph beside the field. Most queries that would have triggered a phone call, or a second trip, are settled from the desk.

Interoperability

It leaves as a model.
Your software takes it from there.

ElecTwin does not compete with your analysis package and does not ask you to change it. It solves the step before it · producing a clean, connected, validated network that the package can ingest without a week of manual entry.

ETAP

Structured export for the Excel and Access data interface, which ETAP imports with any layout and field naming, runs consistency checks on, and can use to generate the one-line automatically.

SKM PowerTools

Component and connectivity export shaped for the import path, so buses, branches and device settings land as objects rather than as a document to re-key.

CYME

Network and equipment export for distribution and industrial models, with the source and feeder topology preserved.

EasyPower

Equipment schedules and connectivity in the structure the model builder expects.

Open formats

Excel, CSV and JSON against a published schema, plus a REST API. If your team has its own toolchain, it reads the same data we do.

Documents out

Equipment schedules, cable schedules, the asset register and a survey report pack · generated, not retyped.

Excel / Access interfaceCSVJSON schemaREST APIEquipment schedule Cable scheduleAsset registerPhotograph archiveDeclared gap report

Where a package offers no documented import route for a given object type, we say so rather than implying a connector exists. The honest position is that ElecTwin removes the data collection and data entry burden from your study, and the last mile into any given package is scoped openly at proposal stage.

Tell us which package you model in.

ETAP, SKM, CYME, EasyPower or something in-house · we will show you exactly what lands in it and what still needs an engineer's hand.

Enquire now
Where it stops being a survey tool

The survey ends.
The model should not.

Most electrical data collection is treated as a one-off cost against a one-off study. Three years later the study is stale, nobody trusts the single-line, and the whole exercise is repeated at full price. That is the cycle this module exists to break.

A survey is a photograph. A twin is a record that stays true.

Once captured, the electrical network lives as a structured asset model · every device, every setting, every connection, with its evidence attached. When a transformer is replaced, a relay is re-set or a feeder is added, that single change is updated rather than the plant being re-walked. The next study starts from a current model, and the re-survey scope is the delta, not the site.

// Consequence 01

The second study costs a fraction

Because the expensive half of it is already done, and done to a standard you can audit. This is the argument that makes the first capture pay for itself.

// Consequence 02

Change control becomes possible

An electrical modification that alters fault level or protection grading is flagged against the model at the time it happens, instead of being discovered at the next audit.

// Consequence 03

It joins the rest of the plant

The electrical network resolves against the same asset register as the machines, so a motor is one asset with both a mechanical and an electrical identity rather than two records in two departments.

Who uses it

Three buyers, one bottleneck.

Buyer 01

Consultants & EPCs

Practices selling arc flash, protection coordination and load flow studies, where field data collection is the least profitable and most schedule-destroying part of every engagement.

The commercial case is direct: fewer field days, no data entry phase, and almost no second site visits · on work you are already winning.
Buyer 02

Plant electrical & EHS heads

Multi-plant Indian manufacturers whose single-lines are out of date, whose last study is years old, and who are asked for electrical safety evidence during customer and statutory audits.

You end up owning a current electrical asset register and a model you can hand to any consultant, instead of renting both every few years.
Buyer 03

Utilities & distribution

Network operators and distribution licensees running asset surveys across substations and feeders, where the field teams are large, geographically spread and working well outside network coverage.

Capture is consistent across every team, every district and every shift, and progress is visible centrally while the survey is still running.
How it works

Four steps. Panel to model.

A single-plant capture typically runs a fortnight end to end, most of which is the field days themselves. Nothing here requires a shutdown that the survey would not have needed anyway.

// 01 · CONFIGURE

Templates set to the project.

Equipment classes, mandatory fields, the naming convention and the target package are agreed before anyone goes to site. Half a day, done remotely.

// 02 · CAPTURE

The team walks the plant.

Tablets, offline, area by area. Each asset captured, photographed, connected to its parent and validated at the panel. Progress visible centrally whenever a device finds a connection.

// 03 · RESOLVE

Merge, check, close gaps.

Records from every surveyor merge against the hierarchy. Conflicts and declared gaps are listed for decision, and anything needing a second look is identified while the team is still on site.

// 04 · PUBLISH

Out to your package.

The connected network exports to ETAP, SKM, CYME, EasyPower or open formats, along with the equipment schedules, cable schedules and photograph archive. The model then stays live for the next change.

Where you start

Prove it on one substation
before you commit a campaign.

Nobody should roll this out across a group on the strength of a demonstration. Every entry point below ends with something real in your hands.

Option 01 · smallest possible test

One substation, one day

We configure the templates to your conventions and capture a single substation or one MCC room with your engineer alongside ours.

You get the captured data, the photographs and the export into your own package, within about a week, and you judge it against what your team would have produced.
Option 02 · the usual entry

One plant, fully captured

The complete electrical network of a single plant, from the incomer to the last distribution board, delivered as a model and an asset register.

Typically a fortnight end to end, ending with a model your consultant can study against immediately and a register you keep.
Option 03 · for practices

Licence it to your own teams

For consultants and EPCs who want their own engineers capturing with it on their own projects, under their own templates and branding.

Your surveyors keep doing the work. They simply stop losing a week to data entry on every job.
Pairs with

What the electrical twin feeds.

Identity

AssetTwin™

The register the electrical network resolves against, so a motor carries one identity across both the mechanical and the electrical world.

→
Signal

ConnecTwin™

Where the static model meets live measurement · the captured network becomes the map that incoming energy and load readings resolve onto.

→
Energy

VolTwin™

Consumption by feeder, machine and shift against the state tariff, structured by the distribution network ElecTwin captured.

→
Compliance

TrusTwin™

Evidence packs with provenance for statutory and customer audits, including the electrical safety records that come out of the study.

→
Inspection

InspectWin™

The same field-capture discipline applied to routine inspection rounds once the register exists.

→
Programme

Smart Factory

The wider programme this sits inside, for plants taking the whole journey rather than a single survey.

→
Questions we get asked

Straight answers,
including the unflattering ones.

These are the questions electrical consultants, plant engineers and survey managers actually put to us. Where the honest answer is “no”, it says so.

Longer than the study, which is the part most people get wrong when they plan it. Published industry guidance puts data collection and scheduling at one to two weeks, the field survey itself at one to three days for a small site and several days for a large industrial plant, engineering and modelling at one to two weeks for a fifty to one-fifty bus system, and the report and labels at three to five days. A further one to two weeks of slippage is common, and it comes from out-of-date drawings, missing breaker settings and equipment nobody can open. Set against all of that, running the numbers is the quick bit. Tell us your bus count and we will estimate the field days for your site specifically.
The app organises it into fifteen component classes · utility, generator, bus, bus duct, transformer, cable, fuse, contactor, HV circuit breaker, LV circuit breaker, switch, relay, motor, load and capacitor. By class: Utility: voltage, fault level or short-circuit MVA, X/R ratio. Transformers: kVA, both voltages, percent impedance, tap position, vector group, winding configuration, neutral earthing. Cables: conductors per phase, size, material, length, installation method, and both end connections. Breakers: frame size, sensor rating, trip unit type and every set point · long-time, short-time, instantaneous, ground fault · plus interrupting rating. Fuses: class, ampere and short-circuit rating. Relays: CT and PT ratios, curve, pickup, time multiplier. Motors: rating, voltage, starting method, drive or direct-on-line. Buses and panels: designation, rating, source and the full outgoing feeder list. Ask for the template set and you can see every field before you commit to anything.
Yes, and it is designed for that to be the normal case rather than the exception. Templates, validation, search, the growing single-line and full-resolution photographs all run on the device with no connection. An entire multi-day campaign can be completed in flight mode. The upload queue publishes in order whenever the device finds any connection · site office, hotel wifi, a phone hotspot · and resumes rather than restarts if it is interrupted. Nothing is removed from the device until the server confirms receipt. Test it on one substation before you trust it with a campaign.
Through a structured export shaped for ETAP's Excel and Access data interface, which imports from a spreadsheet with any layout and field naming, runs consistency checks during exchange, can substitute library defaults where data is genuinely absent, and can generate the one-line diagram automatically from the connectivity. The point is that the data arrives as connected objects rather than as a document somebody keys in. Send us a sample of your current data format and we will show you what the same information looks like coming out of a capture.
Yes, through each package's documented import route, plus Excel, CSV and JSON against a published schema and a REST API for teams with their own toolchain. One honest caveat: import coverage differs by package and by object type, and no vendor's import path is complete for every device class. Where a route does not exist for something, we say so at proposal stage instead of implying a connector. What does not change is that the collection and data-entry burden is removed either way. Tell us which package you model in and we will be specific about what lands and what does not.
It is recorded as a declared gap, not filled with a guess. The surveyor captures whatever is legible, photographs the plate as found, and marks the remaining fields with a reason · painted over, faded, obstructed, inaccessible without a shutdown. That gap travels into the model as a flagged assumption. This matters more than it sounds: the dangerous outcome is not a missing value, it is a default value that nobody remembers was a default, sitting inside an incident energy result that someone will size PPE against. Ask to see a declared gap report from a real capture.
By removing the transcription step entirely. In the conventional method the data is written on paper at the panel and typed into a spreadsheet days later by someone who was not present, and any transposed digit survives untouched into the final result because nothing downstream can catch it. Capturing directly into structured fields, with validation running at the panel and the nameplate photograph attached to the record, means the error is caught by the person standing in front of the equipment · the only point at which fixing it is free. Run it against one panel room and compare the output to your current method.
Yes. Areas or feeder groups are assigned per surveyor, each device holds its own portion offline, and the merge happens server-side against the asset hierarchy. Conflicts are surfaced for a decision rather than silently overwritten, and progress against the planned asset count is visible centrally while the survey is still running · which is usually the first time a survey manager can see how a campaign is actually tracking instead of finding out at the end. Tell us your team size and site spread and we will size the campaign with you.
It is the normal starting condition, and it is an argument for capturing rather than against it. Most plants have an as-built that stopped being true after the second modification nobody drew. The capture builds connectivity from what is physically there · source, bus, feeder, destination · so the single-line comes out of the survey rather than being a prerequisite for it. If you do have drawings they speed up planning and give us something to reconcile against, and the reconciliation itself usually has value independent of the study. Send whatever drawings you have, however old, and we will tell you how much of the survey they shorten.
No, and it is a fair question given how many generic inspection apps are sold into this space. A forms app collects a record. This collects a connected network · every device knows its parent bus, its source and its downstream feeders, which is what makes the output a model rather than a list. The validation rules encode what a power system study needs, so a transformer without a percent impedance or a feeder without a parent cannot be closed. And the output is an importable network, not a PDF of a filled form. Put it side by side with whatever you are using on one panel room and the difference shows in an afternoon.
Either. We run captures with our own engineers where a plant has no spare electrical resource, which is the common case in Indian manufacturing. We also licence it to consultants and EPCs who want their own surveyors using it under their own templates and branding, because for a practice the value is not in outsourcing the walk · it is in never losing a week to data entry afterwards. Plant teams who want to own the capability run it themselves after a short configuration and training pass. Say which of the three you are and we will quote only that.
You do, and yes, in full. The complete capture · every field, every photograph, every declared gap and the connectivity between assets · exports to Excel, CSV and JSON against a published schema, with a REST API behind it. For a consultant this matters commercially: the data you collect on a client's site remains yours to deliver to that client. We would rather be kept because the capture is better than because the export is difficult. Ask for the export schema before you commit, and apply that test to every vendor you are weighing up.
Yes, and it is one of the better fits. Distribution surveys have exactly the conditions the app is built for: large field teams, wide geography, long stretches with no coverage, and a need for every team in every district to capture the same way. Feeder topology, pole and substation assets, and equipment schedules are captured against configurable templates, with central visibility of progress across districts while the campaign runs. Tell us the scale and the geography and we will size the team and the timeline.
That is the whole argument for doing the capture properly rather than as a throwaway. A survey is a photograph of one day; the captured network is kept as a structured asset model with its evidence attached. When a transformer is replaced, a relay re-set or a feeder added, that change is updated rather than the plant being re-walked. The next study begins from a current model, and the re-survey scope is the delta rather than the site · which is the difference between paying for data collection once and paying for it every three years. Start with one plant and the second one is where the economics show.
On Google Play, for any Android phone or tablet. It is published by Vijaya Bhanu Digital Transformations Pvt Ltd under the Business category, and its own listing describes it exactly as it works · collect field data, online and offline, anytime and anywhere, for asset digitalisation. Install it on a device your survey team already carries; there is no hardware to procure and nothing to specify. What you get on a first install is the standard template set, because templates are configured per project. Download it from Google Play, then tell us your conventions and we will shape the templates to them.
Most of what you pay for is not the calculation. Pricing is normally built from the bus or panel count, but the effort behind that count sits in field data collection, chasing missing breaker settings and reconciling a single-line nobody has updated. That is why two plants with the same bus count can be quoted very differently, and why a quote firms up only after someone has walked the floor. The part we change is the expensive part: a clean, validated, connected network handed to whoever does your study means they are pricing engineering rather than pricing uncertainty. Send us your bus count and drawings and we will tell you which part of your own study cost is data collection.
No shutdown for most of it, and the app is built so the surveyor spends less time in front of an open panel, not more. Nameplates, panel fronts, ratings, feeder designations and relay displays are read without opening anything. Where a value genuinely sits behind a door · an internal cable marking, a breaker dial inside the cubicle · that gets scheduled into whatever shutdown window already exists, and until then it is a declared gap rather than a guess. Surveyors follow your site's permit, PPE and approach-boundary rules, which are yours to set and ours to comply with. Send your machine or panel list and we will mark what can be captured live and what has to wait for an outage.
The connectivity that a single-line is drawn from comes out of the capture, and the diagram is generated downstream rather than drawn by hand. Every component records its source and its downstream feeders, so the network exists as data by the time the survey closes. ETAP's data interface can generate a one-line automatically from an imported network, and the equipment and cable schedules come straight out of the capture. The honest limit: an auto-generated diagram is a correct topology, not a draughtsman's drawing · if you need an issued, titled, revision-controlled SLD, that is a drafting step on top and we scope it separately. Ask to see both outputs and we will show you the difference on your own network.
Not today · it is Android only. That is a deliberate choice rather than an oversight: Indian survey teams overwhelmingly carry Android tablets and phones, rugged Android hardware is cheap enough to hand out across a large field team, and building one platform properly beat building two adequately. If iOS is a hard requirement for your team, tell us at the first conversation rather than after · it changes the answer we give you, and we would rather say so than let you find out at deployment. Tell us what your team carries and we will be straight about the timeline.
Captured data sits on the device until it is published, then in the project's cloud workspace, with access by project and by role so a surveyor sees their assignment rather than the whole estate. For defence, PSU and other restricted sites the same stack runs inside your own boundary, so nothing leaves the site at all. Worth saying plainly: an electrical network model is a map of how to damage a plant, and buyers in critical infrastructure are right to ask this before they ask about features. Tell us your site classification and we will send the deployment and access note before any commercial conversation.
We will not quote you a number without seeing your site, and you should be wary of anyone who does. A row of accessible LV panels in a clean MCC room and a switchyard requiring a permit for every approach are not the same day's work. What actually sets the rate is the class mix, physical access, how much is readable without opening anything, and how complete your existing records are. What the app changes is the shape of the day: no evening transcription, no re-typing, and no separate data-entry phase after the team comes home. Send the site details and we will size the field days honestly, including the ones we think will be slow.
Start with one substation

Give us one panel room.
Compare it to how you do it today.

Tell us the site, the approximate bus count and the package your model has to land in. We will configure the templates to your conventions, capture with your engineer alongside ours, and hand back the data, the photographs and the export · usually inside a week. You judge it against what your own team would have produced on the same day.

Enquire now Get it on Google Play Take the 4-min DMM Check™

India work emails only. No sales call until you ask.