A structured journey from Pims to Omega 365

For more than 20 years, Pims has supported project execution in complex, asset-intensive organizations across many industries. It has provided a solid system for project follow-up, governance, and control – and for many customers, it still does.

Over time, the way organizations plan, execute, and operate both projects and assets has gradually changed.

There is more data, stronger demands for integration, and higher expectations for usability and insight across the full lifecycle, and across projects. Platforms are no longer judged only by what they support today, but by how well they can adapt over time.

At the same time, a growing number of customers are already running their projects and assets on Omega 365, gaining experience with a modern, cloud-based platform designed for continuous development.

This is the background for Omega 365.

Not as a replacement for what already works – but as a natural next step, built on experience.

Why evolve?

The move from Pims to Omega 365 is not driven by urgency or disruption. It is driven by how modern platforms need to work.

Omega 365 is built as a cloud-native SaaS platform, designed for continuous improvement rather than periodic upgrade projects. This enables predictable operations, frequent updates, and scalable growth - without customer-specific upgrade efforts.

At the core of the platform is a unified enterprise hierarchy that connects organizations, projects, contracts, and assets. This shared structure provides consistent access, visibility, and reporting across the entire lifecycle.

Just as importantly, Omega 365 is built for configuration rather than customization. Many adaptations that previously required custom code can now be handled through configuration of workflows, data fields, roles, and processes - making it easier to evolve continuously over time.

All of this is delivered through a cohesive platform for projects and assets, while still allowing customers to adopt and expand at their own pace.

And crucially: Omega 365 is built on more than 20 years of proven Pims innovation and domain knowledge.

The foundation everything builds on

Before talking about individual modules or features, it is important to understand the foundation of Omega 365.

The platform is built around a few shared structures:

• Organization - company structure, roles, and contracts

• Scope - work breakdown, processes, and follow-ups

• Assets - asset structures and digital representations

• Documents - connected across organization, scope, and assets

Everything else in the platform - planning, cost, documents, workflows, reporting, and AI - builds on this foundation.

Customers do not need to use everything from day one. But when they choose to expand, they are building on the same structures rather than introducing new silos.

Evolving from customization to configuration

In Pims, flexibility was often achieved through customization. This worked well, but it also meant that changes and upgrades required more effort over time.

With Omega 365, much of that flexibility has moved into configuration.

Workflows, data fields, roles, processes, and registers can be adapted without rebuilding the solution. The platform also comes with several preconfigured processes that can be adjusted to customer requirements.

The result is less customer-specific code, easier upgrades, and a platform that is better suited for continuous improvement.

It also means that customers can configure their own processes – from simple setups to more advanced ones. We increasingly see power users configuring workflows themselves, helping establish more standardized and well-understood ways of working.

This shift is a key part of what it means to evolve with Omega 365.

A cohesive platform - adopt and grow at your own pace

Omega 365 is designed as a cohesive platform, not a collection of loosely connected tools.

Customers typically start with one or two areas that matter most - for example cost management, document management, or planning. Over time, they can expand with additional capabilities as needs evolve.

Because everything is built on a shared data foundation, this expansion does not introduce fragmentation. It strengthens consistency.

There is no requirement to adopt everything at once, no forced scope, and no predefined end state. Omega 365 is a software platform organizations can grow into over time.

From projects to assets - one continuous lifecycle

Traditionally, projects and operations have been handled in separate systems. Handover often means exporting documents and starting over.

In Omega 365, projects and assets can live on the same platform.

The structures, documents, and context established during project execution follow the asset into operations. This reduces handover friction, preserves knowledge, and increases the long-term value of project data.

AI in Omega 365 - built into the platform

AI in Omega 365 is not a separate tool or add-on. It is built into the platform and supports users across workflows, documents, planning, and reporting.

AI works best when data is structured, connected, and contextual. Because Omega 365 is built on a shared foundation, AI can support real work - assisting users, automating repetitive tasks, and highlighting deviations within existing processes.

One example of this capability is AI Knowledge Packs, which capture and reuse structured project knowledge to provide context-aware insights across projects, roles, and phases.

AI Knowledge Packs are one expression of a broader AI capability - not the whole story.

A structured journey - on your terms

Moving from Pims to Omega 365 is not a technical upgrade. It is a structured journey.

Each customer starts from a different point, with different usage patterns and priorities. That is why the transition is approached as a phased and planned process - not a big-bang move.

The journey typically includes:

• Assessment and planning

• A tailored migration strategy

• Enablement and training through documentation and Academy resources

• Ongoing support before, during, and after transition

Pims remains stable and supported during this period, allowing customers to evolve at a pace that fits their organization and projects.

Evolve with Omega 365

Evolving to Omega 365 is about building on what already works - while preparing for what comes next.

It is about flexibility without fragmentation.
About continuity without stagnation.
And about a platform designed to evolve - together with its users.

Our technical and functional experts are ready to assist and support customers throughout the transition, helping ensure a smooth and well-managed journey.