SmartPM Configurations

Activities Started With No Progress
Configure how activities with an actual start date but 0% completion are handled:

• Treat as Started: Assigns 1% completion to enable delay analysis.

• Treat as Unstarted: Marks the activity as not started.

Calendars
Choose the calendar source for scheduling:

• Window Calendars: Use calendars from the current project window.

• Last Update Calendars: Use calendars from the most recent update.

Ignore or Update Actual Start/Finish Dates
Decide how to handle changes to actual start/finish dates in later updates:

• Ignore Changes: Retain original actual dates.

• Update Actuals: Reflect updated start/finish dates.

Analyzed Baseline End Dates
Control the end date displayed on the dashboard:

• Source File End Date: Shows the end date from the source file.

• SmartPM Calculated End Date: Uses SmartPM’s calculated end date.
  Note: Gantt chart dates always reflect SmartPM calculations. For discrepancies, refer to the "End Date Discrepancies" documentation.

Import or Ignore Level of Effort (LOE) Activities
Choose whether to include or exclude Level of Effort activities during import:

• Import LOE Activities: Include in project analysis.

• Ignore LOE Activities: Exclude from analysis.

Set Actual Finish Date When Activity is 100% Complete
Configure how SmartPM handles activities that reach 100% completion but lack an end date:

• Set to File’s Data Date: Automatically assigns the file’s data date as the activity’s end date.

• Leave Blank: Keeps the end date field empty.

Schedule Update Interval
Set the frequency for update alerts:

• Options range from daily, weekly, bi-weekly, or monthly intervals.

• When overdue, the project’s data date turns red on the company dashboard.

Predicted Completion Date Display
Customize how the forecasted completion date is presented:

• Exact Date: Displays a specific predicted date.

• Date Range: Shows a range within which the completion is expected.

Show Source End Date on Company Dashboard
Toggle visibility of the source file’s end date on the company dashboard:

• Show: Displays the source end date.

• Hide: Omits the source end date.

Compression Calculation Based on Percent Complete
Define when to start and stop compression calculations:

• Start: Specify the % completion to begin compression tracking.

• Stop: Specify the % completion to end compression tracking.

Schedule Quality Display
Configure how the quality metric appears on the dashboard:

• Selected Model and Milestone: Based on user-selected model and milestone.

• All Schedules Model (Full Schedule Milestone): Uses all schedules with the full schedule milestone.

• Selected Model (Full Schedule Milestone): Uses the selected model with the full schedule milestone.

Schedule Performance Index (SPI) Calculation
Determine the starting point for SPI calculation:

• Baseline Schedule Status: Starts from the baseline’s completion percentage (e.g., ignores initial 15% if already complete).

• 0% Completion: Calculates SPI from the project’s start.

Slippage Allowance for Late Activities
Set a buffer before an activity is marked as late:

• Days of Clearance: Choose 0–14 days.

• Same Week Rule: Activities starting/ending in the same week as scheduled are not considered late.

End Date Tracking Method
Choose how the project end date is calculated:

• Full Float Path: Uses the latest activity in the path, even if it extends beyond the milestone.

• Milestone Path: Reflects the milestone’s end date, ignoring later activities.

Point of Slippage Calculation
Define the reference for calculating project delays:

• Contractual End Date: Uses a user-defined date.

• Scheduled End Date: Uses the baseline schedule’s end date (full schedule or milestone).

Log Calendar Worktime Changes
Decide whether to track changes to calendar worktimes:

• Log Changes: Record changes in the project’s change log.

• Do Not Log: Exclude changes from the log.

Should Have Started/Finished Float Column
Configure float display in the Should Start/Should Finish report:

• Native Float: Shows negative float from the source schedule.

• SmartPM Float: Uses SmartPM’s calculated float (no negative float, as days late are already tracked).

Near Critical Threshold
Set the float threshold for activities to be considered near critical:

• Enter a numerical value (e.g., 5) to define the maximum float days.

• Input only numbers, without “days” or other text.

Allow Users to Bypass SmartPM Best Practices on Schedule Import
Control whether users can bypass SmartPM’s best practices (e.g., restrictions on very long activity durations or lags) during project import:

• No Bypass Allowed: Enforces all best practices for all users.

• Allow Company Admins to Bypass: Permits users with company admin roles to bypass certain best practices by unchecking a box during import.
  Note: Critical best practices, such as preventing circular references, are always enforced.

Foreman AI Chat Access
Enable or disable access to Foreman AI Chat for users:

• Enable: Allows users to access Foreman AI Chat.

• Disable: Restricts access to Foreman AI Chat.

Automatically Update Contractual End Dates
Decide how SmartPM handles updates to contractual end dates for projects or milestones:

• Automatic Update: Automatically updates the contractual end date when changes are detected in the source file.

• Manual Update: Retains the original contractual end date unless manually updated by the user.