Each project can be configured independently using the settings. The settings control the behaviour of the project including some reference data. Settings can be edited at any time.
|
Setting Area |
Use |
Possible values |
Mandatory |
|
General Settings |
|
|
|
|
System Admin |
|
|
|
|
Name |
The name of the project |
|
✓ |
|
Status Type |
Used for grouping projects according to status |
· Active (default) · Training · Archive |
✓ |
|
Default cost unit of measure |
Sets the UoM for Activity Revised Budget Values which are consistent across all Activities and are displayed on reports |
Based on UoM configuration |
✓ |
|
Protected classification |
To enable the Australian Government's Protective Security Policy Framework's 'Protected' classification for a project. | ||
|
External reference |
Unique identifier |
|
|
|
Location |
Short name or address describing the location of project |
|
|
|
Location Latitude |
Latitude represented as a decimal angle |
(e.g., -27.463881) [-90 < latitude < 90] |
|
|
Location Longitude |
Longitude represented as a decimal angle |
(e.g., 153.012451) [-180 < longitude < 180] |
|
|
Project support contact |
Project support contact details - shown in Help menu | Name, telephone number, email |
|
|
Date format |
Format of how dates are shown in the project | dd/mm/yyyy or mm/dd/yyyy |
✓ |
|
Tags |
Tags created here act as placeholder tags and may be applied to other entities |
|
|
|
Author copyable comment/attachment tags |
Tags created here, and when present on a person, will be automatically applied to new comments and attachments that person creates |
|
|
|
Person display name format |
The default name format for people names across all pages within SYNCHRO Perform (case sensitive) |
· Given Family (default) · FAMILY, Given · FAMILY, GIVEN · FAMILY Given · Family Given · Attendance Ref (5 chars), FAMILY, GIVEN [Supervisor Code] |
✓ |
|
Classification period for Events |
Number of hours in which a new Event must be classified |
|
|
|
Editable discussion period for Comments |
Number of hours for which Comments are editable |
|
✓ |
|
Record time of status change on work |
Automatically record times for status changes on Activities and Events
|
|
|
|
Tagged Item actual quantity resolution order |
The first populated quantity will be used as the Actual Quantity at complete for Tagged Item Activities |
· Actual Quantity at Complete (default) · Actual Quantity at Complete > Revised Budget Quantity · Actual Quantity at Complete > Current Budget Quantity · Actual Quantity at Complete > Revised Budget Quantity > Current Budget Quantity · Actual Quantity at Complete > Current Budget Quantity > Revised Budget Quantity |
✓ |
|
Default Usage Codes |
|
|
|
|
For People |
The default Usage Code that is applied to People Resource Usages (Usage Code is mandatory for all Usages) |
Defaults to “Normal (N)” |
✓ |
|
For Equipment |
The default Usage Code that is applied to Equipment Resource Usages (Usage Code is mandatory for all Usages) |
Defaults to “Normal (N)” |
✓ |
|
For Other |
The default Usage Code that is applied to Other Resource Usages (Usage Code is mandatory for all Usages) |
Defaults to “Normal (N)” |
✓ |
|
Timesheet / Resource Usage configuration |
|
| |
|
Default timesheet entry day |
|
· Today (default) · Yesterday |
✓ |
|
Allow negative Resource Usage values |
Allow resource usages to be entered with negative amounts |
|
|
|
Allow self-approval of Resource Usages |
Only affects Users below System Admin that are permitted to approve entries. Does not affect Client Resource Usage approvals. Only System Admins can change |
|
|
|
Allow rejection of approved Resource Usages |
Only affects Users below Project Config that are permitted to reject entries. Does not affect Client Resource Usage approvals. Only System Admins can change |
|
|
|
Allow Standard Users to create and assign Resources |
Allow standard Users to create and assign Resources via the Resource Usage Matrix |
|
|
|
Allow Subcontractor Users to export Resource Usages |
Allow subcontractor users to export Resource Usages |
|
|
|
Relax Work Reference constraints on Bulk Create & SYNCHRO Perform Mobile |
Relaxes supervisor and actual date constraints on Bulk Create & SYNCHRO Perform Mobile to match the Resource Usage Matrix |
|
|
|
Relax work reference constraints on Resource Usage Entry & Resource Usage Matrix |
Relaxes actual date and active work reference constraints on Resource Usage Entry & Resource Usage Matrix |
|
|
|
Show start/end times on the Resource Usage Matrix, Resource Usage Entry, and Bulk Create pages |
Enables Start Time, End Time, and Break Duration columns on the Resource Usage Matrix, Resource Usage Entry, and Bulk Create pages |
|
|
|
Show SMU Start/End on the Resource Usage Entry and Bulk Create pages |
Shows options to enter Start/End SMU (Service Meter Unit) amounts Equipment Resources on the Resource Usage Entry and Bulk Create pages |
|
|
|
Show the First Receiver column on Bulk Create |
Shows the First Receiver column on Bulk Create which will set the First Receiver of a Docket when provided |
|
|
|
Automatically create Dockets for each resource with Usage |
Automatically created dockets will have a docket reference in the format of "CPY-RES-YYYYMMDD" |
|
|
|
Require Rate Code to be specified on Resource Usages |
This only applies if a Rate exists for the specified resource and date |
|
|
|
Require a Resource Assignment for Resources on Resource Usages |
This will require the Resource specified on a Resource Usage to have a Resource Assignment which covers the specified work date |
|
|
|
Require a Resource Assignment for Resources on Attendances |
This will require the Resource specified on an Attendance to have a Resource Assignment which covers the specified work date |
|
|
|
Enable cascading of approval and locking on Invoices, Dockets, and Resource Usages |
Will approve and lock associated Dockets when an Invoice is Processed. Will approve and lock associated Resource Usages when a Docket is Approved. Enabling this setting does not cascade approve historical data. If you would like to cascade approve historical data, please contact SYNCHRO Perform Support |
|
|
|
Notice notifications |
|
| |
|
Default Notice notification email addresses |
Email addresses entered here will be automatically applied to Notice notifications |
Example: “john@example.com, jane@example.com” (comma separated list) |
|
|
Daily Unissued Notices Summary notification email recipients |
Email addresses entered here will automatically be sent a Daily Unissued Notices Summary email |
Example: “john@example.com, jane@example.com” (comma separated list) |
|
|
Docket notifications |
|
| |
|
Docket notification email |
When a Docket changes state, send this email a notification |
|
|
|
Send daily docket summary to each subcontractor |
Send a daily notification email with a docket-state-change summary to all Subcontractor Companies containing only Dockets with at least one state change from the previous day and only with the last change if the docket's state was updated multiple times |
|
|
|
On creation |
|
|
|
|
Send docket create notification to creator |
When a Docket is created via mobile, send a notification email to the Creator |
|
|
|
Send docket create notification to first receiver |
Send notification email to docket's first receiver on a newly created Docket |
|
|
|
Send docket create notification to each person |
Send notification emails to all People with a Resource Usage on a newly created Docket |
|
|
|
Send docket create notification to subcontractor company |
Send a notification email to the Subcontractor Company on a newly created Docket |
|
|
|
On state change |
When a Docket changes state, send notification emails to the Creator, the Docket's Subcontractor Company, the Project Docket notification email, and any additional recipients specified on the Docket |
|
|
|
Send docket received notification |
Send a notification when the status of the Docket changes to Received |
|
|
|
Send docket approved notification |
Send a notification when the status of the Docket changes to Approved |
|
|
|
Send docket rejected notification |
Send a notification when the status of the Docket changes to Rejected |
|
|
|
On state change (to each person on Docket) |
When a Docket changes state, send notification emails to all People with a Resource Usage on the Docket |
|
|
|
Send docket received notification to each person |
Send a notification when the status of the Docket changes to Received |
|
|
|
Send docket approved notification to each person |
Send a notification when the status of the Docket changes to Approved |
|
|
|
Send docket rejected notification to each person |
Send a notification when the status of the Docket changes to Rejected |
|
|
|
SYNCHRO Perform Mobile |
|
| |
|
Apply default Rate Code to Resource Usages |
If the Rate for a Resource is marked as “Default”, apply the corresponding Rate Code to the Resource Usage |
|
|
|
Add a watermark displaying location, date and time to captured images |
Watermark is automatically applied to all images capture or uploaded to SYNCHRO Perform via the mobile app |
|
|
|
Make Tags a mandatory field on the Comment/Photo screen |
Forces a Tag or Tags to be selected when using the Comment/Photo screen |
|
|
|
Enable Quantity Progress entry on the Comment/Photo screen |
Allows a Quantity Progress amount to be entered for Activities that have an Earned Value Method of “quantity” via the Comment/Photo screen |
|
|
|
Make Attendance Area a mandatory field on all Attendance screens |
Forces an Attendance Area to be selected when submitting an Attendance entry |
|
|
|
Require GPS location on Start/End/Bulk Attendance screens |
Forces GPS location to be captured for Attendance entries |
|
|
|
Show Competencies for the scanned Person on the Start/End Attendance screens |
Ensure a Person's Competencies are shown when scanning a QR for Attendance | ||
|
Show Rate Code and Unit of Measure selector on the Crew Timesheet/Docket screens |
If there is an applicable Rate for a Resource, the Rate Code and Unit of Measure will be shown on the Timesheet/Docket screens | ||
|
Additional Docket submission for the same resource |
|
|
|
|
· Add Resource Usages to existing Dockets (duplicate Resource Usages will be unprocessable) |
The uniqueness constraint of Resource Usages is applied thereby making duplicate Resource Usages unprocessable |
|
|
|
· Create new Dockets with distinct Resource Usages (duplicate Resource Usages will be allowed) |
The uniqueness constraint of Resources Usages is avoided thereby allowing duplicate Resource Usages |
|
|
|
Default note for Attendance start |
Used as the default note when creating an Attendance start on mobile |
|
|
|
Default note for Attendance end |
Used as the default note when creating an Attendance end on mobile |
|
|
|
Activity/Event for Attendance timesheets |
The Activity/Event used for timesheet entries on the Start/End/Bulk Attendance screens |
|
|
|
Client Resource Usage Approvals |
When a Resource Usage is Submitted to the Client for Approval or Approved/Rejected by the Client, send notifications to the specified email recipients |
|
|
|
Allow Clients to approve Resource Usages |
Allow Resource Usages to be submitted to the Client for approval or rejection |
|
|
|
Submitted to Client notification email recipients |
Send a notification to the email address(es) when the Resource Usage is Submitted for Client Approval to the Client Resource Usage Approver user |
Example: “john@example.com, jane@example.com” (comma separated list) |
|
|
Rejected by Client notification email recipients |
Send a notification to the email address(es) when the Resource Usage is Rejected by the Client Resource Usage Approver user |
Example: “john@example.com, jane@example.com” (comma separated list) |
|
|
Approved by Client notification email recipients |
Send a notification to the email address(es) when the Resource Usage is Approved by the Client Resource Usage Approver user |
Example: “john@example.com, jane@example.com” (comma separated list) |
|
|
Internal Resource Usage Approvals |
When a Resource Usage is Submitted/Approved/Rejected internally, send notifications to the specified email recipients |
|
|
|
Submitted notification email recipients |
Send a notification to the email address(es) when the Resource Usage is Submitted |
Example: “john@example.com, jane@example.com” (comma separated list) |
|
|
Rejected notification email recipients |
Send a notification to the email address(es) when the Resource Usage is Approved |
Example: “john@example.com, jane@example.com” (comma separated list) |
|
|
Approved notification email recipients |
Send a notification to the email address(es) when the Resource Usage is Rejected |
Example: “john@example.com, jane@example.com” (comma separated list) |
|
|
Reporting periods |
|
|
|
|
Weekly period ending day |
The day of the week on which the weekly period ends on the Resource Usage Summary page |
Default: Sunday |
✓ |
|
Monthly period ending day |
The date or day of the month on which the monthly period ends in Analytics |
Use “31” for the last day of the month |
|
|
Reporting parameters |
|
|
|
|
Custom project Report values |
Values defined here can be included in Report and Notice Templates |
Example: client_name=Important Customer Pty Ltd |
|
|
Import column mappings |
|
|
|
|
Import column mappings |
Column headers from external systems can be mapped to SYNCHRO Perform column headers on imports |
Example: Custom Name=system_name |
|
|
Report Logo |
| ||
|
Upload report logo | Upload a company logo for use in templated reports | .jpeg or.png format | |