Smallworld services in Edmonton cover the full range of specialist engineering work required to implement, upgrade, customize, integrate, and support GE Vernova’s Smallworld GIS platform used by electric utilities, gas operators, and telecoms to manage their physical network infrastructure. Smallworld runs on a proprietary programming language called Magik and uses a version-controlled spatial database architecture that is unlike any standard GIS platform. It requires engineers who have worked inside it at scale.
Gnapi Technologies delivers Smallworld services in Edmonton and across North America, the UK, and India as a Smallworld GIS partner with over three decades of platform experience across Smallworld 4.3, 5.x, GSS, GSA, Electric Office, Gas Distribution Office, and Physical Network Inventory.
Book An Appointment Now
Smallworld runs on Magik, a proprietary language requiring dedicated specialist engineers
Gnapi Technologies maintains a bench of Magik developers and Smallworld architects with enterprise delivery experience
Services cover upgrades, Magik development, Electric Office, Gas Distribution Office, PNI, OMS integration, GSS/GSA, and managed support
Supported versions: Smallworld 4.3, Smallworld 5.x
Delivery: onshore technical leads in Edmonton, USA, and UK with offshore teams in India
GE Vernova Smallworld is an enterprise GIS platform used almost exclusively by three industries: electric utilities, gas distribution operators, and telecoms to manage their physical network infrastructure. It stores every asset in the network, how it connects, how it changes over time, and provides the network topology that feeds Outage Management Systems (OMS), Advanced Distribution Management Systems (ADMS), field crew applications, and work management platforms.
Smallworld’s alternative worlds versioning model tracks all edits as pending changes until reviewed and approved, which is critical for utilities where network data changes affect operational decisions in live systems. This architecture, combined with the Magik language and the specialist Office modules for electric and gas networks, is what makes Smallworld both powerful and difficult to maintain without engineers who have worked inside it.
Managing Smallworld 4.x to 5.x upgrades from scoping through go-live, including schema migration, custom Magik code rewrites, Physical Network Inventory (PNI) data validation, integration retesting, and parallel environment management. Most enterprise Smallworld upgrades take 12–24 months. Every migration plan accounts for the schema-level issues and downstream integration dependencies that turn a routine upgrade into an extended program because we have seen where they occur.
Writing, extending, and refactoring custom Magik code custom tools, automated workflows, data validation routines, and integration connectors. Auditing existing Magik code bases to identify technical debt and reduce the volume of custom code carried through version transitions. Reducing custom Magik volume before an upgrade directly reduces migration risk and cost.
Customizing Smallworld Electric Office to match each utility's specific data model, feeder structure, switching workflows, and reporting requirements, including schema extension, Magik development, UI customization, and integration with CIS, SCADA, and work management platforms.
Configuring and customizing the Gas Distribution Office module for gas network operators managing pipelines, pressure zones, valve assets, and the compliance data that regulators require. Our engineers understand both the Smallworld data model and the operational context of gas distribution.
Connecting Smallworld GIS network topology to Outage Management Systems and Advanced Distribution Management Systems so outage tracing, crew dispatch, and restoration workflows are driven by accurate spatial data. These integrations require equal knowledge of the GIS data model and the OMS/ADMS architecture.
Implementing and configuring Geo-Spatial Server (GSS), the web services layer that exposes Smallworld data to other systems via standard web services and Geo-Spatial Analysis (GSA), the analytical layer that enables spatial analysis operations on Smallworld data from outside the Smallworld client.
Designing PNI schemas, migrating data from legacy systems, validating network topology, and integrating Physical Network Inventory with downstream OSS and work management platforms. PNI data feeds OMS, work management, and field crew systems data quality errors in PNI propagate directly into operational systems.
Providing ongoing Smallworld engineering capacity as a dedicated extended team operating under client processes covering bug resolution, minor enhancements, version maintenance, and project capacity. Most long-running Smallworld programs begin as fixed-scope upgrades and transition into extended team arrangements after go-live.
Smallworld is not a platform where general GIS or software engineering experience transfers. The Magik language is not taught in standard GIS or software engineering programs. The alternative worlds versioning model, the spatial database architecture, and the Electric Office and Gas Distribution Office data models all require engineers who have worked inside them across multiple versions and 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.
Attribute | Smallworld 4.3 | Smallworld 5.x |
|---|---|---|
Architecture | Legacy monolithic | Modular, service-oriented |
Magik API | Older API | Modernized API |
Web services | Limited | REST services, improved GSS |
Support status | End-of-life trajectory | Current supported version |
Migration required | Yes | Target version |
Smallworld 5.x introduced modular architecture, REST-based web services, and a modernized Magik API, making it significantly easier to expose GIS data to field crew applications and third-party systems. The migration from the 4.x to 5.x requires schema restructuring, custom Magik rewrites, and full integration retesting.
Not universally, and not quickly. Some utilities are migrating from Smallworld to ArcGIS Utility Network, particularly where Smallworld support costs have become difficult to justify at scale. Many large utilities in North America and Europe remain on Smallworld with active Smallworld 5.x investment programs. Some run both platforms in parallel. Gnapi Technologies works across both platforms and advises on migration feasibility based on technical and operational grounds, not platform preference.
Fixed-scope delivery
Defined deliverables, timeline, and price. Suited to upgrades, migrations, and integration projects with clear requirements.
Time and materials
Flexible scope with monthly billing. Suited to Magik development and customization where requirements evolve.
Dedicated extended team
A named team embedded under client processes and suited to long-running programs and ongoing Smallworld support.
Staff augmentation
Individual Magik developers or Smallworld architects placed into a client’s existing team.
Smallworld Services in Edmonton: Delivered by Engineers Who Know the Platform
Whether you are scoping a Smallworld upgrade, planning a PNI migration, need Magik development capacity, or are looking for an ongoing Smallworld managed support arrangement, Gnapi Technologies delivers Smallworld services in Edmonton and globally with the engineering depth that Smallworld programs require. The first step is a technical conversation with one of our Smallworld engineers.
Start a Smallworld scoping conversation with Gnapi Technologies. Book a call with our Smallworld team.
GE Vernova Smallworld is an enterprise GIS platform used by electric utilities, gas distribution operators, and telecoms to manage their physical network infrastructure, storing every asset, how it connects, and how it changes over time. It provides the network topology that feeds OMS, ADMS, field crew applications, and work management systems in large utility and telecom operations.
A Smallworld upgrade from 4.x to 5.x typically takes 12–24 months for enterprise deployments. The timeline depends on the volume of custom Magik code, the complexity of the PNI schema, the number of downstream integrations that need retesting, and the quality of existing network data. Gnapi Technologies scopes each migration individually before providing a timeline estimate.
Magik developers are not widely available; the language is proprietary to Smallworld and is not taught in standard software engineering or GIS programs. Gnapi Technologies maintains a bench of experienced Magik developers across Canada, the UK, and India, available for staff augmentation, project teams, or dedicated extended team arrangements.
Physical Network Inventory (PNI) is the Smallworld module that records every physical asset in a network: cables, conduits, splice closures, poles, fibre spans and the connectivity between them. PNI feeds OMS, work management, and field crew systems. Data quality errors in PNI propagate directly into operational systems, making PNI validation one of the highest-risk workstreams in a Smallworld upgrade.
Yes. Smallworld OMS integration with Oracle's Utilities Network Management System is a common integration pattern for North American electric utilities. The integration connects Smallworld's network topology to Oracle's outage management workflows, enabling accurate customer impact analysis, crew dispatch, and restoration tracking. Gnapi Technologies has built and maintained these integrations across multiple OMS 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 contained within the platform and cannot be consumed by external applications or integration layers.
Gnapi Technologies' extended team model embeds a dedicated group of Magik developers, GIS analysts, and support engineers into the client's Smallworld engineering function — operating under the client's processes, tools, and governance. The team covers bug resolution, minor enhancements, version maintenance, and project capacity. Teams are sized to client requirements and can flex based on program demand.
Yes. Gnapi Technologies configures and customizes the Gas Distribution Office module for gas network operators managing pipeline networks, pressure zones, valve assets, and the regulatory compliance data that gas operators are required to maintain. Our engineers understand both the Smallworld data model and the operational context of gas distribution networks.
Gnapi Technologies is headquartered in Edmonton, Canada, with offices in the USA and UK and engineering delivery centers in Bengaluru, Hyderabad, and Trichy, India. The Smallworld delivery model pairs onshore technical leads with offshore engineering teams, giving clients regional presence alongside the capacity to staff large programs competitively.
The first step is a technical scoping conversation with one of our Smallworld engineers. We ask about the current Smallworld version, what the organization is trying to do, the existing custom code volume, and the downstream integrations involved. From that conversation, Gnapi Technologies gives an honest view of effort, risk, and team composition before any formal proposal. Contact Gnapi Technologies to book a call.
