Vorbereiten von Daten für den Import in das Ressourcenplanungstool

Das Ressourcenplanungs-Tool auf Unternehmensebene ist Procores Lösung für das Bauressourcenmanagement , die einen Echtzeit-Einblick in Ihre Arbeitsaufträge und -verfügbarkeiten bietet.

Um Ihr Ressourcenplanungs-Tool einzurichten, bietet Procore einen einmaligen Daten-Upload an, um Ihre Projekte, Mitarbeiter und mehr einzurichten. Obwohl nur bestimmte Felder erforderlich sind, wird empfohlen, so viele Informationen wie möglich so genau wie möglich auszufüllen, um eine möglichst vollständige Einrichtung zu gewährleisten.

• Kunden können diesen Prozess einmal (1) einmal verwenden, um ihr Ressourcenplanungstool einzurichten.

• Keine Sonderzeichen (~'!@#$%^&*()_{[}]|:;"' <,>.? /)

1. Navigieren Sie zum Ressourcenplanungs-Tool auf Unternehmensebene.

2. Klicken Sie auf das Symbol Einstellungen konfigurieren.

3. Klicken Sie auf Daten-Upload.

4. Klicken Sie auf die Excel-Vorlage , um die Vorlage herunterzuladen.

5. Füllen Sie die folgenden Informationen in der Vorlage aus:

   • Groups Felder ein-/ausblenden

     • Required Fields

       • Group Name. The title of Resource Planning group. Hyphens (-) are accepted. Example: Kansas City

       • Group ID. The abbreviated group identifier. Example: KS

       • Time Zone. The time zone of the group location.

         • America/Chicago

         • America/Los_Angeles

         • America/New_York

         • America/Denver

         • Australia/Brisbane

         • Australia/Sydney

         • Australia/Adelaide

         • Australia/Darwin

         • Australia/Perth

         • Pacific/Auckland

     • Optional Fields

       • Address 1. The address of the group location. Example: 1234 Main St

       • Address 2. The address of the group location. Example: Suite 320

       • City/Town. The city of the group location. Example: Kansas City

       • State/Province. The state abbreviation code of group location, formatted with all uppercase letters. Example: MO

       • Postal Code. The postal code of the group location (for US Customers). Example: 62113

       • Country. The country of the group location, formatted as a standard country code. Example: US

       • Contact Name. The name of the point of contact for the group. Example: John Smith

       • Contact Phone Number. The phone number for the group's point of contact.

         • The format is +[country code]XXXXXXXXXX.

         • Examples: +19135558225, or +6421345687.

       • Contact Email. The email address for the group's point of contact. Example: test@test.com

   • Job Titles Felder ein-/ausblenden

     • Required Fields

       • Job Title Name. The name of the job title. Hyphens (-) are accepted. Example: Apprentice

       • Job Title ID. The abbreviated job title identifier. Example: APP

       • Group ID(s). The group(s) the job titles are a part of. The ID must match Group ID in the 'Group' tab exactly. Example: KS

         • If there are more than one group, each group must be separated by a pipe (|) with no spaces. Example: KC|LA

         • If the job title belongs to all groups, type 'All'. Example: All

     • Optional Fields

       • Job Title Color. The HEX value associated with the Job Title. Example: #FFA500

   • Tags Felder ein-/ausblenden

     • Required Fields

       • Tag Name. The name of certification/training/badging tag. Hyphens (-) are accepted. Example: OSHA 30

       • 5-Digit (Character) Identifier. The abbreviated name of tag that can be easily identified on the Boards and List views. This field can support up to five characters. Example: OSH30

       • Group IDs. The groups the tags are a part of. The ID must match Group ID in the 'Group' tab exactly. Example: KS

         • If there is more than one group, each group must be separated by a pipe (|) with no spaces. Example: KC|LA

         • If the job title belongs to all groups, type 'All'. Example: All

       • Does this Tag Expire? (Y/N). Whether or not the tag can expire, like a certification. Example: Y

     • Optional Fields

       • Tag Color (HEX value). The HEX value associated with the tag. Example: #FFA500

       • # of Days Warning. If this tag expires, a warning period (in days) can be set to notify users about expiring tags. Example: 60

       • Categories. The name of the tag category the tag belongs to. Example: Safety.

         • If there is more than one group, each group must be separated by a pipe (|) with no spaces. Example: Safety|Badging

   • Tag Categories Felder ein-/ausblenden

     • Required Fields

       • Category Name. The category names that are used to organize tags. Example: Safety

   • PeopleFelder ein-/ausblenden

     • Required fields

       • First Name. The first name of employee. Hyphens (-) and apostrophes (') are accepted. Example: John

       • Last Name. The last name of the employee. Example: Smith

       • Group ID(s) Available To. Which groups the employees should be visible.

         • The ID must match Group ID in the 'Group' tab exactly. Example: KS

         • If there is more than one group, each group must be separated by a pipe (|) with no spaces. Example: KC|LA

         • If the job title belongs to all groups, type 'All'. Example: All

       • Status (active/inactive). The current status of the employee. Example: active

       • Assignable (Y). All employees must be added as assignable in the data upload. After the data upload is complete, you can update this in the Resource Planning tool. Example: Y

       • Employee ID. The employee's ID number. Example: B18283

     • Optional Fields

       • Job Title ID. The job title ID of the employee. The ID must match the Job Title ID exactly. Example: APP

       • Date of Hire (MM/DD/YYYY). The date the employee was hired. Example: 01/26/2016

       • Hourly Wage (XX or XX.XX). The employee's hourly rate. Example: 25.50

       • Mobile Phone. The employee's mobile number.

         • The format is +[country code]XXXXXXXXXX.

         • Examples: +19135558225, or +6421345687.

            Note

           The same phone number can not be uploaded for different employees. Please remove any duplicate phone numbers.

       • Can Receive SMS (Y/N). Whether the employee should receive alerts and messages via SMS. Example: Y

       • Email. The employee's email address. Example: test@test.com

          Note

         • If possible, this should be their work email address as this will be their log in to Procore, and receive notifications from Resource Planning.

         • The same email address can not be uploaded for different employees. Please remove any duplicate email addresses.

       • Can Receive Email (Y/N). Whether the employee should receive alerts and messages via email. Example: Y

       • Address 1. The employee's address. This is required for the employee to appear on the Resource Planning map. Example: 1234 Main St

       • Address 2. The employee's address. Example: Suite 320

       • City/Town. The employee's city. This is required for the employee to appear on the Resource Planning map. Example: Kansas City

       • State/Province. The employee's state abbreviation code, formatted with all uppercase letters. This is required for the employee to appear on the Resource Planning map. Example: MO

       • Postal Code. The employee's postal code (for US Customers). This is required for the employee to appear on the Resource Planning map. Example: 62113

       • Country. The employee's country, formatted as a standard country code. Example: US

       • Date of Birth (MM/DD/YYYY). The employee's date of birth. Example: 01/26/1980

       • Gender (M/F). The employee's gender. Example: M

       • Emergency Contact Name. The name of the employee's emergency contact. Example: Jane Smith

       • Emergency Contact Relationship. The relationship between the employee and their emergency contact. Example: Spouse

       • Emergency Contact Phone Number. The phone number of the employee's emergency contact.

         • The format is +[country code]XXXXXXXXXX.

         • Examples: +19135558225, or +6421345687.

       • Emergency Contact Email. The email address for the employee's emergency contact. Example: test@test.com

   • Projects Felder ein-/ausblenden

     • Required Fields

       • Project Name. The name of project. Hyphens, apostrophes, ampersand and periods are accepted. Example: Acme Stadium

       • Group IDs. The groups the projects are a part of. The ID must match Group ID in the 'Group' tab exactly. Example: KS

         • If there is more than one group, each group must be separated by a pipe (|) with no spaces.

         • Example: KC|LA
           If the job title belongs to all groups, type 'All'. Example: All

       • Status (active, pending, inactive). The status of the project. Example: active.

       • Project Number. The tracking number for the project. Hyphens (-) accepted. Example: AC2997

     • Optional Fields

       • Project Color (HEX value). The HEX value associated with the Job Title. Example: #FFA500

          Tip

         Some customers color code their projects by Project Manager, Customer, Project Type, etc.

       • Address 1. The job site's address. This is required for the project to appear on the Resource Planning map. Example: 1234 Main St

       • Address 2. The job site's address. Example: Suite 320

       • City/Town. The job site's city.This is required for the project to appear on the Resource Planning map. Example: Kansas City

       • State/Province. The job site's state abbreviation code, formatted with all uppercase letters. This is required for the project to appear on the Resource Planning map. Example: MO

       • Postal Code. The job site's postal code (for US Customers). This is required for the project to appear on the Resource Planning map. Example: 62113

       • Country. The job site's country, formatted as a standard country code. Example: US

       • Time Zone. The time zone of the job site.

         • America/Chicago

         • America/Los_Angeles

         • America/New_York

         • America/Denver

         • Australia/Brisbane

         • Australia/Sydney

         • Australia/Adelaide

         • Australia/Darwin

         • Australia/Perth

         • Pacific/Auckland

       • Default Daily Start Time (XX:XX AM/PM). The default time assignments start on this project. Example: 07:00 AM

       • Default Daily Stop Time (XX:XX AM/PM). The default time assignments stop on this project. Example: 03:30 PM

       • Estimated Start Date* (MM/DD/YYYY). The estimated start date of the project. Example: 02/22/2021

       • Estimated End Date (MM/DD/YYYY). The estimated end date date of the project. Example: 08/25/2025

       • Average Hourly Bid Rate (XX or XX.XX). The the estimated average hourly rate? Example: 25.10

       • Percentage Complete. Current percentage complete of the project. Example: 95

       • Customer. The customer of the project. Example: ACME Construction Co

       • Project Type. The type of project. Example: Commercial

• Import Resource Planning Data