Smallworld consulting services cover the specialist engineering work required to implement, upgrade, customize, and support GE Vernova’s Smallworld GIS platform, used by electric utilities, gas operators, and telecoms to manage their physical network infrastructure. Services include version 4.x to 5.x upgrades, Physical Network Inventory (PNI) migration, Magik development, Electric Office customization, OMS/ADMS integration, and managed support.
Gnapi Technologies delivers Smallworld consulting services in Edmonton and across North America, the UK, and India as a specialist engineering partner, not a generalist consultancy.
Book An Appointment Now
Smallworld is not a platform where general GIS or software engineering experience transfers. The Magik language, the spatial database architecture, the alternative worlds versioning model, Smallworld’s proprietary approach to version-controlled edits and the Electric Office and Gas Distribution Office data models all require engineers who have worked inside them at scale, across multiple versions, and across multiple client environments.
A failed Smallworld upgrade does not just delay a project. It puts network data at risk, disrupts OMS feeds, and can affect operational decisions for utilities serving hundreds of thousands of customers. The cost of getting it wrong is measured in data integrity, outage response time, and regulatory exposure, not sprint velocity.
Gnapi fields Magik developers and Smallworld architects with hands-on experience across Smallworld 4.3, 5.x, GSS, GSA, and all major Office modules, making our Smallworld consulting services in Edmonton the specialist choice for utilities and telecoms that cannot afford delivery risk.
Smallworld Version | Architecture | Key Differences | Migration Required |
Smallworld 4.3 | Legacy monolithic | Older Magik API, limited web services | Yes, to 5.x for modern support |
Smallworld 5.x | Modular, service-oriented | REST services, improved GSS, modern Magik API | Current supported version |
GSS | Web services layer | Exposes Smallworld data to other systems | Configured, not migrated |
GSA | Spatial analysis layer | Runs analytical operations on Smallworld data | Configured alongside GSS |
Smallworld 5.x introduced a modular architecture with REST-based web services, a modernized Magik API, and improved integration with GSS, making it significantly easier to expose GIS data to field crew applications and third-party systems. The migration of 4.x to 5.x requires schema restructuring, custom Magik rewrites, and full integration retesting before cutover.
A Smallworld 5 migration involves four primary workstreams: schema migration, restructuring how network data is stored in the spatial database; custom Magik code rewriting, updating proprietary code to work with the new version's API; Physical Network Inventory (PNI) data validation, confirming topology integrity before and after migration; and integration, retesting, and revalidating all downstream OMS, SCADA, and work management connections.
We manage migrations from scoping through go-live, including parallel environment management and cutover planning.
Magik is GE Vernova Smallworld's proprietary programming language, the language in which all Smallworld customization, automation, and integration logic is written. Magik development involves writing, extending, and refactoring custom code within a Smallworld deployment, including custom tools, automated workflows, data validation routines, and integration connectors.
Our Magik developers also audit and rationalize existing Magik code bases, identifying technical debt and reducing the volume of custom code that has to be maintained and rewritten through each version transition.
Physical Network Inventory (PNI), the Smallworld module that stores every physical asset in a network and how those assets connect, is the spatial data layer that OMS, field crew applications, and work management systems consume. PNI stores cables, conduits, splice closures, poles, fibre spans, and the connectivity between them.
We design PNI schemas, migrate data from legacy systems, validate topology, and integrate PNI with downstream OSS and work management systems. For telecoms planning fibre rollouts, accurate PNI is not a data project; it is an operational requirement. We design PNI schemas, migrate data from legacy systems, validate topology, and integrate PNI with downstream OSS and work management systems.
Smallworld Electric Office is the Smallworld module used by electric utilities to manage their distribution network feeders, transformers, switches, and meters. Electric Office customization involves extending the data model to match the utility's specific asset types, writing Magik code for custom switching workflows and reporting, and integrating Electric Office with CIS (Customer Information System), SCADA, and work management platforms.
We have delivered Electric Office customizations for utilities ranging from regional distributors to large multi-territory operators, each with different feeder structures, switching workflows, and downstream system requirements.
Gas Distribution Office is the Smallworld module used by gas network operators to manage pipeline networks, pressure zones, valve assets, and compliance data. Configuration involves mapping the operator's specific gas network assets into the Smallworld data model, setting up pressure zone topology, and integrating with SCADA and compliance reporting systems.
Our engineers understand both the Smallworld data model and the operational context of gas distribution.
Outage Management System (OMS), the platform utilities use to manage outages, route repair crews, and track restoration, depends on accurate network topology data from the GIS to function correctly. Smallworld OMS integration connects the GIS network model to the OMS so that when a fault occurs, the OMS can trace the affected network, identify impacted customers, and generate switching orders based on the current network state.
Advanced Distribution Management System (ADMS) integration extends this to real-time distribution automation where the ADMS uses live GIS topology to support automated switching decisions and distributed energy resource management.
We have built and maintained OMS and ADMS integrations across multiple platforms.
Geo-Spatial Server (GSS) is the web services layer of the Smallworld platform. It exposes Smallworld data to other enterprise systems, mobile field crew applications, and third-party platforms via standard web services, including REST and WFS. Without GSS, Smallworld data is largely locked inside the platform.
Geo-Spatial Analysis (GSA) is the analytical layer that enables spatial analysis operations on Smallworld data network tracing, proximity analysis, and spatial reporting to be run from outside the Smallworld client application.
Managed support and extended team arrangements provide ongoing Smallworld engineering capacity as a structured service covering bug resolution, minor enhancements, version maintenance, and project capacity. Teams are sized to the client's requirements, operate under the client's processes and tooling, and are available across time zones from our India delivery centers.
Most long-running Smallworld programs begin as fixed-scope upgrade projects and transition into extended team arrangements once the migration is complete and the system is in production.
This is a question utilities ask frequently. The short answer is: not universally, and not quickly. Some utilities are migrating from Smallworld to ArcGIS Utility Network, particularly where they have strong ESRI enterprise agreements or where Smallworld support costs have become difficult to justify. Others are running both platforms in parallel. Many large utilities in North America and Europe remain on Smallworld and have active investment programs in Smallworld 5.x.
The decision depends on the utility’s existing integrations, data model complexity, internal skills, and long-term platform strategy. Gnapi works on both platforms and advises clients on migration feasibility based on technical and operational grounds rather than platform preference.
GE Vernova Smallworld is used almost exclusively in three industries:
Electric utilities:
for distribution network GIS, including feeder management, transformer records, switching workflows, and OMS/ADMS integration.
Gas distribution operators:
for pipeline network management, pressure zone modelling, valve asset records, and regulatory compliance.
Telecommunications operators:
for Physical Network Inventory, fibre network management, OSS integration, and network planning.
These are the industries where Gnapi’s Smallworld consulting practice operates.
Defined deliverables, timeline, and price. Suitable for upgrades, migrations, and integration projects with clear requirements.
Flexible scope with monthly billing. Suitable for Magik development programs and customization work where requirements evolve.
A named team embedded in the client's engineering function, operating under client processes. Suitable for ongoing support and multi-year programs.
Individual Magik developers or Smallworld architects placed into a client's existing team. Suitable where internal teams need specific skills to complete a program.
If you are scoping a Smallworld upgrade, planning a PNI migration, or need Magik developers to extend your internal team, the first step is a technical conversation, not a sales call.
Start a scoping conversation with Gnapi Technologies. Book a call with our team for Smallworld Consulting Services in Edmonton. Search for Smallworld consulting near me? We have onshore leads in Edmonton, USA, and the UK.
Smallworld consulting services in Edmonton can include platform upgrades, Magik development, Physical Network Inventory migration, Electric Office customization, Gas Distribution Office configuration, OMS and ADMS integration, GSS and GSA setup, and ongoing managed support. Gnapi Technologies provides these services for utilities and telecom operators that rely on Smallworld for network operations.
A Smallworld 5 migration usually involves schema restructuring, custom Magik code updates, PNI Smallworld data validation, integration testing, parallel environment management, and cutover planning. The goal is to move from legacy Smallworld 4.x environments to a more modern architecture without affecting network data integrity or downstream systems.
Magik developers are essential because Smallworld customizations, workflows, validation routines, and integration logic are built using the Magik programming language. During a Smallworld upgrade, existing code often needs to be reviewed, rewritten, or simplified so it works correctly with the newer platform version.
Smallworld OMS integration connects the GIS network model with the outage management system so utilities can trace faults, identify affected customers, support switching decisions, and manage restoration more accurately. When combined with ADMS integration GIS workflows, the same network data can also support real-time automation and distribution planning.
Gnapi Technologies helps design PNI schemas, migrate legacy network records, validate connectivity, configure Smallworld PNI, and integrate Physical Network Inventory Smallworld data with OSS and work management systems. This support helps telecom operators maintain more accurate fibre, cable, conduit, splice, and equipment records across the network.
