Skip to main content
Prevision is a platform for integrated project management in civil construction, focusing on optimizing deadlines and costs. It facilitates collaboration between all stages of a project, from planning to execution, providing tools for detailed monitoring and analysis.

Configuring Prevision as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Prevision option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

You’ll need your Prevision API Token for this connection. Once you have it, add the account access, then click Next.
  • API Token: Your personal access token for the Prevision API. Check how to get it here.
  • Start Date: The earliest record date to sync.

2. Select streams

Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select a name for each table (which will contain the fetched data) and the type of sync.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can determine when to execute a full sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while. Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Below you’ll find all available data streams from Prevision and their corresponding fields:
Stream for fetching project information.
FieldTypeDescription
idStringThe unique identifier for the project.
nameStringThe name of the project.
areaStringThe area of the project.
phaseStringThe phase of the project.
Stream for fetching activity information for a specific project.
FieldTypeDescription
idStringThe unique identifier for the activity.
partStringThe part of the activity.
wbsCodeStringThe WBS code of the activity.
percentageCompletedNumberThe percentage completed of the activity.
expectedPercentageCompletedNumberThe expected percentage completed of the activity.
startAtDateTimeThe start date of the activity.
endAtDateTimeThe end date of the activity.
durationNumberThe duration of the activity in days.
serviceObjectThe service associated with the activity, containing a name (String).
floorObjectThe floor associated with the activity, containing a name (String).
jobsArray of ObjectsA list of jobs associated with the activity, each containing id, name, wbsCode, percentageCompleted, expectedPercentageCompleted, startAt, endAt, and duration.
Stream for fetching budget reports for a specific project.
FieldTypeDescription
idStringThe unique identifier for the budget report.
nameStringThe name of the budget report.
Stream for fetching the last measurement data for a specific project.
FieldTypeDescription
workTypeStringThe type of work (e.g., ActivityDeadlineMeasurement).
percentageCompletedNumberThe percentage completed for this work.
basePercentageCompletedNumberThe base percentage completed for this work.
expectedPercentageCompletedNumberThe expected percentage completed for this work.
workObjectContains detailed information about the work item.
work.idStringThe unique identifier for the work item.
work.workDurationNumberThe duration of the work.
work.durationNumberThe duration.
work.measurementUnitObjectThe measurement unit, containing type and symbol.
work.serviceObjectThe service associated with the work, containing id and name.
work.jobMeasuresPageObjectA paginated list of job measures.
work.jobMeasuresPage.nodesArrayA list of job measure nodes, each containing measuredIn, basePercentageCompleted, percentageCompleted, and expectedPercentageCompleted.
Stream for fetching the last measurement task data for a specific project.
FieldTypeDescription
workTypeStringThe type of work (e.g., ActivityDeadlineMeasurement).
percentageCompletedNumberThe percentage completed for this work.
basePercentageCompletedNumberThe base percentage completed for this work.
expectedPercentageCompletedNumberThe expected percentage completed for this work.
workObjectContains detailed information about the work item.
work.idStringThe unique identifier for the work item.
work.nameStringThe name of the work.
work.partStringThe part of the work.
work.serviceObjectThe service associated with the work, containing id and name.
work.floorObjectThe floor associated with the work, containing id and name.
Stream for fetching the physical schedule table for a specific project.
FieldTypeDescription
codeStringActivity code.
descriptionStringActivity description.
levelIntegerActivity level in hierarchy.
durationIntegerActivity duration in days.
start_atStringActivity start date.
end_atStringActivity end date.
baseline_start_atStringBaseline start date.
baseline_end_atStringBaseline end date.
base_pointsStringBase points for each date (JSON string).
expected_pointsStringExpected points for each date (JSON string).
realized_pointsStringRealized points for each date (JSON string).
Stream for fetching schedule activities for a specific project.
FieldTypeDescription
idStringThe unique identifier for the activity.
endAtDateTimeThe end date of the activity.
deletedAtDateTimeThe deletion date of the activity.
startAtDateTimeThe start date of the activity.
wbsCodeStringThe WBS code of the activity.
workDurationNumberThe work duration of the activity.
partStringThe part of the activity.
serviceObjectThe service associated with the activity, containing id, name, position, startAt, endAt, and createdAt.
floorObjectThe floor associated with the activity, containing id, name, and replicationGroup.
jobsArray of ObjectsA list of jobs associated with the activity, each with its own detailed properties.
workPackageResponsiblesPageObjectA paginated list of responsible contractors for the activity.
measurementUnitObjectThe measurement unit for the activity, containing detailed properties like id, name, type, symbol, quantity, and checklist.
I