Prerequisites
The following requirements must be met to use the Powerproject integration:
Asta Powerproject Version 17 or newer
.NET Framework 4.7.2
Write permissions for the user running Powerproject to place files in the local installation folder of the plugin
Installation & Version Update
Path: oculai App
Open Project settings → Integrations and download the installation file (.exe).
Performing the installation
Start the installation file with a double-click
Powerproject must be closed during installation
After restarting Powerproject, the new "oculai" tab appears in the toolbar.
Plugin Settings
Path:
Powerproject App → Settings → General
Here you get an overview of:
the currently linked oculai project
the installed version of the oculai plugin
This view is exclusively for management and monitoring.
Linking a project in Powerproject
The "Link project" button connects the currently open Powerproject project with an oculai project.
💡 The link is saved in one of the 15 Powerproject additional data fields. If no free field is available, one must first be cleared.
Path:
File → Advanced Properties → Additional fields
Link procedure
Authorize oculai project
Select the appropriate oculai project in the dialog and confirm the connection.
Back to Powerproject
After successful authorization, the link is automatically stored in the project.
Data exchange between Powerproject and oculai
Export: Powerproject → oculai
During export, the current version of the schedule is transferred from Powerproject to oculai.
Procedure:
Start the export in Powerproject
The oculai import editor opens automatically in the browser
The degree of match with the previously uploaded plan is displayed
Structural changes from the previous version are displayed transparently
💡 The degree of match shows how much the new schedule differs structurally from the previous version.
Import: oculai actual data → Powerproject
During import, the actual start and end dates recorded in oculai are transferred to Powerproject.
Procedure:
Start the import in Powerproject
Powerproject updates the relevant activities
The project can then be recalculated and updated
Import logic in detail
Which activities are updated?
Activities that are recorded as active or completed in oculai
Start and end dates are set based on oculai actual data
Which activities are not updated?
Activities outside the oculai detection scope (e.g. not camera-relevant)
Past activities without oculai detection
Existing start and end dates remain unchanged
Stability for past activities
When oculai makes adjustments to activities that affect downstream completed or active activities, the schedule logic remains stable through an automatic adjustment of the dependency offsets.
Example:
For a finish-to-start dependency with an overlap of 5 days, the dependency offset is set to −5 days.
Definition:
An activity is considered to be in the past as soon as at least one downstream activity is active or completed.
Import summary & error messages
Status messages
Updated
Start and end date were successfully transferred from oculai.
Already synchronized
The actual data in Powerproject and oculai are identical — no action required.
Activity not found in Powerproject
The activity ID from oculai does not exist in the current schedule.
Typical cause: oculai plan ≠ current Powerproject version.
Conflicts
Calendar conflict
Occurs when an oculai actual date is not compatible with the Powerproject calendar (e.g. weekend or company holiday).
System behavior:
Powerproject automatically shifts the start or end date to the next valid date
Solutions:
Adjust actual dates in oculai, or
Correct the calendar in Powerproject
Unresolved conflicts are displayed again at the next import.
Example:
[1] Ceiling B2 should be 16.09.2025–20.09.2025, but is 16.09.2025–22.09.2025 (calendar conflict).
Locked activity
The activity is locked in Powerproject and cannot be updated.
Summary task
Summary tasks cannot be overwritten.
If oculai actual data was recorded on a summary task, the subordinate activities in Powerproject remain authoritative.