Imports and Integrations

File Imports:

• Purpose: Used for importing your resource planning data from your other ERP, accounting, HR, or construction management systems.
  
  

• How to:

  • Download the Import Template under “File Imports”

  • Add your data into the template mapped to the correct columns

  • Import the template with your data

  • Review for any errors and re-import if necessary

  • Finalize Import to add/update the data into the system.

Note: If the Vista sync is configured for a company's environment, File Imports is not necessary.

Note: If there is a failure in an import, the specific data lines causing the issue will not be imported.

Import Settings:

• Purpose: This page allows users to list the specific fields they would like updated with each import and sync from their other applications.  By default, there are no fields listed meaning that new data will be inserted once on import, but there will never be updates to it.

• How to: 

  • Select "Add New" 

  • Select a datagrid, such as Employee, Crew, Asset, Job, Labor Type, or Time Off. 

  • Select what information to update in that datagrid each import/sync.

  • Exceptions to this are the following areas that will always be updated on every import/sync.

    • Jobsite Budgets

    • Jobsite Budgets By Month

    • Jobsite Revenue

    • Jobsite Revenue By Month

    • Job Actual Hours

    • Job Departments

    • Cost Types

    • Jobsite CO Header

    • Jobsite CO Detail
      
      

Integrations:

• Purpose: This configuration panel lets admins connect and sync company data to ProjectSight so that data can flow between them automatically.

  • Note: If the customer is not using ProjectSight, then disregard this section.

• How To:

• Enable Integration (toggle)

  • Turning this on activates the connection

• API App Name

  • A label users give this integration (e.g., company or project name)

• Consumer Key & Consumer Secret

  • These are API credentials provided by ProjectSight

  • They act like a username/password for system-to-system communication

• Show button

  • Lets users reveal the hidden credentials

• Test Connection

  • Verifies that the provided credentials work and the systems can talk to each other.

Once enabled, the system will pull specific data from ProjectSight so they can be mapped to the records in Resource Planning.

• On Employee records, admins will see a ProjectSight page where they can map Resource Planning Employee records to ProjectSight Users

• On the Job records, admins will see a ProjectSight page where they can map Resource Planning Job records to ProjectSight Jobs

• On the Position records, admins will see a ProjectSight page where they can map Resource Planning Positions to ProjectSight Security Roles and/or Class

• On the Labor Type records, admins will see a ProjectSight Page where they can map Resource Planning Labor Types to ProjectSight Trade

Once these records are mapped, Resource Planning will do the following:

1. Each morning at 12AM, Resource Planning will send a Daily Report to ProjectSight listing the Employees and number of hours worked based on the assigned schedule in Resource Planning

2. When a new long-term assignment is made to a position that is linked to a ProjectSight Security Role, Resource Planning will assigned that ProjectSight User to the selected job for the Security Role linked to the Position.

   1. This is important if you have tight Project Sight security down to the Job level instead of the Portfolio level.
      
      

API Docs:

This tab shows the Application Programming Interface (API) which is the set of rules that allows the software to communicate, share data, and provide seamless integration of the tools and systems used in construction workflows. On the left shows all available Fiddletree API’s with a search bar. On the right users can view the html format of information under each related tab.

Instead of using the Out-of-the-Box Vista Sync, customers can configure custom integrations using these resource planning APIs.

• Example:

  • Sending data from a data lake to resource planning.