Overview
Each project in Dash360 has an extensive configuration form organized into tabs. These settings control everything about how the project behaves; which code files it uses, how cost classes are structured, how signatures work, and which features are enabled.
Open a project’s settings by clicking the Edit button (pencil icon) on any project row on the Projects page.
Properties Tab
Core project identity, dates, and lock state.
| Field | Description | Required |
|---|
| Name | The project name shown throughout Dash360. Must be unique across all projects. | Yes |
| Application | A short application or program code for this project | No |
| Description | Optional longer description | No |
| Funding Source | Text field identifying the project’s funding source | No |
| Status Date | The current project status date. Used as the data cutoff for earned value calculations and schedule status. | No |
| Reporting Period | The current reporting period end date. Drives which time-phased period is “current” in cost estimates and EV reports. | No |
| Locked | When checked, the project snapshot is locked; no edits to resource assignments or schedule data are allowed. | No |
| Lock Schedule | When checked, prevents any changes to schedule activities on this project, even if the project is otherwise unlocked. | No |
If the registry setting No-Rollback-of-Reporting-Period is enabled for this project, Dash360 will not allow the Reporting Period to be set to an earlier date than the current value. This prevents accidental reversal of period close-outs.
Code Files Tab
Assign the supporting files that define the project’s data structure. Files must be created in the relevant admin pages before they can be assigned here.
| File | Description | Where to Manage |
|---|
| WBS Code File | The Work Breakdown Structure hierarchy for this project | Codes |
| Work Package Code File | The work package numbering codes | Codes |
| Resource File | The resource codes available for resource assignments | Resources |
| Rate File | The rate file used for cost calculations | Rates |
| FTE Code File | A resource code file used for FTE-type calculations (optional) | Resources |
| Activity Code File | Activity codes for schedule integration | Codes |
| Basis Code File | Estimating basis codes (e.g., Analogy, Engineering, Parametric) | Codes |
| Contingency Source File | The contingency source file for risk factor calculations | Contingency Source |
| Registry Set | The registry configuration that controls feature flags and system behavior | Registry |
Code files can be shared across multiple projects. If you select a file that another project is already using, any changes to that file (adding, editing, or deleting codes) will affect all projects sharing it. Use the sharing indicators on the project list to monitor which files are shared.
Unit Time Phase Tab
Controls the time-phasing unit for resource assignment costs in each resource type.
| Field | Description |
|---|
| Labor Unit Time Phase | The time-phasing unit for labor resource assignments (e.g., Monthly, Weekly) |
| Non-Labor Unit Time Phase | The time-phasing unit for non-labor resource assignments |
| Travel Unit Time Phase | The time-phasing unit for travel resource assignments |
Calendar Tab
Controls how the project’s fiscal calendar is structured.
| Field | Description |
|---|
| Custom Calendar | Yes/No toggle. When No, the project uses the standard calendar. When Yes, enables the custom date range and holiday fields below. |
| Calendar or Fiscal Year | Radio: choose Calendar Year (January start) or Fiscal Year (custom start month) |
| Fiscal Year Start Month | The month the fiscal year begins (January–December). Only shown when Fiscal Year is selected. |
Holiday Management: When Custom Calendar is enabled, you can define project holidays:
- Select a date using the date picker
- Click the Add button to add it to the holiday list
- Holidays affect working-day calculations for schedule durations
Cost Classes Tab
Define the cost classes available for this project. Cost classes represent different estimate scenarios; for example, Budget, Earned Value, and Actual Cost.
Cost Classes
Click Add Cost Class to create a new class. Click the edit icon on any row to modify it.
| Field | Description | Required |
|---|
| Name | The display name (e.g., “Budget”, “Baseline”, “EAC”) | Yes |
| Type | The class type: controls which calculations apply | Yes |
| Rate File | The rate file to use for this cost class (can differ from the project default) | No |
| Cost Class Contingency | Yes/No: whether this cost class participates in contingency calculations | No |
Cost class types:
| Type | Description |
|---|
| Budget | The baseline estimate. Resource assignment editing is typically available. |
| Earned | Used for earned value calculations. Typically populated by Dash360 automatically. |
| Actual | Actual costs recorded against the project. |
| Forecast | Forward-looking cost projections. |
The Locked toggle (controlled via the Registry) prevents users from editing resource assignments in that cost class. Cost class locking is a registry-controlled feature; if locking is not enabled in the registry settings, the Locked field has no effect.
Cost Sets
Cost sets group multiple cost classes into a named set for filtering. For example, a “Total Program” cost set might include Budget + Forecast together.
Click Add Cost Set to create a set.
| Field | Description | Required |
|---|
| Name | Display name for the cost set | Yes |
| Included Cost Classes | Multi-select list of cost classes to include in this set | Yes |
Cost sets appear alongside cost classes in Cost Class selectors across Dash360 (Budget Form, Schedule Viewer, reports).
Notebook Fields Tab
Assign notebook categories to this project. Notebook categories appear as custom fields on the Budget Form, Risk Register, WBS Dictionary, and other pages. Categories must be created globally in the Notebooks admin page before they can be assigned here.
Use the dual-list selectors (Available → Selected) to assign categories to each entity type. Drag rows in the Selected list to set the display order.
| Entity Type | Max Categories |
|---|
| Work Package Notebooks | 50 |
| WBS Notebooks | 50 |
| Resource Assignment Notebooks | 50 |
| Control Account Notebooks | 10 |
| Risk Register Notebooks | 50 |
Report Colors Tab
Configure the colors used in earned value charts and summary reports for this project.
EV Chart Colors
| Field | Description |
|---|
| Budget Color | Color for the Budget (BCWS) series in EV charts |
| Actual Color | Color for the Actual Cost (ACWP) series |
| Earned Color | Color for the Earned Value (BCWP) series |
Estimate Type Colors
One color picker per basis code defined in the project’s Basis Code File. Used to distinguish estimate types in cost summary reports.
Resource Type Colors
| Field | Description |
|---|
| Labor Color | Color for labor resource assignments in reports |
| Non-Labor Color | Color for non-labor resource assignments |
| Travel Color | Color for travel resource assignments |
| Contingency Color | Color for contingency amounts |
FTE Type Colors
One color picker per FTE code detail, if an FTE Code File is assigned. Used in staffing plan and FTE reports.
Cost Type Colors
One color picker per cost type value, if a Cost Type notebook category is configured. Used in WBS summary cost-type breakdowns.
Report Settings Tab
Controls how the WBS Summary report presents data for this project.
| Field | Description |
|---|
| Report WBS Summary Cost Type | When enabled, adds a cost type breakdown column to the WBS Summary Report |
| Cost Type Notebook Field | The notebook category used as the cost type dimension (dropdown, only shown when above is enabled) |
| Report WBS Summary Estimate with Description | When enabled, includes the estimate basis description alongside cost values in the WBS Summary |
Thresholds Tab
Define EV performance thresholds for this project. Values outside the threshold range are highlighted in earned value reports and dashboards.
Set upper and lower bounds for metrics such as cost variance, schedule variance, CPI, and SPI. For each threshold type, specify:
| Field | Description |
|---|
| Minimum Threshold | The lower bound (required) |
| Selected Value | The target or acceptable value: must be ≥ Minimum Threshold |
| Text | Label describing this threshold band (e.g., “Warning”, “Critical”) |
Click Add Threshold to add a new band. Click the edit icon to modify an existing one. Thresholds are project-specific and do not affect other projects.
Variance Fields Tab
Configure the fields that appear on the Variance Narrative Report for this project. Each variance narrative field maps to a specific cost class and appears as a column in the variance grid. This tab controls which fields are shown and their display order.
Signatures Tab
Configure the sequential signature workflow for cost estimate approvals on this project. Each signature step represents one approval level.
| Field | Description | Required |
|---|
| Step Name | Label for this approval step (e.g., “CAM Approval”, “PM Review”) | Yes |
| User | The user responsible for this signature step | Yes |
| Order | The sequence: signatures must be completed in order (1 = first) | Yes |
When a user completes their signature step on the Budget Form, the next approver in the chain is notified. The cost estimate value is recorded at each approval step.
Click Add Signature Step to add a level. Drag rows to reorder steps. Deleting a step does not affect already-completed signatures.
Risk Register Setup Tab
Assign the risk categories and risk types available for this project’s Risk Register. Only categories and types assigned here appear when users add risks in the Risk Register.
Risk Categories
A category groups related risks (e.g., “Technical”, “Schedule”, “Cost”). Click Add to create one.
| Field | Description | Required |
|---|
| Name | Category name | Yes |
Risk Types
A risk type classifies the nature of the risk (e.g., “Threat”, “Opportunity”). Click Add to create one.
| Field | Description | Required |
|---|
| Name | Type name | Yes |
Both grids support Save and Close and Save and Add Another for rapid data entry.
Risk ID Prefixes Tab
Define the prefix patterns used to auto-generate Risk IDs when users create risks in the Risk Register.
| Field | Description | Required |
|---|
| Title | A descriptive name for this prefix rule | Yes |
| Prefix | The prefix string prepended to the number (e.g., “R”, “RISK-”) | Yes |
| Starting Number | The first number to assign (whole number ≥ 0) | Yes |
| Increment Value | How much to increment for each new risk (whole number ≥ 0) | Yes |
Example: Prefix = “R-”, Starting Number = 1, Increment = 1 → first risk gets ID “R-1”, next gets “R-2”, and so on.
Deleting a Risk ID Prefix also deletes all risk items that were generated using that prefix. A confirmation dialog lists the affected risk IDs before you confirm. This action cannot be undone.
Risk Thresholds Tab
Define severity thresholds for risks on this project across three dimensions. These thresholds drive risk prioritization and color-coding in the Risk Register.
Each threshold type (Cost, Schedule, Probability) has its own independent table. Click Add Risk Threshold under each section to add a band.
| Field | Description | Required |
|---|
| Minimum Threshold | Lower bound of this severity band | Yes |
| Selected Value | Representative value for this band (must be ≥ Minimum Threshold) | No |
| Text | Label for this severity band (e.g., “Low”, “Medium”, “High”) | Yes |
| Threshold Type | Unit |
|---|
| Cost Thresholds | Dollar amount |
| Schedule Thresholds | Days |
| Probability Thresholds | Percentage (0–100) |
Uncertainty Classes Tab
Define uncertainty classes for this project. Uncertainty classes are used in conjunction with risk factors to calculate contingency bands. Each class has a name and an associated contingency percentage range. These settings integrate with the Contingency Methodology.
Quick Status Settings Tab
Configure the Quick Status submission workflow for this project. Quick Status is the page where CAMs submit activity progress updates.
Feature Toggles
| Setting | Description |
|---|
| Collect Status on Activity Steps | When enabled, the Quick Status screen shows an Activity Steps button. % Complete is calculated from step weights rather than entered manually. |
| Send Status Updates to Admin on Save (no review step) | When enabled, CAM updates are automatically forwarded to the administrator for approval immediately on save; skipping the CAM’s own review step. |
Custom Rules
The rules grid lists configurable validation rules that Dash360 enforces when CAMs submit status updates.
| Column | Description |
|---|
| Enabled | Toggle whether this rule is active for the project |
| Rule Name | The name of the validation rule (read-only) |
| Description | What the rule checks (read-only) |
| Message | The message shown to the CAM when this rule is violated. Edit to customize the wording for your project. |
Click Save at the top of the tab to save both toggle states and all rule changes together.
MTDC Tab
Configure Modified Total Direct Cost (MTDC) settings for this project. MTDC controls how indirect costs are applied to resource assignments. This tab is only visible when MTDCShow is enabled in the project’s registry settings.
Set the MTDC rate structure, the applicable cost categories, and which resource result box the MTDC values feed into.
Premium Pay Tab
Configure premium pay months that may apply to labor resource assignments on this project. This tab is only visible when PremiumPayShow is enabled in the project’s registry settings.
Define which months carry premium pay and which resource result box the premium pay values feed into.
Resource Code Security Tab
Control which users can access specific resource codes on this project. This tab is only visible when CAMAccessToResourceCodes is enabled in the registry.
By default, all users with project access can use all resource codes. Enable resource code security to restrict individual CAMs to a subset of codes; useful when different CAMs own different resource types and should only see their own.
CPR Field Name Overrides Tab
Override the display names of fields and groups in the Cost Performance Report (CPR) for this project. Useful when your organization uses different terminology than the Dash360 defaults.
The tab shows a two-column table:
| Column | Description |
|---|
| Current | The default field or group name |
| New | Your custom override label (leave blank to use the default) |
Overrides are project-specific and only affect display names; they do not change the underlying data structure.
IPMDAR Export
IPMDAR (Integrated Program Management Data Analysis Report) is a government-standard EV data format. Click Download IPMDAR Files to export the full IPMDAR package as a ZIP file containing 24 JSON files.
The export includes:
| File | Contents |
|---|
| SourceSoftwareMetadata | Software name and version |
| DatasetMetadata | Contractor info, contract details, point of contact |
| DatasetConfiguration | Data structure flags (time-phased, direct/indirect, element of cost) |
| ContractData | Contract terms and dates |
| WBS | Full WBS hierarchy |
| OBS | Organizational Breakdown Structure |
| ControlAccounts | Control account definitions, dates, manager assignments |
| WorkPackages | Work package definitions and EV techniques |
| ReportingCalendar | Reporting periods with dates and working hours |
| BCWS_ToDate | Budgeted Cost of Work Scheduled (cumulative, by period) |
| BCWP_ToDate | Budgeted Cost of Work Performed / Earned Value (cumulative) |
| ACWP_ToDate | Actual Cost of Work Performed (cumulative) |
| BCWS_ToComplete | Budgeted cost to complete |
| EST_ToComplete | Estimated costs to complete |
| Summary_Performance | Summary EV metrics (BCWS, BCWP, ACWP, BAC, EAC) |
| SummaryIndirectPerformance | Indirect cost performance (to date and to complete) |
| Subcontractors | Subcontractor information |
| + 7 placeholder files | Reserved for future IPMDAR fields |
Cost data in each performance file is broken down by: Total, Direct, Labor, Material, ODC (Other Direct Cost), Subcontract, Overhead, Common, and G&A.
The export is read-only and does not modify any project data.
Saving
Click Save and Close to save all changes and close the form. Click Save and Add Another (when adding a new project) to save and immediately start configuring another project. Click Close to discard unsaved changes.
Changes to code file assignments may trigger cache rebuilds or recalculation in the background.