- DASH-1673: Reporting → Cost Class Curves: We have added a new report called Cost Class Curves. This report shows a line graph and a table that shows the running total of any Cost Classes that you select from the filter. Now, you can compare Budget vs. Actual even if you haven’t begun calculating Earned Value on your project yet. This report also comes with the ability to filter the data by many fields including any Resource Code Codes and Notebook fields that are of type checkbox, radio button or dropdown.
- DASH-1695: Admin → Import / Export → Export → Resource Assignment Calculations Audit Report: This new Excel export has 1 line in the Excel file for every Resource Assignment in your project. Each line then has columns for every Resource Result in your Resource Calculations. Then, each column contains a formula that will calculate the total value for that Resource Result for that Resource Assignment inside the Excel spreadsheet. This way, you can actually see / understand how Dash360 calculates your Resource Assignment. This spreadsheet also contains a Form 1030 pivot table and all of the source data (Resource Codes, Rates, Resource Calculations, Form 1030 Mappings, MTDC & Longevity Pay) sheets an auditor may need to understand your calculations and your data.
- DASH-1296: Earned Value → CPR & Variance Narrative Report → Comments: We added the ability for you to add comments to your variance narratives. This allows your team to comment on any variance narrative and give feedback to each other. Threaded comments have been added in both the Cumulative to Date and Current Period areas.
- DASH-1619: Add Cost Set / Cost Class Filter to Reports: You now can filter by Cost Class or Cost Set on the following pages: Budget Form, Form 1030 Report, Contingency Assignment Report, Staffing Plan Report, Cost Estimate Detail Report, CAM Summary Report, WBS Summary Report, Cost Summary Report, Cost Summary Resources Report, Project Explorer and Work Package Report. DASH-1620, DASH-1621, DASH-1622, DASH-1623, DASH-1624, DASH-1625, DASH-1626, DASH-1627, DASH-1629, DASH-1630, DASH-1631.
- DASH-1698: Admin → Import / Export → Import Resource Assignments Speed Up:
- We did some work in this release to speed up the Resource Assignment import. In previous versions of the import process, the system would delete and recreate the CostEstimateTimePhase records during the import process twice. We now do this one time and that should speed this import up for some customers.
- DASH-1713: Budget → Budget Form → Import Timephase Data: We had a bug that allowed users to move Budget Resource Assignments from one Work Package to another even when that Budget Resource Assignment had Earned Value attached to it. This is not allowed. The system now correctly throws an error if you try to change the WBS or Work Package for a Budget Resource Assignment that already has Earned Value on it.
- DASH-1703: Admin → Projects → Resources → Bulk Edit Resource Codes Sometimes Throwing Errors: We found an issue that could cause the Bulk Edit Resource Code screen to throw an error. This has been corrected.
- DASH-1719: Estimating → Staffing Plan Report: This report has a CAM field that shows the CAM that is assigned to each Resource Assignment based on the Budget Form → CAM selection. This selection should be the same for every Resource Assignment in a Work Package. In some scenarios, we were seeing this report was incorrectly showing the CAM. This has been corrected.
- DASH-1724 / DASH-1725: Admin → Projects → Shift Project Dates: We made 2 changes to this process. First, we fixed a bug that would occur if a Task was attached to a Resource Assignment that no longer existed. When this occurred, the process would fail. Now, the Task is skipped because it no longer exists. We also changed the order of the steps so that you now choose your project filters first, and then you see the project start date and shifted date. This way, the start date can be based off of the project filters.
- DASH-1693: Estimating → WBS Dictionary: We fixed a bug where this report was not working for some customers with multiple top-level WBS elements (multiple WBS Level 1 elements - NSO).
- DASH-1710: Admin → Projects → Resources → Resource Results: Add Resource Result was Broken: This has now been fixed so you can add a new Resource Result without an error occurring.
- DASH-1699: Admin → Import / Export → Import → Data to Import Box does not Reset Itself correctly after Import: After you imported a file, the Data to Import box would still show the previously selected import type selected even though it was not really selected. If you tried to do another import without reselecting your import type, an error would occur. This has been corrected.
- DASH-1712: Estimating → Budget Form → Rename Work Package When More than 1 Project Shares the Same Work Package Code File: When more than 1 project shares a Work Package Code file and a user would try to rename a work package in 1 project, the system would rename the Cost Estimate’s Work Package Number in the first project and the Work Package Code stored in the Admin. When this occurred, the 2nd project would now still be pointing to the old Work Package Number which now no longer exists. Now, the system also renames the Work Package Number in the 2nd project’s Cost Estimate’s Work Package Number field. This is only in cases where 2 projects share the same Work Package code file.
- DASH-1720 / DASH-1734: Cost / Schedule Integration: The Budget Form → Schedule section and the Reporting → Activities by Resource Assignment Report now match each other when you look at a specific Activity / Resource Assignment’s cost. There were a couple of issues that we fixed in this release. First, neither report handled MTDC or Premium Pay correctly if your Resource Assignment’s Resource Calculation had additional results after the MTDC Indirects or Premium Pay Resource Result. In these cases, the cost / schedule Subtotal would not recalculate the Resource Results that came after the MTDC Indirects or Premium Pay correctly. Second, if you only had 1 Activity attached to a Resource Assignment, then the Subtotal was often wrong. This is because the system was not ensuring that the Subtotal was only added to when the Resource Assignment and Activity dates were in alignment. In these cases, it just added the entire total of the Resource Assignment to the Activity cost. Finally, the Schedule Builder & Viewer were fixed so that you can again see the Resource pane and edit a Resource Assignment. Both operations were broken in a previous release. We also corrected the Cost logic that is shown in the Resource Pane so you can see where the Activity / Resource Assignment costs align (in green) and where they don’t align (in orange).
- DASH-1708 / DASH-1711: Reporting → Tableau: We added the new Resource Result Codes to the new version of the Tableau refresh process. We also fixed some bugs that were occurring that made the new refresh process fail in some circumstances.
- DASH-1704: Admin → Projects → Backup / Restore Project Fixes: We fixed numerous issues in the Backup / Restore Project in this release. First, the Backup Project File had multiple Resource Calculations for the same Resource Code, Resource Result pairing in some cases where customers were using Resource Result Codes. This is not allowed and breaks the Recalculate Project feature. It tries to create 2 Direct, 2 Escalation and 2 Fringe Resource Results (one per Resource Result Code result). This is because the export of Resource Calculations should NOT include the non-Form 1030 Code Result records. There is a stored proc, GetResourceCalculation, that had to be updated. Second, the Backup Project never backs up the code files that are assigned as Resource Result Codes. These codes missing causes none of the Resource Result Codes in the Code Results table to be restored. Finally, the Restore Project also needs to restore the Result Codes Code File and details. Restoring the CodeResults doesn’t properly handle both Form 1030 codes and non-Form1030 codes. All of these were fixed in this release.
- DASH-1700: Earned Value → CPR: Fixed bug where the word Cumulative was spelled incorrectly. (edited)