NextGen FSM

OverIT markets its field service platform as NextGen FSM, part of a NextGen Platform that also includes NextGen Field Collaboration and NextGen Geo. The product lineage matters for search purposes: Geocall was OverIT prior FSM product, and the GEOCALL trademark is still recorded to OVERIT S.P.A. No OverIT page states the Geocall to NextGen rename explicitly, and review aggregators still carry Geocall listings, so expect Geocall, Next-Gen FSM Platform and NextGen FSM all to circulate as names for the same lineage.

On ownership: OverIT S.p.A. is a privately held Italian company that spun off from Gruppo Engineering in October 2021 and is controlled by investment firms Bain Capital and Neuberger Berman. Stake percentages are not public. No later ownership change was found.

The scheduling depth is the strongest documented part, and it is specialised in ways that matter for utilities. Assignment runs in automatic, manual or mixed modes, allocating on skills, location and availability, with multi-team multi-day optimisation, machine learning that adapts from dispatcher adjustments, job duration prediction, and job bundling including bundling along linear assets. Multistage tasks with time dependencies are supported, which is the kind of requirement that eliminates most trades-oriented products immediately. In-day rescheduling handles emergencies, delays and travel disruption. SLA and regulatory compliance monitoring is explicit, with alerts as deadlines approach and compliance reporting for contractual and legal obligations.

• GIS is a native module, not a bolt-on, and GIS and IoT integration runs through the asset maintenance story. For linear-asset operators this is a genuine architectural differentiator.
• Blended workforce is built in. Contractor management covers contracts, scheduling and assigning work to third parties, and OverIT describes a blended employee, contractor and part-time workforce as a first-class case.
• Customer invoicing is recorded as unknown, deliberately. Invoicing appears on OverIT pages only under supplier and purchase management, which is supplier-side rather than customer-side billing. Service contracts are similarly supplier and contractor contract compliance rather than customer entitlement management; read that carefully against your requirement.
• Documentation is gated. The product training portal is password-protected, there is no public API documentation, and no OverIT page states a deployment model, so cloud, on-premises and hybrid are all unknown.
• Integration claims are generic. OverIT states integration with CRM, ERP, asset management, GIS and IoT, but names no specific vendor products on the pages opened, so only GIS and a generic asset-management coupling could be recorded. If you need a named SAP, Oracle, Salesforce or Dynamics connector, treat that as an open question.
• Work intake is designed around other systems. The work management module takes orders from ERP, CRM, EAM or IoT, which tells you OverIT expects to sit in a wider landscape, even though it is a full execution platform rather than a scheduling layer.

Good fit: asset-intensive, mission-critical field operations in the industries OverIT names, which are electric, gas and water utilities, oil and gas, telecommunications and transportation. It is a strong fit specifically where work is organised around linear assets, where tasks have multistage time dependencies, where SLA and regulatory deadlines carry legal exposure, and where a substantial share of the workforce is contracted rather than employed. Organisations that already treat GIS as a system of record rather than a map layer will find the native GIS module a better fit than products that integrate to GIS as an afterthought.

Poor fit: anything outside asset-intensive field operations. OverIT narrows its own industry targeting sharply, and a general commercial services or trades business would be buying specialised machinery it does not need. It is also a poor fit if your requirement centres on customer billing, since customer invoicing could not be verified, or if you need a customer portal, which is unverified. Buyers needing to assess integration risk up front should note there is no public API documentation at all.

Typical use cases: utility crew dispatch across electric, gas and water networks, pipeline and linear-asset inspection and maintenance campaigns, telecoms outside plant work, and transportation infrastructure maintenance with regulatory reporting obligations. Technical and commercial diligence both require vendor contact: there is no published pricing, no public API reference and no stated deployment model.