Frequently asked questions


A typical Visavi customer will have a CMMS, or a maintenance system, like SAP PM, Maximo, COMOS, IFS or Workmate. The most sophisticated features in Visavi revolve around these solutions. We can also import project portfolio management software like Primavera, Safran and MS Project, and write back to them if required.. Work Permitting systems are also commonly integrated.

You can use existing data warehousing technologies, but we recommend pulling data directly from source systems. Integration platforms aren’t necessarily created with real-time data exchange in mind, sometimes leading to suboptimal performance. An important aspect  when choosing integration architecture is to ensure all systems are in sync with each other.

Yes. At Visavi, we have a generalized data model for CMMS and planning systems that we’re currently exposing as APIs. We are refining this.

Visavi imports dependencies that exist in source systems. An upcoming feature of the web client is the ability to connect across systems. As an example, you would be able to align work orders with activities and asset plans. Developing this particular feature is high on our agenda.

Yes. This has been a key feature dating back to the original Scenario Composer, an early-stage solution design. Unlike other solutions that merely consume data from sources, our technology is bidirectional that reads and writes data.

No, Visavi was called LivePlan for a reason: You get live data automatically pulled in. While update frequency varies, in some cases, you need almost real-time updates, such as with work permits. 

Visavi is not a Dashboard, It is a live data hub that collates all your important operational data, reads and writes back to your source systems allowing you to replan quickly, reducing the amount of stops your business incurs.

Yes, the solution can be delivered in your native language.

The solution is hosted on Microsoft Azure in Europe. As per our roadmap we will shortly be offering customers the choice to select other Azure data centres around the world and also the possibility to have the solution hosted on data centres chosen by the customer.

Implementing Visavi is non-intrusive so you can carry on using your existing solutions while the solution is set up. Similarly implementing Visavi typically takes under 12 weeks. If you change your source systems, we will update the APIs linking to Visavi meaning that the disruption to your use of Visavi will be minimal.

We can read data from any source planning and maintenance systems. Examples include but noyt limited to; ERP systems including SAP, PrimaVera and Maximo. Maintenance and planning systems including SAP, Comos and Cognite. Safety Barrier Data systems such as Comos. Weather data. Logistics systems such as Davinci and Vantage. Operational plan grant data systems such as. PirmaVera, MS Project, Direct Planning. Other data sources e.g. Excel Sharepoint.

Visavi is not a planning tool. Visavi collates operational data from all your base operational systems and present this data in one easy to view live system. Visavi supplements your existing planning system allowing you replan with ALL relevant planning and maintenance data at your disposal.

Why settle with the norm? Visavi Maximises to ROI from your existing systems, we do not replace them. Improving your production levels, increasing aspects like tool time and plan attainment. This all leads to reducing stops, reducing down time and increasing your profits.

Visavi is a proven solution with a short ROI. It has taken 80000 hours and 6 years to develop with approximately 30 dedicated developers. Building your own system is of course possible but costly. The solution will need to be supported and updated and your ROI is uncertain.

Functionality & Application

The fundamental value of Visavi’s solution is the same for any industry: The ability to view and interact with a worldwide, multi-site operation, using one single interface that collects all information. The solution is industry independent and suitable for any business dealing with many planning disciplines related to maintenance and operations that need to be coordinated. 

At Visavi, we believe reporting is the old way of sharing information. With a holistic view of your operational workflows streamlined into a single and easy to use interface, the need for reporting isn’t required. With Visavi, information is automatically updated, and available to the entire organization at any given time. 

Visavi works with solutions such as Microsoft Teams, and is a cloud-based solution that’s accessible anywhere, anytime. However, some of the qualities of meeting in front of a large screen, similar to old-fashioned coordination boards, are unfortunately lost when working remotely. The real power of Visavi is when you meet in a collaborative environment. Despite that, one of the things we are doing in the web client is to make it work optimally on very small screen sizes, which makes it more suitable for screen sharing. It should also be noted that while Visavi is certainly useful and usable in meetings, it also serves as a way to actually reduce the need for some types of meetings. It does so by providing different stakeholders with a shared situational awareness without spending so much time and effort on information exchange meetings. 

Implementation & Onboarding

It depends. A clear vision, organizational maturity, and technical abilities may reduce the implementation period, but the actual time also depends on infrastructure and applications. A standard, off-the-shelf implementation takes 6 to 8 weeks.

Visavi is typically delivered in under 12 weeks. Delivery is non intrusive so you can continue using your existing systems while Visavi is being deployed. Customer feedback suggests that a new user will typically understand how to use Visavi within half an hour.

We already have a global presence, with customers across Europe, the United States, Canada, Peru, and Bolivia. We have subsidiaries in Sweden and Singapore, and we are continuously expanding into new regions and industries.