Cobra 8.6 has been released by Deltek in, what some may see, as a quick turn-around after the release of 8.5. Here’s a look at what’s in this release along with some comments and observations.
Support for Narrative Score Assessment on Analyze Form
If you haven’t been following the latest Cobra news, much of the buzz on Deltek Cobra 8.6 surrounds the new AI feature. This can be utilized to evaluate narrative entries in the Analyze function located in the Reporting section of Cobra.
I have not been able to test this new feature due to the requirement that the user purchase Microsoft Azure OpenAI Service. The pricing models allow for a pay as you go model or a monthly or annual plan where predictable usage can be determined.
The release notes include the following categories of analysis the AI tool will evaluate:
- Challenges and Mitigation
- Clarity and Conciseness
- Completeness
- Future Outlook
- Language and Style
- Metrics and Quantification
- Structure
This new feature in Cobra 8.6 is obviously geared to evaluating the Format 5 Variance Analysis Report (VAR). These reports have notoriously challenged Control Account Managers to sufficiently address Root Causes, relevant Impacts and believable Corrective Actions.
This blogger has over 40 years of experience in Project Controls! I can assure you that the same issues we encounter today in preparing the VAR, is painfully similar to those issues encountered in 1984…when I entered this business.
While a tool to evaluate the VAR for completeness and compliance with the customer’s need for a comprehensive report on cost and schedule variances is desirable, I’m wary of anything that removes responsibility and understanding from the author of VARs.
Granted, grammar issues, missing sections, from the report, etc. are nice to have reviewed. But the content of the VAR, the understanding of what had been assumed in the baseline vs. what has occurred since are beyond the realm of current AI machines.
Identifying the root cause is known only by those executing the work, as is the impact to the EAC and project milestones.
So, an understanding of what can only be accomplished by those executing the work and what an AI tool can assist with, are important considerations before users decide all their VAR problems have been solved.
Acknowledging that, I haven’t tested the new AI feature, I am confident that CAMs alone can provide accurate and actionable information via the VAR. I for one can am willing to accept help in the area of poorly constructed text, but am very cautious in overestimating the extent to which an AI tool can assist in the preparation of the VAR.
In addition, the cost of the AI engine may prove excessive when compared to what the tool can actually add to the VAR preparation process. User beware!
Ability to Exclude Hours During the IPMDAR Cost Data Export
The export function that is utilized for IPMDAR reporting now allows the export to exclude hours. This function is found under the Integration menu/Cost Data.
Figure 1
As shown below in Figure 2, chose the IPMDAR option, then navigate to the Data Options page. Select the Dollars option and the hours will not be included in the output.
Figure 2
Bonus Round: As a related note on the IPMDAR export function, if the user desires to completely mask indirect values, the data can be exported using the following settings on the Data Options page.
Figure 3
The output will appear as shown below in the JSON file. Note that the burdens are consolidated with Direct dollars on the Value Dollars and Value Dollars LAB lines. Total Currency alone is shown.
- “ControlAccountID”: “1.1.1.2 / 1420”
- “ReportingPeriodID”: 2
- “Value_Dollars”: 17730.09
- “Value_Hours”: 751.37
- “Value_Dollars_LAB”: 17730.09
- “Value_Dollars_MAT”: 0.0
- “Value_Dollars_ODC”: 0.0
- “Value_Dollars_SUB”: 0.0
This function can satisfy an organization’s desire to mask Indirects from their export when the deliverable is being sent to another contractor who may be a competitor.
Display Control Accounts and Work Packages Added During Integration in the Process Log
When integrating a schedule or worksheet in order to create new control accounts and work packages, it is handy to be able to review via the process log which control accounts and work packages were, in fact, added. Cobra 8.6 will now include this information.
Prior to this feature, identifying new data was difficult without comparing two reports to each other. The user only needs to check the box as shown below on the Change Control page of the Integration Wizard as shown below in Figure 4.
Figure 4
This option can be set to always include added accounts by checking the box in the Integration Wizard Preferences in the Project Properties.
Thanks, Deltek…Nice add!
Display Full Details for Every Error and Warning in the Process Log Viewer
One feature that I found somewhat unhelpful was that when the user selected the “Show Errors or Warnings, the information for each Error/Warning was often truncated, thus not displaying the necessary information needed to identify and correct the issue. Cobra 8.6 now provides the requisite information in both the process log and the Show Errors/Warnings window. Another nice enhancement.
Summary
Cobra 8.6 enhancements, the AI Engine aside, are mainly minor changes…albeit useful. Some of the nuisance items have been addressed, proving that Deltek listens to their users. The Cobra Guy appreciates that Deltek addresses the glitchy issues, that individually may not be significant, but additively can be irritating when we are in the heat of month end battles.
The AI engine is a “to be proven” function. I encourage improvement in the readability of our narratives, but am wary of any dependence on this functionality taking the place of careful analysis by the project team. There are other enhancements included in 8.6 not covered here that can be reviewed in the Cobra 8.6 release notes. Overall, nice enhancements.