Introduction
In this lesson, you will learn the history of development over.vu and its applications were created and designed.
over.vu's History
This platform came from following our core values of problem solving and dedication to collaboration and teamwork. We wanted to help our customers with issues they saw in their processes and issues we identified together through analytics.
Access - <2020
The EKN development journey began with creating Microsoft Access databases to for a way to consolidate several groups and workflows spread across multiple applications and documents.
Access offered functions that allowed EKN developers to transform a complex workflow involving diverse departments and simplify it into a graphic interface with field inputs and outputs. This made what were once complicated workflows, simple for our clients to navigate, track, and use.
This worked incredibly well, and our clients requested similar databases be made for other projects. Access began to show its limitations, the amount of dedicated developer time required to make simple changes, the age of the software, and the loading times incentivized the team to begin investigating a custom solution.
R&D - 2021
As we grew and improved, we identified two important ideas. The custom solution would have to address the pain points of customizability, modernization, and collaboration.
Prime - 2022
Prime was the first trial of this new custom solution; it served as a major upgrade to Access. It was faster, cloud-hosted, user-friendly, and allowed project teams to instantly customize aspects of their own project.
As Prime was used over the next year, additional user needs were identified. While still a major improvement to Access, the platform still required significant development time for minor changes and lacked user configuration required to sustain the growth of the platform.
over.vu - >2023
Prototyping began by rebalancing Prime and developing Manager.
Manager was the first instance of separating out a group of features into their own applications. Manager became the first over.vu application to manage user and application access.
Simultaneously Workflow was being developed as the improved solution for Prime. It would have increased end-user configuration options, the ability to import and manage your data yourself, and a better UX experience.
Assets began development in 2025 as an application that would allow users to geospatially view their company's assets, and all the related work on the assets.
over.vu's Applications
These are the applications that make up the over.vu ecosystem and their purpose within the platform.
Workflow: Ensures every project follows a consistent, reliable process by eliminating ambiguity, removing people-dependent steps, and keeping work moving automatically.
Assets: Reduces asset-related risk by centralizing information, ensuring accuracy, and providing full visibility into condition, history, and future vulnerability.
Scope: Brings financial consistency and transparency by standardizing how estimates and rules are created, preventing errors, and keeping all scope data in one authoritative place.
Manager: Protects data and streamlines operations by governing who has access to what, ensuring the right people have the right permissions, and maintaining a single source of truth for users and contacts.
Wrap-Up
Now you know:
How we got started
Different platforms we've tried
Check Your Understanding
In this lesson you learned about:
What over.vu is
How over.vu applications differ
Next up:
The next lesson of this course covers how to access the application and our resource center for questions and troubleshooting.